Nostr Web Client

I see how pubky can complement nostr. Pubky can be the ‘trust anchor’ that is stable over time. Npubs can point to a pubky and a pubky can point to a npub for strong binding. This is similar to nip05, except that pubky uses the mainline DHT to store records instead of DNS. I see it as a complement/alternative to nip05.

Big Bad John 1y ago

So far, Nostr elders do not seem interested in bridging or breaking the key model, but yes, any platform or protocol could use the pkarr method, and it would almost certainly improve censorship resistance.

My guess is that, once you do something like that, people will just find it easier to use Pubky keys/apps/servers, as they will have all the tools needed to make it easy to maintain your dht records, swap servers when needed, etc, and bridging doesnt seem to usually be a popular feature to maintain.

Reply to this note

Please Login to reply.

Discussion

Tim Bouma 1y ago

It would be nice to standardize “pubky” to be in the kind0 event to be presented on a profile, similar to nip05. I’d be happy with that.

It would also be nice to standardize the resource record formats to be the same for DNS/DHT records.

I totally get the value have a trust anchors in other systems. I see nostr as being fairly transient, so if I compromise a nsec I can rotate easily, because everyone to trust the corresponding npub they would check the pubky trust anchor first.