How Token Locking Keeps Bridge Supply in Balance

Token locking keeps a bridge’s supply in balance by holding tokens on one network while an equal amount is issued on another. The lock makes the original tokens unavailable to spend, so the new tokens have backing. When a user returns, the bridge removes the new tokens and releases the original ones.

How does a bridge lock and issue tokens?

A lock-and-mint bridge starts when a user sends tokens to a bridge contract on the source chain. A contract is software that runs on a blockchain. The bridge holds those tokens, then issues an equivalent amount on the destination chain. That new token is often called a wrapped token: a representation of an asset that remains held elsewhere.

The bridge needs to confirm the source-chain transaction before it issues tokens on the destination chain. This link between the two actions keeps the bridge from issuing tokens based on a transfer that did not happen. For the details of how assets move between Ethereum and Polygon, see Polygon Bridge.

For example, if a user locks 10 tokens on one chain, the bridge can issue 10 matching tokens on another. The user can then use those tokens on the destination chain. The locked originals stay put until a valid return transfer is made. The bridge’s accounting must track both sides: what it holds and what it has issued.

What happens when tokens move back?

On the return trip, the bridge burns or otherwise removes the destination-chain tokens, then releases the corresponding locked tokens on the source chain. Burning means permanently removing tokens from circulation. Removing the destination tokens first prevents the same value from remaining spendable in both places after the original tokens are released.

In a simplified lock-and-mint model, the accounting looks like this:

• The source-chain tokens are deposited and held by the bridge.
• An equal amount is issued on the destination chain.
• The user sends the destination tokens back to the bridge.
• The bridge removes those tokens and releases the original deposit.

Fees, different token units, or bridge-specific rules can affect the exact amounts a user receives. The core check is that the bridge should not release more than it holds or issue more than its rules allow. Users should check the token and network shown for both the deposit and return. The same asset name can refer to different tokens on different chains.

Does locking prevent every supply problem?

No. Locking gives the bridge a way to match issued tokens to held assets, but it does not guarantee that the bridge will work as intended. The contracts must correctly verify deposits, manage issuance, and authorize releases. A bug or compromised bridge controls can break that accounting and put the backing at risk.

Lock-and-mint is also only one bridge design. Some systems burn tokens on the source chain and issue them on the destination, relying on the token’s rules to support both actions. Others use liquidity pools, where users receive tokens already held on the destination chain. Those models handle supply differently, so the word “bridge” alone does not tell you what backs a token.

For most users, the practical check is to confirm the bridge’s model and the destination token before sending funds. A wrapped token backed by locked assets depends on that bridge continuing to hold and release the assets correctly. Locking keeps the amounts connected; the bridge’s contracts and controls determine whether that connection holds.