<p>Debugging print options can be changed without a restart.</p>

CC BY-SA 4.0
2020-11-12T18:17:42.473Z
Thank you for the answer, won't accept it though, because I am hoping for a more complete answer.
Pedro
CC BY-SA 4.0
2020-11-12T18:33:11.570Z
That's the sum total of options you can change.
Claris
CC BY-SA 4.0
2020-11-12T18:37:15.120Z
Are you sure those are the only ones? I'm disappointed, I was hoping there would be more.
Pedro
CC BY-SA 4.0
2020-11-12T18:38:37.980Z
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?
Claris
CC BY-SA 4.0
2020-11-12T18:54:33.430Z
For now: zmq URLs and watermarks, maxmempool, mempoolexpiry, minrelaytxfee, maxuploadtarget
Pedro
CC BY-SA 4.0
2020-11-12T19:47:29.527Z
Wallets can be loaded/unloaded at runtime now (which is arguably changing the "wallet=" option).
Pieter Wuille
CC BY-SA 4.0
2020-11-12T19:50:09.470Z
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.
Claris
CC BY-SA 4.0
2020-11-12T20:06:53.433Z
@PieterWuille that just reminded of 'addnode' which can be done with the corresponding RPC command.
Pedro
CC BY-SA 4.0
2020-11-12T17:52:40.467Z
2020-11-12T17:52:40.467Z
Claris
<p>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.</p>
<p>If I am not mistaken, changing the RPC password, for example, can be done without restarting the node but most options require a restart.</p>
<p>What are the options that require (and don't require) a restart to take effect?</p>

<bitcoin-core><nodes><bitcoin.conf>
What bitcoin core options can be changed without a restart?
Pedro
# What bitcoin core options can be changed without a restart?

(Asked by: username_0 on 2020-11-12)

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?

**Tags:** bitcoin-core, nodes, bitcoin.conf


---

## 1 answers

### Answer by username_1 on 2020-11-12. Score: 3

Debugging print options can be changed without a restart.

> **Comments:**
> **username_0**: Thank you for the answer, won't accept it though, because I am hoping for a more complete answer.  
> **username_1**: That's the sum total of options you can change.  
> **username_0**: Are you sure those are the only ones? I'm disappointed, I was hoping there would be more.  
> **username_1**: 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?  
> **username_0**: For now: zmq URLs and watermarks, maxmempool, mempoolexpiry, minrelaytxfee, maxuploadtarget  
> **username_2**: Wallets can be loaded/unloaded at runtime now (which is arguably changing the "wallet=" option).  
> **username_1**: 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.  
> **username_0**: @username_2 that just reminded of 'addnode' which can be done with the corresponding RPC command.  

---

