Encrypted browser storage
The vault implementation encrypts key material before storing it in the browser. Its password, backup, and unlock behavior are part of the custody model.
A wallet in the browser
The browser is the interface.
The Sigil web wallet brings identities, transaction approvals, and network selection into a web application with an encrypted browser-backed vault.
Web WalletIllustrated study
Signer → signature → record
Identity establishes attribution. Trust needs context.
01 / Built for a purpose
Local keys. Explicit approvals.
The web implementation stores an encrypted vault in IndexedDB and exposes an approval flow for applications. A connection identifies the requesting origin; signing remains a separate action that the user should be able to inspect.
An application bridge
The web integration exposes a window.sigil-style provider through an approval window. Application origins and approval responses must stay bound to the request.
Network-aware requests
The network selector determines which RPC endpoint subsequent requests use. A site should not silently change the network or hide an economic network behind a test label.
A shared frontend
The desktop shell reuses the web interface while providing a different native storage backend. Sharing the interface does not make the custody boundaries identical.
The details matterGood questions.
Good questions.
Clear answers.
Does opening the web wallet restore my wallet automatically?
No automatic cross-device key synchronization is implied. Use the supported import or recovery process and verify the identity and network before signing.
Keep exploringOne capability.