Academy pathway 04 · self-guided beta

On-Chain Laboratory

Learn the query, entity, timestamp, coverage, and versioning disciplines that keep an on-chain dashboard inspectable.

the question

How do you turn public blockchain records into a reproducible analysis?

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: intermediate
Lessons: 4
Delivery: Self-guided beta
Advice: None

learning outcomes

What you should be able to demonstrate

01
Define a blockchain question before selecting tables, labels, or charts.
02
Separate raw observations, derived calculations, entity assumptions, and narrative conclusions.
03
Publish a reproducible query receipt with range, chain, units, freshness, and limitations.

lesson soundings

Follow each question into the instrument

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

01
lesson 1
Start with a falsifiable question
Which chain observation would change your conclusion?
- A query should answer one bounded question, such as supply change, bridge flow, or protocol treasury movement.
- Chain, contract, block range, event signature, unit, and entity assumptions belong in the specification.
- A dashboard assembled before the question encourages decorative charts and post-hoc stories.
Evidence practice
Write a query specification without writing SQL: question, chain, contracts, range, fields, unit, and falsifier.
Inspect mapped entitiesStart from reviewed product identities and relationships.
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.
- Ethereum Developer DocumentationProtocol documentation does not assess a specific token, contract deployment, or investment outcome.
- Dune DocumentationDataset coverage, labels, query logic, and refresh timing still require review by the analyst.
02
lesson 2
Identity and labels are claims
When does an address become an issuer, exchange, bridge, or treasury?
- An address can be observed directly, while its identity usually comes from an official document, verified source, or analyst mapping.
- Labels can become stale, ambiguous, or overbroad. Their source and review time should travel with the result.
- Do not infer a real-world identity merely because an address behaves like a known entity.
Evidence practice
For one mapped contract, record the address source, identity claim, review date, and what the label cannot prove.
Open The HelmCompare fixed-block chain state with mapped product identity.
Sources and limits for this lesson
- Bathymark The HelmAn unresolved control path is not evidence that a contract is immutable.
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
- Ethereum Developer DocumentationProtocol documentation does not assess a specific token, contract deployment, or investment outcome.
03
lesson 3
Derive metrics with receipts
Can another analyst reproduce the displayed number?
- A derived metric needs source fields, transformations, unit, denominator, range, and missing-data behavior.
- Daily, weekly, and rolling windows produce different values even from the same transactions.
- Reorgs, duplicate events, decimals, token migrations, wrappers, and chain boundaries require explicit handling.
Evidence practice
Write the calculation receipt for one derived flow metric and include its zero-versus-missing rule.
Open source rulesInspect runtime, source, and redistribution boundaries.
Sources and limits for this lesson
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
- Bathymark MethodologyA methodology explains the method. It does not guarantee a market outcome.
- Dune DocumentationDataset coverage, labels, query logic, and refresh timing still require review by the analyst.
04
lesson 4
Publish the query, chart, and limit
What makes an on-chain dashboard evidence rather than decoration?
- The chart needs a real query, title, unit, date range, source, and annotation.
- A stable link, query version, update time, and limitation let another reader challenge the result.
- If the data source is incomplete, publish the gap instead of a clean-looking zero.
Evidence practice
Audit one live Bathymark table for title, unit, time, source, limitation, and a source-backed destination.
Audit Bathymark sourcesTrace a public reading back to its source role.
Sources and limits for this lesson
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
- Dune DocumentationDataset coverage, labels, query logic, and refresh timing still require review by the analyst.

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.

Start with a falsifiable questionIdentity and labels are claimsDerive metrics with receiptsPublish the query, chart, and limitGuided project: A reproducible on-chain dashboard specificationDeterministic self-check

guided project · no submission

A reproducible on-chain dashboard specification

Design a live analysis for stablecoin supply, bridge flow, or protocol treasury activity using a public query environment or owned indexer.

Brief available · review planned

Deliverables

Question, entity scope, chain, block or time range, source tables, and query version.
One real chart with title, unit, date range, source, and annotation.
A calculation receipt and missing-data policy.
A limitations section that separates observed addresses from attributed identities.

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.

01A public address repeatedly sends funds to an exchange deposit contract. What does the chain prove?

The address belongs to the exchangeThe transfer path is observable, while ownership attribution needs separate evidenceThe sender is a professional trader

02A query fails for one chain during a cross-chain flow calculation. What is the honest output?

Treat the failed chain as zero flowOmit the chain silentlyMark coverage incomplete and withhold any aggregate that requires the missing chain

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 Methodology

Reviewed 2026-07-11

Supports

Metric definitions, source discipline, known limits, and the boundary between information and financial advice.

Does not prove

A methodology explains the method. It does not guarantee a market outcome.

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 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.

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

Dune Documentation

Reviewed 2026-07-11

Supports

Public guidance for querying blockchain datasets, building visualizations, and sharing reproducible analyses.

Does not prove

Dataset coverage, labels, query logic, and refresh timing still require review by the analyst.

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

Academy pathway 04 · self-guided beta

On-Chain Laboratory

Learn the query, entity, timestamp, coverage, and versioning disciplines that keep an on-chain dashboard inspectable.

the question

How do you turn public blockchain records into a reproducible analysis?

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

learning outcomes

What you should be able to demonstrate

01
Define a blockchain question before selecting tables, labels, or charts.
02
Separate raw observations, derived calculations, entity assumptions, and narrative conclusions.
03
Publish a reproducible query receipt with range, chain, units, freshness, and limitations.

lesson soundings

Follow each question into the instrument

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

01
lesson 1
Start with a falsifiable question
Which chain observation would change your conclusion?
- A query should answer one bounded question, such as supply change, bridge flow, or protocol treasury movement.
- Chain, contract, block range, event signature, unit, and entity assumptions belong in the specification.
- A dashboard assembled before the question encourages decorative charts and post-hoc stories.
Evidence practice
Write a query specification without writing SQL: question, chain, contracts, range, fields, unit, and falsifier.
Inspect mapped entitiesStart from reviewed product identities and relationships.
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.
- Ethereum Developer DocumentationProtocol documentation does not assess a specific token, contract deployment, or investment outcome.
- Dune DocumentationDataset coverage, labels, query logic, and refresh timing still require review by the analyst.
02
lesson 2
Identity and labels are claims
When does an address become an issuer, exchange, bridge, or treasury?
- An address can be observed directly, while its identity usually comes from an official document, verified source, or analyst mapping.
- Labels can become stale, ambiguous, or overbroad. Their source and review time should travel with the result.
- Do not infer a real-world identity merely because an address behaves like a known entity.
Evidence practice
For one mapped contract, record the address source, identity claim, review date, and what the label cannot prove.
Open The HelmCompare fixed-block chain state with mapped product identity.
Sources and limits for this lesson
- Bathymark The HelmAn unresolved control path is not evidence that a contract is immutable.
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
- Ethereum Developer DocumentationProtocol documentation does not assess a specific token, contract deployment, or investment outcome.
03
lesson 3
Derive metrics with receipts
Can another analyst reproduce the displayed number?
- A derived metric needs source fields, transformations, unit, denominator, range, and missing-data behavior.
- Daily, weekly, and rolling windows produce different values even from the same transactions.
- Reorgs, duplicate events, decimals, token migrations, wrappers, and chain boundaries require explicit handling.
Evidence practice
Write the calculation receipt for one derived flow metric and include its zero-versus-missing rule.
Open source rulesInspect runtime, source, and redistribution boundaries.
Sources and limits for this lesson
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
- Bathymark MethodologyA methodology explains the method. It does not guarantee a market outcome.
- Dune DocumentationDataset coverage, labels, query logic, and refresh timing still require review by the analyst.
04
lesson 4
Publish the query, chart, and limit
What makes an on-chain dashboard evidence rather than decoration?
- The chart needs a real query, title, unit, date range, source, and annotation.
- A stable link, query version, update time, and limitation let another reader challenge the result.
- If the data source is incomplete, publish the gap instead of a clean-looking zero.
Evidence practice
Audit one live Bathymark table for title, unit, time, source, limitation, and a source-backed destination.
Audit Bathymark sourcesTrace a public reading back to its source role.
Sources and limits for this lesson
- Bathymark Data SourcesPublic availability does not make every source complete, current, or suitable for raw redistribution.
- Dune DocumentationDataset coverage, labels, query logic, and refresh timing still require review by the analyst.

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 reproducible on-chain dashboard specification

Design a live analysis for stablecoin supply, bridge flow, or protocol treasury activity using a public query environment or owned indexer.

Brief available · review planned

Deliverables

Question, entity scope, chain, block or time range, source tables, and query version.
One real chart with title, unit, date range, source, and annotation.
A calculation receipt and missing-data policy.
A limitations section that separates observed addresses from attributed identities.

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.

01A public address repeatedly sends funds to an exchange deposit contract. What does the chain prove?

The address belongs to the exchangeThe transfer path is observable, while ownership attribution needs separate evidenceThe sender is a professional trader

02A query fails for one chain during a cross-chain flow calculation. What is the honest output?

Treat the failed chain as zero flowOmit the chain silentlyMark coverage incomplete and withhold any aggregate that requires the missing chain

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 Methodology

Reviewed 2026-07-11

Supports

Metric definitions, source discipline, known limits, and the boundary between information and financial advice.

Does not prove

A methodology explains the method. It does not guarantee a market outcome.

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 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.

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

Dune Documentation

Reviewed 2026-07-11

Supports

Public guidance for querying blockchain datasets, building visualizations, and sharing reproducible analyses.

Does not prove

Dataset coverage, labels, query logic, and refresh timing still require review by the analyst.