The claim class: a wrapped or bridged version of an asset on one chain states it is backed one to one by the real underlying asset, locked in a custody or bridge contract on the asset's native chain.
Claim class: a pattern of statements, not one attributed, dated quote.
Receipt to pull The receipt has two halves that need to be read together: the balance locked in the bridge's custody contract on the native chain, read directly from that chain's explorer, and the total supply of the wrapped token on the destination chain, read directly from its own contract. A one-to-one backing claim holds only if those two figures match. No single receipt is linked: this piece explains how to check this kind of claim and does not grade one specific claim.
A matching pair of figures at one point in time does not confirm the bridge's custody arrangement is resistant to the custodian or validator set simply moving or losing the locked assets later, and it does not evaluate the legal or operational structure behind who actually controls the custody contract or multi-signature keys. It is a snapshot of backing, not a guarantee of how that backing is governed going forward.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker.
A wrapped token is only as trustworthy as the thing it claims to represent one-to-one on another chain. The whole promise rests on a comparison almost nobody actually runs: the locked collateral on the source chain against the wrapped supply on the destination chain.
The Claim
The claim class: a wrapped or bridged version of an asset on one chain states it is backed one to one by the real underlying asset, locked in a custody or bridge contract on the asset’s native chain.
The Receipt
The receipt has two halves that need to be read together: the balance locked in the bridge’s custody contract on the native chain, read directly from that chain’s explorer, and the total supply of the wrapped token on the destination chain, read directly from its own contract. A one-to-one backing claim holds only if those two figures match.
Different bridge designs custody collateral differently: some use a single custodian holding the native asset directly, others use a decentralized network of validators or a smart-contract-based lock with no single custodian, and some newer designs use a collateral basket rather than the exact underlying asset. The specific design determines exactly which address or set of addresses needs to be read for the locked-collateral figure.
What It Doesn’t Prove
A matching pair of figures at one point in time does not confirm the bridge’s custody arrangement is resistant to the custodian or validator set simply moving or losing the locked assets later, and it does not evaluate the legal or operational structure behind who actually controls the custody contract or multi-signature keys. It is a snapshot of backing, not a guarantee of how that backing is governed going forward.
How to Check It Yourself
- Identify the native-chain custody contract or address the bridge uses to hold the underlying asset, from the bridge’s own documentation.
- Read the balance of that custody address directly on the native chain’s block explorer.
- Read the wrapped token’s total supply directly from its contract on the destination chain.
- Compare the two figures; they should match closely for a claim of one-to-one backing to hold at that snapshot.
- Check whether the custody design relies on a single custodian, a validator set, or a decentralized smart contract, since this changes who could affect the locked balance going forward.
- If the bridge claims continuous or real-time backing verification rather than a one-time check, look for whether that live feed is independently attested rather than self-reported by the bridge operator alone.
A Worked Example
A wrapped token on one chain claims full backing by the native asset locked on another. A reader reads the custody contract’s balance on the native chain and the wrapped token’s total supply on the destination chain and finds the two figures close enough to support the claim at that moment. Checking again a few weeks later after a reported bridge upgrade, the same reader finds the wrapped supply has grown noticeably faster than the custody balance, a gap worth flagging even without knowing its cause.
What Supported, Contradicted, and No Receipt Look Like
Supported: The native-chain custody balance and the destination-chain wrapped-token total supply match closely at a checked snapshot, and the custody arrangement’s design and controlling parties are disclosed clearly enough to understand what is actually safeguarding the locked assets.
Contradicted: The wrapped token’s total supply on the destination chain exceeds the balance actually held in the native-chain custody contract, indicating the wrapped asset is not fully backed at that snapshot.
No receipt: The bridge does not disclose a specific custody address or contract on the native chain, making it impossible to check the locked side of the comparison at all.
Red Flags
- The bridge’s documentation describes custody only in general terms, with no specific address a reader can check.
- The wrapped supply on the destination chain has grown without a corresponding, checkable increase in the native-chain custody balance.
- Custody rests with a single, undisclosed custodian with no public attestation of the arrangement.
- A “backing” dashboard is run entirely by the bridge operator itself, with no independent party confirming the figures it displays.
- The bridge recently changed its custody design or operator with little public disclosure of what happened to previously locked collateral.
A Practical Complication to Expect
Newer bridge designs sometimes use a basket of related assets, or a synthetic mechanism involving overcollateralization, rather than holding the exact underlying asset one-to-one in a single custody contract, which changes what the correct comparison actually looks like. In an overcollateralized design, a wrapped asset’s supply is expected to be backed by more than one-to-one collateral value, so a reader comparing raw token counts rather than the design’s own stated collateralization target could mistake healthy overcollateralization for a discrepancy, or miss a genuine shortfall if the comparison does not account for the collateral asset being different from the wrapped asset itself. Reading the bridge’s own documented collateral model before running the numeric comparison avoids reaching a false conclusion in either direction.
Why It Matters
A bridge or wrapped-asset failure is one of the more damaging and recurring failure modes in crypto precisely because the backing claim is rarely checked by anyone until something goes wrong. Comparing the two on-chain figures directly, before relying on the wrapped asset, converts a trust assumption into a number that can be checked at any time.
FAQ
Why would locked collateral and wrapped supply ever diverge if the bridge is working correctly?
In a correctly functioning bridge they should track closely together, since minting wrapped tokens is meant to be tied directly to new collateral being locked; a lasting divergence is itself the signal worth investigating.
Does a decentralized custody design remove this risk entirely?
It changes the risk rather than removing it, shifting from trusting a single custodian to trusting a validator set’s honesty and the smart contract’s correctness; the comparison between locked collateral and wrapped supply is still the right check either way.
Can this check be run for any wrapped asset?
It requires the bridge to disclose a specific, checkable custody address or mechanism; where that disclosure does not exist, the check cannot be completed and the backing claim is a no-receipt finding rather than a confirmed one.
How is this different from a stablecoin reserve attestation?
The mechanics are similar in spirit, comparing issued supply to backing assets, but a bridge’s backing is typically checkable directly on-chain in real time, while a stablecoin’s reserves often include off-chain assets that require a separate attestation document rather than a pure on-chain read.
What happens to the backing claim if a bridge operator changes custodians or migrates to a new contract?
A migration is a natural point for the collateral-to-supply comparison to temporarily diverge, since assets may move from an old custody contract to a new one in stages rather than all at once, and a reader checking balances mid-migration could see a misleading snapshot on either the old or new contract alone. Checking both the old and new custody addresses together during a disclosed migration period, rather than assuming the asset has simply vanished from one address, avoids mistaking a transition for a shortfall.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker; we describe how a claim like this can be checked, never whether to buy, sell, or hold anything on the back of it.
Sources
This piece links no outside source: it explains a class of claim and the public records you would check, rather than grading one specific statement. When a specific claim is checked, every source link is listed here with its status.
Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.



