Nuh 🔻 on Nostr: I wouldn't fight changing the crypto as ed25519 is superior in many ways. But I will ...
I wouldn't fight changing the crypto as ed25519 is superior in many ways.
But I will disagree with your bundling of both signatures and lookups. If it works for Nip05 it will work for Pkarr and even better because Pkarr is as secure as npubs. You can add this feature to one client at a time with no consensus needed, it is entirely a question of will, and frankly politics (people worrying they will seem to support a competing thing).
At the end of the day Pkarr is a domain name, of course you can lookup as many diverse services as we can imagine from domain names, that is why they existed.
All the UX that will change is that people sharing their Pkarr domain instead of npubs, and apps knowing how to support that.. or not. Either way, Relays won't even know anything changed. That is not the case for replacing the cryptography signature scheme.
So my point is supporting Pkarr shouldn't be judged with the same dread as changing cryptography.
But I will disagree with your bundling of both signatures and lookups. If it works for Nip05 it will work for Pkarr and even better because Pkarr is as secure as npubs. You can add this feature to one client at a time with no consensus needed, it is entirely a question of will, and frankly politics (people worrying they will seem to support a competing thing).
At the end of the day Pkarr is a domain name, of course you can lookup as many diverse services as we can imagine from domain names, that is why they existed.
All the UX that will change is that people sharing their Pkarr domain instead of npubs, and apps knowing how to support that.. or not. Either way, Relays won't even know anything changed. That is not the case for replacing the cryptography signature scheme.
So my point is supporting Pkarr shouldn't be judged with the same dread as changing cryptography.