pull down to refresh

0 sats \ 5 replies \ @satup OP 20 Aug 2022 \ on: Yggdrasil: End-to-end encrypted IPV6 routing network bitcoin
IMHO it’s suitable to be an option to get a fixed IPv6 address for my lightning node in a format of public-key@permanent-ipv6:port to avoid ephemeral IPv4 addresses.
write
preview
0 sats \ 4 replies \ @based 20 Aug 2022
Sure, so is a Tor onion address or I2P, albeit with higher latency.
reply
0 sats \ 3 replies \ @satup OP 21 Aug 2022
the latency of yggdrasil is much less than Tor while it’s a mesh of nodes that visible to everyone.
reply
101 sats \ 2 replies \ @based 21 Aug 2022
Yes, as I said.
How's "mesh of nodes that visible to everyone" different from Tor/I2P though? You're not getting an IPv6 address on the public Internet so it's not reachable by everyone, all endpoints have to run the software.
reply
101 sats \ 1 reply \ @satup OP 21 Aug 2022
well, it’s true that the software( or module) is prerequisite, there’s one advantage that Ygg would win: the IPv6 address is derived from public key which is coherent with every node. You know the public key, the same time you got IP to route so to speak.
reply
0 sats \ 0 replies \ @based 21 Aug 2022
I don't see why that matters. If you know a Tor/Onion address then you know it, if you know an I2P address the you know it. They are both keys and they don't translate to another address.
There are other tangible differences though, anonymity and latency aside, in how software actually interacts with these networks.
Tor: TCP only, used via software SOCKS proxy support.
I2P: Software is expected to be integrated specifically with I2P.
CJDNS/Yggdrasil: Sets up a VPN interface with access to an internal IPv6 network. Both TCP and UDP supported, software needs no integrations, only IPv6 support.
Bitcoin supports all four, and the reason there are special cases for CJDNS and Yggdrasil even though I said it's not needed, are that Bitcoin Core cares specifically about separating different networks and for gossiping about other nodes.
reply