Skip to content

Newsroom · 91 stories

Crypto News

Reporting on the markets, protocols, and policy shaping crypto — written by people, checked by editors.

Newsroom

Latest stories

What the news desk covers

Reporting on the parts of crypto that have consequences: market structure and flows, protocol changes and the engineering behind them, stablecoin issuance and the plumbing beneath it, and the policy decisions that reshape where and how any of it can operate. Every article carries a named author and a publication date, and the ones we revise carry the date of the revision too.

How these stories are sourced

Claims are built from primary material: protocol documentation, issuer disclosures, regulatory registers, published audit reports and the filings of the parties involved. Where a figure comes from a company about itself, the article says so. We do not report exploits, incidents or accusations from memory — where a project documents something itself, we cite it; where nothing is published, our silence means we found no source we were willing to print against.

Corrections

When we get something wrong we fix it and note the change rather than editing it away quietly. If a figure no longer matches its source, or you believe a claim is wrong, send the page address and the specific issue through our contact page and we will correct and re-date the piece. The full process is in our corrections policy.

What you will not find here

No price predictions and no trading calls. For the mechanics behind the stories, the Learn desk explains how the systems work; for services rather than events, the ratings score providers against published criteria.

Frequently asked questions

How often is crypto news published here?

Every article carries the date it was published and, where revised, the date of the revision. We do not promise a fixed publishing cadence we cannot guarantee — the date on the page is the honest record of how current it is.

Where do the facts in these articles come from?

Primary material: protocol documentation, issuer disclosures, regulatory registers, published audit reports and the filings of the parties involved. Where a figure comes from a company about itself, the article says so rather than presenting it as independent.

Do you report on hacks and exploits?

Only where the affected project documents the incident itself, in which case we cite it. We do not reconstruct security incidents from memory or from second-hand accounts, because a page about somebody else's security is the wrong place for an unsourced claim.