Shouldnt one private key have multiple public keys? That way we don't have to bother about multiple private keys for multiple profiles/aliases.

Replies (13)

While it seems like a good idea to have multiple accounts on a single NSec it is the combo with the Npub that builds security. If your Nsec was made public it would burn all Pulbic as it is no longer under your single control. There's no port over your followers, its a new start from day 1
There should be a way to move your follows and followers to a new account tho.
Currently one private key maps to a single public key. Why can't we have multiple public keys for a single private. Let's say there are two nostr clients. One similar to linkedIn and another similar to Instagram. I want a single private key to access both clients but my public profile ought to be different. I wouldn't want all my LinkedIn guys on my Instagram. Yes this can be achieved by having two separate private keys for both clients. I don't know why that should be the case. What difference does it make to security? Nobody really knows that these multiple public keys belong to the same private key. @fiatjaf
Let's say my private key got exposed. I need a new private key and kill the old one. There should be a way transfer data from one private key to the other and killing the previous.
Yes, or maybe I’m just worried about it being leaked. But someone said the person that stole it could do the same thing, so I’m not sure how it would work.
You don’t. Those people you trust your credit card and bank accounts with will. Come now, the only reason there is security because banks and sneakers, why reinvent themselves?!
I think that’s a separate issue, how could you verify it’s me now? Isn’t that what the domain verification is meant to do? This is more for peace of mind if I suspect it’s been leaked or something.