A bridge moves assets between blockchains. The canonical pattern locks or burns the asset on the source chain and mints or unlocks a representation on the destination, with a set of validators attesting the transfer.
Bridges concentrate risk: the locked collateral is a honeypot, and history's largest exploits are bridge exploits. The alternative (swapping through liquidity on each chain, so no pooled custody exists) trades some price impact for the removal of that honeypot.
A bridge moves assets between chains by locking or burning on one side and minting or unlocking a representation on the other, with some mechanism attesting that the two sides stay in step. Validators, multisigs, or light-client proofs play the attester role, and the locked pool on the source chain is the value backing every representation in circulation.
That pool is also the problem. Bridge history is the industry's grave ledger: the largest exploits were nearly all breaks of the attestation or custody layer, not of the chains. Value concentrated in one contract, guarded by a small set of signers, is the exact shape attackers look for.
The alternative that U.CASH favors where possible is liquidity-based movement: swap through pools on each chain, or between a token's native forms, so no pooled custody exists to attack. Where a bridge is unavoidable, the diligence items are the attester set, its size and independence, and the limits imposed per transfer.
A token with native deployments on two chains moves between them as a swap between forms: sell one, buy the other, value crossing through liquidity. A wrapped-asset bridge instead holds the original in a pool and mints representations, concentrating risk in the custodian.
Cross-chain movement on U.CASH routes through the swap engine's liquidity-first paths where forms exist, so value moves between a token's deployments without a pooled bridge holding it.
Merchants should care which pattern moves their money. Settlement that routes through liquidity inherits market risk priced in the quote; settlement through a pooled bridge inherits custodian risk that prices in only when it fails. Asset pages state which forms are native where, which determines the pattern. The decision rule that falls out of the history: prefer native forms and liquidity paths whenever the asset offers them, and treat an unavoidable bridge as a short exposure with a size limit, not as settled infrastructure. The chain of forms each asset supports is on its page precisely so this rule can be applied without guesswork.
Every term behind the rails, the assets, and the settlement.