SEAL accounts with optional Google Drive backup

Create and receive

On a deployment with a private intent service, choose Create account → Use Google Drive backup. Sign in to Google, choose Create new account, and save a recovery password of at least 12 characters. The app generates your SEAL identity locally and verifies its encrypted backup before showing your payment address. Creating the account does not submit a transaction or require MetaMask, ETH or a signature.

Share that seal. address with a sender. The sender deposits from their wallet and pays deposit gas, then sends a private transfer. Claim it through the intent service, paying the reviewed fee from the incoming assets. A transfer must be large enough to cover its claim fee. You can choose a supported fee asset present in the selected inputs; no prior public wallet balance is required.

Use the account menu to create another account or restore an existing one. Accounts sharing a Google login have independent keys and immutable backup namespaces. On another device, choose the saved account and enter its recovery password. Restoration merges saved history and checks chain state before spending.

Link MetaMask later

Open Settings → Linked recovery wallets → Link a wallet, or Link a wallet in the Google account menu. Connect MetaMask and sign the displayed recovery message. This adds access to the existing SEAL keys: the payment address, balances and saved transfers stay the same. It costs no gas. If that wallet already has its own SEAL account, its separate keys, local files and Drive backups are preserved. Merely connecting a wallet does not link it.

To recover on another device, choose Restore account → Restore from Google Drive, sign in, select the saved SEAL account, then choose Use linked wallet. Connect the previously linked wallet and sign the same message. SEAL verifies the signature, opens its encrypted key capsule and merges the account's saved history. Your recovery password remains an independent alternative. Recovery through a linked wallet uses the encrypted Drive capsule. Funding-wallet connection is separate: any supported EVM wallet can deposit into this same account without linking recovery access or changing its keys.

Each link is an immutable encrypted capsule in Drive, scoped to both the SEAL identity and Ethereum address. The capsule holds the original keys, not a snapshot of balances. A key derived from the verified, canonical EIP-191 signature encrypts it with AES-GCM. The message and key-derivation domain differ from ordinary wallet-based SEAL account unlock. Signatures stay local. Treat a link signature as a recovery secret; it is not a server login.

Link only wallets you control. Linked wallets must reproduce the signature on another device; a change in signing behavior can require the original signing device. There is no unlink/revocation mechanism in this version. Removing a Drive file would not revoke copies of an already decrypted key. Retain your password recovery method and test recovery before relying on a linked wallet.

Availability and deployment

The UI supports claims, combines, reclaims, sends and ordinary withdrawals through the existing Rust intent service. Withdrawals need an explicit Ethereum destination. Deposits can use any connected funding wallet, with direct wallet submission or a supported permit deposit. Swaps and margin use the intent service when configured. The overview always shows Deposit, Swap, Margin, Send, Receive and Withdraw; unavailable deployment integrations explain their status. Terminal vault-share exits are not offered for independent accounts.

While Google backup is enabled, an expired authorization or failed upload preserves the proof and stops submission. Reconnect, or explicitly choose Settings → Google Drive backup → Use local-only storage to keep using the same account without Google. Opting out preserves existing Drive files and keeps encrypted state in the browser. If the intent service is unavailable, keep the account and retry after it recovers. Transfer-file import still works for missing delivery data, but claiming still requires the intent service.

Account names, identifiers, linked Ethereum addresses, creation times and file sizes are visible as Drive metadata. Keys, notes and transaction history are encrypted. Password changes and password resets are not supported in this first version. New exports use a self-contained password-encrypted file: Settings → Advanced → Account state → Export account state. Import that file and enter its password on a clean device without Google, preserving every saved network and the SEAL address. Older seal-account history-only files still require their original key bootstrap or remembered device. Keep downloads current; clearing browser storage loses the local copy.