Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
Free 30-min Web3 Consultation
Book Consultation
Smart Contract Security Audits
View Audit Services
Custom DeFi Protocol Development
Explore DeFi
Full-Stack Web3 dApp Development
View App Services
defi-renaissance-yields-rwas-and-institutional-flows
Blog

Why Proof-of-Reserves Are a Start, But Proof-of-Solvency Is the Goal

Proof-of-reserves is a half-truth. It proves assets exist but hides liabilities. Proof-of-solvency cryptographically proves a platform's entire balance sheet is solvent in real-time. This is the non-negotiable standard for institutional trust.

introduction
THE ACCOUNTING GAP

Introduction

Proof-of-Reserves verifies assets, but only Proof-of-Solvency proves that a custodian's liabilities do not exceed them.

Proof-of-Reserves is insufficient because it audits only the asset side of the ledger. A protocol like MakerDAO can prove it holds collateral, but this says nothing about its outstanding DAI liabilities or rehypothecation risks.

The goal is Proof-of-Solvency, a cryptographic audit of the entire balance sheet. This requires proving customer liabilities (e.g., user balances) are less than or equal to verifiable on-chain assets, closing the accounting gap that doomed FTX.

Modern frameworks like zk-proofs enable this. Projects like Mina Protocol use zk-SNARKs to create succinct proofs of state, while entities like Chainlink are exploring proof of reserves for real-world assets, laying the technical groundwork for full solvency proofs.

thesis-statement
THE ACCOUNTING GAP

The Core Argument: Reserves ≠ Solvency

Proof-of-Reserves audits assets but ignores liabilities, creating a dangerous false sense of security.

Proof-of-Reserves is incomplete accounting. It verifies an entity holds assets but provides zero visibility into its liabilities. This is the fundamental flaw that doomed FTX and Celsius. A balance sheet with only one side is useless.

Solvency requires liability verification. True solvency proves that total assets exceed total customer liabilities at a specific point in time. Protocols like MakerDAO and Aave enforce this programmatically with on-chain collateralization ratios, a model CEXs lack.

The industry standard is flawed. Most CEX audits, like those using Merkle tree proofs, are voluntary snapshots. They fail to prove the absence of hidden debts or double-counted assets, which are the real risks.

Evidence: Following FTX's collapse, Binance's PoR audit by Mazars was discontinued, highlighting the methodology's lack of accepted standards and inherent limitations for proving financial health.

CUSTODIAL ACCOUNTING

Proof-of-Reserves vs. Proof-of-Solvency: A Technical Breakdown

A comparison of cryptographic audit methods for centralized exchanges (CEXs) and custodians, highlighting the critical distinction between verifying assets and verifying net obligations.

Feature / MetricProof-of-Reserves (PoR)Proof-of-Solvency (PoS)Ideal Standard

Core Objective

Verify existence of claimed assets

Verify assets >= total user liabilities

Assets >= Liabilities + Real-Time Verification

Proves Solvency

Audits Liabilities

Detects Fractional Reserve

Common Implementation

Merkle Tree of user balances (e.g., Binance, Coinbase)

Zero-Knowledge Proof of non-negative net capital (e.g., zk-proof-of-solvency research)

PoS with frequent, on-chain attestations

Primary Cryptographic Tool

Merkle Proofs

Zero-Knowledge Proofs (ZK-SNARKs/STARKs)

ZK-SNARKs/STARKs + On-Chain State Commitments

User Verification Time

Minutes to manually verify inclusion

Seconds via verifier contract

< 1 second via light client

Key Weakness

Omits liability proof; 'liabilities' can be fabricated

Computationally intensive; nascent tooling

Requires full transparency of asset/liability schemas

Industry Adoption (2024)

50% of Top-20 CEXs

< 5% of Top-20 CEXs (Mostly R&D)

0% (Theoretical gold standard)

deep-dive
FROM ACCOUNTING TO CRYPTOGRAPHY

The Technical Path to Real Solvency Proofs

Proof-of-reserves is a necessary but insufficient audit; true solvency requires cryptographic proof of liabilities against on-chain assets.

Proof-of-Reserves is incomplete. It cryptographically proves an entity controls assets, but reveals nothing about its liabilities. This creates a false sense of security, as seen with FTX, which held reserves but owed more.

Proof-of-Solvency requires liability proof. The goal is a zero-knowledge proof that total verifiable liabilities are less than total proven reserves, without revealing individual user balances. This is the cryptographic standard set by protocols like zkSync and Starknet for their state.

The technical barrier is data availability. Proving liabilities requires a cryptographically committed user ledger. Exchanges like Binance and Coinbase use Merkle trees for reserves, but their liability ledgers are opaque, off-chain databases.

Evidence: True solvency proofs require systems like Chainlink's Proof of Reserve or Mina Protocol's recursive zk-SNARKs to continuously attest to the full balance sheet, moving beyond periodic snapshots.

protocol-spotlight
FROM TRANSPARENCY TO TRUST

Who's Building the Solvency Layer?

Proof-of-Reserves is a reactive snapshot; Proof-of-Solvency is a real-time, cryptographically enforced guarantee of full collateralization.

01

The Problem: Proof-of-Reserves is a Broken Promise

Current PoR audits are point-in-time attestations that fail to detect intra-period insolvency, rely on trusted third parties, and obscure liability composition.\n- FTX Gap: Audited by Armanino, yet hid a $8B liability shortfall.\n- Blind Spot: Cannot detect if user funds are double-pledged as collateral elsewhere.\n- Manual Lag: Typically quarterly, leaving months of risk exposure.

~90 Days
Audit Lag
$8B+
Undetected Risk
02

The Solution: Continuous Proof-of-Solvency via ZKPs

Protocols like Succinct Labs and RISC Zero enable cryptographically-verifiable, real-time solvency proofs. The system cryptographically attests that total user liabilities are fully backed by on-chain assets, continuously.\n- Real-Time: Solvency state proven with every block.\n- Privacy-Preserving: Uses zero-knowledge proofs (ZKPs) to verify obligations without exposing individual balances.\n- Trustless: Verification is on-chain, removing auditor dependency.

24/7
Coverage
~0 Trust
Assumptions
03

Succinct Labs: The Generalized Prover Network

Building SP1, a high-performance zkVM that makes generating complex proofs (like solvency) feasible and cost-effective. This is infrastructure for the solvency layer.\n- Performance: ~100x faster than prior zkVMs for large-scale state proofs.\n- Universal: Can prove solvency logic written in Rust, bridging CEX databases to blockchain verification.\n- Ecosystem Play: Powers applications like zkPass (privacy-preserving verification) and on-chain AI.

100x
Faster Proving
Rust
Developer UX
04

The Endgame: On-Chain Verification as a Market Signal

When solvency proofs are cheap and continuous, they become a real-time risk premium. Exchanges and lending protocols will compete on their verifiable collateralization ratio.\n- Dynamic Rates: Borrowing rates adjust automatically based on live proof quality.\n- Capital Efficiency: Over-collateralized protocols can safely increase leverage with proof.\n- Regulatory Clarity: Provides an unambiguous, automated standard for compliance beyond manual audits.

Live
Risk Pricing
Auto
Compliance
counter-argument
THE REALITY CHECK

The Pushback: Is This Overkill?

Proof-of-Reserves is a necessary but insufficient audit that fails to prove solvency, creating a false sense of security.

Proof-of-Reserves is incomplete. It verifies asset holdings but ignores liabilities, allowing an exchange to be technically insolvent while appearing healthy. This is the fundamental flaw in the current CEX audit model.

The goal is Proof-of-Solvency. This cryptographic proof combines a Merkle proof of liabilities with a proof of reserves, demonstrating total assets exceed total user balances. Protocols like zk-proofs enable this without exposing private data.

The industry standard is evolving. Projects like Binance's zk-SNARK-based audit and frameworks from Nansen and Chainlink push beyond simple reserves. The end-state is continuous, automated verification, not quarterly attestations.

Evidence: The FTX collapse proved a $9B liability hole existed despite prior 'audits'. A true Proof-of-Solvency system would have flagged this insolvency in real-time, preventing the catastrophe.

risk-analysis
THE RESERVE GAP

The Bear Case: What Could Go Wrong?

Proof-of-Reserves audits are a reactive snapshot, not a real-time guarantee of solvency. They fail to capture the systemic risk of fractional reserves and inter-exchange liabilities.

01

The Snapshot Fallacy

PoR provides a point-in-time attestation, not continuous proof. An exchange can be fully reserved at audit time but become insolvent minutes later due to a hack or withdrawal run.\n- Time Lag Risk: Audits are quarterly at best, creating a multi-month blind spot.\n- Data Manipulation: Audits rely on self-reported data; a malicious actor can spoof wallet ownership or hide liabilities.

90+ days
Audit Lag
0
Real-Time Coverage
02

The Fractional Reserve Blindspot

PoR only proves assets exist, not that they cover all customer liabilities. An exchange can hold $1B in BTC but owe customers $2B, remaining technically 'reserved' but functionally insolvent.\n- Liability Obfuscation: PoR does not cryptographically link assets to specific customer obligations.\n- Systemic Risk: This enables the same asset to be promised to multiple parties, replicating traditional fractional banking risks.

>100%
Possible Liability Ratio
0
Liability Proof
03

The Inter-Exchange Liability Problem

Exchanges often re-hypothecate assets or use them as collateral on other platforms (e.g., FTX/Alameda). PoR cannot trace these off-balance-sheet obligations, creating a contagion vector.\n- Hidden Leverage: Assets shown in a PoR may be double-pledged on Compound, Aave, or other CEXs.\n- Contagion Risk: The failure of one entity can cascade, as seen in the $10B+ 2022 collapses.

Nested
Exposure Risk
Chainlink
Oracle Dependency
04

Proof-of-Solvency: The Cryptographic Standard

The goal is a cryptographic system that proves total assets ≥ total liabilities in real-time without revealing individual balances. It combines PoR with Proof-of-Liabilities (PoL).\n- Zero-Knowledge Proofs (ZKPs): Enable privacy-preserving verification of solvency.\n- Merkle Trees for Liabilities: Commit to all customer balances, allowing users to verify inclusion.\n- Continuous Attestation: Moves from periodic audits to a cryptographically enforced state.

24/7
Verification
ZK-Proofs
Core Tech
future-outlook
THE SOLVENCY SHIFT

The Inevitable Standard: What's Next (6-24 Months)

Proof-of-reserves is a reactive snapshot, but the industry is converging on continuous, cryptographic proof-of-solvency as the non-negotiable standard.

Proof-of-reserves is insufficient. It proves asset existence at a point in time but not ownership or net liabilities. This model failed to prevent the FTX collapse, where client assets were co-mingled and leveraged off-chain.

Proof-of-solvency is the goal. It cryptographically proves total assets exceed total liabilities in real-time, without revealing individual positions. This requires zero-knowledge proofs and Merkle sum trees to validate the entire balance sheet.

The standard is being built now. Protocols like zk-proof-of-solvency and tools from Succinct Labs enable this. The shift moves trust from periodic audits to continuous, on-chain cryptographic verification.

Evidence: After FTX, Binance's PoR audits faced scrutiny for omitting liabilities. In contrast, a true proof-of-solvency system, as conceptualized by Vitalik Buterin, would have made the shortfall provably impossible to hide.

takeaways
FROM TRUST TO TRUTH

TL;DR for Busy Builders

Proof-of-Reserves is a basic audit; Proof-of-Solvency is a cryptographic guarantee of solvency without revealing liabilities.

01

The Problem: Proof-of-Reserves is a Marketing Gimmick

A PoR audit is a point-in-time snapshot of assets, not a real-time guarantee. It's vulnerable to liability obfuscation and asset borrowing between audits, as seen in the FTX collapse. It creates a false sense of security for users and regulators.

0
Liability Proof
~$10B+
FTX Hole
02

The Solution: Zero-Knowledge Proof-of-Solvency

Cryptographically proves total assets ≥ total liabilities without revealing sensitive user data. Enables continuous, real-time verification. Projects like zkSNACKs (Wasabi Wallet) and research from Nym and Espresso Systems are pioneering this approach.

  • Privacy-Preserving: User balances remain confidential.
  • Unforgeable: Based on cryptographic proofs, not auditor opinions.
24/7
Verification
ZK-Proof
Tech Stack
03

The Implementation: Merkle Trees & ZK-SNARKs

The standard architecture combines a Merkle tree of liabilities with a ZK-SNARK proof. The exchange proves it knows a secret commitment to the tree root and that the sum of its UTXOs/reserves exceeds the sum of the leaf commitments.

  • User-Verifiable: Anyone can check the proof.
  • Exchange-Optimized: Computationally intensive proof generation is a one-time cost.
~1M
Users/Proof
Seconds
Verify Time
04

The Hurdle: Privacy vs. Regulatory Compliance

ZK-PoS anonymizes liability data, which conflicts with Travel Rule and Anti-Money Laundering requirements. Solutions like Findora and Aztec are exploring selective disclosure, but the regulatory path is unclear. This is the primary adoption blocker for CEXs.

FATF
Rule Conflict
Selective
Disclosure
05

The Benchmark: Look for On-Chain Proofs

Evaluate custodians by where the proof is published. On-chain verification (e.g., via a smart contract) is the gold standard—it's immutable and permissionless. Off-chain or auditor-hosted proofs reintroduce trust. The goal is a system where solvency is as transparent as a blockchain's state.

L1/L2
Settlement
Trustless
Verification
06

The Future: Cross-Chain Proof-of-Solvency

Solvency must be proven across fragmented liquidity on Ethereum, Solana, Bitcoin L2s, and beyond. This requires universal proof systems and bridged asset attestations. Projects like Polygon zkEVM and Succinct Labs are building infrastructure to make cross-chain state proofs viable for this use case.

Multi-Chain
Assets
Universal
Proof System
ENQUIRY

Get In Touch
today.

Our experts will offer a free quote and a 30min call to discuss your project.

NDA Protected
24h Response
Directly to Engineering Team
10+
Protocols Shipped
$20M+
TVL Overall
NDA Protected Directly to Engineering Team
Proof of Solvency vs Proof of Reserves: The Real Trust Layer | ChainScore Blog