One advantage of https://github.com/nostr-protocol/nips/pull/158 over NIP-26 for key security is that it only requires a single app to monitor key invalidations and update your list of followed keys for a key to be invalidated/rotated mostly successfully.

While NIP-26 requires all apps and relays to support it for it to work.

However, NIP-26 could work with much less than 100% if it was only used for sporadic delegations for niche use cases, or for grandfathering keys in custodial services.

Reply to this note

Please Login to reply.

Discussion

This should a standard.

I definately want to generate keys by hardware wallet.

One question that I don't see to be answered is why not just always create a new derived path instead of needing to contain the next key.

That way clients could verify that the 100th derived path is greater than the 20th, so the 20th is invalidated, so it would need less storage on the clients.