https://github.com/bitcoin/bitcoin/blob/f984c7d7adf40e8517437f7b8c3704a63e1ca034/src/init.cppSee line 865:
if (mapArgs.count("-bind") || mapArgs.count("
-whitebind")) {
Also:
https://github.com/bitcoin/bitcoin/pull/4378It seems like -whitelist and -whitebind is missing from the wiki:
https://en.bitcoin.it/wiki/Running_Bitcointhey also seem to be missing from the help output in --bitcoind
Should that not be fixed? If someone with wiki access and having a github account would fix it, it would be nice. It should be included, no? The 2nd link in this post is dated july 14 2014.
If someone haven't fixed it until I get back, I will see if I can fix it myself.
However, it seems it's added to the bitcoind --help output:
https://github.com/bitcoin/bitcoin/blob/f984c7d7adf40e8517437f7b8c3704a63e1ca034/src/init.cppLine 278 onwards.
It's however not present in "bitcoind --help" output of Bitcoin Core Daemon version v0.9.3.0-g40d2041-beta.
I was trying to see when line 278 onwards in init.cpp was added, is there some easy way to see when it was last changed and by whom?
I think it should be a rule to update both the wiki and the help output in the source once for anyone adding a new parameter.
In addition, I notice that the bitcoin core daemon by default binds to all interfaces? Would it be possible to bind only to one interface. For example, if you have a machine with several interfaces, you might want bitcoind only to bind to one or two of them.
For example, if you have lo,venet0:0 and venet0:1, you might only want to bind to lo and venet0:0, for example 127.0.0.1 and 222.222.222.222. I've played around with -bind and -externalip, but still the daemon is binding its port 8333 to all interfaces. I'd like to be able to control that behaviour. Is that possible as of yet?
I will look into the source code and see what I can find out when I get back, unless some other bright heads have already figured it out.
And lastly from bitcoind -testnet getinfo on Bitcoin Core Daemon version v0.9.3.0-g40d2041-beta:
"errors" : "Warning: This version is obsolete, upgrade required!"
Is there no point in running a testnet node with this version number?
Also, regarding the version number v0.9.3.0-g40d2041-beta, what does the g40d2041 part mean? And how is it decided what this value should be, is there any logical meaning to it?