How Can You Verify an Omnibridge Token’s Ethereum Backing?
To verify an Omnibridge token backed on Ethereum, match its Gnosis Chain contract in the registry, then compare Ethereum reserves with its supply.
Merkle Street Newsroom#2f783c4 min read
To verify that an Omnibridge token is backed on Ethereum, match its Gnosis Chain contract to its Ethereum origin in the Canonical Bridged Token Registry, then compare the origin token held by the Ethereum mediator with the representation’s total supply.
- Start with the exact Gnosis Chain token contract, not its ticker.
- Read the Gnosis representation’s totalSupply and the origin token’s balance at the Ethereum mediator.
- Compare the readings in the same units and account for any special token mechanics.
In an Ethereum-to-Gnosis transfer, the user sends the origin token to Omnibridge on Ethereum. The bridge locks it there; after validators relay the message, Omnibridge mints a representation on Gnosis Chain. Think of the mediator as a shared vault: the contract address tells you which vault balance to inspect, while the registry tells you which token belongs to it.
That lock-and-mint path is the context for how Omnibridge locks Ethereum tokens: it helps explain what the reserve reading means when you trace a Gnosis Chain token. Gnosis Bridge uses this mechanism for its Omnibridge route, so the token mapping is the starting point for checking the backing.
How do you match the token to its Ethereum origin?
The Canonical Bridged Token Registry identifies the origin contract for a Gnosis Chain representation. Open the official registry, select Ethereum as the origin chain and find the entry matching the token contract you want to verify.
Start by copying the full contract address from the token’s GnosisScan page. Confirm that the registry entry is for Gnosis Chain and that the representation address matches character for character. Then record the full Ethereum origin address shown in that entry. A matching ticker or token name is not enough: the same asset can arrive through different bridges or from different origin chains, producing separate contracts with similar names.
This mapping makes the reserve check meaningful. Without it, you might inspect the balance of a different Ethereum token that happens to share the ticker. Keep both network names and both full addresses in your notes so another person can repeat the check.
What should you compare in the explorers?
On GnosisScan, open the mapped representation contract and read its ERC-20 totalSupply. On an Ethereum explorer, open the mapped origin token and inspect its token balance at the official Ethereum Omnibridge mediator proxy: 0x88ad09518695c6c3712AC10a214bE5109a655671. The proxy address is published in Gnosis Chain’s bridge documentation; verify the network is Ethereum before relying on it.
Compare the reserve and supply after accounting for each token’s decimals. For a standard lock-and-mint token, the Ethereum balance held by the mediator should correspond to the outstanding Gnosis representation supply. The two explorer readings are public contract data, so you can perform this check without connecting a wallet.
Take a simple case: the registry maps the Gnosis contract in your wallet to a particular Ethereum ERC-20. You read that representation’s totalSupply, then read the mapped ERC-20 balance at the mediator. If the amounts correspond after decimal adjustment, that is contract-level evidence that the representation is backed by the mapped reserve. Record both readings, the network names and the full contracts; a ticker-only note is hard to audit later.
Do not treat every difference as proof of missing backing. Rebasing tokens have bridge operations disabled, and inflationary tokens can accrue inflation on Ethereum that is not returned to users when they exit. A token’s mechanics or other supply changes can therefore make a simple equality comparison misleading. Review its bridge notes before drawing a conclusion.
Suppose the origin token is inflationary. The registry mapping still identifies which Ethereum token belongs to the Gnosis representation, but the reserve-to-supply comparison needs to account for the token’s inflation behavior. The mapping remains the useful first check; the simple one-to-one reading may not.
Related
Why can Gnosis Chain show multiple tokens with the same ticker?
Different origin chains or bridges can create separate Gnosis contracts for tokens with the same ticker. Use the registry and full contract address to identify the one you hold.
Can you check bridge reserves without connecting a wallet?
Yes. The registry and both explorers show public contract data. You need the token address, not a wallet connection, to read the mapping, reserve balance and totalSupply.
Look again after a bridge upgrade, a change in token mechanics or a material change to the token’s supply. The registry mapping can still identify the origin, while the reserve comparison may need to reflect the new conditions.