OverviewPayout FlowDemo & AuditTeamBuild TimelineFAQ & Security
Run the payout flow
DAO AI Treasury Officer

Where DAO treasury decisions become executable payment flows

from contributor records to wallet execution — risk-checked, human-approved, audit-ready

Signed Alice Dev reward20.00 USDC
Parsed contributions.csv4 entries
Signed Charlie QA task10.00 USDC
Blocked Bob Designer15.00 USDC
Signed Indexer query5.00 USDC
Confirmed on Sepoliatx 0xae3f…2c91
Settlement report sealedaudit-2026-06-09
Sync safe thresholds250.00 USDC
Pulled contributor table12 rows
Paid Gas Relayer150.00 MATIC
Signed Alice Dev reward20.00 USDC
Parsed contributions.csv4 entries
Signed Charlie QA task10.00 USDC
Blocked Bob Designer15.00 USDC
Signed Indexer query5.00 USDC
Confirmed on Sepoliatx 0xae3f…2c91
Settlement report sealedaudit-2026-06-09
Sync safe thresholds250.00 USDC
Pulled contributor table12 rows
Paid Gas Relayer150.00 MATIC
Signed Alice Dev reward20.00 USDC
Parsed contributions.csv4 entries
Signed Charlie QA task10.00 USDC
Blocked Bob Designer15.00 USDC
Signed Indexer query5.00 USDC
Confirmed on Sepoliatx 0xae3f…2c91
Settlement report sealedaudit-2026-06-09
Sync safe thresholds250.00 USDC
Pulled contributor table12 rows
Paid Gas Relayer150.00 MATIC
Secured

AI Treasury Agent

Autonomous payment planning, risk validation, and controlled wallet execution for DAO treasuries.

COBO CLIENT ID
CAW-90A81D-CFO
SAFE BOUNDARIES
4 RUN RULES READY
AGENT LOG OVERVIEWACTIVE
[--:--:--] Fetching payroll record list...
[--:--:--] Testing Whitelist validations...
Rule Approved: Alice (20 USDC)
Risk Flagged: Bob (Unverified)
[--:--:--] Synthesized payment queue created. Waiting human check.
Web3 Trust Stack

Web3 Trusted Infrastructure Integration Map

AgentCFO weaves multi-sig suites, automation modules and Cobo HSM into a closed-loop trusted capital allocation network, granting Agent payment sovereignty under control.

Hover or move mouse to explore underlying trusted protocols...

CAW
CAW
Gnosis
Gnosis
MetaMask
MetaMask
Sepolia
Sepolia
Sablier
Sablier
Drizzle
Drizzle
Framer
Framer
GitHub
GitHub
Cobo
Interactive Split

One budget card. Split into targeted payouts.

Scroll down to see how AgentCFO breaks a single master budget into individual contributor cards.

DEVELOPER BOUNTY

Alice Dev Rewards

ACTIVE
Spent: $20Limit: $50
RECIPIENT: 0xAlice123...12
Sepolia100% Secure
AUDIT SERVICES

Charlie Security Pool

LIMITED
Spent: $10Limit: $30
RECIPIENT: 0xCharlie123...ff
Whitelisted
INFRASTRUCTURE

Indexer Subscriptions

METERED
Spent: $5Limit: $10
RECIPIENT: 0xDataAPI12...de
Auto Relayed
COBO CLIENT MASTER

AgentCFO Elite

•••• •••• •••• 90A8
EXPIRE: 06/2030
SECURE RUN STATE
The 5-Stage Pipeline

From contributionto audit trail.

One visible loop, five stages. Each one tells a story — from raw signal to on-chain proof.

01Records
02Risk
03Approval
04Wallet
05Audit
01
Stage 01 · Records
Contribution records
become payout plans.

Every payout starts with a signal. A GitHub issue closed, a Notion row filled, a CSV uploaded — AgentCFO reads them all and turns messy contribution records into structured payment plans.

Contributors don't file expense reports. They write code, design posters, host AMAs. AgentCFO meets them where they work — pulling structured signals from the tools they already use, not adding another form to fill.
Each contribution is automatically tagged with a reason, a recipient, and an amount. No manual data entry. No forgotten line items. Just raw signals transformed into a payment plan where every line has a purpose.
CSV / JSON upload
Drop a spreadsheet, get a structured plan
GitHub Issues
Closed issues become payable tasks automatically
Notion database
Sync contributor rows without leaving Notion
records.log
PAYMENT PLAN — 4 entries
alice.eth    20 USDC  wrote event recap
bob.eth      15 USDC  designed poster
charlie.eth  10 USDC  hosted AMA
data-api      5 USDC  subscription · jun
Next stage
03
Stage 03 · Approval
A human approves
the final move — always.

No autonomous transfers. Ever. A real person reviews the cleared queue, sees exactly what's being paid and why, and clicks Approve & Execute. Blocked items stay blocked — with their reasons right there.

AI can draft the plan, run the risk check, and prepare the execution — but it cannot sign the transaction. Human-in-the-loop isn't a setting you toggle off. It's the architecture.
The approval view shows every line item with its risk status, reason, and amount. The operator sees the full picture in one screen. No spreadsheets, no email threads, no "wait, who approved this?"
One-click approve
Clear queue, single action
Blocked visibility
Rejected items stay visible with reasons
Audit trail
Every approval logged with approver identity
Batch execution
Approve multiple payments in one go
approval.log
APPROVAL QUEUE — 3 approved · 1 blocked
APPROVED:
  alice.eth    20 USDC  ✓
  charlie.eth  10 USDC  ✓
  data-api      5 USDC  ✓
BLOCKED:
  bob.eth      15 USDC  ✗ not in whitelist
 
[ Approve & Execute · 35 USDC ]
Next stage
02
Stage 02 · Risk
Five policy gates run
before any wallet call.

Before any wallet opens, five policy gates run in sequence. Budget cap, whitelist, single-payment limit, token policy, duplicate guard — each gate gets a vote. One "no" and the payment stops cold.

The risk engine doesn't guess. It applies deterministic rules to every line item: Is the total within budget? Is the recipient on the whitelist? Does any single payment exceed the limit? Is the token allowed? Has this exact payment been requested before?
Blocked items never reach the execution queue. They stay visible with their reasons attached — so contributors know why, and operators know what to fix. Transparency is the default, not a feature toggle.
Budget cap
Monthly spending limits enforced per DAO
Whitelist
Only approved recipients receive funds
Single limit
Max amount per transaction, configurable
Token policy
Restrict to specific tokens and chains
Duplicate guard
Catch accidental double payments
risk.log
RISK CHECK — 5 gates · 4 pass · 1 block
✓ Budget cap      50 USDC monthly · 50 used
✓ Whitelist       alice / charlie / data-api
✓ Single limit    ≤ 25 USDC · max 20
✓ Token policy    USDC · sepolia testnet
✗ Duplicate guard bob.eth not in whitelist
Next stage
04
Stage 04 · Wallet
Cobo Agentic Wallet,
inside a policy boundary.

AgentCFO never holds keys. Every approved payment routes through Cobo Agentic Wallet — a policy-bound agent wallet that enforces the rules at the protocol level, not just in the UI.

The wallet is configured with the same rules as the risk engine: same whitelist, same budget, same token restrictions. Even if something slips through the app layer, the wallet catches it. Defense in depth.
Every transfer returns a real transaction hash on Sepolia testnet. You can trace it, verify it, audit it. The demo uses testnet funds — zero real money at risk — but the flow is identical to mainnet.
Cobo Agentic Wallet
Policy-enforced agent wallet
Testnet execution
Real tx hashes, zero real funds at risk
Configurable policy
Wallet rules synced with risk engine
Tx hash traceability
Every payment on-chain and auditable
wallet.log
WALLET EXECUTION — 3 transfers
0xae3f...2c91  → alice.eth    20 USDC  ✓ confirmed
0x8b21...4ee0  → charlie.eth  10 USDC  ✓ confirmed
0x4c7d...91b3  → data-api      5 USDC  ✓ confirmed
 
Policy: testnet-simulated · agent-wallet-bound
Next stage
05
Stage 05 · Audit
Every run writes a
settlement report.

Every run produces a settlement report — not as an afterthought, but as the natural output of the pipeline. Tx hash, recipient, risk result, approver, blocked reasons: everything in one exportable document.

The report isn't a spreadsheet you compile at month-end. It's generated automatically at the moment of execution — with every decision, every check, every approval logged in real time. Audit-grade by default.
Export as PDF or JSON. Share with accountants, auditors, or the community. The entire payment history is transparent, traceable, and tamper-evident because every hash lives on-chain.
Auto-generated
Report created at execution time
Exportable
PDF or JSON output
On-chain proof
Every tx hash included and verifiable
Full traceability
From contribution record to settlement
audit.log
SETTLEMENT REPORT — audit-2026-06-09
Approved: 3    Blocked: 1    Settled: 35 USDC
 
ON-CHAIN PROOF:
0xae3f...2c91  ✓
0x8b21...4ee0  ✓
0x4c7d...91b3  ✓
 
RISK: 4 pass · 1 block
APPROVER: human
Move funds with confidence

Every payout is checked, approved, and reported.

AgentCFO turns messy contribution records into payout plans, blocks risky transfers, waits for human approval, and produces an audit-ready settlement report.

View audit report

Scroll down to see the 5-stage workflow in action.

testnet-simulated·no real funds·deterministic demo
agentcfo — demo.mp4
REC
records
plan
risk
approve
execute
audit
1 payment blocked
bob.eth · not in whitelist
✓3 executed · 35 USDC settled

AgentCFO · DAO AI Treasury Officer · Cobo Agentic Commerce · Mock demo, no real transactions

v0.1 · 2026

Built by theTEAM.

Five roles, one mentor, one controlled money pipeline.

Mentor
✦
ZanyK

Last year's hackathon veteran, guiding the team through the chaos

Delivery & Ops
欢

Coordination, pitch and final delivery

Backend & Agent
九九八乂

FastAPI payment plans and risk engine

Frontend
threetwoa

Product UI and mock demo mode

Contracts & CAW
purple sun

Cobo Agentic Wallet testnet execution

Design & Content
呱呱

Slides, video and visual assets

2026-06-08 · Phase 0

Kickoff

Repo created, team roles, backend P0 APIs and frontend scaffold

2026-06-09 · Phase 1

Core Integration

P0 API integration, CAW testnet execution, Vercel deploy

2026-06-10 · Phase 2

Polish Sprint

Landing visual polish, Console component refinement, demo rehearsal

2026-06-12 · Phase 3

Freeze & Submit

Feature freeze, final rehearsal, submission package

Kickoff
01Phase 0Kickoff
Core Integration
02Phase 1Core Integration
Polish Sprint
03Phase 2Polish Sprint
Freeze & Submit
04Phase 3Freeze & Submit

Frequently Queried Specifications

Understand the core mechanics protecting your DAO Treasury against rogue behaviors through cryptographic hardware limits.

01

Is my corporate money secure under AI automated operations?

SECURED
> expanded
$

Absolutely. Crucially, the AI Agent (AgentCFO) NEVER holds your private keys. It only reads contribution metrics and signs raw intent data packages under pre-approved, non-custodial boundaries defined strictly in your hardware and policy config.

ADDR:0x000 · OFF:0x000
┌─ PKCS#11 · FIPS 140-2 L3 · SECP256k1 · CAW-BUS v2.1 ─┐
#HSM-CAW Node Monitor█
[PROBE::ON]TLS1.3
shell@hsm-caw:~$ > await probe input_
REG[0x00]HSM SIGNER LATENCY0.12ms :: FAST
REG[0x01]MULTI-SIG QUORUM2/3 :: REGISTERED
REG[0x02]VAULT ENCRYPTIONAES-256-GCM
REG[0x03]ACTIVE SAFE BOUNDS4 :: ACTIVE
CAW Hardware signing load:14%CPU
0x000xFF
SHA256::a3f8c2e1 · 9b4d7f0a · e2c8915b · 7f3a0d4e · c8b1e6f2 · 4a9d2c7b · f0e3b8a1 · 6c2f9d4e ·
[OK] COBO_CLIENT::INTGEnter Console
└─ NODE_ID: CAW-90A81D-CFO · UPTIME: 99.97% ─┘