use-developer-controlled-wallets

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

1|Updated Sep 4, 2025
One-click install
npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill use-developer-controlled-wallets-fuzzystodd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-developer-controlled-wallets
Source: https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO/tree/main/skills/use-developer-controlled-wallets
Command: npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill use-developer-controlled-wallets-fuzzystodd

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 secure key management, transaction lifecycle handling, and multi-chain support. This Skill guides you through Circle's developer-controlled wallets SDK so you can create wallets, move tokens, sign messages, and execute smart contracts without managing raw private keys yourself. ## Core Features & Use Cases - Wallet Creation & Management: Create wallet sets and wallets across EVM chains, Solana, Aptos, NEAR, and Arc, with support for both EOA and SCA account types, upgrades, and cross-chain derivation. - Transfers, Signing & Contract Execution: Send tokens, check balances, estimate fees, sign EIP-191/EIP-712 messages, and execute smart contract functions via ABI or raw calldata. - Transaction Lifecycle Handling: Track asynchronous transactions through states like INITIATED, CONFIRMED, and COMPLETE using polling or webhook notifications. - Use Case: A fintech app wants to give each user a custodial USDC wallet on Polygon. Use this Skill to register an entity secret, create a wallet set, generate wallets, and process deposits and withdrawals programmatically. ## Quick Start Ask the assistant to set up the Circle developer-controlled wallets SDK and create a testnet wallet using your API key and entity secret.

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 Circle?▼

Install the @circle-fin/developer-controlled-wallets package, initialize the client with your API key and entity secret, then call createWalletSet followed by createWallets with a UUID v4 idempotency key. You must register your entity secret with Circle before making API calls.

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 contract accounts supporting gas sponsorship and batching, but are EVM-only and costly on Ethereum mainnet.

Which blockchains does Circle developer-controlled wallets support?▼

Supported chains include EVM networks such as Ethereum, Polygon, Avalanche, Arbitrum, Base, Monad, Optimism, and Unichain, plus Solana, Aptos, NEAR, and Arc. On Arc, the gas asset is USDC rather than a separate native token.

How do I track the status of a Circle wallet transaction?▼

Poll getTransaction with the transaction ID until it reaches a terminal state: COMPLETE, FAILED, DENIED, or CANCELLED. Circle recommends subscribing to webhook notifications instead, which push an event when the transaction reaches a terminal state.

Why can't I get wallet balances from getWallet or getWallets?▼

The getWallet and getWallets endpoints never return balance data. You must use the dedicated balance approach described in the balance and transfer reference, which queries token balances separately from wallet metadata.

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 manage keys on behalf of users through a server-side entity secret.