Skip to main content
Embedded wallet architecture
The embedded wallet stack combines four core systems that work together to deliver non-custodial, frictionless wallets for financial products.

Core systems

  • Smart Sessions remove signing friction by sandboxing permissions per app. Users approve a session once; the app executes within that scope automatically. See Smart Sessions.
  • Identity Instrument handles authentication and session attestation inside an AWS Nitro Enclave. Your app never handles raw OAuth tokens or client secrets. See Identity Instrument.
  • Merkleized wallet configuration stores a single onchain root that commits to all signers, sessions, recovery keys, and extensions. Cross-chain by default. See Wallet Configuration.
  • Guard Firewall reviews every transaction against ecosystem policies, threat simulations, and blacklists before allowing onchain execution. See Guard Firewall.

Deployment options

Hosted Wallet

Sequence operates the wallet on your domain with your branding. Control configuration in Builder and launch on a custom domain.

Custom Wallet

Build a wallet with the Wallet Development Kit on top of Sequence infrastructure. Critical components can be self-hosted. Includes native mobile (iOS and Android) via React Native.

Security model

  • Users control their keys. No single party, including Polygon, can unilaterally move funds.
  • Key shards use Shamir’s Secret Sharing distributed across geographically separate remote key holders.
  • Critical signing and identity operations run in TEEs (AWS Nitro Enclaves), hardware-verified and publicly attestable.
  • Contract audits are published in the Sequence technical references.