MCAP $2.77T ▼ 2.39% 24H VOL $64.1B BTC.D 60.2% FEAR & GREED 59 Greed BTC FEE 1 sat/vB BTC $82,766 ▲ 1.42% ETH $2,432 ▲ 1.03% USDT $0.9994 ▲ 0.02% BNB $727.06 ▲ 1.02% XRP $1.31 ▲ 1.58% USDC $0.9999 ▲ 0.01% SOL $105.70 ▲ 2.19% TRX $0.3313 ▼ 0.53% FIGR_HELOC $1.08 ▲ 0.74% ZEC $1,163 ▲ 2.90%

Editorial standards

These standards describe what the desk accepts as evidence, how it checks a claim, and what it refuses to publish.

Last reviewed 13 Oct 2026

What counts as a source

A source is a named publication, a regulator, or an official project channel with a feed the desk can read. Outlets that only republish another outlet are treated as the same voice, not as extra confirmation.

A story needs at least two independent publisher websites, or one publisher plus a separate primary source such as a regulator notice or official project post. At least one publisher must be in the desk’s higher trust tiers. The operator can raise these minimums. Website identity is a practical check, not proof that reports were produced independently.

How claims are checked

The writing response lists individual claims with an entity, a field, a value and a date where available. Local checks require each quote to appear in its source and support the stated value, entity, event type and date. In this site’s fact sheets, verified means the claim passed those source checks; it does not mean an independent human investigation confirmed it.

Every number that appears in a story is compared with a stored claim or a stored data value before publication. If a number does not match, the story is rejected and the reasons are logged.

The writing must cite a confirmed claim or data value in each paragraph. A similarity check compares the text with the source articles and with our own recent stories to keep the wording original.

What the desk will not publish

Unattributed price predictions, trading advice, invented quotes, unnamed sourcing, or causal claims that the data does not support. A named analyst’s forecast must remain clearly attributed and uncertain. Sponsored posts and press releases are not used as the basis of a story.

If the desk cannot verify an event, it records the event on the relevant profile timelines without creating a story page.

When we get something wrong

New information is attached to the same story page as a dated update. When a claim was wrong, the page carries a correction that states what changed and when. The corrections page lists how this works and the log stays public on the story itself.

How our AI desk works Editorial standards Contact