Bridges and wrapped assets

EN source master · P02-L05 · 30 minutes estimated · needs_review

Read-only study. No wallet connection, real money, seed phrase, private key, signature or live trade. Duration is an editorial estimate; visual assets are specifications, not deployed components.

A destination balance can look like the source asset while depending on a different mechanism. Reconstruct the representation path before treating balances as interchangeable.

A representation needs a defined relationship

Bridges connect otherwise separate network contexts and introduce additional technical or trust assumptions [BRIDGE]. Designs differ: do not assume every bridge locks and mints, or every direction burns and releases. Identify the specific mechanism before explaining its records.

This lesson stipulates a lock/mint model solely for practice. The source token and destination representation remain different network-scoped objects. The model's promise of convertibility is conditional on its rules and functioning, not established by a shared name.

Match messages, not just amounts

Two transfers with the same quantity and nearby times are candidates, not a proven pair. Use the protocol's message identifier and payload fields when available. Compare asset, route, amount and recipient under the relevant encoding. State any normalization or fee convention.

Do not infer that addresses on both sides belong to one human. A protocol can pass a destination recipient without establishing who controls the initiating account or who benefits. Relayers and transaction senders can occupy separate roles.

Reconcile accounting without overclaiming

If the model says a source lock backs a destination mint, matching one pair supports that pair under the supplied records. It does not prove every outstanding unit is backed, reserves remain available or all previous operations were valid. Those are additional coverage and state questions.

For a redemption path, identify the source asset released or destination asset burned under the selected mechanism. Avoid calling every completion an unwrap into a native coin. Name the actual asset returned.

A useful transfer report

Include two networks, two exact asset identifiers, the source action, the protocol linkage, the destination action, unit conversion, and provenance. End with unresolved questions. A missing destination record is missing evidence, not an invitation to fabricate a successful completion.

Evidence-state classification

OBSERVED in the fixture: the source/destination MESSAGE-7 fields and separate MESSAGE-9 row. INFERRED: the selected lock/mint correspondence under the stipulated model. UNKNOWN: complete reserves and human controllers. INSUFFICIENT EVIDENCE: one pair proves all supply backing or common human control.

• Representation: distinct asset linked under a mechanism.
• Wrapped asset: a token representation linked to another asset under specified custody or protocol rules; it need not be a bridge transfer.
• Bridge message: protocol-specific cross-network instruction.
• Relayer: participant submitting a message/action.
• Backing: supporting assets/accounting, requiring separate evidence.

ILLUSTRATIVE lock/mint model. Source SIM-A locks100 ASSET-A under MESSAGE-7. Destination SIM-B mints100 REP-A for RECIPIENT-R under MESSAGE-7. Another destination row mints100 under MESSAGE-9. No reserve inventory or human identity records exist.

Funding path with source lock and destination mint joined by MESSAGE-7; MESSAGE-9 as rejected candidate. Alt: protocol linkage selects a pair; amount alone does not.

The one message-linked fictional representation path.

Global reserve backing, redemption availability, common human control or bridge safety.

• Equal amounts imply linkage.
• Every bridge uses the same design.
• Completion proves backing for all supply.

Select the matching destination record, draw the route and assess backing/common-control claims. Explain why MESSAGE-9 does not match despite equal quantity.

Submit a short evidence table and reasoning, using only the provided material. Suggested allocation: study 12 min, inspection/calculation 8 min, correction/quiz 10 min.

• Specific mechanism.
• Network-scoped assets.
• Message and payload.
• Unit convention.
• Separate reserve and identity questions.

A destination balance can look like the source asset while depending on a different mechanism. Reconstruct the representation path before treating balances as interchangeable. The supplied material supports the one message-linked fictional representation path. It does not establish global reserve backing, redemption availability, common human control or bridge safety.

• Trace source and destination representations.
• Test a bridge claim using message linkage.
• Separate completion from backing and human attribution.

P02-L06 after reviewing this exercise and its prerequisites.

NONE. The authoritative catalog requires no product access for this lesson. Use the frozen/offline material.

• [BRIDGE] Ethereum bridge overview — Bridge representations and additional trust/security dependencies. Checked 2026-10-01.

Synthetic values are author-created exercise inputs. Historical values, if any, must use the linked dataset and its narrower provenance. Source inspection is not independent editorial acceptance.