Proof of Reserve vs Proof of Liabilities for Bridged Asset Safety

15 October 2026

The difference between proof of reserve and proof of liabilities is the difference between verifying that a bridge custodian actually holds the assets it claims to hold (proof of reserve) versus verifying that its recorded obligations match those holdings (proof of liabilities). For bridged asset safety, neither alone is sufficient - you need both, and you need them to be independently auditable in real time.

What each term actually means

Proof of reserve is a demonstration that a custodian controls a specific amount of an asset on a public blockchain. The custodian signs a message from a known wallet or publishes a list of wallet addresses, and anyone can check the balances on-chain. It answers: "Does the custodian have the native asset?"

Proof of liabilities is a cryptographic or publicly verifiable record of how many wrapped tokens are in circulation. The custodian publishes a Merkle tree or similar structure that lets individual users confirm their own balance is included in the total. It answers: "How many wrapped tokens exist?"

Proof of solvency combines the two: the total liabilities (wrapped tokens issued) must be less than or equal to the total reserves (native assets held). That is the only state in which every wrapped token can be redeemed one-for-one.

Why proof of reserve alone is misleading

A bridge custodian can publish wallet addresses holding billions in native assets and still be insolvent if it has issued more wrapped tokens than those reserves can cover. This happens more often than you might expect:

• The custodian may have lent out reserves to earn yield, accepting IOUs that are not on-chain.
• The custodian may hold reserves in a different asset and rely on a price oracle to claim equivalence.
• The custodian may have already committed those reserves to cover losses from a previous exploit or operational error.

Looking only at a reserve wallet tells you nothing about the other side of the balance sheet.

Why proof of liabilities alone is meaningless

A custodian can publish a perfectly accurate list of all wrapped tokens in circulation and still be completely insolvent. The liabilities number is only useful when compared to reserves. Without that comparison, the liability figure is just a count of tokens that may or may not be redeemable.

What a real solvency check looks like

For a wrapped token to be safe, the bridge operator must provide both numbers in a way you can verify independently:

1. Find the reserve addresses. The bridge should publish a set of wallet addresses it controls. These are usually multisig or smart contract wallets. Check the balances of the native asset on the source chain.

2. Find the wrapped token supply. On the destination chain, look up the total supply of the wrapped token contract. This is available on any block explorer.

3. Compare. If the reserve balance of the native asset is lower than the total supply of the wrapped token, the bridge is undercollateralized. If the reserve balance is higher, the bridge is overcollateralized - safe, but inefficient.

4. Check the reserve addresses are still controlled by the bridge. A custodian can publish old addresses it no longer controls. Verify recent transactions from those addresses to confirm ongoing control.

The limits of on-chain proof

On-chain proof of reserve and liabilities is only as good as the last block. A bridge can be solvent at block 10,000,000 and insolvent at block 10,000,001 if the custodian moves the reserves. Real-time verification requires either:

• A live dashboard that reads both numbers from the chain at every block.
• A third-party monitoring service that alerts when the ratio drops below a threshold.

Neither guarantees future solvency. The custodian can always move funds after you check.

What to do when you cannot verify

Most bridges do not provide easy, real-time proof of solvency. If you cannot find both numbers in a form you can check yourself, you are trusting the bridge operator. That trust is the same as trusting any custodian. The technical term for that is "counterparty risk," and it is the reason wrapped tokens are not trustless.

If a bridge does not publish reserve addresses and a liabilities tree, or if the published data is stale, the safest assumption is that you cannot verify solvency at all. Treat the wrapped token as an unsecured claim on the custodian.

The Practical Takeaway

Proof of reserve tells you what the bridge has. Proof of liabilities tells you what the bridge owes. Only together do they tell you whether the bridge can honor redemptions. Checking one without the other is like checking a bank's vault without counting its deposit slips.

For any bridged asset you hold, you should be able to answer two questions from public on-chain data: "How much native asset does the custodian control?" and "How many wrapped tokens are in circulation?" If you cannot answer both, you are not verifying solvency - you are hoping for it.

Back to wrapped assets