Topic: Running a full node vs running with "prune mode" enabled (Read 3933 times)
Cool, exactly my use case, adding new addresses!
importing private keys without rescanning the blockchain is possible by entering importprivkey [key] [label] false . but you probably shouldn't import a used address.
But how does importprivkey work with pruning?!
I'm not sure if that command is even allowed when running in prune mode but if it is allowed then it would only be permitted for adding a new (never used before) address (same would apply to importaddress also).
But how does importprivkey work with pruning?!
Block pruning was introduced with 0.11.0, you can run a pruned node right now if you wanted to. There is no security compromise here, but you lose some functionality in not having the entire block chain stored at your node. If you have HD space to spare and a decent internet connection there's really no reason to run in pruned mode.
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
Keep in mind that a pruned mode can currently not offer a wallet and it does not relay blocks. It is thus no help to SPV clients or at least thats my understanding of SPV. A pruned node will just relay transactions.
Why does it not relay blocks ? It can relay blocks that it has. Only the pruned blocks it cannot relay.
Another question, why was this method of "pruning" chosen? Why does it just keep track of the last X amount of blocks?
This seems like an awkward implementation because it doesn't actually help anything directly, and just leaves a huge gap in the blockchain.
It would work without keeping any of the blockchain. After it verifies the blocks there really is no need for the blockchain. It keeps those blocks in case of blockchain reorgs.This seems like an awkward implementation because it doesn't actually help anything directly, and just leaves a huge gap in the blockchain.
Wouldn't it be more effective to prune by following the coins from the blocks they were mined from?
I.E. Keeping a record of where the coin was mined and where it is currently.
This is pruning at the node level, not shrinking the blockchain which is what you are suggesting. And at the protocol level, there is no such thing as a "coin", it is all inputs and outputs so such an idea does not work.I.E. Keeping a record of where the coin was mined and where it is currently.
Ok, thanks for the further explanation. Things are a little clearer now.. I've been doing my best to learn more about the "technical" side of bitcoin, and so far the community has been wonderful for it.
Some of us will run more than one computer with up-to-date cores on them. It will depend on the circumstances of the moment. ie. are you at home, or in McDonalds. Maybe you are in a nature park filming wildlife, and doing some domain name trading while you wait for some event.
I think those who will run this pruned mode would not have run a full node anyway. This new feature might actually pull more people running SPV wallets or web wallets into running pruned nodes. Security of the network will not be impacted much.
I think your right, i run a full node because i enjoy knowing i am contributing to the network, i think anyone who runs a pruned node wouldn't have bothered with a full node anyway.
Another question, why was this method of "pruning" chosen? Why does it just keep track of the last X amount of blocks?
This seems like an awkward implementation because it doesn't actually help anything directly, and just leaves a huge gap in the blockchain.
It would work without keeping any of the blockchain. After it verifies the blocks there really is no need for the blockchain. It keeps those blocks in case of blockchain reorgs.This seems like an awkward implementation because it doesn't actually help anything directly, and just leaves a huge gap in the blockchain.
Wouldn't it be more effective to prune by following the coins from the blocks they were mined from?
I.E. Keeping a record of where the coin was mined and where it is currently.
This is pruning at the node level, not shrinking the blockchain which is what you are suggesting. And at the protocol level, there is no such thing as a "coin", it is all inputs and outputs so such an idea does not work. I.E. Keeping a record of where the coin was mined and where it is currently.
Another question, why was this method of "pruning" chosen? Why does it just keep track of the last X amount of blocks?
This seems like an awkward implementation because it doesn't actually help anything directly, and just leaves a huge gap in the blockchain.
Wouldn't it be more effective to prune by following the coins from the blocks they were mined from?
I.E. Keeping a record of where the coin was mined and where it is currently.
This seems like an awkward implementation because it doesn't actually help anything directly, and just leaves a huge gap in the blockchain.
Wouldn't it be more effective to prune by following the coins from the blocks they were mined from?
I.E. Keeping a record of where the coin was mined and where it is currently.
So from my understanding, the implications of "prune mode" would be to allow transactions to be relayed as in a full-node, but without the (heavy)-storage dedication. I'm assuming these "prune mode" machines still confirm transactions, and so this would result in a more efficient, lighter protocol.
Is that right?
Is that right?
Nope, just a smaller blockchain, in my particular configuration the last 5 GB of the blockchain.
Then I'm missing the point entirely. If it's not to make blockchain lighter and more situional-ly efficient to encourage more nodes and cut-down resources where appropriate.. How does a smaller blockchain benefit anybody?
So from my understanding, the implications of "prune mode" would be to allow transactions to be relayed as in a full-node, but without the (heavy)-storage dedication. I'm assuming these "prune mode" machines still confirm transactions, and so this would result in a more efficient, lighter protocol.
Is that right?
Is that right?
Nope, just a smaller blockchain, in my particular configuration the last 5 GB of the blockchain.
Then I'm missing the point entirely. If it's not to make blockchain lighter and more situional-ly efficient to encourage more nodes and cut-down resources where appropriate.. How does a smaller blockchain benefit anybody?
So from my understanding, the implications of "prune mode" would be to allow transactions to be relayed as in a full-node, but without the (heavy)-storage dedication. I'm assuming these "prune mode" machines still confirm transactions, and so this would result in a more efficient, lighter protocol.
Is that right?
Is that right?
Nope, just a smaller blockchain, in my particular configuration the last 5 GB of the blockchain.
So from my understanding, the implications of "prune mode" would be to allow transactions to be relayed as in a full-node, but without the (heavy)-storage dedication. I'm assuming these "prune mode" machines still confirm transactions, and so this would result in a more efficient, lighter protocol.
Is that right?
Is that right?
Synchronized pretty quick comparing with previous versions, I'm now running a full node with a 5GB blockchain with wallet. 
Synchronization is really frustrating sometimes!
And if you need fast acting with your BTCs it is better to stick with multibit or similar wallets..
https://multibit.org/
And if you need fast acting with your BTCs it is better to stick with multibit or similar wallets..
https://multibit.org/
Block pruning was introduced with 0.11.0, you can run a pruned node right now if you wanted to. There is no security compromise here, but you lose some functionality in not having the entire block chain stored at your node. If you have HD space to spare and a decent internet connection there's really no reason to run in pruned mode.
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
Keep in mind that a pruned mode can currently not offer a wallet and it does not relay blocks. It is thus no help to SPV clients or at least thats my understanding of SPV. A pruned node will just relay transactions.
This is great news, gonna try it right now.
These I am not sure. You can run 0.12.0rc2 to try it out.
Is there a bin of this somewhere?
Only for 0.12.0rc1 here -> https://bitcoin.org/bin/bitcoin-core-0.12.0/test/
Thank you very much, synchronizing as we speak.
Is there a bin of this somewhere?
Only for 0.12.0rc1 here -> https://bitcoin.org/bin/bitcoin-core-0.12.0/test/
Block pruning was introduced with 0.11.0, you can run a pruned node right now if you wanted to. There is no security compromise here, but you lose some functionality in not having the entire block chain stored at your node. If you have HD space to spare and a decent internet connection there's really no reason to run in pruned mode.
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
Keep in mind that a pruned mode can currently not offer a wallet and it does not relay blocks. It is thus no help to SPV clients or at least thats my understanding of SPV. A pruned node will just relay transactions.
This is great news, gonna try it right now.
These I am not sure. You can run 0.12.0rc2 to try it out.
Is there a bin of this somewhere?
Only for 0.12.0rc1 here -> https://bitcoin.org/bin/bitcoin-core-0.12.0/test/
Block pruning was introduced with 0.11.0, you can run a pruned node right now if you wanted to. There is no security compromise here, but you lose some functionality in not having the entire block chain stored at your node. If you have HD space to spare and a decent internet connection there's really no reason to run in pruned mode.
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
You still have to d/l the entire 40GB+ blockchain the first time you install before it can be pruned, so starting a pruned node will still take some time, but once it's pruned you don't need to keep all the data.
Here's some good reading for you: https://news.bitcoin.com/pros-and-cons-on-bitcoin-block-pruning/
Keep in mind that a pruned mode can currently not offer a wallet and it does not relay blocks. It is thus no help to SPV clients or at least thats my understanding of SPV. A pruned node will just relay transactions.
This is great news, gonna try it right now.
These I am not sure. You can run 0.12.0rc2 to try it out.
Is there a bin of this somewhere?
Jump to: