What bitcoin core options can be changed without a restart?


I often experiment with new bitcoin core options (like zmq, debug and fee options) and I would like to avoid restarting my node for them to take effect.

If I am not mistaken, changing the RPC password, for example, can be done without restarting the node but most options require a restart.

What are the options that require (and don't require) a restart to take effect?


Posted 2020-11-12T14:51:13.603

Reputation: 641



Debugging print options can be changed without a restart.


Posted 2020-11-12T14:51:13.603

Reputation: 12 846

Thank you for the answer, won't accept it though, because I am hoping for a more complete answer. – Pedro – 2020-11-12T18:17:42.473

That's the sum total of options you can change. – Anonymous – 2020-11-12T18:33:11.570

Are you sure those are the only ones? I'm disappointed, I was hoping there would be more. – Pedro – 2020-11-12T18:37:15.120

The configuration options are things like how much memory can be allocated, how much caching to use, if peers should be sending transactions or not. Being able to configure these on the fly would come at an absurd cost of complexity, for very little in the way of use cases. What would you like to be configuring on the fly? – Anonymous – 2020-11-12T18:38:37.980

For now: zmq URLs and watermarks, maxmempool, mempoolexpiry, minrelaytxfee, maxuploadtarget – Pedro – 2020-11-12T18:54:33.430

2Wallets can be loaded/unloaded at runtime now (which is arguably changing the "wallet=" option). – Pieter Wuille – 2020-11-12T19:47:29.527

I'm not sure I'd even consider loading wallets on the fly to meaningfully be different than taking down the node and adding it to the configuration. The majority of the time it will require a rescan, which hogs cs_main, and you desync from the network. – Anonymous – 2020-11-12T19:50:09.470

2@PieterWuille that just reminded of 'addnode' which can be done with the corresponding RPC command. – Pedro – 2020-11-12T20:06:53.433