Follow the message across the two chains

A destination chain needs evidence that an event occurred on the source chain before it can act on that event. Different bridge designs check proofs against source-chain state or rely on attestations from an external group. The choice determines which assumptions the destination makes about the source chain and about the people or software carrying the message.

Find out what backs the token

In a simplified lock-and-mint design, a bridge locks one unit on the source chain and issues one corresponding wrapped unit on the destination chain after verification. The wrapped unit’s backing depends on the locked asset remaining available and the supply rules being enforced. A failure in custody or verification can leave wrapped units without their expected backing. Other bridges burn and mint assets or use liquidity already available on the destination, which changes where the backing or settlement risk sits.

Check when a source event counts as settled

A source-chain event may disappear during a reorganization. A bridge needs rules for how much confirmation or finality it requires before the destination acts. A chain can also stall, or a verification service can stop relaying messages. Both networks may continue producing blocks while a bridge is unable to process a message because its own contracts or services have paused.

Read the permissions alongside the audit

A bridge audit covers a particular scope and version. The deployed contracts may permit upgrades, changes to the verifier set, or emergency pauses. In the design documentation, identify who can accept a source event, how many approvals are needed, and who can change those rules. Then compare that description with what is deployed, including the role of the contracts that hold or issue assets.

Sources

  1. Ethereum 官方开发文档:跨链桥
  2. Chainlink 官方文档:跨链桥及相关风险

Prepared with AI assistance. This guide explains protocol behavior for educational use.

Editorial policy (Chinese)