Advanced DeFi bridges are cross-chain systems that move assets or messages between independent blockchains using different verification, liquidity, and settlement designs. The distinction matters: a fast route that fills a user’s request from destination-chain liquidity may settle its accounting later, while a messaging protocol may deliver data without moving a token at all.
Asset-transfer designs
In a lock-and-mint design, a source-chain asset is locked and a representation is issued on the destination chain; redemption depends on the bridge’s verification and custody model. Burn-and-mint designs destroy or retire a representation on the source before issuing it on the destination. These approaches can involve issuer-controlled minting, bridge contracts, validators, or other verification systems; the label alone does not establish the trust assumptions.
Liquidity networks and intents
Some bridge routes use local liquidity instead of waiting for a canonical bridge transfer. A user signs an intent describing the desired result, and a relayer or solver may fill it with funds already available on the destination chain. In Across’ documented design, relayers fill deposits on destination pools and later receive repayment through a separate settlement process. This can shorten the user-facing wait, but it depends on available liquidity, quote and fill conditions, and the settlement mechanism.
General message passing
Cross-chain messaging carries data or instructions between applications. In Wormhole’s documented flow, a source contract publishes a message, Guardians observe and attest to it, a relayer carries the signed message, and a destination contract verifies it before the receiving application acts. A message can coordinate governance or application state without itself transferring the asset that funds the action. The receiving contract must still validate the source application and define what the message is allowed to do.
Questions when comparing architectures
- What evidence authorizes the destination action: a multisignature attestation, a proof, a validator set, or another mechanism?
- Does the route transfer a native asset, mint a representation, use destination liquidity, or carry only a message?
- When do source-chain finality, destination execution, and settlement occur, and what happens if one step is delayed or fails?
- Which contracts, operators, relayers, upgrade keys, and liquidity providers can affect the route?
These models have different trust and operational assumptions. Review the specific contracts and current documentation for a route; a bridge category or interface is not a safety guarantee.
Related Terms
Sources
- Across Docs: Intent Architecture
- Wormhole Docs: Messaging Overview
- Wormhole Docs: Verifiable Action Approvals
- Ethereum.org: Bridges
Architecture descriptions checked against protocol and network documentation on 2026-10-29.