Simpler yes, but I’m stuck on manual verification step.. doesn’t seem feasible IRL / at scale… lots of headache to implement an actual recovery.

Also doesn’t seem to solve re-association of past data. User loses a lot in transition. Lots of expectation for other users to do manual steps to recover the social graph. It’s still too damaging.

Yes, our proposal would require a lot of different parties to get behind it to make it work. Inherent complexity there- but activation by the user would be a lot simpler once this is implemented across most clients+relays.

Also, the Excalibur-as-insurance-policy model provides client/relay revenue therefore an incentive for them to implement and make it seamless. I’m certain they could use the revenue from premiums paid by all users who want a recovery option.

I’d pay sats to know my account is recoverable across x number of relays and keep my secure key completely offline until needed, god forbid.

Reply to this note

Please Login to reply.

Discussion

I don't think there is a good way to move data between keys. For instance, you can't get your friends to resign for all DMs they encrypted to you. Same for moving likes, replies, etc to the new key. I think the user will always lose all the data regardless of which key migration we implement.