Verification standards
Fact-Checking Policy
Crypto facts decay fast. Supply counts change, exchange status changes, product pages move, posts disappear and communities rename channels. Our fact-checking process is built for that reality.
What we verify before publication
We verify names, project titles, token symbols, dates, supply figures, stated utilities, exchange names, chain IDs, explorer URLs, documentation links, social handles and any quoted public claims that can be checked against source material. When a number is self-reported, we say so. When a claim depends on an explorer, repo, listing page or archived page, we inspect that source directly.
How we confirm contentious points
We look for at least two independent confirmations for contested or consequential facts whenever the underlying data permits it. For example, an exchange update may be checked against an official notice and a project channel. A chain parameter may be checked against docs and a live explorer. A historical claim may be checked against a whitepaper, a legacy page and a dated community update. We do not present a single social post as settled truth when a stronger source is available.
Archived, deleted and legacy material
Archived pages are valid reporting tools when clearly identified as historical. We preserve dates, old URLs and the context in which the material originally appeared. Deleted pages, inaccessible apps and altered social posts are handled with care: we note the latest verifiable version we can inspect and avoid overclaiming beyond what the record supports.
Screenshots, social claims and community statements
Screenshots are checked against source pages when possible. Telegram, X, Medium and similar channels are treated as direct project communications, not neutral evidence. We use them to establish what was said and when it was said, then match those statements against documentation, explorer data, code, exchange pages or later corrections.
Updates, reader notices and error handling
Readers can flag factual concerns through info@egoncoin.com. We review correction requests promptly, re-check the cited material and update the article if the challenge is valid. Where an error changes interpretation, we add a dated correction note inside the story. Privacy or contact-data issues can also be sent to yash@egoncoin.com.