You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When protocol v1 is published, it will open a lot of eventual avenues of improvement not possible under v0. One such path is a specialized recovery paths for Nomen names in the event of a key theft. An event likely to be common in coming years, as Nostr early adopters are used to plugging their secret keys into all sorts of applications.
It could work like this (provisionally):
After a name has been claimed, the user may make a second transaction on chain to do a pre-transfer to a specialized recovery path. The recovery path will be hidden, perhaps like this:
SHA256(secret || new pubkey)
Secret is some secret value, like a password, and new pubkey is the pubkey to be transferred to. This reserves the transfer path and any normal transfers made after this are invalid. The only valid transfer after this time is to the recovery path.
At recovery time, the user will make a recovery transaction revealing their secret and the new pubkey, completing the recovery and transferring ownership to the backup key.
The text was updated successfully, but these errors were encountered:
When protocol v1 is published, it will open a lot of eventual avenues of improvement not possible under v0. One such path is a specialized recovery paths for Nomen names in the event of a key theft. An event likely to be common in coming years, as Nostr early adopters are used to plugging their secret keys into all sorts of applications.
It could work like this (provisionally):
After a name has been claimed, the user may make a second transaction on chain to do a pre-transfer to a specialized recovery path. The recovery path will be hidden, perhaps like this:
SHA256(secret || new pubkey)
Secret is some secret value, like a password, and new pubkey is the pubkey to be transferred to. This reserves the transfer path and any normal transfers made after this are invalid. The only valid transfer after this time is to the recovery path.
At recovery time, the user will make a recovery transaction revealing their secret and the new pubkey, completing the recovery and transferring ownership to the backup key.
The text was updated successfully, but these errors were encountered: