ZK Solvency Proofs
Prove the assets cover the liabilities, without publishing either.
What it does
Proof of Reserve answers half the question: it shows what is held. It does not show whether what is held covers what is owed, and publishing a full liability list would expose every holder's position. This module is designed to commit customer balances to a cryptographic tree and prove that total reserves meet or exceed total liabilities, so anyone can verify the system is solvent while each holder can independently check that their own balance was included. The balance sheet stays private; the solvency claim becomes checkable. In development.
How it works
ZK Solvency Proofs extend Proof of Reserve. Proof of Reserve supplies the asset side, Data Oracles the valuations, and this module proves the two sides balance without revealing either.
Select a step to replay it. Hover to pause.
Step 1 of 3: Commit. Every holder balance is committed to a cryptographic tree, without any of them being published.
Key capabilities
Liabilities committed, not published
Customer balances are committed cryptographically so they can be proved without being disclosed.
Reserves ≥ liabilities, proved
The claim that matters is the one that is verified, rather than asserted in a report.
Per-holder inclusion check
A holder can confirm their own balance formed part of the total, without seeing anyone else's.
Verifiable by anyone
Solvency becomes something a counterparty can check rather than take on trust.