←back to thread

Yggdrasil Network

(yggdrasil-network.github.io)
322 points BSDobelix | 5 comments | | HN request time: 0.686s | source
1. PhilipRoman ◴[] No.42156775[source]
I really like the idea of address being derived from public key, but there is a problem with this approach - since Yggdrasil currently uses IPv6 addresses, the length is very limited and you can find collisions (there is a workaround which involves brute forcing a key with more leading bits). As I understand, the long term plan is adding a custom protocol which has no limits for address length.
replies(3): >>42156869 #>>42156876 #>>42157301 #
2. Retr0id ◴[] No.42156869[source]
My napkin math says it'd be plausible to generate a pair of colliding addresses (birthday paradox etc.), but still implausible to collide with the set of existing in-use addresses. How much would the former actually matter, in the context of Yggdrasil?
3. Its_Padar ◴[] No.42156876[source]
Why not use the entire public key and let entropy do the rest, like the Reticulum Network?
4. neilalexander ◴[] No.42157301[source]
Truncating the public key to fit in an IPv6 address isn’t totally ideal, agreed, but for now it means that just about any existing IPv6-capable application will work over Yggdrasil without modification, which is a nice property for a testnet.
replies(1): >>42158362 #
5. Retr0id ◴[] No.42158362[source]
What about truncating a hash of the whole public key? (what's what I'd assumed was happening already)