What Replaces Proof of Reserves: 7 Approaches to Continuous Reserve Verification

TL;DR

• Inherence proves each covered action satisfied defined policies before execution. Best for continuous mandate evidence.

• Chainlink relays reserve data on-chain. Best for collateral checks and mint controls.

• DIA exposes reserve-feed sourcing and computation. Best for auditable oracle data.

• The Network Firm provides frequently refreshed accountant attestations. Best for stablecoin and RWA issuers.

• Merkle sum trees prove customer liabilities were included in a solvency snapshot. Best for exchanges.

• Full financial audits examine assets, liabilities, and controls. Best for periodic, broad assurance.

• Layered attestation stacks combine CPA reports, oracle feeds, and audits. Best for regulatory and continuous coverage.

Request access to Inherence for pre-execution enforcement and independently verifiable receipts.

Why proof of reserves stopped being enough

Proof of reserves gained traction after FTX collapsed because exchanges needed a way to demonstrate control of customer assets. A typical proof combines wallet balances with a Merkle tree, which converts customer account records into hashes and combines them into one published value. Each customer can confirm that the platform included their balance without seeing other customers’ information. The model provides a narrow guarantee that specified assets and balances existed at a particular time.

The liabilities gap prevents a basic proof of reserves from establishing solvency. A Merkle proof can confirm that one account appeared in the supplied balance list, but it cannot prove that the operator disclosed every account or outside debt. Wallet ownership also does not reveal whether assets were borrowed, pledged as collateral, or otherwise encumbered. A platform can therefore demonstrate control of $100 million while owing more than $100 million.

The snapshot gap leaves activity between reporting dates unverified. A platform could borrow assets before the measurement and return them afterward, while the published proof would still show full backing on the selected block. Continuous trading, transfers, and redemptions can change both sides of the balance sheet within minutes.

An attestation provides less assurance than a financial statement audit. Under agreed-upon procedures, an accountant performs the checks specified in the engagement and reports the findings. The accountant does not necessarily examine internal controls, search for undisclosed obligations, or form an opinion on the company’s full financial position.

The GENIUS Act exposes the mismatch between periodic reporting and continuous obligations. The law requires payment stablecoin issuers to publish reserve composition monthly and obtain examination by a registered accounting firm, while holders retain a right to redeem at par on demand under disclosed terms. Monthly reporting therefore establishes a regulatory baseline, but it leaves the periods between reports untested while stablecoin markets continue settling around the clock.

The approaches that follow address different parts of these gaps. Some update asset data more frequently, some add liabilities, and others verify whether each reserve action followed a defined policy before execution. Most issuers and risk teams will need more than one approach because no single method proves custody, solvency, and continuous policy compliance.

What to look for in a reserve verification approach

Reserve verification approaches answer different questions, so no single criterion determines the strongest option.

Balance-sheet coverage. Identify whether an approach checks reserve assets, customer liabilities, or both. Asset proof confirms holdings, while a paired liabilities proof can support a solvency claim at the measured moment.

Cadence. Check whether evidence covers one date, updates at intervals, or accompanies every relevant transaction. More frequent updates narrow the period in which changes can go unobserved.

Source independence. Determine whether the provider independently reconstructs the reported figure or publishes data supplied by a custodian, bank, or accountant. A fast oracle feed can still inherit errors or limits from its upstream source.

Object of verification. Separate balance verification from mandate and action verification. Reserve feeds report what assets exist, and solvency schemes compare assets with liabilities. Pre-execution controls instead check whether a proposed action follows defined reserve rules and can produce evidence for that action.

Use these axes to identify which gap each approach covers and where another layer remains necessary.

Inherence

Best for Buyers who need independently verifiable evidence that a financial mandate governed every covered action.

Inherence converts a written mandate into an inline control that checks each covered action before execution. The control blocks actions that violate the mandate. Approved actions generate zero-knowledge receipts that third parties can verify without seeing private transaction data or policy thresholds.

Inherence fits buyers who need to confirm that mandates governed capital whenever it moved. An allocator can require a vault to enforce approved-asset and exposure rules on every covered trade. A stablecoin issuer can enforce transaction limits or approval requirements before settlement. The resulting receipts provide continuous evidence between monthly attestations.

Inherence proves policy adherence for covered actions. A receipt cannot establish that a custodian holds claimed assets or that total assets exceed liabilities. Reserve feeds, attestations, and proof-of-liabilities schemes provide those balance-sheet checks. Inherence pairs with those tools by showing whether specific actions followed the declared rules. Its assurance depends on correct policy definitions and reliable upstream facts, while actions outside the integrated path receive no coverage.

Pros

• The inline control blocks policy violations before execution and produces evidence for approved actions.

• Zero-knowledge receipts let counterparties verify compliance without receiving sensitive amounts or strategy details.

• Independent verification reduces reliance on operator-controlled logs and reporting portals.

Cons

• Inherence does not verify asset custody or balance-sheet solvency.

• Coverage requires relevant actions to pass through the integrated enforcement path.

• External facts such as screening results and market data still require upstream providers.

Pricing

Inherence does not publish pricing. Prospects request access directly from the company.

Chainlink Proof of Reserve

Best for

Continuous on-chain collateralization checks and mint controls for stablecoins, wrapped assets, and tokenized real-world assets.

Chainlink Proof of Reserve updates an on-chain feed when reported reserves move beyond a configured deviation threshold. Smart contracts can read the feed without waiting for a monthly report. Secure Mint can then block new token issuance when reported reserves fall below token supply.

Chainlink relays data supplied by custodians, auditors, or other providers rather than independently checking the underlying holdings. Incorrect or stale source data can therefore produce an incorrect on-chain figure. The feed also does not reveal hidden liabilities, confirm that reserves remain unencumbered, or prove compliance with a mandate for each transaction.

Pros

• Deviation-triggered updates provide more frequent collateral information than periodic snapshots.

• Smart contracts can use the feed as an automated minting or risk-control circuit breaker.

• On-chain publication gives users and applications a shared audit trail.

Cons

• Verification remains dependent on the integrity and freshness of upstream data.

• The feed covers reported assets rather than the issuer’s complete solvency position.

• Threshold-based updates do not necessarily record every reserve movement.

Pricing

Chainlink does not publish standard Proof of Reserve pricing. Buyers need a deployment quote based on their data sources, chains, update conditions, and contract integrations.

DIA

DIA exposes five stages behind each reserve or price feed. DIA sources first-party data from exchanges, processes it with published methods, and makes the formulas and computed feed inspectable. Published contracts then let users verify the resulting feed on-chain.

Best for: DIA suits risk teams that want to audit how an oracle sourced and computed a number before relying on it.

DIA’s tGBP proof-of-reserves oracle values the stablecoin using reserve backing rather than thin secondary-market trading. DIA ZK adds zero-knowledge proofs that can verify parts of the off-chain data pipeline on-chain.

DIA provides stronger sourcing transparency than an oracle that only publishes an output. However, a reserve feed still covers the asset side of the balance sheet. DIA does not prove liabilities, establish that assets remain unencumbered, or enforce reserve policies whenever funds move.

Pros

• DIA lets risk teams inspect and reproduce feed calculations.

• First-party sourcing reduces reliance on opaque third-party APIs.

• On-chain publication makes feeds available to smart contracts.

Cons

• Feed accuracy still depends on the quality and scope of source data.

• Reserve feeds do not establish full solvency.

• Oracle monitoring does not block transactions that violate an issuer’s mandate.

Pricing

DIA does not publish standard pricing for custom reserve feeds. Buyers must request terms based on the assets, chains, update frequency, and deployment requirements.

The Network Firm

The Network Firm suits stablecoin and RWA issuers that need CPA reporting more often than the GENIUS Act’s monthly minimum. Its 30-second heartbeat polls blockchains, banks, and custodians, including JPMorgan, Coinbase, Kraken, and BitGo. The slowest source sets the actual reporting interval, which can range between 30 seconds and daily.

The service refreshes a licensed accountant’s opinion under AICPA standards. It compares reported assets with disclosed on-chain liabilities and gives clients source-level logs, system health data, and a public widget. The service does not independently inspect every bank account or verify upstream data through an on-chain network. Incorrect source data can therefore produce an incorrect attestation.

Pros

• Frequent refreshes expose reserve shortfalls sooner than monthly attestations.

• CPA oversight gives issuers a familiar reporting format for regulators and traditional counterparties.

• Bank, custodian, and blockchain integrations support mixed off-chain and on-chain reserves.

Cons

• The attestation still depends on banks, custodians, and issuers supplying accurate data.

• Reported liabilities may omit obligations outside the defined engagement.

• Integration takes roughly six weeks, and source limitations can reduce the advertised update frequency.

Pricing

The Network Firm does not publish standard pricing. Issuers must request a quote based on their engagement scope, reserve sources, and reporting requirements.

Merkle sum tree proof-of-liabilities schemes

Best for: Exchanges and platforms that want to demonstrate assets equal or exceed customer liabilities without exposing individual balances.

A Merkle sum tree commits customer balances to one cryptographic root. Each leaf represents an account balance, while each parent records the combined value and hash of its children. Customers can verify that the platform included their balances, and an independent reviewer can compare the aggregate liability total with verified reserves. Distributed auditing research describes how this structure supports public solvency checks without revealing other customers’ account data.

Merkle sum trees cover the liability side that standard proof of reserves omits. Their reliability still depends on customers checking inclusion and reviewers testing whether the liability set is complete. A platform could otherwise exclude accounts or mishandle negative balances.

Each published tree remains a snapshot. The platform must recompute and republish it whenever balances change, so the proof does not provide continuous coverage between reporting dates. It also cannot show whether individual transactions complied with reserve mandates.

Pros:

• Covers both assets and liabilities when paired with reserve verification.

• Protects individual account balances while supporting inclusion checks.

• Lets third parties test the platform’s aggregate solvency claim.

Cons:

• Requires periodic recomputation rather than continuous verification.

• Cannot prove that every liability was included without added audit controls.

• Does not enforce policies before transactions execute.

Pricing:

No standard category price exists. Costs depend on implementation, proof frequency, independent review, and any zero-knowledge privacy features.

Layered attestation stacking (oracle + CPA + audit)

Issuers increasingly combine three forms of assurance because each answers a different question. A monthly CPA attestation meets the GENIUS Act’s reporting floor, while an on-chain proof-of-reserves feed monitors reported collateral between attestations. An annual full audit examines broader financial statements, controls, and financial health.

Best for: Stablecoin issuers and risk teams that need regulatory reporting alongside frequent on-chain reserve updates.

The layered transparency model serves both conventional financial reviewers and crypto-native users. The CPA provides a licensed accountant’s opinion, and the oracle makes reserve data available to smart contracts. The annual audit supplies broader scrutiny that neither feed offers.

Pros

• Multiple layers cover different reporting cadences and assurance needs.

• Oracle feeds can flag balance changes before the next monthly attestation.

• Audits examine a wider financial scope than reserve attestations.

Cons

• Every layer still depends partly on the accuracy and access of upstream data sources.

• More vendors increase integration work, governance needs, and cost.

• The stack does not prove that every reserve transaction followed an investment mandate.

Pricing

No standalone price applies. Total cost combines CPA attestation and audit fees with oracle integration, data-provider, and ongoing feed costs.

How the seven approaches compare

✅ indicates direct coverage, 🟡 indicates partial or source-dependent coverage, and ❌ indicates no coverage.

Approach	Assets verified	Liabilities verified	Cadence	Independent verification	Action-level enforcement
Inherence	❌ Not custody proof	❌ Not solvency proof	✅ Every covered action	✅ Verifiable receipts	✅ Pre-execution controls
Chainlink Proof of Reserve	✅ Custodian balances	❌ No liabilities	✅ Event-driven feeds	🟡 Upstream source dependent	✅ Mint gating available
DIA	✅ Sourced reserve data	❌ No liabilities	✅ Frequent feeds	🟡 Transparent pipeline	❌ No native enforcement
The Network Firm	✅ Attested balances	🟡 Engagement dependent	✅ Near real time	🟡 CPA opinion	❌ Post-action evidence
Merkle sum tree schemes	🟡 Requires paired assets	✅ Aggregate obligations	❌ Periodic snapshots	✅ Inclusion proofs	❌ No enforcement
Layered attestation stack	✅ Multiple evidence sources	🟡 Scope dependent	✅ Mixed cadence	✅ Multiple checkers	🟡 Oracle-based controls
Full financial audit	✅ Audited assets	✅ Audited obligations	❌ Annual or periodic	✅ Independent auditor	❌ No enforcement

Which approach fits your situation

Stablecoin issuers under the GENIUS Act. Pair monthly CPA attestations with a Chainlink or DIA reserve feed for updates between reporting dates. Add Inherence when reserve policies must govern each mint, redemption, or transfer before execution.

Exchange risk teams. Combine Merkle sum tree proofs of liabilities with verified asset balances to assess solvency at each snapshot. Continuous attestation can shorten the interval between checks, but it cannot prove that reserves remained unencumbered throughout the period.

Institutional allocators diligencing a vault. Use reserve attestations to confirm asset custody and Inherence to verify that exposure limits, approved assets, and withdrawal rules governed each covered action. The combination addresses both held assets and mandate compliance without requiring disclosure of the vault’s full strategy.

DeFi protocol builders. Chainlink suits protocols that need established on-chain reserve feeds and automated mint controls. DIA suits builders who prioritize transparent sourcing and computation. Inherence adds pre-execution enforcement when the protocol must block actions that breach defined rules.

Most buyers will combine two or three approaches because asset verification, liability verification, and action-level enforcement answer different questions.

Why Inherence leads for continuous mandate evidence

Inherence covers a gap that reserve feeds, attestations, and liability proofs leave open. Those tools can report assets or solvency at a given time, but they do not prove that every covered transaction followed an issuer’s or allocator’s mandate.

Inherence evaluates each action against defined policies before execution. An issuer could require approved reserve assets, exposure limits, eligible counterparties, or multiple approvals for withdrawals. Inherence blocks actions that fail those rules and produces a zero-knowledge receipt for each approved action. Allocators, auditors, and counterparties can verify the receipt without seeing confidential positions or transaction details.

Per-action receipts provide evidence for the periods between balance checks. They let an allocator verify that a vault followed its mandate whenever capital moved, and they let an issuer demonstrate that covered reserve operations stayed within policy throughout the reporting period.

Inherence does not independently prove custody, total liabilities, or solvency. Issuers should pair it with oracle feeds, CPA attestations, and proof-of-liabilities schemes when those checks apply. Inherence adds pre-execution enforcement and independently verifiable evidence to that reserve transparency stack.

Request access to Inherence.

How we evaluated these approaches

We selected approaches supported by public product documentation, named legal requirements such as the GENIUS Act, and deployments that identify participating customers or vendors. We also reviewed Chainlink’s Proof of Reserve documentation and DIA’s public materials rather than relying on unsupported marketing claims.

We categorized each approach by what it proves, whether it covers assets or liabilities, and how often verification occurs. We also assessed whether the provider independently derives the data or relays an upstream source, and whether the approach checks balances, policies, or individual actions.

FAQs

What is proof of reserves and what does it actually prove?

Proof of reserves confirms that a custodian controlled specified assets at a particular time. Inherence instead verifies whether each proposed action follows a defined reserve policy before execution. Using both gives you asset evidence and continuous mandate evidence.

Does proof of reserves check liabilities?

Standard proof of reserves checks assets, while a Merkle sum tree can add a privacy-preserving proof of customer liabilities. Inherence addresses a separate issue by enforcing rules whenever capital moves. Combining these methods can support solvency checks and transaction-level policy verification.

How often does the GENIUS Act require reserve attestation?

The GENIUS Act requires payment stablecoin issuers to publish reserve composition monthly and obtain examination by a registered accounting firm. Inherence can provide per-action evidence between those monthly reporting dates. Issuers can meet the monthly statutory baseline while maintaining evidence throughout continuous operations.

Can proof of reserves and pre-execution enforcement be used together?

Proof of reserves verifies balances, while pre-execution enforcement checks a proposed action against policy before allowing it. Inherence can operate alongside reserve feeds, liability proofs, and accountant attestations. The combined approach covers periodic financial position and ongoing compliance with reserve mandates.