https://support.torproject.org/onionservices/v2-deprecation/
BIP:
https://github.com/bitcoin/bips/blob/master/bip-0155.mediawiki
Implementation:
bitcoin/bitcoin#19954
Currently Fluxd still implements the deprecated v2 onion addresses. This means that no nodes can advertise themselves with onion addresses.
This is quite limiting as a large chunk of flux nodes have no inbound connections due to nat. If fluxd supported v3, we could advertise every fluxnode with a v3 onion address and therefore allow inbound connections.
This wouldn't be that much work as it's just a matter of porting the code over from Bitcoin.
https://support.torproject.org/onionservices/v2-deprecation/
BIP:
https://github.com/bitcoin/bips/blob/master/bip-0155.mediawiki
Implementation:
bitcoin/bitcoin#19954
Currently Fluxd still implements the deprecated v2 onion addresses. This means that no nodes can advertise themselves with onion addresses.
This is quite limiting as a large chunk of flux nodes have no inbound connections due to nat. If fluxd supported v3, we could advertise every fluxnode with a v3 onion address and therefore allow inbound connections.
This wouldn't be that much work as it's just a matter of porting the code over from Bitcoin.