use-developer-controlled-wallets

Create and manage Circle developer-controlled wallets for transfers, signing, and contract execution.

3|1|Updated May 17, 2026
One-click install
npx skills add https://github.com/levantuy/arc-quantum --skill use-developer-controlled-wallets-levantuy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-developer-controlled-wallets
Source: https://github.com/levantuy/arc-quantum/tree/main/.agents/skills/use-developer-controlled-wallets
Command: npx skills add https://github.com/levantuy/arc-quantum --skill use-developer-controlled-wallets-levantuy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @circle-fin/developer-controlled-wallets, and includes references (resource) components.

What problem does it solve? Building applications that custody crypto wallets on behalf of end users requires handling key management, transaction lifecycle tracking, gas fees, and multi-chain support. This Skill guides an AI through the Circle developer-controlled wallets SDK so wallet creation, token transfers, message signing, and smart contract execution are implemented correctly and securely. ## Core Features & Use Cases - Wallet Provisioning: Create wallet sets and EOA or SCA wallets across EVM chains, Solana, Aptos, and NEAR, with entity secret registration guidance. - Transactions & Balances: Check token balances, transfer tokens, estimate fees, and accelerate or cancel pending transactions while polling the asynchronous transaction state machine. - Signing & Contract Execution: Sign EIP-191 messages, EIP-712 typed data, and raw transactions, plus execute smart contracts via ABI signatures or raw calldata. - Use Case: A fintech backend needs to custody USDC wallets for users. Use this Skill to register an entity secret, create a wallet set on Polygon Amoy testnet, fund wallets from a faucet, and execute a confirmed USDC transfer. ## Quick Start Ask the AI to create a developer-controlled wallet set and two testnet wallets using the Circle developer-controlled wallets SDK, then transfer a small amount of testnet USDC between them.

Frequently Asked Questions about use-developer-controlled-wallets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a developer-controlled wallet with the Circle SDK?

Call createWalletSet to create a wallet set, then call createWallets with an accountType (EOA or SCA), a list of blockchains, a count, and the wallet set ID. You must first register an entity secret and initialize the client with initiateDeveloperControlledWalletsClient.

What is the difference between EOA and SCA wallets on Circle?

EOA wallets are the default with no creation fees, higher outbound TPS, and support for all EVM chains plus Solana, Aptos, and NEAR, but require native tokens for gas. SCA wallets are ERC-4337 smart accounts supporting gas sponsorship and batching, but are EVM-only and costly on Ethereum mainnet.

How do I check a Circle wallet's token balance?

Use getWalletTokenBalance with the wallet ID to retrieve token balances and token addresses. Do not use getWallet or getWallets for balances, since those endpoints never return balance data.

Does the Circle wallets SDK support signing typed data and raw transactions?

Yes. The SDK supports signMessage for EIP-191 and chain-native signing, signTypedData for EIP-712 structured data on EVM chains, signTransaction for raw transactions on Solana, NEAR, and EVM, and signDelegateAction for NEAR meta-transactions.

Why is my Circle transaction stuck and how do I fix it?

A transaction enters the STUCK state when its fee parameters fall below the blockchain's required fee. Use accelerateTransaction to resubmit with higher gas or cancelTransaction to attempt cancellation, and poll getTransaction until a terminal state like COMPLETE or FAILED is reached.

When should I use user-controlled wallets instead of developer-controlled wallets?

Use user-controlled wallets when end users should custody their own keys through social login, email OTP, or PIN authentication. Developer-controlled wallets fit applications that retain full custody of keys on behalf of users via the entity secret model.