LIVEBTC $84,208 ↗ +4.85%ETH $2,713 ↗ +5.46%SOL $115.80 ↗ +7.18%XRP $1.49 ↗ +8.02%BNB $783.36 ↗ +4.61%HYPE $95.37 ↗ +4.86%ZEC $1,533 ↗ +6.64%STRK $0.05 ↗ +3.24%BTC $84,208 ↗ +4.85%ETH $2,713 ↗ +5.46%SOL $115.80 ↗ +7.18%XRP $1.49 ↗ +8.02%
Monday, September 21, 202610:49 UTC
Corrections

Getting it wrong

Every publication gets things wrong. What separates them is what happens next. This page says what happens here.

How a correction is marked

When a story is corrected, the change is made on the story itself and the time it was made is recorded. The Updated stamp beneath a byline means the text changed after publication — it is not a freshness badge, and it is not applied for typographical fixes that leave the meaning alone.

Silent edits are not the practice here. A substantive change to what a story claims carries a note saying what changed. A story that turns out to be wrong in its central claim is corrected rather than quietly deleted; the URL keeps working.

What counts as substantive

  • A figure, date, name or jurisdiction that was wrong.
  • A claim attributed to the wrong person, company or document.
  • A characterisation the underlying source does not support.
  • A source link that pointed at the wrong story.

Why errors are likelier here

Chainpress does not claim individual editorial sign-off on each item, and it does not print a claim of review it cannot stand behind. Treat what you read as you would any unreviewed source: the facts should be verifiable in the reporting credited at the foot of each story, and where they are not, the story is wrong and is worth reporting.

Aggregated headlines are a different case. Those are the publisher’s own headline and summary, carried unchanged with a link back — a mistake in one is theirs to fix, though telling us means the card comes down. How Chainpress works sets out the distinction.

Reporting one

No corrections address is published yetThere is no mailbox behind this site, and printing an address that bounces would make this process look real while being unusable — which is worse than saying so. This is an open dependency, recorded here rather than hidden. For the site owner: NEXT_PUBLIC_CONTACT_EMAIL is the setting, and every contact route on the site — corrections, publisher removal, privacy — goes live the moment it points at an inbox that receives mail.

If you are a publisher

Removal →

A request to remove your reporting from this site is handled separately from a correction, needs no justification, and is set out in full on the Source Network page.