P01-L07 · P01 · P01-M02
Identify issuer reserve and bridge dependencies
Prerequisites: P01-L06
Learning objectives
- Identify issuer reserve and bridge dependencies
- Distinguish issuer-native issuance from bridged representation.
- Separate reserve disclosure from independent assurance.
- Map redemption dependencies.
EN source master · P01-L07 · 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.
Why this matters
A shared dollar-oriented ticker can hide different issuers, chains and redemption paths. The label ‘stable’ describes an objective, not an unconditional outcome.
Explanation
Identify the representation before the peg
A stablecoin aims to track a reference value, but a displayed price and a redemption right are different concepts. Start with network and exact contract or mint. Circle publishes network-specific USDC identifiers [CIRCLEID]; that is an example of an issuer source, not permission to identify every similarly named token as its issuance.
‘Native issuance’ here means issued directly under an issuer's arrangement on that chain. It does not mean the network's native fee coin. A bridged token can be a representation of another token held or accounted for elsewhere. The redemption path then includes bridge assumptions in addition to the original asset's dependencies [BRIDGE].
Ask who promises what
An issuer disclosure can describe reserves, operations and redemption terms. Circle's transparency page publishes its own reserve statements and points to assurance material [CIRCLE]. Reading that statement is not the same as independently checking bank balances or auditing all liabilities. Record the publisher, reporting period and exact claim.
Do not upgrade an attestation to a universal or continuous guarantee. In a real dossier, inspect the report's date and scope before describing its assurance. This lesson does not inspect a current attestation or certify any issuer's present reserves.
Trace the full route
For the fictional bridge representation, write each conversion as a conditional step: represented token to source token under bridge rules; source token to reference asset under issuer conditions. A familiar symbol at the beginning does not remove intermediate permissions, availability or accounting questions.
A direct issuer token can still have issuer and network dependencies. A bridged token can introduce additional ones. This is a structural comparison, not a claim that every bridge uses one design or that one chosen instrument is suitable for a person.
Keep market and redemption evidence separate
A last-trade price near one reference unit is a market observation at a particular size and time. It does not independently prove reserve adequacy or that every holder can redeem immediately. If a claim says ‘always redeemable’, ask whose rules, for which holders, through which route and with which evidence.
Evidence-state classification
OBSERVED in the fixture: issuer sheet's statement, displayed price and stipulated issuance roles. INFERRED: the two conditional redemption dependency paths. UNKNOWN: eligibility, actual reserves and bridge accounting. INSUFFICIENT EVIDENCE: equal price/symbol proves equivalent immediate redemption or independent reserve verification.
Key terms
- Peg: target relationship to a reference value.
- Issuer-native issuance: issuer's token on a specific network.
- Bridged representation: asset linked through bridge rules.
- Reserve disclosure: attributed statement about supporting assets.
- Attestation: a third-party assurance report on specified assertions for a stated date or period; its scope is not a continuous guarantee.
Historical example
ILLUSTRATIVE. TOKEN-U on SIM-A is stipulated direct issuance by ISSUER-U. TOKEN-U-B on SIM-B is stipulated a bridge representation of TOKEN-U through BRIDGE-B. A fictional issuer sheet states reserves=100 units and liabilities=100 at SIM-DAY-1, but no independent report or redemption terms are supplied. Both screens show symbol USD-U and price1.
Visual specifications
Mint comparison with separate direct and bridged rows; conditional redemption arrows and missing-terms boxes. Alt: bridged USD-U adds BRIDGE-B before the issuer path; a shared symbol does not erase dependencies.
What the evidence proves
The stipulated dependency paths and existence of an attributed statement.
What the evidence does not prove
Current reserves, universal redemption rights, stable price or representation equivalence.
Common mistakes
- Confusing issuer-native with native fee asset.
- Taking a one-unit quote as reserve proof.
- Dropping the bridge from the redemption map.
Practical exercise
Draw both redemption dependency paths. Classify the reserve statement and assess ‘both are equally and immediately redeemable for everyone’. Identify missing documents.
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.
Show worked correction
Direct path: TOKEN-U→issuer process, subject to its terms. Representation path: TOKEN-U-B→bridge→TOKEN-U→issuer process. The sheet is an observed fictional declaration, not independent reserve verification. The equivalence/immediacy claim is INSUFFICIENT EVIDENCE. Terms, eligibility, bridge accounting and independent reserve evidence are UNKNOWN.
Review rubric: 1 point each for exact scope, source/fixture provenance, correct reasoning, explicit limitations and safe offline handling (5 total). An invented observation or unsupported human attribution requires correction regardless of score. This is formative feedback, not certification.
Checklist
- Exact chain and identifier.
- Direct issuance or representation.
- Issuer and bridge dependencies.
- Disclosure date, scope and attribution.
Summary
A shared dollar-oriented ticker can hide different issuers, chains and redemption paths. The label ‘stable’ describes an objective, not an unconditional outcome. The supplied material supports the stipulated dependency paths and existence of an attributed statement. It does not establish current reserves, universal redemption rights, stable price or representation equivalence.
Summary
- Distinguish issuer-native issuance from bridged representation.
- Separate reserve disclosure from independent assurance.
- Map redemption dependencies.
Next lesson
P01-L08 after reviewing this exercise and its prerequisites.
Tools
NONE. The authoritative catalog requires no product access for this lesson. Use the frozen/offline material.
Sources & claim boundaries
- [CIRCLE] Circle transparency — Issuer reserve disclosures; statements are attributed, not independently audited here. Checked 2026-10-01.
- [CIRCLEID] Circle USDC contract addresses — Issuer-published network-specific identifiers, not a safety guarantee. Checked 2026-10-01.
- [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.
Visual specifications
P01-L07-V01
Identify issuer reserve and bridge dependencies
Illustrative teaching data; not a live screen
Mint comparison with separate direct and bridged rows; conditional redemption arrows and missing-terms boxes. Alt: bridged USD-U adds BRIDGE-B before the issuer path; a shared symbol does not erase dependencies.
bridged USD-U adds BRIDGE-B before the issuer path; a shared symbol does not erase dependencies.
390px stacked rows with complete text equivalent; 768px/desktop render acceptance pending
RTL prose; identifiers and number units remain LTR; preserve factual arrow directions
FIX-P01-L07
Sources & claim boundaries
CIRCLE · PRIMARY_DOCUMENTATION
Circle transparency
- Supported claim
- Issuer reserve disclosures; statements are attributed, not independently audited here.
- Verification boundary
- Primary page inspected for the stated mechanism or attributed publication; does not authenticate illustrative data.
- Checked at
- 2026-10-01
https://www.circle.com/transparency
CIRCLEID · PRIMARY_DOCUMENTATION
Circle USDC contract addresses
- Supported claim
- Issuer-published network-specific identifiers, not a safety guarantee.
- Verification boundary
- Primary page inspected for the stated mechanism or attributed publication; does not authenticate illustrative data.
- Checked at
- 2026-10-01
https://developers.circle.com/stablecoins/usdc-contract-addresses
BRIDGE · PRIMARY_DOCUMENTATION
Ethereum bridge overview
- Supported claim
- Bridge representations and additional trust/security dependencies.
- Verification boundary
- Primary page inspected for the stated mechanism or attributed publication; does not authenticate illustrative data.
- Checked at
- 2026-10-01
https://ethereum.org/en/bridges/
Dataset provenance
id: FIX-P01-L07
dataStatus: ILLUSTRATIVE
source: Original teaching fixture embedded below; not externally observed
observedAt: null
timeBasis: SIM/T markers are fictional; no real timestamp or chain observation
scope: Invalid training labels; no usable wallet, key or signature