Oddbean new post about login | logout I think I’m not explaining it well enough. I want to have two key pairs (or more), but I want my main one to announce it’s “adopting” the other. then second can handshake this relationship with my main account. Once that is done. I can use my second key pair npub with close to zero risk. If it gets compromised in an insecure app, the main key will denounce it. If someone wants to send me a dm to the secondary npub, the client will look for the main one and send it. I feel like I’m not making sense 🤣😅 this needs a nostr nest.
Yeah, we can link the two, but DMs, mentions, notifications to the sub key will not show up on the main key's client. Even if they are all linked, every sub key is its own thing. There is a proposal for using FROST for multi-key setups with key rotation without changing the public key. But I have not seen it working yet.
It works -- I've already signed events with it.
But can you rotate keys (deauthorize old, add new) without changing the pubkey?
I don’t think so, but YOU shard the key, so all the signers would need to know about the other signers (they don’t need to) AND all collude against you
I thought It was something to do with finding a new polynomial matches the keys you want to keep. But idk...
What I don’t understand, Vitor says that DMs, notifications, mentions etc won’t reach the main account, why? Let the client tag, DM, Mention, both npubs, sub and main. No?
Sure, but only clients that implement this NIP will tag both. Majority of the clients will just do the basic one and tag the subkey. Which now turns into a mess because some clients work others don't. + For DMs, the encryption happens to each key. You can't just tag both. You have to create a NIP-17 group with the 3 of you (2 of your keys + 1 for your friend) so that you can reply to the other two at all times.