Identity on-chain, data off-chain: design proposal #495

Closed
opened 2023-02-27 06:22:44 +00:00 by serrq · 0 comments

I used SimpleX for around 8 months and making backup all the time result boring.

There was a time when I used Nostr, and so maybe I had an idea to eliminate (maybe) the need for a local backup, at least in terms of identity and login, not data (chats, etc.).

In my idea the identity (pubkey) resides in the blockchain while the unlock key (private key or spend key) is in our hands locally.

As for the data exchanged, nothing will change compared to the current design: the data will be encrypted locally.

What changes is not having to have a backup to restore an account on a new device.

I am not a developer so my idea is related to reasoning alone. I have no idea about the security implications.

That is why I ask you to evaluate my idea from an expert.

I used SimpleX for around 8 months and making backup all the time result boring. There was a time when I used Nostr, and so maybe I had an idea to eliminate (maybe) the need for a local backup, at least in terms of identity and login, not data (chats, etc.). In my idea the identity (pubkey) resides in the blockchain while the unlock key (private key or spend key) is in our hands locally. As for the data exchanged, nothing will change compared to the current design: the data will be encrypted locally. What changes is not having to have a backup to restore an account on a new device. I am not a developer so my idea is related to reasoning alone. I have no idea about the security implications. That is why I ask you to evaluate my idea from an expert.
serrq closed this issue 2023-02-27 18:06:02 +00:00
serrq changed title from Identity online, data offline: design proposal to Identity on-chain, data off-chain: design proposal 2023-03-03 08:57:03 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtch.im/cwtch#495
No description provided.