Im curious, because new versions of bitcoin core coming so fast i can't keep up with new features and all wiki page's can't keep up also.
I wanted to ask about pruning mode because in Bitcoind 0.12 and 0.13 usage of prunning mode was causing wallet functionality to beign disabled. This changes fast tho.
1. How about Bitcoind 0.14 prunning mode? Can i use prunning function and still have all wallet capabilities?
You can use the wallet stuff while pruned. This functionality has been available since 0.12.0, it was only disabled in 0.11.x. 2. What downsides are there in using Bitcoind 0.14 - pruning mode? All of them.
- If the blockchain or the databases corrupt, you will need to redownload the entire blockchain in order to reindex.
- You won't be able to import addresses or private keys
- You won't be helping the network as much as you won't be able to bring new nodes up to sync or out of sync nodes back up to sync.
There may be more, but that's all the important ones I can think of right now. |
|
|
|
So, i am run Bitcoin Core 0.14 node with prune mode.
Is It normal that my 0.14 bitcoin core node not view on bc.info in node IP addreses.
Yes. Blockchain.info's list of node's is not definitive. It is simply a list of nodes that their own node(s) have connections to. |
|
|
|
|
Firstly, the Bitcoin is not actually sent back to your wallet. Your wallet just "forgets" the transaction and reverts to a state where the transaction was never sent. However, that does not mean that everyone else on the network has forgotten your transaction as well and someone could be rebroadcasting continuously.
However, there is a bigger issue here, the addresses in the transaction changing. This should not happen unless you are sending the Bitcoin again. If this is happening, that means that someone has gotten your private keys and compromised your wallet.
|
|
|
|
But the mirror spec does support BIP32/39/44?
The C++ wallets will support BIP 32/44 at some point, as the goal is to move off of the python wallets over to the C++ wallets which will be the entirely new format. The plan is for that to support BIP 32/44, Segwit, and compressed keys. I think it may also support BIP 39 and P2SH, but I'm not sure about that as it's up to goatpig. I received my Trezor recently, and would like it working with Armory ASAP
Armory would need to have hardware wallet support for that to work, and that is something I am planning on doing after the new wallet stuff is finished. So 0.96 signing will be recommended for compatibility from now on? And the recommended signing version should freeze at 0.97 assuming the wallet format is finalised in that version?
Yes. 0.96 is the new recommended offline signer version as it will have support for segwit and the other output types. How does the rewrite improve privacy?
There were changes to coin selection which optimize for privacy, i.e. sticking to inputs from the same address instead of any input in the wallet. |
|
|
|
|
That's not how transaction fees work. The transaction fee is the difference between the value of the inputs and the value of the outputs. There is no way to control who gets the transaction fee as it is implied, not explicit.
|
|
|
|
I didn't received them yet.
Did SatoshiTango not send the Bitcoin, or did you just not see the transaction in your wallet? Can you look up the transaction on a block explorer? So, how do i get back that 4th address where i've send the bitcoins from Satoshi?
Click the Receive Bitcoin button a few times again and you will see your addresses again. |
|
|
|
|
Please post your debug.log, found in the Bitcoin data directory.
Also, what are the specs of the machine you are attempting to run Bitcoin Core on?
|
|
|
|
|
Shouldn't you instead be looking at the transactions tab to see what the transactions are and the details of such transactions? That would give you far more detail than just the receiving address.
|
|
|
|
|
No RPC commands were removed in 0.14.0. New ones were added, and some old ones were marked as deprecated, so they will be removed in a future release.
|
|
|
|
what is pruning?
Pruning deletes the blockchain on the fly as it is downloaded. It ensures that some blocks are kept, but then deletes the rest of the blockchain after the blocks become too old. Basically most of the blockchain ends up being deleted, with only the most recent few hundred blocks kept, and the oldest ones are deleted as new blocks are received. The downside is that you won't be able to get any new nodes synced and if the blockchain gets corrupted, you will need to redownload (but not store) the whole thing. |
|
|
|
Auto sweep or forward, (Automaticaly sweep or forward the balance to another address), do you have names of those wallets?
What do you mean by "automatically sweep"? Electrum, Armory, Bitcoin Core, and Mycelium (to name a few) all allow you to either sweep or import a private key into your wallet. |
|
|
|
|
You run out of hard drive space. Then your software will tell you and then stop working. After that, you can get a bigger hard drive, stop running a node, or enable pruning.
|
|
|
|
|
Why do you need an online tool for this? Pretty much any modern wallet has the capability to sweep or import Bitcoin from private keys.
|
|
|
|
This isn't as much a "bug" as a "design decision". Bitcoin Core is very tightly integrated by design. Properly modularized Bitcoin client wouldn't be so easy to keep under tight control of a single development team. I wouldn't expect them to ever fix it in the open source release.
What are you talking about? Tightly integrating the GUI to the rest of the code is not a design decision made by the current Core developers. It is a holdover from the Satoshi days when Satoshi originally release Bitcoin as a Windows-only Gui-only software. They have done a ton of work to separate out and modularize everything. They may have a closed source release without the extra-tight interlocking, the same thing that large miners do for their "bitcoind" daemons.
There is no closed source release. What the hell are you talking about? The Core devs aren't out to make everyone's lives terrible. If there were a closed source version that was much better, they would release it. Also, Core dev is an extremely nebulous term, and there really is not a formal "team" that people join. |
|
|
|
|
Who malleated those transactions?
I know that those who have chains of unconfirmed transactions that were based off of the original non-malleated ones were, but how many transactions is that? Who else was affected by these transactions?
|
|
|
|
How can I check the quality of the my bitcoin core node? Is it enough that the port 8333 is open?
If you have not touched any of the command line options, then you are running a full node. If you have port 8333 open, that's even better as you will be accepting incoming connections. |
|
|
|
i sent message to quickseller and macbook-air to put it to f2pool but still not response
You need to wait. People do not and cannot respond immediately. |
|
|
|
Your transactions are quite large, but pay a very low fee rate, ~9 sat/byte on the first, and ~3 sat/byte on the second. According to http://bitcoinfees.21.co/, the current recommended fee rate for the fastest confirmation is ~240 sat/byte. Read https://bitcointalk.org/index.php?topic=1802212.0 for what you can do to fix the issue. Note that miners probably will not help you because the transactions pay too low of a fee rate. The first thing you should try is ViaBTC's transaction accelerator. It's a little crowded right now due to the high fees on the network, but it'll probably help to get your transaction through. ViaBTC will not accept their transaction because they do not accept transactions with fee rates less than 10 sat/byte. |
|
|
|
Achow, the Apple support people did this and I just did it again. Armory does not show up in the library/applications.
The folder is ~/Library/Application Support/ (not the two word folder name, Application Support). What version of Mac OS are you running? |
|
|
|
|
Show Posts
