bitcoin core – BIP324 v2transport is redundant on tor + i2p connections?


Simply testing the current BIP324 on my node, since Bitcoin Core v26 and having v2transport=1 in bitcoin.conf set, I’ve observed that I’m receiving some incoming connections utilizing the v2 transport protocol to my node, which might solely be reachable to incoming connection, utilizing Tor and I2P, with my onion/I2P addresses, and if I make outgoing peer connections utilizing the v2 transport protocol from my node to some Tor or I2P addresses, the connection is profitable. It really works with out issues, okay.

However, contemplating that these two networks are encrypted by design, is it redundant to make use of this extra safety layer for these networks? If, sure, should not it solely be used for ipv4/ipv6 connections to keep away from this pointless redundancy?

Refs:

https://help.torproject.org/about/

https://geti2p.internet/en/

https://github.com/bitcoin/bips/blob/grasp/bip-0324.mediawiki

Leave a Reply

Your email address will not be published. Required fields are marked *

Back To Top