corrections

Corrections policy

If a reading is wrong, it should get easier to see what changed, not harder.

Open dataSource trailsNo paid rankingsUnknowns stay unknown

What this page answers

Bathymark corrects source mistakes, stale data, broken links, unclear limits, and methodology drift in public. Wrong calls are not removed from The Log, because the record is only useful if misses stay visible.

Contact Bathymark The public call record Methodology

Correction ledger fields

Every material correction should be structured enough for a reader to audit.

Field	Requirement	Why it matters
Date	When corrected	Separates the original read from the updated read
Page affected	Product, report, index, comparison, or source page	Shows scope
Issue type	Source error, stale source, broken link, classification change	Explains the failure mode
Original state	What the page said before	Prevents silent rewriting
Corrected state	What the page says now	Makes the change inspectable
Reason	Why it changed	Shows method, not mood
Source	Public link where possible	Keeps the correction sourced
Methodology impact	Yes or no	Flags changes that affect more than one page

Published correction receipt

This material interpretation change remains visible so screenshots and older references can be reconciled.

Field	2026-07-11 receipt
Date	2026-07-11 UTC
Pages affected	Stablecoin monitor and detail pages, product records, peg-stress indices, Almanac, reports, proof blocks, and generated analysis
Issue type	Instrument-classification and source-unit correction
Original state	Accumulating-NAV tokens including USYC, USDY, and reUSD could be interpreted mechanically against one dollar. The list endpoint circulation value was also described as token supply or reference-currency value.
Corrected state	USYC, USDY, and reUSD use accumulating-NAV treatment with no mechanical one-dollar verdict. Fixed-price rebasing units remain eligible. The list endpoint value is labelled circulating USD market value, while history remains token units.
Reason	Issuer mechanics distinguish variable-price yield accrual from fixed-price rebasing, and the DeFiLlama server computes the list circulation field as token units multiplied by current USD price.
Taxonomy boundary	peggedREAL maps to BRL. peggedVAR is a variable or custom target and is never treated as an ISO currency or sent to FX normalization.
Taxonomy version	2026-07-11.3
Methodology impact	Yes. Stablecoin analysis, metric definitions, aggregation, peg eligibility, confidence, and every downstream consumer were revised and regression-tested.

Evidence for the 2026-07-11 correction

Product mechanics are grounded in the official Circle USYC overview, Ondo USDY and rUSDY documentation, and Re Protocol reUSD documentation. The list-field unit is verified against the public DeFiLlama stablecoin server implementation.

What gets corrected

We correct factual errors, bad links, stale source labels, incorrect units, broken entity matches, and explanations that overstate what a number can mean.

What does not get rewritten

A resolved miss in The Log stays a miss. An old Dispatch can be annotated if a source or method changed, but the original market read should remain inspectable.

Method changes

Material changes to source choice, weighting, route shape, or signal thresholds are tracked through the public changelog and, when relevant, the methodology page.

commercial use case

Found a source error or stale read?

Send the page URL, source URL, timestamp, expected value, and observed value. Corrections improve the public record, not a private score.

Submit Correction Open The Log Methodology

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