- What happens when my nsec is compromised?
- You cry
👉 we need a better answer if we want to go mainstream
If there is a way to announce what relays we use, there should be a way to also announce other npub we use (and the ones we revoke). This would make it easy to “add devices” to our Nostr “meta account” and therefore protect it from device/nsec loss (it also removes the need to ever export the nsec which is a big security issue)
Wdyt?
Solutions will be built, when the need (urgency) is really there.
The needs of the first adopters aren’t the same than the ones of the late ones.
(That’s how couch surfing never became Airbnb.)
Just to be clear, I agree we need a solution for the mentioned problem. For now it's maybe fine to just go cry (maybe nostr:npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw will let you enter his forest for some extra comfort).
Somewhere in the future we will need something like key delegation (by default).
I agree that it's a bad answer. But I also don't have a better solution, especially for loss of nsecs...
You are overthinking.
Crying is, and forever will be, thruthfull only answer in existence.
And it is the exact reason all other protocols are a bunch of pussies, because they are afraid some-one at some-point, will have to cry.
As to what happens when keys get compromised:
The reason i basically dont awnser is because its is a complicated clusterfuck. My proposal would be to self publish your privatekey, and thereby put a lot of pressure on relays to start blocking your stuff. But you can imagine a million things.
But all if it involves crying to one degree or another.
