Editorial standards

• Bitcoin protocol, consensus, fees, and network health.
• Mining, difficulty, hashrate, hosting, and power markets.
• Lightning / L2s where they materially use or affect Bitcoin.
• Wallets, custody, and infrastructure that matter for actual users.
• Regulation, taxation, accounting, and enforcement that directly touch BTC.

• Altcoin, NFT, and generic “web3” coverage with no clear Bitcoin impact.
• Price targets, leverage calls, and “next 10x” trading content.
• Puff pieces whose only purpose is marketing a token or stock.
• Pure politics that doesn't materially affect Bitcoin users or infrastructure.

We may mention non-Bitcoin stories only when they have a real spillover into Bitcoin's legal, regulatory, or liquidity environment.

• “Not your keys, not your coins” is treated as the baseline.
• Custodial services are covered as risk-bearing infrastructure, not the default way to use Bitcoin.
• We highlight counterparty risk, surveillance risk, and operational fragility instead of pretending they don't exist.

We accept industrial-scale mining, but the north star is resilience and credible neutrality, not nostalgia.

• Preference for geographically and energy-diverse hashrate.
• Close attention to pool, jurisdiction, and manufacturing concentration.
• Coverage of grid interactions, flexible load deals, and the real economics miners face.

• Real usage: remittances, savings in weak currencies, circular economies.
• Infrastructure that helps people hold and use Bitcoin safely.
• Corporate and institutional moves that actually involve holding or securing BTC, not just slapping a ticker in a press release.

Default values: pro-privacy, anti–mass surveillance, skeptical of overreaching KYC and data collection.

• Explain the rules clearly: what the law says and how it bites in practice.
• Focus on incentives and realistic paths for change.
• Treat states, corporations, and NGOs as adversarial actors, not saviours or cartoon villains.

Submissions do not go straight onto the site. There is always an editor in the loop.

The data job, which runs once a day on the Data Desk, is the one routine that files figures into the record without a person reading them first. Today it files six things by itself: the weekly pool block-share sample; Strategy’s row in Company treasuries, only when the filing’s own table states the holding and every rule in the job’s method holds, else the row waits for a person; the claims floor, recomputed from that row when it moves; each difficulty retarget, once its block is six deep; a node software release, and a Bitcoin Core release line’s end of life; and a credit of two bitcoin or more to El Salvador’s disclosed wallet. Every Wire, Story and Brief is read by an editor before it goes live. An editor can switch off its publishing, or hold one dataset; a held dataset keeps its last figure and date.

• No paid token coverage disguised as editorial.
• Sponsorships, if they exist, are clearly labelled as such.
• Material conflicts (equity, token exposure, advisory roles) must be disclosed in or alongside coverage.
• Material errors get explicit, timestamped corrections. We do not silently edit core facts.
• An unused source becomes eligible for deletion after seven days; a source used in published work is kept with it.