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:
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:
👀👀👀
Could just reuse existing syntax like below in a TXT record for a given domain/sub-domain:
oa1:nostr recipient_address=58ead82fa15b550094f7f5fe4804e0fe75b779dbef2e9b20511eccd69e6d08f9
Thoughts on this as an extension of NIP-05, #[2]?
spoofing a domain to give the wrong key must be a thing
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.
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.
I’d prefer openalias over NIP-05 as well. Eliminates the webserver and generally makes life easier.
Would love to see that be supported in nostr land.
Using DNS records instead of hosting a file for NIP-05 would be a much simpler solution. Organising hosting is a step too far for most but setting a DNS record or 2 is doable and would be cheaper
