NIP-07 extensions and NIP-55 signers are pretty good. NIP-46 is less good IMO (too slow). Delegations will never work (IMO). FROST might work, but it is quite complicated (managing keys for each app/device etc)

It is overwhelming indeed. But no protocol is perfect. We shouldn't be trying to solve all of it in one. The goal is to find a set of decisions in each of those buckets that work so well together that can 2-10x Nostr even though we know they are not perfect.

Reply to this note

Please Login to reply.

Discussion

I'm not looking for perfect. But I would like to roll over my keypair.

If the goal is just to arrange roll overs, we can probably do something about it without a new Nostr.

I don't like any of the structured seed/key migration schemes. I feel like they create more attacking possibilities than benefits with the current structure of Nostr.

But soft migration via Web Of Trust could be effective. https://github.com/vitorpamplona/nips/blob/key-rotation/22.md

Why would using FROST imply managing keys for each device/app?

The idea is to use a multi-key FROST npub to allow you to add and remove keys for each device/app that you sign up. In that way if that client misbehaves and leaks your key, you can rotate that client's key out of your FROST setup