- works for multiple device without need to scan a QR code to link device because it derives keys from username/password combo.
- also uses zero knowledge proofs to retrieve the key on login to validate that the user logging in knows the password. This is nice because you don’t need to memorize or save a seed phrase, but is vulnerable to weak passwords.
- random salts + password to generate keys for security
- append-only log of events that uses smart contracts that run on client to process new events.
- snapshots of state every
N messages in order to catch up on the latest state of the contract without having to sync the entire chain (and optionally prune the old messages)
- chains store data in a content-addressed key-value store (can be any?)
- how does the client-side sandbox work?
- iframe / service worker solution
- state snapshots
- just a proposal, has not been implemented
- clients take local state and send to server as a signed snapshot and there’s also a consensus on what that snapshot should be