The treasury that pays its own way.
BoopBoop turns your Safe into a working-capital engine: idle stablecoins earn on Aave (more engines soon), payments and payroll redeem exactly what’s needed, and every limit is enforced by a smart contract — not by us.
Aavelive
Morphosoon
Sparksoon
FluidsoonRead-only — paste a Safe address, no wallet connection
§ 02 · The problem
Your treasury is a checking account with extra steps.
Idle at 0%.
Payroll hits on the 1st. The other 29 days, six and seven figures sit still — while onchain yields pay 3–8%.
Manual everything.
Batching exists — the ceremony doesn’t. Someone still queues the sweep, chases the third signer, and remembers to redeem before payroll. So the float sits, and payday is still an event.
No control layer.
You can’t safely let an operator — or an AI agent — near the treasury, because “we promise” isn’t a permission system.
§ 03 · Foundations
First, the account you already own.
Every BoopBoop treasury lives in a Safe — the smart-account standard behind much of the onchain treasury world. Not our product. Not a custodian. Yours.
An account that’s a contract.
No username, no password, no ledger at a bank. A Safe is a smart contract on Ethereum that holds assets and enforces its own rules — in public.
Money moves by threshold.
You pick the signers and the number: 3-of-5, 4-of-7. No single key — including ours — can ever move funds alone.
Custody never changes hands.
A Safe has no owner but its signers. BoopBoop is not a signer. We’re a member with a badge — one you can remove.
§ 04 · How it works
One balance. Every dollar working or moving.
See the real number.
USDC and aUSDC become one spendable balance, split by liquidity: available now / near / delayed. No other wallet shows you this.
// wallet + aUSDC → one balance, split by liquidity
Put the float to work.
Activate a mandate: which assets, how much may be lent, how fast. You sign the exact permissions — supply and withdraw only, withdrawals always back to your Safe.
// mandate = signed Roles conditions: supply · withdraw-to-Safe · daily caps
Pay from the earning balance.
$300K payroll with $80K liquid? One transaction redeems the rest from the lending engine and pays all 47 recipients. Scheduled payments run themselves, within limits you set.
// one tx: redeem shortfall from the engine → pay every recipient
Get the statement.
Yield earned, fees taken (from yield — never principal), every transaction, exports your accountants already use.
// yield, fees, every transfer — exportable
Aave is the first engine, not the destination. Morpho, Spark and Fluid board next — same sweep, same revocable role, same onchain limits. When the list grows, nothing about custody changes.
§ 05 · The machinery
Policy as law, by Zodiac.
We author almost nothing new. Your Safe attaches one module: Roles — the open-source permission engine from the Zodiac ecosystem, built by Gnosis Guild and battle-tested across the largest DAOs. Every limit becomes an onchain condition; every operator is a role you granted; everything else gets rejected at the door.
Fig. 1 — the actor model
Your Safe
smart account · your keys · 3-of-5 signers · funds never leave
↓ attaches module
Roles Modifier
Zodiac · open source · onchain
supply USDC · engines
withdraw → this Safe only
within $250K / day
everything else → reject()
↓ within policy
revoke · one click — every BoopBoop permission, gone
You keep the Safe. We hold a role. That’s the whole relationship.
Roles v2 is open source — read the conditions yourself, or point your auditor at them.
§ 06 · Trust
Limits enforced by the contract, not the vendor.
Policy as law.
“This role may supply USDC to Aave, withdraw only to this Safe, deploy at most $250K/day” — each clause is an onchain condition. Auditable by anyone. Changeable only by your signature.
Bounded worst case.
Rate caps and allowlists mean even a fully compromised operator is limited by allowances — not by promises.
The exit strategy is a feature.
One click revokes every BoopBoop permission. If we disappear tomorrow, you lose the automation — never the money.
Fees from yield, visible to the cent.
We earn a capped share of the yield we generate. The fee permission is onchain, like everything else.
§ 07 · Who it's for
DAOs & treasury councils
Idle stables between payrolls; payday as one batch; statements your forum can read.
Web3 companies paying in stablecoins
Runway that earns between payroll days; founders who stop doing treasury ops by hand.
Grant programs & foundations
Scheduled tranches, idle float working between rounds, transparency by default.
§ 08 · Automation
AI with onchain handcuffs.
Your agents (or ours) can read the treasury and draft payments and rebalances — through an MCP server that plugs into the AI assistants you already use. Claude, ChatGPT, whatever’s next: if it speaks MCP, it can draft. What they can never do: authorize anything. Proposals only; the contract enforces.
The AI has opinions. The contract has authority.
§ 09 · Questions
Is BoopBoop custodial?
No. Funds never leave your Safe. We operate as a permission-scoped, instantly revocable role. That’s architecture, not policy.
What if BoopBoop shuts down?
You click revoke (or do nothing — funds are already yours). You keep the Safe, the positions, and the lent balances. You lose the automation.
What can the operator actually do?
Exactly what you signed: e.g. supply/withdraw specific assets on Aave, withdraw only to your Safe, within daily caps. The full permission list is rendered in plain English before activation and lives onchain after.
What about a bug or an exploit?
Every role is rate-capped and allowlisted, so the blast radius is bounded by design. Conservative accounts can add a timelock (24h cooldown) on top.
How do you make money?
A share of the yield we generate — capped onchain, shown on every statement. Pilots run at 0%. We never take a cut of principal, and payments stay free.
Is this an asset manager? Do you have my keys?
No keys, ever, and no discretion: mandates are templates you activate with explicit permissions. We build the automation, you keep the authority.
Which chains and venues?
Five chains — Ethereum, Polygon, Base, Arbitrum and Avalanche. Aave is the first yield engine; Morpho, Spark and Fluid are next.
§ 10 · Rewind
Point it at any Safe. Get the number.
Rewind is our read-only analyzer, live now: paste any Safe address and it rebuilds the treasury’s full token history — then prices, day by day, the yield its idle float could have earned. Aave is priced today; every engine that boards makes the number truer. That’s the gap the product closes.
Stop leaving yield on the table.
Book a 20-minute pilot demo. We’ll paste in your Safe address and show you exactly how much your idle float could have earned last quarter — then pay a test payroll from it.