circle-wallet

**Quick judgement** This skill is a strong, pragmatic choice for giving OpenClaw agents real USDC wallet capabilities on top of Circle’s Developer-Controlled Wallets, especially in sandbox/testnet or carefully controlled mainnet environments. It focuses on core wallet operations (create, list, balance, send) across many chains and integrates cleanly with OpenClaw’s filesystem and tooling model. **What it’s good for** - Multi-chain USDC agents that need to create wallets, check balances, and send funds on 21 supported chains (mainnets + testnets). - Sandbox/testnet agents for demos, prototyping, and education, using `drip` to obtain testnet USDC. - Agent-driven wallet management where a CLI-oriented interface is acceptable and tools can be orchestrated carefully. **Key strengths** - Tight OpenClaw alignment: install and config paths match typical OpenClaw conventions, making integration straightforward. - Good coverage of basic wallet operations: setup, configure, chain listing, wallet creation, balances, sends, and testnet drip. - Multi-chain abstraction: agents don’t need to manage chain selection manually; `send` infers the correct chain from the selected wallet. - Gas-free transaction support via Circle Gas Station simplifies UX and operational overhead. **Main risks / limitations** - **Real-funds risk:** On mainnets, any agent misbehavior or prompt injection could cause irreversible USDC loss. You should add higher-level safety policies (human confirmations, spending limits, allowlists) outside this skill. - **Security of credentials:** API keys and entity secrets are stored locally under `~/.openclaw/circle-wallet`. You must ensure file-system and host security; there is no mention of hardware-backed or encrypted key storage. - **Environment confusion:** Sandbox vs production is controlled by `CIRCLE_ENV`; misconfiguration could result in operations on mainnet when testnet was intended. - **Not an official Circle product:** The repo is a personal, MIT-licensed project and explicitly “not officially endorsed by Circle,” so you should not treat it as vendor-supported infrastructure. **Recommended usage scenarios** Use this skill when: - You want an OpenClaw agent to manage USDC wallets and perform simple wallet operations, especially in **sandbox/testnet** for safety. - You’re building prototypes, internal tools, or educational agents where multi-chain USDC behavior is important but full enterprise-grade controls can be layered externally. - You have a secure runtime for OpenClaw agents and can implement your own **governance and guardrails** (confirmation prompts, spending limits, allowlisted addresses) around any mainnet usage. Avoid or limit this skill when: - You cannot adequately secure API keys or host environment. - You need strict compliance, auditability, or formally supported enterprise integrations directly from Circle without relying on community tooling.