What is a liquidity provider bridge and how is it different from lock-mint?

06 October 2026

A liquidity provider bridge uses pooled funds from external lenders to facilitate token transfers between blockchains, while a lock-mint bridge relies on a custodian or smart contract to hold the original asset and issue a wrapped version on the destination chain. The fundamental difference is that a liquidity provider bridge does not wrap your token at all - it simply swaps it against a pool of pre-deposited assets, then reissues an equivalent amount on the other side. No single custodian holds the original; instead, a network of liquidity providers supplies the capital that makes the transfer possible.

How a liquidity provider bridge works

When you want to move 1 ETH from Ethereum to Polygon using a liquidity provider bridge, the process is not a lock-and-mint. It is closer to a cross-chain swap.

1. You send your ETH to the bridge contract on Ethereum.
2. The bridge contract holds your ETH and notifies a relayer or validator network.
3. On Polygon, the bridge contract releases an equivalent amount of ETH (or a representative token) from a pool that liquidity providers have deposited in advance.
4. Your original ETH remains on Ethereum, now in the bridge’s custody. It becomes part of the liquidity pool for the reverse direction.

You do not receive a wrapped token that is a direct claim on your specific deposit. You receive a token from a shared pool. The bridge maintains a balance: for every token sent out on one chain, an equal amount must be held on the other.

How lock-mint bridges differ

A lock-mint bridge follows a different logic. When you send ETH to a lock-mint bridge:

• Your ETH is locked in a smart contract or custodian wallet.
• A corresponding wrapped token (like WETH on Polygon) is minted on the destination chain.
• That wrapped token is a direct representation of your specific locked ETH. When you burn it, the locked ETH is released.

The key distinction is that lock-mint bridges create a one-to-one mapping between your original asset and the wrapped token you receive. Liquidity provider bridges do not. They create a synthetic representation backed by a pool, not by your individual deposit.

Liquidity provider bridges are not custodial in the traditional sense

A lock-mint bridge typically has a single custodian - either a smart contract or a centralized entity - that holds all locked assets. If that custodian fails, all wrapped tokens become worthless.

A liquidity provider bridge spreads the risk. The liquidity is supplied by many independent providers who have deposited assets into the bridge’s pools. If one provider withdraws their liquidity, the bridge may become unbalanced, but the system can continue operating as long as there is sufficient capital on both sides.

However, this design introduces a different risk: liquidity provider bridges depend on the continued presence of that pooled capital. If too many providers withdraw at once, the bridge can become unusable for one direction of transfer, leaving your funds stuck on the source chain until liquidity is restored.

Which one is safer?

There is no simple answer. Lock-mint bridges concentrate risk in a single custodian or contract. If that custodian is a reputable, audited smart contract, the risk is technical - exploit or bug. If the custodian is a company, you add counterparty risk.

Liquidity provider bridges distribute the custodial risk across many participants, but they introduce liquidity risk. A lock-mint bridge cannot run out of liquidity because it mints tokens on demand. A liquidity provider bridge can, and does.

Both types of bridges have been exploited. Both have failed. The difference is in the failure mode: a lock-mint bridge fails when the custodian is compromised; a liquidity provider bridge fails when the pool becomes imbalanced or when the provider network collapses.

What backs the token you receive

With a lock-mint bridge, the wrapped token is backed by the specific asset you locked. You can verify this by checking the custodian’s wallet or the smart contract’s balance. The backing is direct and auditable.

With a liquidity provider bridge, the token you receive is backed by the pool’s total assets. Your token is not linked to your original deposit. The backing is collective. If you bridge 1 ETH from Ethereum to Polygon, the 1 ETH you left behind becomes part of the pool that backs all transfers in the opposite direction. The token in your wallet is only as good as the bridge’s ability to maintain that pool balance.

When to use each

Use a liquidity provider bridge when you want fast transfers and do not need a wrapped token that is a direct claim on your original asset. These bridges often settle in seconds or minutes because they do not require minting or burning.

Use a lock-mint bridge when you need a wrapped token that you can verify is fully collateralized by its native counterpart. This matters if you plan to hold the wrapped token for a long time, use it in DeFi protocols that require proof of backing, or want to avoid the liquidity risk of pooled models.

Neither type is inherently superior. Both have been exploited. Both continue to operate with billions of dollars in volume. The choice depends on what you value more: speed and convenience, or direct, verifiable backing of every token you hold.

Back to wrapped assets