| name | use-circle-wallets |
| description | Choose and implement the right Circle wallet type for your application. Compares developer-controlled, user-controlled, and modular (passkey) wallets across custody model, key management, account types, blockchain support, and use cases. Use whenever blockchain wallet integrations are required for onchain application development. Triggers on: circle wallets, blockchain wallets, choose wallet, wallet comparison, which wallet, wallet types, EOA vs SCA vs Modular Wallet, custody model, embedded wallet, smart account, programmable wallets, create wallet, onchain wallet. |
Overview
Circle offers three wallet types -- developer-controlled, user-controlled, and modular -- each with different custody models, account types, key management, and capabilities. This skill helps you pick the right one.
Quick Comparison
| Developer-Controlled | User-Controlled | Modular (Passkey) |
|---|
| Custody | Developer | User | User |
| Auth | API key + entity secret (backend) | Social login / email OTP / PIN | Passkey (WebAuthn) |
| Account types | EOA, SCA | EOA, SCA | Modular Wallet SCA (ERC-6900) |
| Gas sponsorship | SCA via Circle Paymaster | SCA via Circle Paymaster | Circle Paymaster or third-party paymaster |
| Custom modules | No | No | Yes |
| Architecture | Backend SDK only | Backend + frontend SDKs | Frontend SDK only |
Decision Guide
For the latest supported account types on different blockchains: https://developers.circle.com/wallets/account-types
For the latest supported features on different blockchains: https://developers.circle.com/wallets/supported-blockchains
Step 1 -- Who controls the keys / who is the custodian?
- Developer controls -> Developer-controlled wallets -> Step 3
- End user controls -> Step 2
Step 2 -- Auth method?
- Passkey (WebAuthn biometric) with extensible modules -> Modular wallets -> Step 4
- Social login, email OTP, or PIN -> User-controlled wallets -> Step 3
Step 3 -- Account type?
- Solana, Aptos, or NEAR -> EOA (only option)
- Ethereum mainnet -> EOA (SCA gas costs prohibitive, Modular Wallet not supported)
- L2 (Arbitrum, Base, Polygon, Optimism, etc.) -> EOA if max TPS needed; SCA if gas sponsorship or batching needed; Modular Wallet if passkey or other modular plugins needed
Step 4 -- Chain check (Modular wallets)
- Supported: Arbitrum, Avalanche, Base, Monad, Optimism, Polygon, Unichain
- NOT supported: Ethereum, Solana, Aptos, NEAR. Fall back to user-controlled wallets with SCA.
Example Scenarios
| Scenario | Decision | Skill |
|---|
| Payment backend, programmatic payouts, high TPS | Developer-controlled + EOA | use-developer-controlled-wallets |
| Consumer app with Google/Apple login, gasless UX | User-controlled + SCA on L2 | use-user-controlled-wallets |
| DeFi app with biometric auth, custom modules | Modular Wallet on L2 | use-modular-wallets |
| NFT marketplace on Ethereum L1 | User-controlled + EOA | use-user-controlled-wallets |
| AI agent, autonomous multi-chain transactions | Developer-controlled + EOA | use-developer-controlled-wallets |
Implementation Patterns
Once a wallet type has been determined, TRIGGER the corresponding skill:
- Developer-controlled ->
use-developer-controlled-wallets skill
- User-controlled ->
use-user-controlled-wallets skill
- Modular (Passkey) ->
use-modular-wallets skill
Strict Rules
- ALWAYS select the wallet type before starting implementation using the comparison table and decision guide above.
- ALWAYS use EOA on Ethereum mainnet (SCA gas prohibitive, Modular Wallet not supported) and on Solana, Aptos, NEAR (SCA/Modular Wallet not available).
- ALWAYS prefer SCA or Modular Wallet on L2 chains (Arbitrum, Base, Polygon, Optimism, etc.) when gas sponsorship or batch operations are needed.
- NEVER mix wallet types in a single user flow -- pick one and use its corresponding skill.
- ALWAYS delegate to the specific wallet skill (
use-developer-controlled-wallets, use-user-controlled-wallets, or use-modular-wallets) for implementation.
Reference Links
DISCLAIMER: This skill is provided "as is" without warranties, is subject to the Circle Developer Terms, and output generated may contain errors and/or include fee configuration options (including fees directed to Circle); additional details are in the repository README.
