Replying to Avatar Silberengel

From 3d450733917dafd6bfc6f2b1fc7aa32f09efec6d Mon Sep 17 00:00:00 2001

Subject: [PATCH 0/1] Burning an npub

The npub+nsec combination brings the advantage that no user can have their passkey stolen and end up "locked out" of their own profile or app accounts by the thief changing their passkey. This is a securtiy advancement. However, the problem remains that the passkey (nsec) could be stolen or be given to a bad actor, and then the user must helplessly "share" the passkey with them. Both owner and thief can continue to sign events using this passkey. For this reason, I suggest we give users the possibility to burn an npub, by issuing a final event describing the npub as "retired".
39
purple.co 1y ago

retired or locked

Reply to this note

Please Login to reply.

Discussion

Avatar
Silberengel 1y ago

Locked implies it could eventually be unlocked. Sounds less final.

Can't really lock and then unlock an npub because the nsec can't change, as far as I know.

39
purple.co 1y ago

A lot of events are signed with the key, and very hard to delete all, to keep but locked will allow history/backup, before retire.

Avatar
Silberengel 1y ago

Are you defining

"locked" as "frozen, but don't delete anything, yet"

versus

"retired" as "already locked and events now ready for deletion"?

Or are you using locked as a different word for the second thing?

39
purple.co 1y ago

I think 2 stages can be useful. Retired imply deletion, and more difficult to implement by all relays. Or, maybe, locked is like blocked.