In this track: Scaling and layer 2
intermediate · 3 MIN READ

Bridges as separate risk systems

Moving claims between networks introduces additional verification and custody mechanisms.

LET’S PICTURE IT

Two towns can exchange vouchers through a courier whose rules and reliability are separate from either town’s accounting office.

SEE IT FOR YOURSELF
Receive, check and share across independent nodesStep 1 / 4
Receive, check and share across independent nodesIncoming dataCandidate instructionNot yet trustedNode AReceives the messageApplies local checksEach participant has a local view of incoming informationNode A checksAuthorizationProtocol validityValid candidateEligible for next stepsNot a finality promiseApplication safety is a different claim from protocol validityNode AShares checked dataNode BChecks for itselfNode CChecks for itselfNode ARules checked✓Node BRules checked✓Node CRules checked✓Agreement on history adds the consensus mechanism

A node receives a proposed transaction or block-related message. Receipt is not the same as accepting its claims.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

A bridge connects state contexts

A bridge may lock, burn, mint or release representations according to messages and evidence from another system. Its design defines what a user actually receives on the destination network.

Message authenticity matters

A destination contract must determine which cross-network claims are valid and whether they were already processed. Bad verification or replay protection can undermine the transfer mechanism.

Custody and control vary

Some designs rely on administrators or a signer group; others use more direct chain evidence. Upgrade powers, available liquidity and emergency controls can also affect outcomes.

A familiar asset name is insufficient

A bridged token can use a recognizable symbol while depending on this separate mechanism. Inspect network, contract and redemption rules rather than assuming identical native-asset guarantees.

QUICK CHECK · NO PRESSURE

Does an asset’s familiar bridged symbol eliminate the bridge’s trust assumptions?

Your progress stays in this browser.
Keep exploring the original referenceethereum.org ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.