pull down to refresh

0 sats \ 1 reply \ @k00b 22h \ on: DNN: Decentralized Naming Network nostr
Interesting scheme. I was curious how it was both "anchored in the bitcoin" and not putting data on-chain which is laid out in (4):
  1. Publish a kind:61600 event with your desired name.
  2. Publish a kind:62600 event with connection data.
  3. Publish a kind:63600 event with metadata.
  4. Publish a kind:60600 event, referencing the above and including a Bitcoin self-transfer as proof.
This inversion of offchain referencing onchain rather than the reverse is not something I've seen before.
I was also curious how one can "Have whatever name you want and change it whenever you want" and it appears that that's only true if your name carries metadata about how to verify the name:
alice.n50.5 alice.b1000050.5
This can be shortened to another encoding I guess:
To improve human readability and memorability and make referencing DNN names easier, DNN supports an extra encoded format that compresses the block number and transaction position into a compact alphanumeric string.
The above example becomes:
alice.agd-abandon alice.ytj-abandon-zoo
Which is objectively more human friendly even if it's unsatisfying.
Overall I feel like I'm not able to "Have whatever name I want" but it's an interesting scheme.
write
preview
21 sats \ 0 replies \ @freakoverseOG OP 19h
I'm basically differentiating between an "ID" and a "name", where "alice.n50.5" can be "bob.n50.5" where the change happens in nostr event kind:61600
reply