Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: John (John K.) on November 04, 2015, 06:09:33 AM



Title: Running bitcoind in pruning mode
Post by: John (John K.) on November 04, 2015, 06:09:33 AM
Hi all,

I'm trying to run a bitcoin node (satoshi 0.11) in pruning mode. If I want to keep the blockchain size at 30gb, should I just restart bitcoind with the command 'bitcoind -prune=30000' ?

Cheers,
John


Title: Re: Running bitcoind in pruning mode
Post by: John (John K.) on November 04, 2015, 06:17:26 AM
Also, is there any benefit in running a pruned node? Would that still contribute to the bitcoin network as a whole?


Title: Re: Running bitcoind in pruning mode
Post by: John (John K.) on November 04, 2015, 06:32:56 AM
Hi all,

I'm trying to run a bitcoin node (satoshi 0.11) in pruning mode. If I want to keep the blockchain size at 30gb, should I just restart bitcoind with the command 'bitcoind -prune=30000' ?

Cheers,
John

Went through the code on github, yep I was doing it correctly.


Title: Re: Running bitcoind in pruning mode
Post by: shorena on November 04, 2015, 10:09:10 AM
Also, is there any benefit in running a pruned node? Would that still contribute to the bitcoin network as a whole?

You still verify and relay transactions. Other nodes can no longer get block from you though, at least for now.

You can also add prune=30000 to the bitcoin.conf file.


Title: Re: Running bitcoind in pruning mode
Post by: John (John K.) on November 04, 2015, 04:08:03 PM
Also, is there any benefit in running a pruned node? Would that still contribute to the bitcoin network as a whole?

You still verify and relay transactions. Other nodes can no longer get block from you though, at least for now.

You can also add prune=30000 to the bitcoin.conf file.

Gotcha, thanks!


Title: Re: Running bitcoind in pruning mode
Post by: Carlton Banks on November 04, 2015, 04:20:02 PM
Note that only the blocks component of the database can be chosen, so -prune=30000 is specifying the size of that portion only. I'm not sure if the rest of the database remains the same size or grows at a tiny rate, not familiar with running in pruned mode long-term.


Title: Re: Running bitcoind in pruning mode
Post by: gmaxwell on November 04, 2015, 04:31:57 PM
You still verify and relay transactions. Other nodes can no longer get block from you though, at least for now.
If you run git master (to be 0.12 later) instead of 0.11 you will also relay new blocks as they are found while pruning.


Title: Re: Running bitcoind in pruning mode
Post by: mezzomix on November 04, 2015, 06:50:26 PM
Did somebody already create an address index patch (UTXO and mempool) that is working in pruned mode?


Title: Re: Running bitcoind in pruning mode
Post by: John (John K.) on November 08, 2015, 10:35:37 PM
You still verify and relay transactions. Other nodes can no longer get block from you though, at least for now.
If you run git master (to be 0.12 later) instead of 0.11 you will also relay new blocks as they are found while pruning.


Hmm... so the server is up to date with the newest blocks now, but I'm still not getting more connections then 8. I've verified that it can be reachable from outside networks.


Title: Re: Running bitcoind in pruning mode
Post by: John (John K.) on November 08, 2015, 11:21:41 PM
You still verify and relay transactions. Other nodes can no longer get block from you though, at least for now.
If you run git master (to be 0.12 later) instead of 0.11 you will also relay new blocks as they are found while pruning.


Hmm... so the server is up to date with the newest blocks now, but I'm still not getting more connections then 8. I've verified that it can be reachable from outside networks.

Never mind, I got it working now. Gonna find the time to update it to 0.12 next. :D


Title: Re: Running bitcoind in pruning mode
Post by: John (John K.) on November 09, 2015, 08:19:34 PM
Did somebody already create an address index patch (UTXO and mempool) that is working in pruned mode?

No idea, but the relay block service is active now with the latest git master.