Nuh 🔻 on Nostr: ok I will engage with the divergence instead of repeating myself about the rest I ...

ok I will engage with the divergence instead of repeating myself about the rest I think we are mostly in agreement.

1. option one and two seems to me just a matter of encoding. The way Pkarr does it is literally encoding a DNS reply packet as is. So if you know how to encode and parse DNS records you are set. You can then choose TXT records or A,AAAA records or my favorite HTTPS records, depending on what are you trying to advertise. I say TXT record is good enough to advertise your relays. But the real magic is when you publish HTTPS records and use them in an HTTP client and use public keys as domains and even use TLS with that... I had a demo for that but I won't post it again, I don't expect you to run code in your weekend.

2. I am not really sure you are stuck with secp as that strikes me as a premature declaration of takeoff growth. Fwiw, you can use Pkarr as the root of the identity, use it to point to an npub, and use the secp to sign events... not much different than Nip5 other than being more sovereign. But just like nip5, most clients won't support it