21Relay

Trust and accountability

Editorial standards, reviewers and corrections

21Relay publishes its review method so readers can judge the material, report problems and understand the limits of the platform.

Source hierarchy

Protocol claims are checked first against BIPs, Bitcoin Core documentation and source code, the Bitcoin white paper, and other original technical material. Secondary explainers may provide context but do not override primary sources.

Review ownership

21Relay is the publisher and current editorial reviewer. No independent external technical reviewer is claimed. Material reviews and source changes are recorded by the project before publication.

Editorial boundaries

Content separates consensus rules from relay policy, facts from estimates, and education from financial opinion. It avoids price predictions, product endorsements and claims of guaranteed privacy or returns.

Data transparency

Live metrics identify their source, update time and unavailable or cached state. Estimates remain labelled as estimates and should not be treated as authoritative network totals.

Corrections workflow

  1. 1. Triage: submissions are checked for a reproducible page, claim or data issue.
  2. 2. Verify: factual reports are compared with the strongest available primary source.
  3. 3. Correct: material errors are amended promptly; minor clarity changes enter the normal editorial queue.
  4. 4. Record: significant corrections are documented on this page when they affect the meaning of published material.

Target response standard: acknowledge actionable reports during the next editorial review cycle. Safety-critical errors receive priority. A submission is not a promise that the suggested change will be accepted.

Corrections log

No material published corrections are recorded yet. This log will identify the affected page, correction date and nature of any substantive change.

Report a correction

Educational disclaimer

21Relay provides general Bitcoin education and planning tools, not financial, legal, tax or investment advice. Examples and estimates are not predictions or guarantees.

Privacy

The public V1 experience requires no account. Learning progress is stored locally in the current browser, and public tools never need seed phrases or private keys. The correction form asks for no name or email.

Data-source limits

Third-party APIs can be delayed, unavailable or revised. Cached and estimated values are labelled and should be independently verified before consequential use.

Last internal editorial and structural review: 17 August 2026