Editorial policy

1 · How a topic enters the pipeline

Topics come from three places. Reader email — corrections and topic requests. Primary documents — new attestation letters, regulator releases, court filings, exchange policy updates. Gaps between the published numbers and the marketing claim — an unexpected fee buried in a schedule, a bridge route the official table glosses over, a withdrawal allowance that does not match the help-page promise.

If we cannot say what an article would add beyond what the issuer already publishes, the topic is dropped.

2 · Every operational number is sourced and dated

Every operational claim is tied to a verifiable source. When a piece talks about a fee figure, a bridge speed, a CEX confirmation count or a withdrawal allowance, it is compiled from the platform's published fee schedule, on-chain records and public incident reports, and the figure is quoted in the article with the date the data was read. Figures that move in real time — gas, P2P spreads, yield — are flagged as illustrative snapshots, not promises. Where a number cannot be confirmed against its source, it is left out. We do not republish another site's comparison table.

3 · Source rules for the figures we use

Key figures are tied to one of these source categories wherever we can:

• Primary attestation or audit. Tether's BDO quarterly attestation. Circle's monthly attestation. Paxos monthly. First Digital Trust monthly. MakerDAO end-of-month collateral snapshot.
• Regulator release. SEC, CFTC, NYAG, NYDFS, FinCEN, OFAC, FCA, ESMA, MAS, HKMA, SFC, FSA.
• On-chain. Etherscan, TRONSCAN, Solscan, BscScan, Arbiscan. The transaction hash referenced is public and recorded.
• Platform-published. Each exchange or bridge's own fee schedule, withdrawal-limit page and status/incident reports.
• Third-party tracker. DeFiLlama, CoinGecko, CoinMarketCap, Dune query. Used only as cross-check, not as the only source.

News outlets and second-hand reporting are not sources. If a Bloomberg or Reuters piece points at a primary document, we read that document and cite it directly.

4 · Risk language

Risk does not get buried at the foot of a piece; we try to put it near the top. What we aim for:

• If the article describes any token that has historically depegged, the depeg low and the date sit in the lead section.
• If the article touches a chain or bridge that has had a major exploit, the exploit and the dollar size of the loss are named the first time the chain is referenced.
• If a yield figure appears, the source (CEX product, DeFi pool, RWA strategy) and its smart-contract or custodial risk are named in the same paragraph.
• If the operation is restricted in a jurisdiction we know about, that restriction is noted, not omitted.

5 · Tone

Short sentences. Specific verbs. Documents named by document. No hype. No "as we all know". No "ultimate" anything. If we cannot say something plainly, the paragraph is not finished.

6 · Corrections

Three rules, repeated from the corrections page for clarity:

• If we are wrong on a fact, we fix the article once the error is confirmed and add an entry to the corrections page.
• The corrections entry carries the date, the article URL, the old line, the new line and the reason.
• We do not silently rewrite history.

7 · Conflicts of interest

StableDesk takes part in the Binance referral programme and may earn a commission when readers sign up through it. That is the only commercial relationship on the site. It is disclosed on the disclaimer and in the note under the referral-code box wherever the code appears.

No issuer pays the desk. No exchange other than Binance pays the desk. No project provides "marketing tokens" in exchange for coverage. If a future commercial relationship is added, it goes on this page first.