I’m trying to use the new v2transport argument on addnode= in bitcoin.conf to attempt to connect to the peer using BIP324 v2 transport protocol.
I tried using, for example, the bitcoin-cli addnode "192.168.1.94:8333" "add" true command, and it worked.
Now, I want to use it by adding it to the bitcoin.conf file to get persistent configuration and always exec this at startup, but any combination that I try, works for me, the connection with the peer always fails.
Someone knows if this feature was added with v26.0 or not and if yes, what nomenclature I should use to get this?
Refs:
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/
