Replying to Avatar Seth For Privacy

Anyone know if there is a technical reason that NIP-05 couldn’t be done for a single pubkey via OpenAlias?

Would greatly simplify NIP-05 for anyone who has a proper domain name, and would be an excellent alternative option to serving a static JSON file via a web server.

More here:

https://openalias.org/

And if you’ve never seen what it can be used for, it’s excellent for static addresses or reusable payment codes, like PayNym’s or as seen in Monero:

https://medium.com/@JEhrenhofer/openalias-the-best-cryptocurrency-wallet-feature-youve-never-heard-of-bbf4a991d0a8

34
royaoid 2y ago

spoofing a domain to give the wrong key must be a thing

Reply to this note

Please Login to reply.

Discussion

Avatar
4c648e19... 2y ago

Isn't that already a problem with the current system? It's already based on DNS, like almost everything on the internet, just with the extra step of a webserver.

I imagine DNSSEC could solve much of that.

Avatar
Seth For Privacy 2y ago

Yeah, the current approach is already entirely reliant on DNS security, so OpenAlias would have the same concerns (and solution in DNSSEC) while removing the hosting/infrastructure requirements.

34
royaoid 2y ago

not exactly because a signed note defines the id at the domain, only thing missing is the proof at the domain also being signed