Documentation about `bitcoin.conf` file

[28e7166c23e70c2014feb5d64]

Where can I find the official documentation for what can be put in the `bitcoin.conf` file, and the meaning of each option?

From [here](https://github.com/bitcoin/bitcoin/blob/master/doc/bitcoin-conf.md) I understand that (almost) any argument of the `bitcoin-cli` command is possible. My next question is, where are the arguments of `bitcoin-cli` described? I cannot find them in [the official documentation](https://github.com/bitcoin/bitcoin/blob/master/doc), only in [the website](https://developer.bitcoin.org/reference/rpc/), but I am not sure in this case whether the latter is updated.

[achow101]

Pretty much any argument of bitcoind (not bitcoin-cli) can be specified in the bitcoin.conf. You can get the full list by doing bitcoind -help -help-debug

[nc50lc]

Since the first question is answered, I'll skip it:

My next question is, where are the arguments of `bitcoin-cli` described?

If you actually mean args, those are in: bitcoin-cli --help
If you mean RPC commands like in your links, use: bitcoin-cli help instead (requires a running daemon)
Then use bitcoin-cli help <command> to get its documentation and examples.

only in [the website](https://developer.bitcoin.org/reference/rpc/), but I am not sure in this case whether the latter is updated.

Those documents are open source, so you can immediately check its last edit timestamp by clicking "Edit Page" under Contribute.
e.g. your link's last commit currently shows "4 years ago": github.com/bitcoin-dot-org/developer.bitcoin.org/blob/master/reference/rpc/index.rst

For the latest RPC command list (specific to Bitcoin Core versions), use this list: bitcoincore.org/en/doc/

[takuma sato]

Does anyone know if you can use tags like [test] to separate configs that are only applied to testnet or [main] to mainnet? I've seen some people do this.

[achow101]

Does anyone know if you can use tags like [test] to separate configs that are only applied to testnet or [main] to mainnet? I've seen some people do this.

Yes

[takuma sato]

Does anyone know if you can use tags like [test] to separate configs that are only applied to testnet or [main] to mainnet? I've seen some people do this.

Yes

So to understand the formatting, everything needs to be packed right next below the tag or can you sort it out with comments, gaps etc? example

[main]
#RCP
bind=127.0.0.1
rcpbind=127.0.0.1

#enable this when not using tor
#listen=0

#tor
proxy=127.0.0.1:9050
listen=1
listenonion=1
onlynet=onion

[test]
bind=127.0.0.1
rcpbind=127.0.0.1
listen=0

I mean what im saying is, everything under [main] until the next tag [test] is applied in main, and anything under [test] is applied in testnet3, even if there are these gaps or #.

[achow101]

I mean what im saying is, everything under [main] until the next tag [test] is applied in main, and anything under [test] is applied in testnet3, even if there are these gaps or #.

Yes. Whitespace and comments are ignored entirely and have no meaning when parsed.

Options that you want to apply to all networks need to come before the first network section header. Anything after a header will apply to that network only, until the next network section header. The allowed names for network sections are the same as those for the -chain option.

[nc50lc]

Does anyone know if you can use tags like [test] to separate configs that are only applied to testnet or [main] to mainnet? I've seen some people do this.

Looks like takuma sato needed a second opinion on my suggestion in his other thread to use tags on his bitcoin.conf file to separate the options :P

For additional confirmations, there should be a sample bitcoin.conf file in your Knots install directory or inside its /share/examples/ folder.
Scroll-down to its footer and you'll find some information about "sections" and the available network tags.

[takuma sato]

Does anyone know if you can use tags like [test] to separate configs that are only applied to testnet or [main] to mainnet? I've seen some people do this.

Looks like takuma sato needed a second opinion on my suggestion in his other thread to use tags on his bitcoin.conf file to separate the options

For additional confirmations, there should be a sample bitcoin.conf file in your Knots install directory or inside its /share/examples/ folder.
Scroll-down to its footer and you'll find some information about "sections" and the available network tags.

Yeah, it was hidden right at the end of the bitcoin.conf sample file. Btw, do you know why my tor node is not findable on bitnodes.io only when on testnet3 mode? I don't get it, it works fine with the main blockchain, but it's not reachable when on testnet3. I don't have anything on the [test] section other than the 2 bind options which are just the same as on the main anyway.

[nc50lc]

-snip-

Btw, do you know why my tor node is not findable on bitnodes.io only when on testnet3 mode? I don't get it, it works fine with the main blockchain, but it's not reachable when on testnet3. I don't have anything on the [test] section other than the 2 bind options which are just the same as on the main anyway.

We're getting off-topic here but if your testnet3 node has any inbound connections, there's no issue with its setup and it's just Bitnodes can't connect to it.

And are you using Bitnodes in testnet3 version?
Because AFAIK the live version is only for mainnet, unless you're using your own instance or a testnet3 link that I'm not aware of.