Welcome to Wallet API v2

The v2 Wallet API is currently in Alpha. Reach out in the #wallet-api channel of the CDP Discord for any questions.

Overview

The v2 Wallet API enables developers to programmatically create, manage, and use crypto wallets while CDP secures the private keys and handles complex infrastructure management. Developers can access the v2 Wallet API through either the CDP SDK or CDP’s REST endpoints.

Compared to v1, the v2 Wallet API is designed for developers, offering the following:

Feature	v1 Wallet API 🔴	v2 Wallet API 🟢
Security management	Complex	Easy
Private key security	Developer-managed	Secured in AWS Nitro Enclave TEE
Network support	EVM only	EVM and Solana
Authentication	One secret per account	Single secret for all accounts
Wallet scope	Single EVM network	Multiple EVM networks
Viem compatibility	✅	✅
Gas sponsorship (via EIP-4337)	➖	✅
Spend permissions (via EIP-4337)	➖	✅

Secure key management

Instead of securing your own private keys or needing to set up MPC keyshare infrastructure, v2 Wallets greatly simplify crypto key management by signing all of your transactions within a Trusted Execution Environment (TEE).

The TEE ensures that sensitive cryptographic material is never exposed to the outside world (not even to Coinbase!).

The Trusted Execution Environment (TEE) provides a secure environment for signing your transactions, and ensures that your private keys are never exposed to Coinbase, AWS, or the outside world. Read more in our Security documentation.

Single secret authentication

Previously, developers needed a separate secret per account to authenticate, and this was only supported for EVM networks.

In v2, authentication is handled using a Wallet Secret - a single secret that grants access to your accounts across both the EVM and Solana ecosystems. This secret is used for sensitive wallet operations, such as account creation and transaction signing.

Viem compatibility

EVM Accounts in v2 Wallet API can be used directly with viem as custom accounts. This allows you to leverage viem’s client abstraction while using CDP Wallets as the signer. Refer to the quickstart for an example of using CDP Wallets with viem.

EIP-4337 support

The v2 Wallet API supports EIP-4337 Smart Accounts, which provide the following advanced features via smart contract calls:

• Gas sponsorship
• Transaction batching
• Spend permissions

More on Smart Accounts

Also known as a smart contract account, a Smart Account is an account abstraction powered by a smart contract instead of an externally owned account (EOA).

With a CDP Smart Account, you can:

• Sponsor gas fees so users don’t need ETH to interact onchain
• Batch multiple requests in a single transaction
• Enforce custom access policies, such as spend limits or time-based rules

Implemented using the EIP-4337 standard, a Smart Account can function like a “normal” wallet account, enhancing usability, security, and flexibility for developers and end-users.

Expanded Wallet scope

Instead of an EVM-based wallet being scoped to a single EVM network, EVM-based wallets in v2 are compatible across all EVM chains.

Support and feedback

Join #wallet-api in the CDP Discord to access FAQs, schedule project discussions, and connect with other developers. We welcome your feedback and suggestions for improvement.

What to read next

• Quickstart: Create onchain accounts and send funds within minutes using the v2 Wallet API.
• Security: Learn about new security features and how the v2 Wallet API protects your private keys.
• Accounts: Descriptions of v2-supported account types and how to use them.
• API Reference: Full API reference for the v2 Wallet API.