Skip to main content
Sign in
Dash3 decisions on this page

Audit log

Every state-changing event for Dash: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1publishby system:backfill
    2026-05-14 06:02:33Z
    Score: ?? (no score change)
    anchoranchored
    chain
    mainnet-betaslot 419,628,924
    sig
    29dy1pLQ2X7t…vemnQuTmexplorer ↗
    hash
    1qTChYjH1iC2…YGBY7R7gsha256 → base58
    verifying row…full verify ↗
    canonical bytes (6161 B) ▸
    {"actor":"system:backfill","investigation_id":"8968605b-bdbe-4f99-97fd-36ef3c917306","kind":"publish","page_slug":"dash","published_at":"2026-05-14T06:02:33.579Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"Dash","sections":[{"content":"Dash was created by Evan Duffield and launched January 18, 2014 as XCoin, a fork of Litecoin's codebase. It was renamed Darkcoin, then rebranded to Dash ('Digital Cash') in March 2015. Duffield introduced masternodes — incentivized full nodes requiring 1,000 DASH collateral — as the first implementation of this concept in cryptocurrency. Duffield stepped back from day-to-day involvement around 2017.","heading":"Founder and Origins","severity":"low","sources":[{"credibility":2,"name":"Grokipedia: Dash Cryptocurrency","type":"other","url":"https://grokipedia.com/page/Dash_(cryptocurrency)"},{"credibility":2,"name":"Satoshi Watch: Dash by Evan Duffield","type":"other","url":"https://satoshiwatch.com/dash/"}]},{"content":"In the first 48 hours after launch (January 2014), approximately 1.9 million DASH (~10% of the 18.9M maximum supply) were mined. This 'instamine' resulted from an inherited low initial difficulty adjustment mechanism from Litecoin's codebase that delayed the first difficulty retarget until block 3,396 (~8 hours post-launch), allowing ~1.57M coins to be generated before normalizing. Duffield, himself one of the early miners, called it an accident but chose to continue rather than relaunch. Critics characterized the instamine as potentially deliberate, enabling a small group of early miners to accumulate substantial holdings.","heading":"Instamine Controversy","severity":"high","sources":[{"credibility":1,"name":"Bitcoin Magazine/Nasdaq: Closer Look at Origins of DASH","type":"news_article","url":"https://bitcoinmagazine.com/business/op-ed-closer-look-origins-dash-part-2"},{"credibility":2,"name":"CoinsPaid Media: Dash History and Criticism","type":"news_article","url":"https://coinspaidmedia.com/learn/what-dash-history-features-and-criticism/"}]},{"content":"Masternodes require 1,000 DASH collateral and provide governance voting rights plus block rewards. Centralization concerns exist: if masternode ownership is concentrated, privacy features and governance processes may be controlled by a small number of entities. The question of whether the majority of governance votes are potentially under the control of one entity remains unresolved.","heading":"Masternode Concentration Concerns","severity":"medium","sources":[{"credibility":1,"name":"Nasdaq: Battle of Privacy Coins — Dash Not Really Private","type":"news_article","url":"https://www.nasdaq.com/articles/battle-of-the-privacycoins:-why-dash-is-not-really-that-private-2018-09-06"}]},{"content":"Dash faces mounting regulatory pressure as a categorized 'privacy coin.' Gate.io removed DASH at end of 2024; Bybit deleted the DASH/USDT pair early 2025. The EU Anti-Money Laundering Regulation (effective July 2027) bans privacy coins from regulated platforms. FinCEN proposed rules (January 2025) mandating record-keeping for private coin transactions exceeding $500. However, Dash's opt-in PrivateSend (CoinJoin-based mixing) model provides an argument that mandatory privacy coins like Monero cannot make: the base layer is fully transparent, and PrivateSend can be disabled.","heading":"Privacy Coin Regulatory Pressure","severity":"high","sources":[{"credibility":2,"name":"TradersUnion: What Happened to Dash","type":"news_article","url":"https://tradersunion.com/news/editors-picks/show/307798-what-happened-to-dash/"},{"credibility":2,"name":"Financial Content: Dash Surges Amid Privacy Coin Scrutiny","type":"news_article","url":"https://markets.financialcontent.com/wral/article/breakingcrypto-2025-10-13-privacy-under-pressure-dash-surges-amidst-intensifying-regulatory-scrutiny-on-privacy-coins"}]}],"sources_used":[{"credibility":1,"name":"Bitcoin Magazine: Dash Origins","type":"news_article","url":"https://bitcoinmagazine.com/business/op-ed-closer-look-origins-dash-part-2"},{"credibility":1,"name":"Nasdaq: Dash Privacy Critique","type":"news_article","url":"https://www.nasdaq.com/articles/battle-of-the-privacycoins:-why-dash-is-not-really-that-private-2018-09-06"},{"credibility":2,"name":"Grokipedia: Dash","type":"other","url":"https://grokipedia.com/page/Dash_(cryptocurrency)"},{"credibility":2,"name":"TradersUnion: Dash History","type":"news_article","url":"https://tradersunion.com/news/editors-picks/show/307798-what-happened-to-dash/"}],"summary":"Dash (DASH) is a privacy-focused cryptocurrency launched January 2014 by Evan Duffield as a Litecoin fork (originally XCoin, then Darkcoin). The 'instamine' controversy is central to Dash's history: ~1.9M DASH (~10% of max supply) were mined in the first 48 hours due to a low difficulty adjustment bug inherited from Litecoin. Duffield called it accidental but chose to continue rather than relaunch. Masternode concentration concerns persist. Privacy coin regulatory pressure is mounting: Gate.io removed DASH end of 2024, Bybit deleted DASH/USDT early 2025. EU AML Regulation (effective July 2027) bans privacy coins from regulated platforms. Dash's opt-in PrivateSend model provides some regulatory flexibility vs. mandatory privacy coins.","timeline":[{"date":"2014-01-18","event":"Dash launches as XCoin; ~1.9M DASH (10% of max supply) instamined in first 48 hours","source":"bitcoinmagazine.com","source_url":"https://bitcoinmagazine.com/business/op-ed-closer-look-origins-dash-part-2"},{"date":"2015-03-01","event":"Darkcoin rebrands to Dash ('Digital Cash')","source":"grokipedia.com","source_url":"https://grokipedia.com/page/Dash_(cryptocurrency)"},{"date":"2024-12-01","event":"Gate.io removes DASH from trading","source":"tradersunion.com","source_url":"https://tradersunion.com/news/editors-picks/show/307798-what-happened-to-dash/"},{"date":"2025-01-01","event":"Bybit deletes DASH/USDT trading pair; FinCEN proposes $500 threshold record-keeping for privacy coins","source":"tradersunion.com","source_url":"https://tradersunion.com/news/editors-picks/show/307798-what-happened-to-dash/"}]},"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 106162dd-4263-4d0b-b9f3-64fcf9780131
  2. #2reviewby reviewerreviewer
    2026-08-27 10:51:44Z
    Score: 4545 (no score change)
    The page's core factual claims (founding history, instamine mechanics, masternode design, the EU AMLR ban, and the PrivateSend architecture) check out against independent sources, and none were found to be outright disputed. However, several claims in the regulatory-pressure section overstate the scope or precision of the underlying events (Gate.io's action was narrower than 'removed from trading', the Bybit timeline date is off by roughly two months, and a specific FinCEN $500-threshold proposal could not be independently verified). The most consequential finding is not any single false claim but the page's thinness relative to its subject: a fourteen-year-old, historically major cryptocurrency is covered in four short sections with no mention of its well-documented pre-2024 delisting history, no current market data, and no on-chain governance analysis.
    anchorpending
    chain
    hash
    G7F6733LnJJ5…iaTBhAczsha256 → base58
    verifying row…
    canonical bytes (1206 B) ▸
    {"actor":"reviewer","decided_at":"2026-08-27T10:51:43.620Z","decision":"review","investigation_id":"8968605b-bdbe-4f99-97fd-36ef3c917306","new_score":45,"page_slug":"dash","prev_score":45,"reason":"The page's core factual claims (founding history, instamine mechanics, masternode design, the EU AMLR ban, and the PrivateSend architecture) check out against independent sources, and none were found to be outright disputed. However, several claims in the regulatory-pressure section overstate the scope or precision of the underlying events (Gate.io's action was narrower than 'removed from trading', the Bybit timeline date is off by roughly two months, and a specific FinCEN $500-threshold proposal could not be independently verified). The most consequential finding is not any single false claim but the page's thinness relative to its subject: a fourteen-year-old, historically major cryptocurrency is covered in four short sections with no mention of its well-documented pre-2024 delisting history, no current market data, and no on-chain governance analysis.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 2026c5c7-49db-4fba-96ef-b42b437ac2cf
  3. #3review reviseby judgejudge
    2026-08-27 10:51:44Z
    Score: 4539 (-6)
    Independently recomputing from the reviewer's claim_findings array gives (0 disputed + 1 unverifiable) / 11 = 9.1% disputed, which sits inside the 0-10% approve band on accuracy grounds alone: nothing on this page was found to be false. Seven of eleven claims, including the founding history, instamine mechanics, and the EU AMLR ban, were independently confirmed (claim_findings[0-4], [8], [10]). But three findings temper that: the Gate.io claim (claim_findings[6]) is accurate to its cited source, but that source itself overstates a narrower margin/perpetual delisting as a full trading removal; the Bybit delisting date (claim_findings[7]) is off by about two months from a placeholder; and a specific FinCEN $500-threshold claim (claim_findings[9]) could not be verified because the source returned an error and no matching FinCEN action was found. None of these rise to 'disputed,' but they show a pattern of imprecision in the page's most recent, least-checked section. More consequential are two high-priority coverage gaps: the page omits Dash's decade-long pre-2024 delisting history (Coincheck 2018, Upbit and Bittrex 2021), which makes its 'mounting regulatory pressure' framing read as a newer development than the record supports, and the page is disproportionately thin (four short sections, four sources) for a fourteen-year-old top-tier asset with an extensive public record. This is not an ordinary 'more detail would help' gap; it changes how an accurate claim on the page is read, so it is treated as pushing the verdict out of the approve band even though the raw disputed percentage would otherwise clear it, consistent with the rule that high-priority coverage gaps can move the verdict independent of disputed_pct. The revision is placed at the low end of its penalty range because the reviewer's confidence (0.70) is moderate and no claim was actually found false.
    anchorpending
    chain
    hash
    HtJ2RqDqeD9f…6kNbuCmjsha256 → base58
    verifying row…
    canonical bytes (2235 B) ▸
    {"actor":"judge","decided_at":"2026-08-27T10:51:43.620Z","decision":"review_revise","investigation_id":"8968605b-bdbe-4f99-97fd-36ef3c917306","new_score":39,"page_slug":"dash","prev_score":45,"reason":"Independently recomputing from the reviewer's claim_findings array gives (0 disputed + 1 unverifiable) / 11 = 9.1% disputed, which sits inside the 0-10% approve band on accuracy grounds alone: nothing on this page was found to be false. Seven of eleven claims, including the founding history, instamine mechanics, and the EU AMLR ban, were independently confirmed (claim_findings[0-4], [8], [10]). But three findings temper that: the Gate.io claim (claim_findings[6]) is accurate to its cited source, but that source itself overstates a narrower margin/perpetual delisting as a full trading removal; the Bybit delisting date (claim_findings[7]) is off by about two months from a placeholder; and a specific FinCEN $500-threshold claim (claim_findings[9]) could not be verified because the source returned an error and no matching FinCEN action was found. None of these rise to 'disputed,' but they show a pattern of imprecision in the page's most recent, least-checked section. More consequential are two high-priority coverage gaps: the page omits Dash's decade-long pre-2024 delisting history (Coincheck 2018, Upbit and Bittrex 2021), which makes its 'mounting regulatory pressure' framing read as a newer development than the record supports, and the page is disproportionately thin (four short sections, four sources) for a fourteen-year-old top-tier asset with an extensive public record. This is not an ordinary 'more detail would help' gap; it changes how an accurate claim on the page is read, so it is treated as pushing the verdict out of the approve band even though the raw disputed percentage would otherwise clear it, consistent with the rule that high-priority coverage gaps can move the verdict independent of disputed_pct. The revision is placed at the low end of its penalty range because the reviewer's confidence (0.70) is moderate and no claim was actually found false.","score_delta":-6,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision d8e88f9d-10b9-44ab-94a6-8bc8dfae8d9c
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.