Key features
User retains custody
Users control their keys via passkeys (WebAuthn). Keys stay on the user’s
device; your app never holds them. Optional
recovery lets users restore access with
a recovery key.
Gasless transactions
Use Gas Station to sponsor network fees so users
don’t need native tokens. Set paymaster policies in the Circle Console and
pass
paymaster: true when sending user operations.Batch and parallel execution
Send multiple operations in one user op for better UX and efficiency. Use 2D
nonces to run independent transactions in parallel. See Modular Wallet
Operations for details.
What you can build
Use modular wallets when you want user-owned keys with a simple onboarding flow. Common use cases:Consumer apps with passkeys
Consumer apps with passkeys
Onboard users with biometrics or device unlock, with no seed phrases or
passwords. Users sign transactions from your app; you orchestrate flows with
the modular wallets SDK and never hold keys.
Gasless and batch flows
Gasless and batch flows
Sponsor gas so users don’t need native tokens. Combine multiple actions (for
example approve and transfer) in one user operation, or run independent
operations in parallel with 2D nonces.
Programmability through modules
Programmability through modules
Add modules to smart accounts for allowlisted
transfers or custom logic.
Third-party wallet connection
Third-party wallet connection
Expose modular wallets as an EIP-1193 provider so other Web3 SDKs (for
example Web3.js) can connect to Circle Smart Accounts. See Modular Wallet
Operations for the
pattern.
Get started
Passkey and Smart Account
Understand passkey as signer and the Circle Smart Account flow before you
run the quickstart.
Create a Modular Wallet
Set up the SDK, register with a passkey, create a smart account, and send a
gasless user operation.