Identity on-chain, data off-chain: design proposal #495
Labels
No Label
applications
BLOCKED
bug
design
duplicate
enhancement
fixed?
funding-needed
help wanted
infrastructure
invalid
payments
qubes
question
ready-for-implementation
refactor
spam
tapir-server
testing
tor
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#495
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Identity online, data offline: design proposalto Identity on-chain, data off-chain: design proposal