Skip to main content
The Wallet Development Kit (WDK) lets you build a custom non-custodial wallet while using OMS wallet infrastructure for identity, sessions, transactions, and data. You own the UI, routing, and product decisions, and you can self-host critical components where required.

​
What you build vs what OMS provides

AreaYou buildOMS provides
UI/UXWallet screens, flows, routing, themingReference components and SDKs
Auth and sessionsLogin UX, flow wiringWaaS enclave (session attestations), Smart Sessions
TransactionsApp-specific flows and UXTransaction API for relaying and sponsorship
DataCustom views and analyticsIndexer for balances, tokens, events, prices
Node accessOptional custom providersBlockchain RPC via Node Gateway
BackendOptional business logicSidekick for secure server-side endpoints

​
Available capabilities

  • Smart Sessions and session attestations for scoped, low-friction execution.
  • Social logins and email with enclave-signed sessions.
  • Cross-chain accounts with a single onchain configuration root covering signers, sessions, and recovery.
  • Timed recovery keys for passphrase-based recovery with a 30-day lockdown.
  • Developer integrations: Web via existing SDKs.
  • Services: Indexer for reads, Transaction API for writes, Node Gateway RPC for raw calls.

​
Integration flow

1

Install and plan hosting

Add the package: pnpm add @0xsequence/wallet-wdk. Decide which components you will self-host (UI, enclave services) versus use hosted.
2

Configure wallet metadata

Set the wallet domain, supported chains, branding, and session policies. Use Builder for environment, keys, and policy management.
3

Wire identity and sessions

Use the WaaS enclave for session attestations. Implement the login and session callback flow, and store session keys securely.
4

Connect services

Read with Indexer, write with Transaction API, and access nodes with Blockchain RPC.
5

Test and ship

Validate Smart Session scopes, recovery paths, and cross-chain actions. Roll out on your domain.

​
Self-hosting options

  • Wallet Infrastructure describes the enclave architecture in full. The enclave service can be self-hosted in your own AWS Nitro Enclave environment if your compliance model requires it.
  • You can run your own Sidekick instance for controlled server-side writes and key custody.
  • Contracts, audits, and deployments are documented in the Sequence technical references.

​
Further reading

Hosted Wallet

Managed deployment option; OMS runs the infrastructure.

Wallet Infrastructure

The enclave-backed auth and session attestation architecture.