Academy pathway 07 · self-guided beta

Risk Navigation

Trace custody, contract control, oracle, bridge, governance, stablecoin, leverage, liquidity, and communication risk as separate evidence lanes.

the question

Which failure paths sit underneath a token before price reacts?

The reading material and fixed self-check are available now. The project is a guided brief only. There is no upload, grading, instructor review, cohort, paid enrollment, certification, or accreditation.

Level: advanced
Lessons: 4
Delivery: Self-guided beta
Advice: None

learning outcomes

What you should be able to demonstrate

01
Build a product-specific risk map without compressing every dependency into an opaque score.
02
Separate observed control capability from intent, safety, audit quality, and legal enforceability.
03
Write an incident analysis that preserves timing, sources, affected dependencies, controls, and unresolved questions.

lesson soundings

Follow each question into the instrument

Every lesson ends with an evidence practice and a source-backed Bathymark destination.

01
lesson 1
Control and governance
Who can change the code, permissions, supply, or emergency state?
- Proxy administrators, owners, multisigs, timelocks, role holders, and governance executors are different control paths.
- A recognized capability can show who may upgrade, pause, mint, freeze, or change an oracle under the observed interface.
- It cannot prove signer identity, future intent, review quality, or the absence of nonstandard control logic.
Evidence practice
Trace one product's control path and list every capability, source, fixed block, and unresolved interface.
Open The HelmInspect source-backed contract control observations.
Sources and limits for this lesson
- Bathymark The HelmAn unresolved control path is not evidence that a contract is immutable.
- Bathymark Intelligence GraphA mapped relationship does not prove solvency, signer identity, legal enforceability, or the absence of an unrecognized dependency.
- Ethereum Developer DocumentationProtocol documentation does not assess a specific token, contract deployment, or investment outcome.
02
lesson 2
Oracle and bridge dependencies
Which shared service can widen the blast radius?
- A product can depend on a price feed, bridge, chain, issuer, custodian, transfer agent, or redemption provider.
- Shared dependencies create concentration and contagion even when the product contracts differ.
- A mapped address without a reviewed live adapter remains a dependency map, not a freshness conclusion.
Evidence practice
Find one shared dependency and list the products that would require review if it changed.
Open the dependency graphTrace product relationships and explicit limits.
Sources and limits for this lesson
- Bathymark Intelligence GraphA mapped relationship does not prove solvency, signer identity, legal enforceability, or the absence of an unrecognized dependency.
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
03
lesson 3
Exit and stress
Can the holder use the market, primary redemption, both, or neither?
- Secondary exit depends on route, size, liquidity, spread, price impact, venue concentration, and observation time.
- Primary redemption depends on eligibility, minimum size, fees, cutoff, settlement, rails, and whether the terms are contractual or unclear.
- A historical peg observation can describe prior stress, but sparse samples cannot reconstruct continuous market behavior.
Evidence practice
Write separate market-exit and primary-redemption classifications for one product, then name what remains unknown.
Open Exit SoundingCompare observed market routes with published redemption terms.
Sources and limits for this lesson
- Bathymark Exit SoundingA quote is a point-in-time simulation. It does not guarantee later execution or holder eligibility.
- Bathymark Stablecoin MonitorA market-price observation cannot prove reserves, solvency, legal rights, or universal redemption access.
- Bathymark Product RiskObserved public risk fields are not a complete legal, custody, security, or counterparty review.
04
lesson 4
Incident and communication
How do you report a failure without inventing cause or certainty?
- Separate what happened, when it happened, when Bathymark observed it, and which dependencies may be affected.
- A transaction, pause, role change, source change, or market shock can be observed before motive and impact are known.
- Corrections, source limits, conflicts, and unresolved questions remain visible throughout the incident record.
Evidence practice
Draft a short incident receipt with supports, cannot-prove fields, affected products, and next verification step.
Open Notice to MarinersInspect source-backed material-event receipts.
Sources and limits for this lesson
- Bathymark Notice to MarinersNo recorded event does not prove that no historical or unrecognized change occurred.
- Bathymark Product RiskObserved public risk fields are not a complete legal, custody, security, or counterparty review.
- FINRA Crypto and Blockchain Education ProgramBathymark is not affiliated with FINRA and this curriculum is not FINRA training or approval.
- ASIC: Discussing Financial Products and Services OnlinePublic guidance is not legal advice and does not determine the status of a specific product communication.

private progress

Mark what you have worked through

Loading locally

This checklist stays in this browser. There is no account, streak, ranking, grading, or credential.

guided project · no submission

A product incident analysis

Create an evidence-led risk and incident review for one product without inferring safety from missing data.

Brief available · review planned

Deliverables

Identity, economic claim, control, dependencies, exit routes, and current source freshness.
An event timeline separating effective, observed, and publication times.
Affected-product and shared-dependency analysis.
Prevention, detection, response controls, unresolved questions, and correction policy.

Evidence gate

Every factual claim names its source and links to it.
Every market observation includes the observation time or source cadence.
Every number includes a unit, denominator, and calculation path where derived.
Missing inputs remain missing and do not become zero, calm, flat, or safe.
The conclusion includes a limit and a measurable condition that would change it.

Bathymark does not currently accept, grade, review, or certify this project. Keep your work locally or publish it through a tool whose terms and source rights you have reviewed.

deterministic self-check

Test the evidence boundary

Choose an answer, then check it. These fixed questions do not call a model and do not produce a grade or credential.

01Bathymark does not recognize a contract's upgrade mechanism. What can it conclude?

The contract is immutableThe product is safeThe control path is unresolved and manual source review is required

02A one-million-dollar quote succeeded at a recorded block. What does it support?

A guaranteed later exitA point-in-time route simulation under the stated assumptionsUniversal primary redemption eligibility

evidence shelf

Sources for this pathway

Each source has a narrow job. Its limit remains attached so a lesson cannot claim more than the evidence supports.

bathymark

Bathymark Data Sources

Reviewed 2026-07-11

Supports

The open sources, cadence, runtime role, and redistribution boundaries used by Bathymark.

Does not prove

Public availability does not make every source complete, current, or suitable for raw redistribution.

bathymark

Bathymark Stablecoin Monitor

Reviewed 2026-07-11

Supports

Reference-aware stablecoin supply and peg observations with instrument taxonomy and source limits.

Does not prove

A market-price observation cannot prove reserves, solvency, legal rights, or universal redemption access.

bathymark

Bathymark Exit Sounding

Reviewed 2026-07-11

Supports

Stored standardized direct-market quote observations and separately sourced primary-redemption terms.

Does not prove

A quote is a point-in-time simulation. It does not guarantee later execution or holder eligibility.

bathymark

Bathymark Intelligence Graph

Reviewed 2026-07-11

Supports

Mapped product control, dependency, oracle, redemption, and source relationships.

Does not prove

A mapped relationship does not prove solvency, signer identity, legal enforceability, or the absence of an unrecognized dependency.

bathymark

Bathymark The Helm

Reviewed 2026-07-11

Supports

Recognized control paths, proxy state, ownership reads, roles, and fixed-block observations.

Does not prove

An unresolved control path is not evidence that a contract is immutable.

bathymark

Bathymark Product Risk

Reviewed 2026-07-11

Supports

Source-backed observations across product, peg, exploit, exit, and dependency risk.

Does not prove

Observed public risk fields are not a complete legal, custody, security, or counterparty review.

bathymark

Bathymark Notice to Mariners

Reviewed 2026-07-11

Supports

Stored material control and source-document changes after a valid comparable observation.

Does not prove

No recorded event does not prove that no historical or unrecognized change occurred.

official guidance

Ethereum Developer Documentation

Reviewed 2026-07-11

Supports

First-party explanations of Ethereum accounts, transactions, blocks, gas, nodes, and smart contracts.

Does not prove

Protocol documentation does not assess a specific token, contract deployment, or investment outcome.

official guidance

FINRA Crypto and Blockchain Education Program

Reviewed 2026-07-11

Supports

A neutral education model covering digital-asset foundations, products, risks, fraud, and applied scenarios.

Does not prove

Bathymark is not affiliated with FINRA and this curriculum is not FINRA training or approval.

official guidance

ASIC: Discussing Financial Products and Services Online

Reviewed 2026-07-11

Supports

Australian guidance on factual information, recommendations, opinions, misleading conduct, and financial-services licensing boundaries.

Does not prove

Public guidance is not legal advice and does not determine the status of a specific product communication.

sounding open dataReading the waterlineLive sources are loading. Nothing is filled with placeholder market data.

Academy pathway 07 · self-guided beta

Risk Navigation

Trace custody, contract control, oracle, bridge, governance, stablecoin, leverage, liquidity, and communication risk as separate evidence lanes.

the question

Which failure paths sit underneath a token before price reacts?

Level: advanced
Lessons: 4
Delivery: Self-guided beta
Advice: None

learning outcomes

What you should be able to demonstrate

01
Build a product-specific risk map without compressing every dependency into an opaque score.
02
Separate observed control capability from intent, safety, audit quality, and legal enforceability.
03
Write an incident analysis that preserves timing, sources, affected dependencies, controls, and unresolved questions.

lesson soundings

Follow each question into the instrument

Every lesson ends with an evidence practice and a source-backed Bathymark destination.

01
lesson 1
Control and governance
Who can change the code, permissions, supply, or emergency state?
- Proxy administrators, owners, multisigs, timelocks, role holders, and governance executors are different control paths.
- A recognized capability can show who may upgrade, pause, mint, freeze, or change an oracle under the observed interface.
- It cannot prove signer identity, future intent, review quality, or the absence of nonstandard control logic.
Evidence practice
Trace one product's control path and list every capability, source, fixed block, and unresolved interface.
Open The HelmInspect source-backed contract control observations.
Sources and limits for this lesson
- Bathymark The HelmAn unresolved control path is not evidence that a contract is immutable.
- Bathymark Intelligence GraphA mapped relationship does not prove solvency, signer identity, legal enforceability, or the absence of an unrecognized dependency.
- Ethereum Developer DocumentationProtocol documentation does not assess a specific token, contract deployment, or investment outcome.
02
lesson 2
Oracle and bridge dependencies
Which shared service can widen the blast radius?
- A product can depend on a price feed, bridge, chain, issuer, custodian, transfer agent, or redemption provider.
- Shared dependencies create concentration and contagion even when the product contracts differ.
- A mapped address without a reviewed live adapter remains a dependency map, not a freshness conclusion.
Evidence practice
Find one shared dependency and list the products that would require review if it changed.
Open the dependency graphTrace product relationships and explicit limits.
Sources and limits for this lesson
- Bathymark Intelligence GraphA mapped relationship does not prove solvency, signer identity, legal enforceability, or the absence of an unrecognized dependency.
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
03
lesson 3
Exit and stress
Can the holder use the market, primary redemption, both, or neither?
- Secondary exit depends on route, size, liquidity, spread, price impact, venue concentration, and observation time.
- Primary redemption depends on eligibility, minimum size, fees, cutoff, settlement, rails, and whether the terms are contractual or unclear.
- A historical peg observation can describe prior stress, but sparse samples cannot reconstruct continuous market behavior.
Evidence practice
Write separate market-exit and primary-redemption classifications for one product, then name what remains unknown.
Open Exit SoundingCompare observed market routes with published redemption terms.
Sources and limits for this lesson
- Bathymark Exit SoundingA quote is a point-in-time simulation. It does not guarantee later execution or holder eligibility.
- Bathymark Stablecoin MonitorA market-price observation cannot prove reserves, solvency, legal rights, or universal redemption access.
- Bathymark Product RiskObserved public risk fields are not a complete legal, custody, security, or counterparty review.
04
lesson 4
Incident and communication
How do you report a failure without inventing cause or certainty?
- Separate what happened, when it happened, when Bathymark observed it, and which dependencies may be affected.
- A transaction, pause, role change, source change, or market shock can be observed before motive and impact are known.
- Corrections, source limits, conflicts, and unresolved questions remain visible throughout the incident record.
Evidence practice
Draft a short incident receipt with supports, cannot-prove fields, affected products, and next verification step.
Open Notice to MarinersInspect source-backed material-event receipts.
Sources and limits for this lesson
- Bathymark Notice to MarinersNo recorded event does not prove that no historical or unrecognized change occurred.
- Bathymark Product RiskObserved public risk fields are not a complete legal, custody, security, or counterparty review.
- FINRA Crypto and Blockchain Education ProgramBathymark is not affiliated with FINRA and this curriculum is not FINRA training or approval.
- ASIC: Discussing Financial Products and Services OnlinePublic guidance is not legal advice and does not determine the status of a specific product communication.

private progress

Mark what you have worked through

Loading locally

This checklist stays in this browser. There is no account, streak, ranking, grading, or credential.

guided project · no submission

A product incident analysis

Create an evidence-led risk and incident review for one product without inferring safety from missing data.

Brief available · review planned

Deliverables

Identity, economic claim, control, dependencies, exit routes, and current source freshness.
An event timeline separating effective, observed, and publication times.
Affected-product and shared-dependency analysis.
Prevention, detection, response controls, unresolved questions, and correction policy.

Evidence gate

Every factual claim names its source and links to it.
Every market observation includes the observation time or source cadence.
Every number includes a unit, denominator, and calculation path where derived.
Missing inputs remain missing and do not become zero, calm, flat, or safe.
The conclusion includes a limit and a measurable condition that would change it.

Bathymark does not currently accept, grade, review, or certify this project. Keep your work locally or publish it through a tool whose terms and source rights you have reviewed.

deterministic self-check

Test the evidence boundary

Choose an answer, then check it. These fixed questions do not call a model and do not produce a grade or credential.

01Bathymark does not recognize a contract's upgrade mechanism. What can it conclude?

The contract is immutableThe product is safeThe control path is unresolved and manual source review is required

02A one-million-dollar quote succeeded at a recorded block. What does it support?

A guaranteed later exitA point-in-time route simulation under the stated assumptionsUniversal primary redemption eligibility

evidence shelf

Sources for this pathway

Each source has a narrow job. Its limit remains attached so a lesson cannot claim more than the evidence supports.

bathymark

Bathymark Data Sources

Reviewed 2026-07-11

Supports

The open sources, cadence, runtime role, and redistribution boundaries used by Bathymark.

Does not prove

Public availability does not make every source complete, current, or suitable for raw redistribution.

bathymark

Bathymark Stablecoin Monitor

Reviewed 2026-07-11

Supports

Reference-aware stablecoin supply and peg observations with instrument taxonomy and source limits.

Does not prove

A market-price observation cannot prove reserves, solvency, legal rights, or universal redemption access.

bathymark

Bathymark Exit Sounding

Reviewed 2026-07-11

Supports

Stored standardized direct-market quote observations and separately sourced primary-redemption terms.

Does not prove

A quote is a point-in-time simulation. It does not guarantee later execution or holder eligibility.

bathymark

Bathymark Intelligence Graph

Reviewed 2026-07-11

Supports

Mapped product control, dependency, oracle, redemption, and source relationships.

Does not prove

A mapped relationship does not prove solvency, signer identity, legal enforceability, or the absence of an unrecognized dependency.

bathymark

Bathymark The Helm

Reviewed 2026-07-11

Supports

Recognized control paths, proxy state, ownership reads, roles, and fixed-block observations.

Does not prove

An unresolved control path is not evidence that a contract is immutable.

bathymark

Bathymark Product Risk

Reviewed 2026-07-11

Supports

Source-backed observations across product, peg, exploit, exit, and dependency risk.

Does not prove

Observed public risk fields are not a complete legal, custody, security, or counterparty review.

bathymark

Bathymark Notice to Mariners

Reviewed 2026-07-11

Supports

Stored material control and source-document changes after a valid comparable observation.

Does not prove

No recorded event does not prove that no historical or unrecognized change occurred.

official guidance

Ethereum Developer Documentation

Reviewed 2026-07-11

Supports

First-party explanations of Ethereum accounts, transactions, blocks, gas, nodes, and smart contracts.

Does not prove

Protocol documentation does not assess a specific token, contract deployment, or investment outcome.

official guidance

FINRA Crypto and Blockchain Education Program

Reviewed 2026-07-11

Supports

A neutral education model covering digital-asset foundations, products, risks, fraud, and applied scenarios.

Does not prove

Bathymark is not affiliated with FINRA and this curriculum is not FINRA training or approval.

official guidance

ASIC: Discussing Financial Products and Services Online

Reviewed 2026-07-11

Supports

Australian guidance on factual information, recommendations, opinions, misleading conduct, and financial-services licensing boundaries.

Does not prove

Public guidance is not legal advice and does not determine the status of a specific product communication.

Which failure paths sit underneath a token before price reacts?

What you should be able to demonstrate

Follow each question into the instrument

Control and governance

Oracle and bridge dependencies

Exit and stress

Incident and communication

Mark what you have worked through

A product incident analysis

Deliverables

Evidence gate

Test the evidence boundary

Sources for this pathway

Which failure paths sit underneath a token before price reacts?

What you should be able to demonstrate

Follow each question into the instrument

Control and governance

Oracle and bridge dependencies

Exit and stress

Incident and communication

Mark what you have worked through

A product incident analysis

Deliverables

Evidence gate

Test the evidence boundary

Sources for this pathway