Trustless spending accounts for AI agents on Solana with on-chain enforced limits.
Trustless spending accounts for AI agents on Solana
AI agents need to spend money autonomously. But giving them wallet access is dangerous:
Agent-side limits don't work - the agent has the keys and can bypass its own rules.
On-chain enforced constraints that agents literally cannot bypass.
┌─────────────────────────────────────────────────────────────────┐
│ CLOAKED AGENT │
├─────────────────────────────────────────────────────────────────┤
│ Owner: Human wallet (full control) │
│ Delegate: AI agent key (can spend within limits) │
│ │
│ Constraints (enforced by Solana program): │
│ ├── max_per_tx: 0.1 SOL │
│ ├── daily_limit: 1 SOL │
│ ├── total_limit: 10 SOL │
│ ├── expires_at: 2026-02-15 │
│ └── token_limits: │
│ └── USDC: 5/tx, 50/day, 500 total │
│ │
│ Even if jailbroken, agent CANNOT exceed these limits. │
└─────────────────────────────────────────────────────────────────┘
Cloaked offers dual-mode privacy:
┌─────────────────────────────────────────────────────────────────┐
│ PRIVACY STACK │
├─────────────────────────────────────────────────────────────────┤
│ ZK Circuits: Noir (Aztec) │
│ Client Prover: Barretenberg (UltraHonk via WASM) │
│ On-chain Verify: Sunspot (Groth16 on Solana) │
│ Hash Function: Poseidon (ZK-friendly) │
│ Anonymous Funding: Privacy Cash (privacycash.org) │
└─────────────────────────────────────────────────────────────────┘
Private Agent Creation:
Wallet signs message → Master secret derived → Commitment generated
On-chain: owner_commitment (hash), NOT wallet address
To manage: Prove knowledge of preimage via ZK proof
| Component | Technology |
|---|---|
| Blockchain | Solana |
| RPC | Helius |
| Smart Contract | Anchor Framework |
| ZK Proofs | Noir + Barretenberg + Sunspot |
| Frontend | Next.js 16, React 19, TypeScript |
| Backend | Express.js (Relayer) |
| AI Integration | MCP (Model Context Protocol) |
| Token Support | USDC |
| x402 Payments | Native support |
Cloaked Program: 3yMjzAeXXc5FZRUrJ1YqP4YMPhPd5bBxHQ6npNSPCUwB
ZK Verifier: G1fDdFA16d199sf6b8zFhRK1NPZiuhuQCwWWVmGBUG3F
{
"mcpServers": {
"cloaked": {
"command": "npx",
"args": ["cloaked-mcp"],
"env": {
"CLOAKED_AGENT_KEY": "your-agent-key-here"
}
}
}
}
The agent can pay in SOL or USDC - pass token: "USDC" to cloak_pay.
npm install @cloakedagent/sdk
import { CloakedAgent } from "@cloakedagent/sdk";
// Load agent (can spend)
const agent = new CloakedAgent(agentKey, rpcUrl);
// Spend within limits
await agent.spend({
destination: recipientPubkey,
amount: 100_000_000 // 0.1 SOL
});
// Spend USDC (requires token enabled on agent)
await agent.spendToken({
destination: recipientPubkey,
mint: USDC_MINT,
amount: 5_000_000 // 5 USDC (6 decimals)
});
cloaked/
├── programs/cloaked/ # Anchor program (constraints, ZK verification)
├── circuits/ # Noir ZK circuits (ownership proofs)
├── app/ # Next.js frontend (dashboard, docs)
├── backend/ # Express relayer (fee payer, ZK ops)
└── sdk/ # TypeScript SDK (@cloakedagent/sdk)
└── src/mcp/ # MCP server (cloaked-mcp binary)
Full documentation available at cloakedagent.com/docs
| Problem | Cloaked Solution |
|---|---|
| AI can drain wallet | On-chain limits can't be bypassed |
| No spending visibility | Real-time dashboard |
| Can't stop runaway agent | Instant freeze |
| Wallet identity exposed | Private mode with ZK proofs |
| Complex integrations | Native x402 support |
Cloaked - Trustless spending accounts for AI agents
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @cloakedagent/sdkMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cloakedagent-cloaked": {
"command": "npx",
"args": [
"-y",
"@cloakedagent/sdk"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@cloakedagent/sdknpmCloaked Agent works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.