No unfortunately it has to be ed25519 keys because it leverages the massive 15 yrs old BitTorrent DHT, and it doesn't return events it returns a <1000 bytes compressed array of Resource Records

Think of how BlueSky use TXT records to map domain names to DIDs, well the same but the domain name is a publickey and the Resources Records are signed.

Reply to this note

Please Login to reply.

Discussion

Work in progress to derive ed25519 keys from nostr:

https://melvincarvalho.github.io/noskey/docs/

Didn't know that is at all possible, derive as in actually I can see npub and ed pubkey and verify they are related?

Either that works, or Nostr profiles include the ed25519 key, then use Pkarr to lookup the current relays if the user ever switched to an obscure or even single tenant relay.

Really bullish on this as I have stress tested as much as I could and didn't crack yet.