Comprabtc

CompraBTC

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.

• Live app: https://comprabtc.vercel.app (works in MiniPay and any injected wallet)
• Agent API: https://comprabtc-api.vercel.app (GET / service descriptor · GET /api/stats public metrics)
• Built for the Celo Agentic Payments & DeFAI Hackathon — leaderboard

Deployed contracts (Celo mainnet, chain 42220)

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.

How it works

flowchart TB

USER["👤 User wallet (MiniPay / MetaMask / Valora)"] FE["Frontend — Next.js PWA (Vercel)"]

subgraph onchain["⛓️ Celo mainnet"] USDT["USDT (ERC-20)"] EXEC["DCAExecutor 0xd03f…4189 non-custodial, on-chain limits"] ROUTER["Uniswap V3 SwapRouter02 USDT/WBTC 0.3% pool"] TREASURY["Treasury"] end

subgraph backend["🤖 Agent backend — Vercel"] KEEPER["Keeper (Vercel Cron, 5 min) scans PlanCreated events, checks due plans"] API["Express API POST /api/execute (x402-gated, permissionless)"] DB[("Supabase plans · executions")] TG["Telegram bot purchase alerts + ops"] end

FACIL["x402 facilitator api.x402.celo.org"]

USER -- "① approve(budget) — once" --> USDT USER -- "② createPlan(amount, interval) — once" --> EXEC FE -.-> USER KEEPER -- "discovers plans (PlanCreated events)" --> EXEC KEEPER -- "③ pays 0.02 USDT via x402 (EIP-3009 signature)" --> API API -- "verify + settle" --> FACIL API -- "④ execute(user, minOut)

• ERC-8021 attribution tags" --> EXEC EXEC -- "⑤ transferFrom

(one installment)" --> USDT EXEC -- "fee 1% + $0.005" --> TREASURY EXEC -- "⑥ swap USDT→WBTC" --> ROUTER ROUTER -- "⑦ WBTC straight to the user's wallet" --> USER API -- "records execution" --> DB API -- "🔔 purchase alert" --> TG

1. The user approves USDT to 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)).
2. The keeper discovers plans from 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.
3. On-chain limits mean even a compromised keeper can't overcharge: it can never pull more than amountPerRun or execute before minInterval elapses.
4. Users get Telegram alerts on every purchase (link from Settings in the app).

Repository layout

Running locally

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

For AI agents

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):

• MCP server (treasury DCA): 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.
• Agent skill: npx skills add csacanam/comprabtc — covers plan creation (viem), monitoring, budget math, cancelling, and the permissionless x402 execution trigger.
• Service descriptor (machine-readable how-to): GET https://comprabtc-api.vercel.app/ · LLM index: comprabtc.vercel.app/llms.txt
• Agent identity: ERC-8004 #9665 on Celo — metadata · 8004scan

Transparency

Operator wallets (declared):

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.

Hackathon tracks

• Track 1 — on-chain revenue: protocol fee charged inside execute(), every tx tagged with ERC-8021 attribution.
• Track 2 — x402 payments: the keeper pays /api/execute per run via the Celo x402 facilitator. The endpoint is permissionless — any agent can pay to trigger an execution.
• Track 4 — Aigora: agent registered on the Aigora marketplace (#395) + feedback PRs at trionlabs/aigora-skills.

License

MIT