Possibility to dump all runtime parameter values #28790

1. 
   Gitsarry commented at 6:01 pm on November 4, 2023: none

   Please describe the feature you’d like to see added.

   I would like to be able to see all parameters and it’s values that bitcoind “knows” when it is running. That are at least those parameters you can set in bitcoin.conf file, e.g. upnp, disablewallet etc.

   My use case is with bitcoind v26.0.0rc2 I want to test enabling v2 transport with v2transport=1.

   Since I have since then not one v2 connection (which is perfectly reasonable, I guess, since it is a new feature disabled by default), I would like to verify that bitcoind has v2transport really enabled, to be sure that the reason is not a config problem.

   I think this would be generally good because users where able to verify if the running values are those that they expect (e.g. they have set them like in my use case above, or they should have their default value, so users can verify the documentation of default values)

   Is your feature related to a problem, if so please describe it.

   See also #15021

   Describe the solution you’d like

   A RPC command dumpconfig that dumps a list of all runtime parameters as key-value-pairs.

   Describe any alternatives you’ve considered

   A setting in bitcoin.conf dumpconfig_file which defaults to dumpconfig.json (analog to existing settings file option) that makes bitcoind dump it’s parameters in that dumpconfig.json file on startup.

   Please leave any additional context

   No response

2. Gitsarry added the label Feature on Nov 4, 2023
3. 
   achow101 commented at 6:13 pm on November 4, 2023: member

   All interpreted config options are logged to the debug.log file.
4. 
   Gitsarry commented at 6:27 pm on November 4, 2023: none

   @achow101 Thanks, I did not know that, I guess that feature was added some time after I last inspected the debug log in detail (some years ago? ;). I guess you mean lines like these?

   02023-08-08T17:44:49Z Config file: /home/user/.bitcoin/bitcoin.conf
   12023-08-08T17:44:49Z Config file arg: i2psam="127.0.0.1:7656"
   22023-08-08T17:44:49Z Config file arg: listen="1"
   

   That solves my particular use case, but maybe it’s worth to consider dumping all runtime values as written in OP before closing this.

5. 
   maflcko commented at 2:26 pm on January 3, 2024: member

   To get all config options (and their default) you can run -help.

   To get all interpreted config options, you can look a the debug log, as already explained.

6. 
   fanquake commented at 2:49 pm on January 3, 2024: member

   Going to close this for now.
7. fanquake closed this on Jan 3, 2024

   ---

Contributors
Gitsarry achow101 maflcko fanquake

Labels
Feature