
What you get
- Your domain and brand: run at
wallet.yourdomain.comwith your theme, logo, and copy. - Smart Sessions: scoped, sandboxed permissions per app to reduce signing prompts and protect users.
- Passkeys and social logins: passkeys plus email and social logins; external wallets can be linked.
- Attested identity: sessions are signed by an enclave-based Identity Instrument. Apps never handle social auth keys.
- Cross-chain by default: multi-chain accounts, balances, and transactions.
- Admin in Builder: configure chains, branding, session policies, and integrations from an ecosystem admin panel.
- Production ops: Sequence runs the wallet stack, Identity Instrument, monitoring, and updates.
Smart Sessions are central to wallet safety and UX. See Smart Sessions for the full breakdown.
How it works
Configure your ecosystem
In Builder, set your wallet domain, branding, supported chains, and initial policies.
Set up identity and auth
Enable passkeys and connect your identity providers. Session attestations are issued by the enclave-based Identity Instrument.
Define session policies
Create Smart Session scopes for your apps (methods, limits, timeouts) and register app origins.
Security and reliability
- Non-custodial: users control their keys. Timed recovery keys can be enabled for worst-case scenarios.
- Hardware isolation: critical signing and identity attestations use TEEs (AWS Nitro Enclaves).
- Key Machine: only the latest wallet configuration is accepted onchain, supporting safe key rotation.
- Audited architecture: see Sequence technical references for contracts, audits, and deployments.
Who it is for
Financial products that want a branded wallet, fast time to market, and managed operations without building wallet infrastructure from scratch.Further reading
Smart Sessions
How session permissions work and how to configure them.
Wallet Architecture
Full breakdown of the identity, session, and configuration systems.