A Wrapped Balance Looks Like the Same Coin

A wrapped balance looks like the same coin. A wallet holds a token that shares a name with one locked on another chain. The name is the first story. The vault that is supposed to hold the original is not.

A wrap can be a receipt. It can also be a promise with a hole. I read a bridge the way a cloakroom ticket is read: the ticket is not the coat. The coat has to still hang on the hook.

• A shared name is the first reading
• Lock and mint is a hook
• A pool is not a hook
• Note I kept for a wrap called FERRY
• A wrap that still matches
• Check the hook before you trust the ticket

A shared name is the first reading

The problem is easy to name. Two tickers look alike. The first reading treats the wrapped unit as interchangeable with the locked unit. They trade near each other until the vault is empty, the signer set is captured, or the pool on the far side runs dry.

Is the first reading always false? No. Some wraps can be redeemed one-for-one because the lock still holds and the redeem path works. The first reading fails when the lock address is a multisig that already sent the coins out, when “wrapped” is only a pool token, or when the official vault and the live vault are different addresses.

My claim is narrow. A wrap is a claim on a mechanism. A peg is a later fact: redeem still returns the original. Mixing them turns a ticket into a coat.

Opinion, not a law for every bridge: the ticker is a costume. The lock balance is the room.

Lock and mint is a hook

Lock and mint takes coins on chain A, holds them, and mints a receipt on chain B. Burn the receipt, unlock the original — if the hook still has the coat.

Question I keep on the page: does the lock address still hold at least as many original units as receipts exist? If receipts exceed the hook, the name is already ahead of the coat.

Exception: some designs move the lock to a new contract. The old address can look empty while the new one holds. Write both. Do not call an upgrade a theft because the first vault is dry.

A pool is not a hook

A liquidity-pool bridge does not always lock the same unit. It swaps against a pool on the far side. The “wrap” can be a pool share or a minted unit backed by whatever sits in that pool. When the pool tilts, the ticket and the coat stop matching.

Observation from public explorers: I have lined a mint on chain B next to a lock on chain A and found the lock smaller than the mint. That pairing is a fact on two pages. It is not a verdict on every design.

Condition: if the docs say lock and mint and the live path is a pool, the paper and the chain disagree. Stop. Name both.

Note I kept for a wrap called FERRY

I keep a note for a made-up wrap I call FERRY. Receipts on chain B: 50 units. Lock on chain A, official address: 50 at the start of the week. Midweek the lock sent 20 to a new address the docs did not list. Receipts stayed 50. A dashboard still printed “backed.”

Question in the margin: what was backed? Answer I could defend: 30 at the published hook, plus 20 in a room with no plate. Not 50 at the name on the page.

Was I looking at a live book? No. FERRY is a page. The experience was subtracting the outgoing from the hook. A reader can repeat that subtract on any public vault without taking a position.

Exception I left beside the note: if the 20 landed in a new official vault, the coat moved. Until that vault is named, the 20 are only a hop.

A wrap that still matches

The first reading works when receipts do not exceed the hook, when redeem works in a window you can try or at least read, and when the official address and the live address match. It works for that window.

It fails when a shared ticker is treated as a shared vault. It fails when a depeg is called impossible because the name matched last month.

I do not treat a gap as a command to act. I treat it as a reason to keep the ticket and the hook on two lines.

Check the hook before you trust the ticket

The solution that holds under the conditions above is a short check, not a slogan.

Write the receipt supply on the far chain. Write the lock balance on the home chain. Write whether the path is a hook or a pool. Write who can send from the lock. If a page will not show the lock address, the “same coin” sentence is not ready to stand.

If two explorers disagree on the vault, say so and stop before the peg becomes certain.

The spare thought on the desk is small. A wrap can be a real receipt. The hook can still be light. I check the hook first. I do not call the ticket the coat because the first reading stopped at the name.

The articles on this site are not investment recommendations or financial advice. They are structural analysis based on on-chain data and project documents.