Peer – Is it possible to use addnode + v2transport(BIP324) arguments in bitcoin.conf?
I’m going to try something new v2transport
arguement addnode=
In ~ bitcoin.conf
Attempts to connect to the peer using the BIP324 v2 transport protocol.
for example bitcoin-cli addnode "192.168.1.94:8333" "add" true
I gave the command and it worked.
bitcoind(935): 2023-12-14T12:28:33Z New manual v2 peer connected: version: 70016, blocks=2542818, peer=7
now bitcoin.conf
I use a file to import a persistent configuration and always run it on startup, but every combination I try works for me and the connection to the peer always fails.
Does anyone know if this feature was added in v26.0, and if so, what nomenclature should I use to get it?
reference:
https://github.com/bitcoin/bitcoin/pull/28331
https://bitcoincore.org/en/releases/26.0/
https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-26.0.md#updated-rpcs
https://bitcoincore.org/en/doc/26.0.0/rpc/network/addnode/