Editorial standards
This page explains how technical and research content on the Bitroot website (bitroot.co) is selected, written, reviewed, and corrected. It exists so readers can see how pages are produced and how to report errors.
What this site publishes
Blog posts and guides on this site are written for developers and researchers. They describe protocol and engineering design—parallel EVM, consensus, and scaling trade-offs. The material is educational and technical. It is not financial, investment, legal, or tax advice, and it is not an offer to buy or sell any digital asset. See the Terms of Use for the full legal boundary.
Topic selection and information gain
We prioritize questions readers cannot answer from a quick search or a one-line docs blurb: design trade-offs, differences from related approaches, and architecture notes that can be checked. We avoid publishing near-duplicates just to inflate post count. Articles on neighboring topics should take distinct angles (for example overview versus deep mechanism), not the same essay under a new title.
Writing and human review
Drafts may use research tools and writing assistants, but nothing ships without human editing: technical claims, zh/en structural parity, real link targets and titles, and avoidance of empty parallel phrasing. We do not batch-publish templated shorts without review.
Performance numbers (TPS, finality, and similar) must state context—test environment, target, or observed result. Operational parameters that change by version (for example a specific RPC endpoint) should not be hard-coded when a link to an authoritative source is safer.
Release timing
The date field in article frontmatter is the planned or actual publish day. Drafts dated in the future do not appear in the blog list, the sitemap, or crawlable detail URLs until that day; they become visible through the normal build and release process. We prefer steady, checkable updates over exposing a pile of future-dated pages on the same day.
What we do not publish
- Investment advice, return promises, trading tips, or price commentary.
- Scraped or lightly rewritten third-party material with no added explanation.
- Invented authorship, fake endorsements, or false affiliations.
Corrections and feedback
If you find a factual error, a dead link, or a serious zh/en mismatch, email [email protected] with the page URL and a short description. After verification we will fix the page and, when appropriate, note the change through official channels.
For press or partnership requests, use the Media Contact page rather than the corrections mailbox.