Having to stop and restart a bitcoind to change the blocksize soft limit would be better handled by an RPC interface command to change it, to avoid the need for a restart.
RPC: add support to change the block size soft limit #6605
issue kanoi opened this issue on August 31, 2015-
kanoi commented at 11:37 AM on August 31, 2015: none
-
luke-jr commented at 4:46 PM on August 31, 2015: member
Agreed. I wonder if there should simply be a RPC method to change any of the command-line options? (and only officially support it for a specific set that is known to react to changes in mapArgs)
-
jameshilliard commented at 10:37 PM on August 31, 2015: contributor
Maybe just a RPC command to reload settings from bitcoin.conf without a restart? This would certainly be handy as I've had to change some settings to handle the transaction spam attacks and restarting bitcoin core is not something that is easy to do on an active pool.
- laanwj added the label RPC on Sep 4, 2015
-
meshcollider commented at 3:38 AM on March 14, 2018: contributor
-
jnewbery commented at 2:44 PM on March 29, 2018: member
No-one appears to be working on this, and it's been untouched for over 2 years. Close with 'up for grabs'?
-
MarcoFalke commented at 2:48 PM on March 29, 2018: member
I think this goes under the general topic of "Allow command line args to be overridden at run-time". Making it safely possible for a single arg is probably as much effort as the general case.
- MarcoFalke closed this on Mar 29, 2018
- DrahtBot locked this on Sep 8, 2021
Labels