// EDITORIAL POLICY

Every article is built on a base of primary documents, not aggregator summaries. We pull directly from regulator filings (SEC EDGAR, OFAC SDN, Federal Register), platform data (Steam, GitHub, on-chain transactions), economic series (Federal Reserve FRED, exchange order books), academic preprints (arXiv, OpenAlex), and vendor security advisories (CVE, CISA KEV, GitHub advisories). Secondary reporting is cited only when a primary source is unavailable, and only from outlets we'd link by name. If a claim isn't traceable to something we'd hand to a fact-checker, we don't make it.

Every numerical claim, dollar figure, percentage, date, and direct quotation in a published article is required to have an inline source URL, either in the same paragraph or the immediately preceding paragraph, that a reader can click and verify. Drafts where any specific claim lacks attribution are sent back for revision or killed. An unsupported number is the single biggest credibility risk in fast-moving news, and a wrong direct quote is defamation territory. We'd rather drop a claim than publish one we can't defend.

Articles that don't clear our review thresholds are not published. The current gates are:

• SEO & readability score ≥ 95/100, measured against tier-1 newsroom prose norms (lede length, sentence cadence, headline craft, source-anchor density).
• Primary source requirement: synthesis pieces must cite at least three primary documents from at least two source types (e.g. SEC filing + on-chain transaction + Federal Register notice).
• Plagiarism check: 8-gram overlap against the source corpus must be below 0.15. Anything higher is rewritten or killed.
• Claim grounding: every dollar figure, percentage, date, and direct quote in the body must have an inline citation in the same or previous paragraph (see above).

Articles are bylined to a named author who is responsible for the piece. Our current author is Dillon Nye. The byline is real and the author is reachable through the contact channels on this site.

When we make a factual mistake, we fix it and we say so. Every change to a published article, whether a correction, update, retraction, or clarification, is timestamped and logged on our public corrections page and surfaced on the affected article itself with a visible "Corrections & Updates" block. We also emit a CorrectionComment schema so search engines pick up the change. If you spot an error, email us via the contact page. We'd rather hear it from you than from a reader who lost trust because we missed it.

Some stories, like sanctions actions, exchange filings, and security advisories, have facts that change within hours. We flag these as live stories and re-check the original primary sources on a recurring schedule. If a flagged source has materially changed (a new SEC amendment, a formal OFAC SDN entry, a CISA catalog update), we publish an update with a visible "Updated [date]" banner on the article and log it on the corrections page. The original article body is preserved; updates are appended, never silently rewritten.

CryptoTechHQ does not currently run an affiliate program. No news article on this site contains affiliate links. If that changes, this section will be updated and any article carrying affiliate links will use rel="sponsored nofollow"with a visible disclosure at the top. We don't accept paid guest posts or ghost-written sponsorships.

CryptoTechHQ is self-funded and independently owned. No investor, publisher, or commercial partner influences what we cover or how we cover it. Rankings in our guides are based on product merit alone.