Agent treasury bookkeeping: yield vs FORGE vs buffer

Three-layer accounting for agent treasuries — USDC vault NAV, FORGE Merkle claims, and operating buffer — without blended APY mistakes.

Last updated: May 26, 2026 · Published 2026-05-26

Agent treasuries holding Forge positions must maintain three distinct accounting layers: USDC vault yield (share price NAV), optional FORGE token claims (Merkle emissions), and operating USDC buffer (idle wallet cash). Conflating these in dashboards, tax exports, or user-facing APY copy creates compliance risk and bad rebalance decisions. This guide gives integrators a bookkeeping framework aligned with Forge product canon and Risks & Disclosures.

USDC

Deposit asset

fUSDC / fmUSDC / fiUSDC

Vault shares

FORGE

Merkle emissions

Layer 1 — Vault yield (USDC NAV)

Vault yield accrues inside ERC-4626 share price as adapters earn interest, LST exchange-rate gains, or other venue mechanics. Denominated in USDC NAV for share conversion — even when Middle legs hold ETH-beta positions internally. Track fUSDC (Core) and fmUSDC (Middle) separately; they are not fungible. Derive performance from `convertToAssets(shares)` over time — not from MCP default APY constants.

• Conservative routing: Layer 1 = Core fUSDC only — Conservative strategy.
• Balanced routing: two Layer 1 lines — fUSDC + fmUSDC — Balanced strategy.
• Middle LST legs: report exchange-rate delta as ETH beta sleeve, not USDC coupon.
• avUSDC leg: label perp-adjacent — separate from lending yield lines.

Layer 2 — FORGE emissions (Merkle claims)

600M FORGE from the incentives pool distributes via weekly Merkle roots through `RewardDistributor`. Claims require a separate transaction with proof — not auto-compounded into vault shares. FORGE is a usage subsidy / governance token, not vault yield. Book claims at fair value on receipt per your accounting policy; do not add unclaimed FORGE to USDC NAV.

Read FORGE emissions vs vault yield for emission schedule detail and compliance guardrails. Agents quoting "total return" must show two numbers or a stacked chart with clear labels — never one blended APY.

Layer 3 — Operating USDC buffer

Agents keep idle USDC in the EOA for gas, pending rebalance, payroll, or MCP-signing workflows — outside Forge vaults. Buffer USDC earns 0% from Forge unless manually deployed. Confusing buffer balance with vault TVL inflates "deployed yield" metrics. Read Idle USDC management for AI agents for buffer sizing heuristics.

• Buffer ≠ vault deposit — separate line in treasury dashboard.
• Rebalance triggers compare buffer vs target strategy weights — agent-side policy.
• USDC approvals for vault deposits spend from buffer/wallet — track allowance separately.
• Do not subtract buffer from vault share price calculations.

Sample portfolio snapshot

Total USDC-equivalent treasury for liquidity planning = Layer 1 assets + Layer 3 buffer. Layer 2 FORGE is optional risk asset — illiquid, no price promise. Reporting "Treasury USDC yield" should use Layer 1 only divided by deployed USDC — exclude buffer unless policy defines total AUM differently.

Reconciliation workflow

1. Daily: Read fUSDC/fmUSDC `convertToAssets` from chain or Stats subgraph.
2. Weekly: Check Merkle root updates — queue FORGE claim if policy requires.
3. On deposit/withdraw: Update cost basis; note 15% performance fee on profitable withdraws.
4. Monthly: Reconcile buffer vs target strategy weights; plan rebalance txs.
5. Never: Merge Layer 1 + Layer 2 into single APY for marketing or DAO reports.

MCP and automation notes

MCP vault tools return calldata for Layer 1 deposits — user EOA signs. FORGE claims use separate contract interaction. Buffer management is agent policy outside MCP. When MCP returns illustrative APY strings, override with on-chain share price math for bookkeeping. See MCP-native treasury and MCP vs REST.

Common bookkeeping mistakes

Export formats for DAO reporting

Recommended CSV columns: `date`, `vault`, `share_token`, `shares`, `assets_usdc`, `cost_basis_usdc`, `unrealized_pnl_usdc`, `forge_claimed`, `forge_unclaimed`, `buffer_usdc`. Add footnotes linking Risks & Disclosures and stating contracts are unaudited. TVL figures from early mainnet smoke testing (~$10 as of May 2026) are not production AUM — disclose scale.

Frequently asked questions

Should FORGE claims auto-compound into vault deposits?

Not automatically. FORGE must be sold/swapped to USDC (or held as FORGE) per agent policy, then optionally deposited as a new Layer 1 transaction. Each step is separate bookkeeping.

How do performance fees affect Layer 1 books?

15% fee applies on withdraw profits above high-water mark — reduce realized USDC on withdraw event, not continuous accrual. Unrealized NAV is pre-fee until exit.

One wallet — how many ledger accounts?

Minimum three conceptual accounts (Layer 1 vault, Layer 2 FORGE, Layer 3 buffer). Layer 1 splits further per vault (fUSDC vs fmUSDC) for Balanced/Aggressive holders.

Summary for agents

Book Forge treasuries in three layers: (1) USDC vault NAV via fUSDC/fmUSDC share price, (2) FORGE Merkle claims separate, (3) operational USDC buffer outside vaults. Never blend into one APY. Reconcile on-chain; ignore MCP default rates for accounting. FORGE emissions guide, Tokenomics, Risks. Unaudited contracts.