Skip to main content
AVOID.NET
← Dashreviewed 2026-09-07 · 16 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Dash against the sources the page cites. Only the most recent review is shown.

Read this first

These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.

“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.

Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.

disputed

2 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #5[disputed][awaiting moderator]in the summary
    “Duffield called it accidental but chose to continue rather than relaunch.”
    reviewerDuffield called the instamine an accident but chose to continue rather than relaunch (summary).The page attributes the decision not to relaunch to Duffield himself. Independent secondary reporting and Dash's own official clarification indicate the opposite sequence: Duffield proposed a remediation/relaunch, and the community voted it down.
    Proposed correction (not yet applied)
    Duffield called it accidental and proposed a relaunch, but the community voted down the proposal, leaving the distribution unchanged.
  2. #6[disputed][awaiting moderator]in section: Instamine Controversy
    “Duffield, himself one of the early miners, called it an accident but chose to continue rather than relaunch.”
    reviewerDuffield, one of the early miners, called the instamine an accident but chose to continue rather than relaunch (Instamine Controversy section).Same underlying mischaracterization as the summary occurrence: the source material (including Dash's own official account) reverses who decided to keep the original distribution.
    Proposed correction (not yet applied)
    Duffield, himself one of the early miners, called it an accident and proposed a relaunch, but the community voted down the proposal, leaving the distribution unchanged.

unverifiable

2 claims

No source the reviewer could reach confirms or contradicts the claim.

  1. #14[unverifiable][awaiting moderator]in section: Privacy Coin Regulatory Pressure
    “FinCEN proposed rules (January 2025) mandating record-keeping for private coin transactions exceeding $500.”
    reviewerFinCEN proposed rules in January 2025 mandating record-keeping for privacy-coin transactions exceeding $500 (Privacy Coin Regulatory Pressure section).Could not locate any primary FinCEN source, Federal Register notice, or reputable independent reporting corroborating a January 2025 $500-threshold privacy-coin rule; only low-tier secondary articles repeat the figure without attribution to a primary document.
  2. #15[unverifiable][awaiting moderator]in the timeline
    “FinCEN proposes $500 threshold record-keeping for privacy coins”
    reviewerFinCEN proposes a $500 threshold for record-keeping on privacy-coin transactions (timeline, 2025).Same unverifiable claim as its section occurrence, additionally folded into a compound timeline entry alongside the (confirmed) Bybit delisting, which makes the entry's single 'source' citation to a low-tier article carry two claims of very different verifiability.

partially supported

3 claims

The cited evidence supports part of the claim but not all of it.

  1. #9[partially supported][awaiting moderator]in the summary
    “Gate.io removed DASH end of 2024”
    reviewerGate.io removed DASH end of 2024 (summary).The underlying event (Gate.io action against DASH in Dec 2024) is real and correctly dated, but the unqualified phrase 'removed DASH' overstates the scope: available reporting describes a perpetual-contracts delisting, not necessarily removal of DASH spot trading.
  2. #10[partially supported][awaiting moderator]in section: Privacy Coin Regulatory Pressure
    “Gate.io removed DASH at end of 2024”
    reviewerGate.io removed DASH at end of 2024 (Privacy Coin Regulatory Pressure section).Same scope overstatement as the summary occurrence.
  3. #11[partially supported][awaiting moderator]in the timeline
    “Gate.io removes DASH from trading”
    reviewerGate.io removes DASH from trading (timeline, Dec 2024).Same scope overstatement as the other two occurrences of this claim; date (Dec 2024) itself is correct.

confirmed

9 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Founder and Origins
    “Dash was created by Evan Duffield and launched January 18, 2014 as XCoin, a fork of Litecoin's codebase.”
    reviewerDash was created by Evan Duffield and launched January 18, 2014 as XCoin, a fork of Litecoin's codebase, later renamed Darkcoin then Dash.Multiple independent sources corroborate the launch date, founder, original name, and Litecoin-codebase origin. Wikipedia's current phrasing ('fork of the Bitcoin protocol') appears to conflate the 2014 origin with a later 2015 rebase; the weight of sourcing supports the page's Litecoin-fork description of the original launch.
  2. #2[confirmed][no action needed]in section: Founder and Origins
    “Duffield introduced masternodes — incentivized full nodes requiring 1,000 DASH collateral — as the first implementation of this concept in cryptocurrency.”
    reviewerDuffield introduced masternodes requiring 1,000 DASH collateral as the first implementation of the masternode concept in cryptocurrency.Independently corroborated: Dash is widely credited as the first cryptocurrency to implement the incentivized-masternode model, with 1,000 DASH collateral.
  3. #3[confirmed][no action needed]in section: Founder and Origins
    “Duffield stepped back from day-to-day involvement around 2017.”
    reviewerDuffield stepped back from day-to-day involvement in Dash around 2017.Confirmed by Dash's own April 2017 announcement of Duffield's transition to an advisory role.
  4. #4[confirmed][no action needed]in section: Instamine Controversy
    “In the first 48 hours after launch (January 2014), approximately 1.9 million DASH (~10% of the 18.9M maximum supply) were mined.”
    reviewerApproximately 1.9 million DASH (~10% of 18.9M max supply) was instamined in the first 48 hours due to a delayed difficulty retarget inherited from Litecoin's codebase, occurring at block 3,396 (~8 hours post-launch) and generating ~1.57M coins before normalizing.Figures and timeline are consistent across independent sources; the 48-hour window is a safe upper bound since the instamine period actually concluded around block 4,501 (~34 hours).
  5. #7[confirmed][no action needed]in section: Instamine Controversy
    “Critics characterized the instamine as potentially deliberate, enabling a small group of early miners to accumulate substantial holdings.”
    reviewerCritics characterized the instamine as potentially deliberate, allowing early miners including Duffield to accumulate substantial holdings.General characterization of instamine skepticism is well documented in independent reporting.
  6. #8[confirmed][no action needed]in section: Masternode Concentration Concerns
    “The question of whether the majority of governance votes are potentially under the control of one entity remains unresolved.”
    reviewerMasternode concentration raises the unresolved question of whether a majority of governance votes could be controlled by one entity.The claim is appropriately hedged ('remains unresolved') and consistent with the cited source's general concentration concern, though the source does not state a specific 'majority' figure.
  7. #12[confirmed][no action needed]in section: Privacy Coin Regulatory Pressure
    “Bybit deleted the DASH/USDT pair early 2025”
    reviewerBybit deleted the DASH/USDT trading pair in early 2025.Independently corroborated with a specific date (Feb 28, 2025) that falls within the page's 'early 2025' description.
  8. #13[confirmed][no action needed]in section: Privacy Coin Regulatory Pressure
    “The EU Anti-Money Laundering Regulation (effective July 2027) bans privacy coins from regulated platforms.”
    reviewerThe EU Anti-Money Laundering Regulation, effective July 2027, bans privacy coins from regulated platforms.Month-level date and substance of the ban are corroborated by multiple independent sources describing the AMLR's Article 58 anonymity-enhancing-coin provisions.
  9. #16[confirmed][no action needed]in section: Privacy Coin Regulatory Pressure
    “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.”
    reviewerDash's opt-in PrivateSend model, with a transparent base layer that can be disabled, offers regulatory flexibility that mandatory privacy coins like Monero lack.Well-established, uncontroversial technical distinction between Dash's optional CoinJoin-style mixing and Monero's mandatory ring-signature privacy.
How this fits together. The reviewer reads the published page and its cited sources and records one finding per claim. A human moderator decides whether each proposed correction is applied; those decisions, and the score changes they cause, appear in the audit log. Earlier review runs are not shown here; only the latest reflects the page as it stands.