Non-custodial Bitcoin DCA for agent treasuries: approve USDT once, stack WBTC on Celo forever.
Non-custodial Bitcoin DCA agent on Celo. Define your plan once — $X every hour/day in BTC — and an on-chain agent buys Bitcoin for you, straight into your own wallet. Funds never leave your wallet between purchases.
GET / service descriptor · GET /api/stats public metrics)| Contract | Address |
|---|---|
| DCAExecutor (verified) | 0xd03ffeBBCaaA8aA21053eEB0EeAde39EFC504189 |
| USDT (token in) | 0x48065fbBE25f71C9282ddf5e1cD6D6A887483D5e |
| WBTC — native bridge (token out) | 0x8aC2901Dd8A1F17a1A4768A6bA4C3751e3995B2D |
| Uniswap V3 SwapRouter02 | 0x5615CDAb10dc425a742d643d949a7F474C01abc4 |
Swaps route through the USDT/WBTC 0.3% Uniswap V3 pool. Protocol fee: 1% + $0.005 flat per execution, with on-chain hard caps (≤1%, ≤$0.05 flat) and a revert if the fee would ever eat the installment.
Agent identity: ERC-8004 #9665 on Celo mainnet (8004scan). Every transaction carries ERC-8021 attribution tags.
flowchart TB
USER["👤 User wallet<br/>(MiniPay / MetaMask / Valora)"]
FE["Frontend — Next.js PWA<br/>(Vercel)"]
subgraph onchain["⛓️ Celo mainnet"]
USDT["USDT (ERC-20)"]
EXEC["DCAExecutor<br/>0xd03f…4189<br/>non-custodial, on-chain limits"]
ROUTER["Uniswap V3 SwapRouter02<br/>USDT/WBTC 0.3% pool"]
TREASURY["Treasury"]
end
subgraph backend["🤖 Agent backend — Vercel"]
KEEPER["Keeper (Vercel Cron, 5 min)<br/>scans PlanCreated events,<br/>checks due plans"]
API["Express API<br/>POST /api/execute<br/>(x402-gated, permissionless)"]
DB[("Supabase<br/>plans · executions")]
TG["Telegram bot<br/>purchase alerts + ops"]
end
FACIL["x402 facilitator<br/>api.x402.celo.org"]
USER -- "① approve(budget) — once" --> USDT
USER -- "② createPlan(amount, interval) — once" --> EXEC
FE -.-> USER
KEEPER -- "discovers plans<br/>(PlanCreated events)" --> EXEC
KEEPER -- "③ pays 0.02 USDT via x402<br/>(EIP-3009 signature)" --> API
API -- "verify + settle" --> FACIL
API -- "④ execute(user, minOut)<br/>+ ERC-8021 attribution tags" --> EXEC
EXEC -- "⑤ transferFrom<br/>(one installment)" --> USDT
EXEC -- "fee 1% + $0.005" --> TREASURY
EXEC -- "⑥ swap USDT→WBTC" --> ROUTER
ROUTER -- "⑦ WBTC straight<br/>to the user's wallet" --> USER
API -- "records execution" --> DB
API -- "🔔 purchase alert" --> TG
DCAExecutor (cap = total plan budget) and creates a plan with on-chain limits (amount per run, minimum interval). Cancelling = one click (cancelPlan or approve(0)).PlanCreated events, and each cycle pays the execution API with an x402 micropayment before calling execute() — so every purchase is also an agent-to-agent payment.amountPerRun or execute before minInterval elapses.| Directory | What it is |
|---|---|
contracts/ | DCAExecutor.sol (Foundry) — 21 tests incl. mainnet fork tests, deploy script |
backend/ | Express API + keeper loop (viem) + x402 middleware + Supabase + Telegram bot |
frontend/ | Next.js PWA (wagmi/viem) — MiniPay auto-connect, plan creation, BTC portfolio |
docs/ | Unit economics, copy review |
PLAN.md | Full architecture plan and piece-by-piece feasibility verification |
Frontend (needs NEXT_PUBLIC_EXECUTOR_ADDRESS, NEXT_PUBLIC_API_URL, NEXT_PUBLIC_ATTRIBUTION_CODE, NEXT_PUBLIC_TELEGRAM_BOT in frontend/.env.local):
cd frontend && pnpm install && pnpm dev # http://localhost:3000
Backend + keeper (Node 22; see backend/src/config.ts for required env vars — executor address, keeper key, Supabase credentials, x402 API key; DB schema in backend/supabase/schema.sql + migrations in the same folder):
cd backend && pnpm install && pnpm dev # API on :8080, keeper ticks every 60s
Locally the keeper runs as an in-process loop (setInterval). Deployed on Vercel the whole Express app is a single function and the keeper is driven by Vercel Cron hitting GET /api/cron/keeper (guarded by CRON_SECRET, schedule in backend/vercel.json) — serverless instances are frozen and reused, so an interval there would fire duplicated, off-schedule ticks. Anything the keeper needs to remember between ticks (alert cooldowns, digest cadence, last scanned block) lives in agent_keeper_state, not in memory.
Contracts:
cd contracts && forge test # unit + Celo mainnet fork tests
forge script script/Deploy.s.sol --rpc-url celo --broadcast --verify --interactives 1
An agent with its own funded wallet can set up a Bitcoin savings plan in two transactions — and so can an agent assisting a human (the web app handles the signing):
claude mcp add comprabtc -- npx -y comprabtc-mcp — tools to check status, create/renew/cancel the plan and track the portfolio, signing with the treasury's own wallet. See mcp/README.md.npx skills add csacanam/comprabtc — covers plan creation (viem), monitoring, budget math, cancelling, and the permissionless x402 execution trigger.GET https://comprabtc-api.vercel.app/ · LLM index: comprabtc.vercel.app/llms.txtOperator wallets (declared):
| Role | Address |
|---|---|
| Keeper (executes plans) | 0x2F6a8283546d28506B312013F77aA38e60AF99B0 |
| Treasury / payTo (receives fees) | 0x6Bd5c303b2ed7E264C1Ce9D3592457292a1F1c43 |
On-chain volume is real user capital. Each plan starts with a user's own approve; the keeper pulls one installment per run via transferFrom and the purchased WBTC goes straight to the user's wallet, where it stays. No custody, no round-trips — the volume is actual BTC purchases with real economic intent.
x402 is internal metering with an open door. The keeper pays x402 on every run, so each x402 payment maps to one real executed purchase — not standalone dust. /api/execute is permissionless and auto-registers plans from on-chain events, so any external agent or human can invoke it and settle their own x402; it is not a closed loop.
execute(), every tx tagged with ERC-8021 attribution./api/execute per run via the Celo x402 facilitator. The endpoint is permissionless — any agent can pay to trigger an execution.MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y comprabtc-mcpMerge 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-csacanam-comprabtc": {
"command": "npx",
"args": [
"-y",
"comprabtc-mcp"
]
}
}
}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 referencecomprabtc-mcpnpmio.github.csacanam/comprabtc 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.