Onchain treasury reporting is the practice of producing balance, P&L, and counterparty-exposure dashboards directly from blockchain data, without relying on quarterly issuer attestations or manual reconciliation. As of Q1 2026, more than 180 DAOs and 240 corporate treasuries publish recurring onchain reports through tools like Den, Steakhouse Financial, Karpatkey, Llama, and Coinshift. The category has shifted from spreadsheet exports to true block-by-block dashboards, but reporting standards remain fragmented — there is no equivalent of GAAP for onchain treasury yet.
​

This guide covers what onchain treasury reporting needs to capture, which tools handle which slice of the workflow, what the emerging standards look like, and where the gaps are. The reader should walk away able to evaluate a reporting setup, identify what it does and doesn't cover, and decide whether to build, buy, or use a hybrid stack.
​

Onchain treasury reporting produces auditable disclosures of treasury position from public blockchain data. The reports cover four standard dimensions: balance (what's held, where), flows (deposits, withdrawals, swaps, transfers), P&L (yield earned, fees paid, mark-to-market changes), and exposure (counterparty risk, smart-contract risk, asset concentration).
​

The use cases vary by treasury type. DAO treasuries publish reports for governance transparency — token holders need to see how protocol revenue flows and where the treasury sits before voting on grants or budget allocations. Corporate treasuries use onchain reporting for internal management and external auditor support; the auditor needs the same data the CFO uses. Investor reporting for crypto-native funds increasingly includes onchain holdings broken out by asset, chain, and protocol.
​

The data exists by definition — every transaction is public — but raw blockchain data is not a treasury report. The work happens in classification, aggregation, valuation, and presentation. A USDC inflow could be a customer payment, a yield distribution, an internal transfer between two treasury wallets, or a swap return. Without classification, the inflow is just a number.
​

Three structural differences matter.
​

Continuous availability. Bank statements arrive monthly. Onchain balance is queryable every block (12 seconds on Ethereum, 2 seconds on Base, 400ms on Solana). Reporting tools can produce dashboards that update in near-real-time without batch processes.
​

Public verifiability. Every position can be independently verified by anyone with a block explorer. A treasury's claim that it holds $5M USDC on Base is provable in 30 seconds via BaseScan. Traditional treasury claims require either trust in the bank's statement or audit attestation.
​

Programmable structure. Onchain positions can be wrapped in smart-contract policy — multisig signing thresholds, automated rebalancing, conditional transfers, time-locked withdrawals. The reporting tool needs to surface not just balance but also policy state (pending proposals, signer set, time-lock countdowns).
​

The structural advantages don't translate automatically into better reports. Most onchain treasuries publish reports that look worse than a CFO's spreadsheet because the reporting tooling hasn't matured to match the underlying data quality.
​

The reporting tool stack splits into four categories, each handling a different slice.
​

Safe (formerly Gnosis Safe). The dominant multi-sig wallet — $112B in TVL across all Safes per Safe's homepage stats March 2026. Safe's UI provides a basic position view per chain but is not a treasury report; it's a transaction interface.
​

Den. Multi-sig operations layer built on Safe with treasury reporting features: position aggregation across chains, transaction approval workflows, and a reporting export. Used by Frax, Gitcoin, ENS, and ~130 other DAOs as of Q1 2026.
​

Coinshift. Treasury operations platform with payment workflows, transaction batching, and reporting. Targets DAOs and crypto-native businesses; used by Aave, Synthetix, Pooltogether, and ~75 others.
​

These tools cover the operational primitives — initiating, approving, and recording transactions — but generally do not produce final reports.
​

Steakhouse Financial. Provides monthly treasury and P&L reports for Sky (formerly MakerDAO), Lido, and ~12 other large DAOs. The reports are publicly available; the Steakhouse site archives them. Reports cover income, expenses, balance sheet, asset allocation, and risk exposure. The work is largely manual analyst output, not automated dashboard.
​

Karpatkey. Manages treasury operations and reporting for GnosisDAO, Balancer, ENS, and others. Public dashboards via Karpatkey's site. Mix of automated dashboards and analyst-prepared reports.
​

Llama. Acquired by Uniswap Foundation in 2023. Built treasury reporting and grant management for Uniswap, Aave, and Polygon ecosystem grants. Now operates primarily within Uniswap.
​

These platforms produce institution-grade reports but charge accordingly — typical engagements run $15K-50K/month for full coverage.
​

Dune Analytics. Open SQL workbench for blockchain data. Treasury teams build custom dashboards by writing SQL against indexed chain data. Dune dashboards for treasury cover ENS, Optimism, Arbitrum, Polygon, and most major DAOs. Free for public dashboards; paid for private.
​

Flipside Crypto. Similar to Dune but with broader analyst community and bounty programs. Common for ad-hoc treasury queries.
​

Footprint Analytics, Token Terminal. Pre-built dashboards covering most major protocols and DAOs. Token Terminal in particular focuses on protocol P&L and is widely used for protocol-revenue treasury attribution.
​

Self-serve analytics give the most flexibility but require SQL skills and time investment to set up and maintain.
​

Cryptio. Crypto-native accounting platform with general ledger, transaction classification, and audit support. Used by ~600 companies including Animoca, Consensys, and Ledger.
​

Bitwave. Enterprise crypto accounting and tax. Targets Fortune 500 and large corporates with crypto exposure.
​

Tres Finance. Treasury and accounting platform with multi-chain coverage and ERP integration (NetSuite, QuickBooks).
​

Lukka. Reference data and pricing for crypto assets; used by major auditors as a pricing source.
​

These tools translate onchain activity into double-entry bookkeeping, FASB-compliant valuations, and tax reporting. They are operationally heavier than DAO-style dashboards but required for any treasury subject to traditional financial-reporting obligations.
​

The accounting industry has moved faster on stablecoin and crypto treasury accounting in the last 24 months than in the prior decade. Three standard developments matter.
​

FASB ASU 2023-08. Issued December 2023, effective for fiscal years beginning after December 15, 2024. Requires fair-value measurement of crypto assets held by US public companies, with changes recognized in net income each period. Replaces the prior cost-less-impairment model that produced asymmetric reporting (write-downs but no write-ups). FASB's standards page hosts the full text.
​

The practical impact: a treasury holding $10M USDC reports it at fair value ($10M) every reporting period, not at historical cost. Stablecoins where fair value rarely deviates from $1 are uncomplicated; volatile crypto holdings (BTC, ETH) now produce mark-to-market P&L every quarter.
​

SEC SAB 121 rescission. Staff Accounting Bulletin 121, which had required custodians to report customer crypto as both an asset and a liability on their balance sheet, was rescinded in January 2025 via SAB 122. The rescission opened the door for traditional banks (BNY Mellon, State Street) to offer crypto custody without the prior balance-sheet penalty. This affects custodian selection rather than reporting directly.
​

EU MiCA reporting requirements. Stablecoin issuers operating in the EU must publish quarterly reserve composition reports under MiCA Article 36. Treasury teams holding MiCA-regulated stablecoins (USDC, USDT was delisted, others) can rely on these as audit evidence for issuer reserve adequacy.
​

No equivalent of GAAP for DAO or crypto-native treasury reporting exists yet. Industry working groups (SKT, RWA.xyz, Steakhouse) have proposed templates, but adoption is informal.
​

A defensible monthly treasury report includes seven sections.
​

Position summary. Total balance by asset, chain, and custody location. Breakdown should reconcile to the sum across all wallets and custodial accounts.
​

Flow statement. Inflows (revenue, transfers in, yield distributions) and outflows (expenses, transfers out, swap costs) for the period, classified by category.
​

P&L attribution. Yield earned by source (T-bills, money markets, private credit, staking), fees paid, mark-to-market changes on volatile assets.
​

Concentration analysis. Asset concentration (% in single stablecoin), chain concentration (% on single chain), protocol concentration (% in single yield protocol), counterparty concentration (% with single custodian or bridge).
​

Risk exposure. Smart-contract exposure (TVL in each protocol used), bridge exposure (any wrapped-asset positions), upcoming liquidity events (token unlocks, vesting, lockup expirations).
​

Policy compliance. Whether positions are within policy caps; any breach should be flagged with remediation timeline.
​

Forward-looking liquidity. Expected inflows/outflows for the next 1-3 months; runway implication.
​

The Steakhouse Financial reports for Sky and Lido are the public reference for what this looks like at scale. Steakhouse's Sky monthly report covers each section above plus protocol-specific KPIs.
​

Three failure modes recur across reports observed in the wild.
​

Missing internal transfers. A transfer between two treasury wallets shouldn't show as either inflow or outflow at the consolidated level. Reports that classify every onchain transfer as external income or expense overstate gross flow by 2-5x.
​

Stale pricing. Reports priced at month-end snapshot can miss volatile intra-period moves. The right approach is volume-weighted average price for flow valuations, with snapshot pricing only for closing balance.
​

Misclassified yield. Yield distributions from rebasing tokens (BUIDL, USDY) sometimes show as principal returns rather than yield. The accounting treatment matters for both P&L attribution and tax purposes.
​

The fix for all three is consistent transaction classification — every onchain transaction needs a category assigned at ingestion, with the category logic version-controlled and auditable.
​

External auditors increasingly accept onchain data as audit evidence, but the workflow is still maturing. The current pattern: the auditor receives a position snapshot from the treasury team, independently verifies the balances using a block explorer or a tool like 0xPredict or Cryptio, samples transactions for classification accuracy, and reviews the policy compliance memo.
​

The Big Four firms (Deloitte, PwC, EY, KPMG) all have crypto-asset audit practices as of 2024. Mid-tier firms (Armanino, RSM, Grant Thornton) cover crypto-native clients including DAOs and protocols. The audit cost premium for onchain holdings versus traditional cash management has compressed from ~3x in 2022 to ~1.4x in 2026.
​

For DAOs without statutory audit requirements, the equivalent function is community review — token holders or independent analysts review treasury reports and raise objections through governance forums. The function is less rigorous than statutory audit but operates on a faster cycle.
​

Treasury reporting depends on clean transaction data — every cross-chain movement needs to be classified and reconciled. Treasuries that route across multiple bridges (CCTP, LayerZero, Hyperlane, Across) end up with reconciliation overhead because each bridge produces different transaction signatures and different metadata. Eco is the stablecoin execution network that consolidates that movement under a single intent abstraction; the resulting transaction data is consistent across the 15 chains Eco supports, which simplifies the reporting team's classification work. For the broader treasury management context, see the treasury management pillar; for cross-chain mechanics, see Eco Routes.
​

Den and Coinshift cover most DAO operational and reporting needs at the platform level. For analyst-grade monthly reports with P&L attribution and policy compliance memos, Steakhouse Financial and Karpatkey are the dominant options. Smaller DAOs often use Dune dashboards plus periodic Steakhouse-style reports for governance milestones. See the DAO treasury management guide.
​

FASB ASU 2023-08, effective for fiscal years beginning after December 15, 2024, requires US public companies to measure qualifying crypto-asset holdings at fair value with changes recognized in net income each reporting period. Note: many fiat-pegged stablecoins fall outside the ASC 350-60 scope and remain under financial-instrument accounting. For stablecoins, fair value rarely deviates from $1, so the reporting impact is minimal in normal conditions but becomes material during depeg events.
​

Monthly is the institutional norm. Continuous dashboards (updated every block) are increasingly available through tools like Den and Karpatkey but supplement, not replace, the monthly narrative report. Quarterly reports suffice for some smaller DAOs. The cadence should match the treasury's operational tempo and stakeholder expectations.
​

The standard requires fair-value measurement of crypto-asset holdings (including stablecoins) on the balance sheet, with changes recognized in net income. For US-pegged stablecoins held at $1, the practical impact is minimal — the position remains at $1 each period. During depeg events, the mark-to-market loss flows through earnings immediately. See the diversification guide for context on depeg events.
​

Yes. All Big Four firms (Deloitte, PwC, EY, KPMG) and several mid-tier firms have established crypto-asset audit practices. The audit relies on independent verification of onchain balances, sample transaction testing, and review of internal classification policies. The cost premium versus traditional cash audit has compressed substantially over the past three years.
​