use-developer-controlled-wallets

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

1|Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Lightupwrld/Cycuxio --skill use-developer-controlled-wallets-lightupwrld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-developer-controlled-wallets
Source: https://github.com/Lightupwrld/Cycuxio/tree/main/.agents/skills/use-developer-controlled-wallets
Command: npx skills add https://github.com/Lightupwrld/Cycuxio --skill use-developer-controlled-wallets-lightupwrld

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 agent through Circle's 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, NEAR, and Arc, with entity secret registration handled via the SDK. - Transactions & Signing: Transfer tokens, check balances, estimate fees, accelerate or cancel pending transactions, sign EIP-191 messages, EIP-712 typed data, and raw transactions. - Contract Execution & Management: Execute smart contract functions via ABI signatures or raw calldata, derive wallets to new chains, and track asynchronous transaction states through polling or webhooks. - Use Case: A developer building a fintech backend asks the agent to create two testnet wallets, fund one from a faucet, transfer USDC between them, and poll the transaction until it reaches a terminal state. ## Quick Start Use the developer-controlled wallets skill to create a wallet set and two SCA wallets on Polygon Amoy testnet, then transfer 0.01 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 the wallet set ID, an account type (EOA or SCA), target blockchains, and a count. The SDK returns wallet objects containing IDs and addresses for subsequent operations.

How do I transfer tokens between Circle developer-controlled wallets?

Use getWalletTokenBalance to find the token address, then call createTransaction with the source wallet ID, token address, destination address, and amount. Poll getTransaction until the state reaches COMPLETE, FAILED, DENIED, or CANCELLED.

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

EOA wallets are externally owned accounts with no creation fees, higher outbound TPS, and support for all chains including 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.

Does the Circle wallets SDK support signing EIP-712 typed data?

Yes, the signTypedData method signs EIP-712 structured data on EVM-compatible chains, useful for permit approvals and off-chain order signing. The SDK also supports signMessage for EIP-191, signTransaction for raw transactions, and signDelegateAction for NEAR.

Why is my Circle transaction stuck in the SENT state?

A transaction in SENT or STUCK state has fee parameters below the current network requirement. Use accelerateTransaction to resubmit with higher gas, or cancelTransaction to attempt cancellation, noting that cancellation is best-effort once submitted on-chain.

Can I register the entity secret programmatically for production wallets?

The registerEntitySecretCiphertext SDK method registers the secret and downloads a recovery file, but on mainnet the developer must generate, register, and store the secret and recovery file themselves. Never commit the entity secret or recovery file to version control.