Skip to main content
AVOID.NET
← CoinDCX7 versions

Version history

Every immutable snapshot of CoinDCX. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.

Compare→
  1. v7currentTrust score: 622026-11-03 23:21:11Z

    Community evidenceA moderator accepted a piece of community-submitted evidence: Decrypt confirms CoinDCX acknowledged a 15.99M USDT loss on Tron on Oct 21 after its CEO called it a false alarm, and ZachXBT's April/May sweeping claim. Trust score now 62.

    hash: 9b56xX65uDTf…changes from v6
  2. v6Trust score: 642026-11-03 23:21:10Z

    Community evidenceA moderator accepted a piece of community-submitted evidence: Cointelegraph confirms ~$16M of flagged transfers, CoinDCX's shifting explanation (compromised July 2025 addresses, then failed sweep process), and ZachXBT's challenge. Trust score now 64.

    hash: 9hqQBurzNxXP…changes from v5
  3. v5Trust score: 662026-11-03 23:19:51Z

    Community evidenceA moderator accepted a piece of community-submitted evidence: crypto.news confirms Darcy's flag of ~15.99M USDT, CEO Gupta's denial, ZachXBT's $15.8M allegation, and that no new breach is independently confirmed. Ambiguous, neutral context. Trust score now 66.

    hash: 5rDifGm6Piae…changes from v4
  4. v4Trust score: 662026-11-02 00:08:20Z

    Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the trust score was recalculated from the page's findings, 62 → 66.

    hash: b55cd4c97d7b…changes from v3
  5. v3Trust score: 662026-11-02 00:08:20Z

    Score recalculatedRecalculated after the fact-check of 2026-11-02. Rescored under Scoring v2, the published formula (avoid.net/scoring): 62 → 66. Problems weighed by who is responsible: incidents the subject suffered −16, concerns that are not fraud −6.4, problems around the subject, caused by others −1.8; legitimacy credit long-running +10, regulated +5; 2 section(s) set aside until a failed fact-check is resolved.

    hash: b55cd4c97d7b…changes from v2
  6. v2Trust score: 622026-10-27 06:14:53Z

    Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 38 → 62. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −6.4, problems around the subject, caused by others −2.1; legitimacy credit long-running +10, regulated +5; the penalty for incidents it suffered is capped at 20.

    hash: e9e4c3505b4c…changes from v1
  7. v1Trust score: 382026-10-27 06:14:53Z

    Before rewriteThe page as it stood just before its Scoring v2 rescore; the next version says why.

    hash: 0364ac0b4f17…