11:58 <stevenroose> Hmm, I was always under the impression that -port= is the port that would be used for p2p and that -bind was the same thing, but to also specify the interface. But now I notice that -bind and -port have different default port numbers. Are they for different things? We specify -port and -rpcport for all our nodes in an integration test environment, but since v28 suddenly they all also want

11:58 <stevenroose> port 18445, which is the one mentioned in -bind.

12:03 <stevenroose> Seems that the 18445 is the default onion port? -listenonion=0 seems like it might work.

13:01 <Chris_Stewart_5> stevenroose: -listenonion doesn't do what you expect it to do, vasild described the actual behavior of that setting a few weeks back

13:01 <Chris_Stewart_5> 2024-10-09 23:11:26 vasild_ What listenonion=1 does is to automatically create the hidden service with the tor daemon, so that users don't have to manually add HiddenServiceDir and HiddenServicePort in their torrc. But it does not control where bitcoind listens, I think a name like -autotorservice would be more appropriate than -listenonion.

13:01 <Chris_Stewart_5> 2024-10-09 23:17:34 vasild_ A real problem with <28.0 that could happen is this: if two bitcoinds are started on the same machine with "port=10833 rpcport=10832 listenonion=1" and "port=20833 rpcport=20832 listenonion=1", then only the first would manage to bind on 127.0.0.1:8334. The second would "think" it did because the bind error was ignored. Due to listenonion=1 both will create a

13:01 <Chris_Stewart_5> tor service, telling the tor daemon

13:01 <Chris_Stewart_5> 2024-10-09 23:17:40 vasild_ to redirect incoming connections to that service to 127.0.0.1:8334. For example first.onion:8333 -> 127.0.0.1:8334 and second.onion:8333 -> 127.0.0.1:8334.

13:02 <Chris_Stewart_5> 2024-10-09 23:20:23 vasild_ So all incoming tor connections for the second bitcoind would be redirected to the first bitcoind :/

13:20 <pinheadmz> #22729 i believe ?

13:20 <gribble> https://github.com/bitcoin/bitcoin/issues/22729 | Make it possible to disable Tor binds and abort startup on bind failure by vasild · Pull Request #22729 · bitcoin/bitcoin · GitHub

15:25 <stevenroose> Chris_Stewart_5: I am starting two of them with `port= rpcport=` without anything else and with v28 they conflict on port 18445 which seems to stem from the default -bind= which I thought would be overwritten by -port=.

15:30 <stevenroose> I mean, I can always just add a -bind=127.0.0.1:<port> -port=<port>`, but I thought the bind would be redundant in this case.

15:30 <stevenroose> Just asking if I interpret that incorrectly, before I open an issue.

15:41 <bitcoin-git> [bitcoin] sipa opened pull request #31112: Improve parallel script validation error debug logging (master...202410_parcheck_debug) https://github.com/bitcoin/bitcoin/pull/31112

16:57 <lightlike> stevenroose: yes, I think that there should be an issue for this,even if there is a -bind alternative. These -port setups are widespread and don't work anymore with v28, so I expect there will be multiple other people running into this in the next weeks

19:32 <Chris_Stewart_5> stevenroose: You interpret it correctly, imo the -port setting should probably just be deprecated and the removed

19:32 <Chris_Stewart_5> and then removed*

21:15 <bitcoin-git> [bitcoin] toogoodtofail opened pull request #31114: Simple security.doc improvement (28.x...28.x) https://github.com/bitcoin/bitcoin/pull/31114