Skip to main content
AVOID.NET
Sign in
← Kaspareviewed 2026-09-09 · 48 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Kaspa 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 1unverifiable 3stale 3link rot 10partially supported 4confirmed 2714 corrections pending · 0 applied

disputed

1 claim

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. #16[disputed][awaiting moderator]in section: Mining Centralization and ASIC Development
    “In practice, Bitmain and IceRiver have released dedicated Kaspa ASIC hardware: the Bitmain Antminer KS7 delivers approximately 23 TH/s at 3,300W; the IceRiver KAS KS7 reaches 30 TH/s.”
    reviewerBitmain and IceRiver ASIC hardware specs: Antminer KS7 ~23 TH/s at 3,300W; IceRiver KAS KS7 ~30 TH/sThe IceRiver KS7 figure (30 TH/s) is accurate, but the Bitmain Antminer KS7 figure is materially wrong across every retailer/spec source checked; no source supports 23 TH/s at 3,300W.
    Proposed correction (not yet applied)
    In practice, Bitmain and IceRiver have released dedicated Kaspa ASIC hardware: the Bitmain Antminer KS7 delivers approximately 40 TH/s at approximately 2,772W; the IceRiver KAS KS7 reaches 30 TH/s.
    citedwww.cryptominerbros.com/blog/what-is-khe…yhash-algorithm/

unverifiable

3 claims

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

  1. #15[unverifiable][awaiting moderator]in section: Regulatory Status
    “Crypto exchange Gate.com published an analysis in December 2025 noting general regulatory risks for Kaspa include potential listing delistings if regulatory frameworks shift, but no specific action is pending.”
    reviewerGate.com's December 2025 analysis noted general regulatory risks for Kaspa including potential listing delistings if regulatory frameworks shift, with no specific action pendingCould not directly access the full article text to confirm the specific delisting-risk framing; the broader regulatory context it's embedded in checks out.
    citedwww.gate.com/crypto-wiki/article/what-ar…in-2025-20251203
  2. #21[unverifiable][awaiting moderator]in section: Smart Contract Roadmap and Current Limitations
    “A code freeze for Toccata was finalized on April 30, 2026.”
    reviewerA code freeze for Toccata was finalized on April 30, 2026Plausible given the surrounding roadmap timeline, but I could not independently verify this specific date.
    citedmedium.com/@michaelsuttonil/kaspa-covena…ook-a4d81a40900c
  3. #26[unverifiable][awaiting moderator]in the timeline
    “First hard fork since genesis reset, addressing deep side-chain spam attacks.”
    reviewerA hard fork addressing deep side-chain spam attacks occurred on 2022-04-14Could not locate independent reporting confirming this specific hard fork date or its stated purpose within the research budget for this review.
    citedkaspa-lens.com/kaspa/wiki/introduction-t…-and-fair-launch

stale

3 claims

The claim was accurate when written but events since have overtaken it.

  1. #20[stale][awaiting moderator]in section: Smart Contract Roadmap and Current Limitations
    “On the L1 roadmap, the Toccata hard fork is scheduled for mainnet activation between June 5 and June 20, 2026.”
    reviewerThe Toccata hard fork is scheduled for mainnet activation between June 5 and June 20, 2026The June 5-20, 2026 window was an earlier projection (published April 2026) that was superseded by the actual activation on June 30, 2026, per subsequent official/industry reporting; since the investigation date (per the page) is after this event, the page should reflect the actual outcome rather than the earlier projection.
    Proposed correction (not yet applied)
    On the L1 roadmap, the Toccata hard fork activated on mainnet on June 30, 2026, at DAA score 474,165,565.
    citedkas.live/medium.com/@michaelsuttonil/kaspa-covena…ook-a4d81a40900c
  2. #37[stale][awaiting moderator]in the timeline
    “Toccata hard fork mainnet activation window opens (June 5–20, 2026), introducing native L1 programmability, covenants, and ZK infrastructure.”
    reviewerToccata hard fork mainnet activation window opens June 5-20, 2026Same underlying defect as the sections[7] Toccata finding; the timeline's date field also needs correction (see accompanying timeline[15].date finding).
    Proposed correction (not yet applied)
    Toccata hard fork activated on mainnet on June 30, 2026, at DAA score 474,165,565, introducing native L1 programmability, covenants, and ZK infrastructure.
    citedkas.live/
  3. #38[stale][awaiting moderator]in the timeline
    “2026-06-05”
    reviewerToccata hard fork mainnet activation window opens on the date 2026-06-05The stored date field should be updated to the confirmed actual activation date, not left at the start of the originally projected window.
    Proposed correction (not yet applied)
    2026-06-30
    citedkas.live/

partially supported

4 claims

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

  1. #10[partially supported][awaiting moderator]in section: Genesis Reset and Early Transaction History Gap
    “However, that post relies primarily on circumstantial reasoning and lacks independent technical verification or documented victims.”
    reviewerThe 'Factual Account of the Kaspa Fraud Scheme' Substack post relies primarily on circumstantial reasoning and lacks independent technical verification or documented victimsThe page's characterization is substantially accurate but slightly overstates the total absence of any documented complainant; one anecdotal Discord report exists, though it falls short of a verified victim.
    citedtechleaks24.substack.com/p/a-factual-acc…-the-kaspa-fraud
  2. #14[partially supported][awaiting moderator]in section: Regulatory Status
    “Kaspa is listed on major exchanges including Binance, Coinbase, and Kraken without SEC challenge.”
    reviewerKaspa is listed on major exchanges including Binance, Coinbase, and Kraken without SEC challengeCoinbase and Kraken both list KAS on spot markets, but Binance offers only futures/perpetual contracts on KAS, not a spot listing, so grouping Binance alongside the others overstates its exposure.
  3. #17[partially supported][awaiting moderator]in section: Mining Centralization and ASIC Development
    “In June 2024, Marathon Digital Holdings (MARA), a publicly listed Bitcoin mining company, announced it had deployed 30 petahash of Kaspa ASIC capacity and was targeting approximately 16% of Kaspa's global hashrate — a concentration that, if realized, would represent a significant single-actor share of the network.”
    reviewerMarathon Digital deployed 30 petahash of Kaspa ASIC capacity and was targeting approximately 16% of Kaspa's global hashrateThis creates an internal inconsistency with the page's own timeline entry, which correctly states '60 petahashes' for the same announcement; the section text should be reconciled to the 60 PH total figure that the 16% target is actually based on.
    citedcryptoslate.com/marathon-digital-diversi…lobal-hash-rate/ir.mara.com/news-events/press-releases/d…ining-operations
  4. #28[partially supported][awaiting moderator]in the timeline
    “Developer Ori Newman discovered the sig_op_count consensus vulnerability during the Rust rewrite process.”
    reviewerOri Newman discovered the sig_op_count consensus vulnerability on 2022-09-12The vulnerability and its discovery in September 2022 are confirmed; the exact day-level date could not be independently pinned down.
    citedmedium.com/@michaelsuttonil/kaspa-securi…022-12da617b0094

confirmed

27 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Technical Architecture: GHOSTDAG and blockDAG
    “The GHOSTDAG protocol, formalized in academic research by Yonatan Sompolinsky and Aviv Zohar, instead retains parallel blocks and orders them into a consistent ledger, enabling higher throughput while preserving the security guarantees of Nakamoto consensus.”
    reviewerGHOSTDAG protocol was formalized in academic research by Yonatan Sompolinsky and Aviv Zohar and retains parallel blocks rather than orphaning themGHOSTDAG's authorship and blockDAG mechanics are well documented and consistently described across official and independent sources.
    citedkaspa.org/what-is-ghostdag-and-dagknight/kaspa.org/features/
  2. #2[confirmed][no action needed]in section: Technical Architecture: GHOSTDAG and blockDAG
    “Following the Crescendo hard fork, which activated on the mainnet in May 2025, the network processes 10 blocks per second (10 BPS), up from 1 BPS at launch.”
    reviewerThe Crescendo hard fork activated on mainnet in May 2025, raising throughput from 1 BPS to 10 BPSMatches the corresponding timeline entry (2025-05-05) and independent reporting.
    citedkaspa.org/kaspa-updates-to-crescendo-and-10bps/
  3. #3[confirmed][no action needed]in section: Technical Architecture: GHOSTDAG and blockDAG
    “The mining algorithm is kHeavyHash, a variant of the HeavyHash algorithm that sandwiches matrix multiplication between two Keccak (SHA-3) hashes.”
    reviewerkHeavyHash sandwiches matrix multiplication between two Keccak (SHA-3) hashesConsistent technical description across several independent mining-hardware references.
    citedwww.cryptominerbros.com/blog/what-is-khe…yhash-algorithm/
  4. #4[confirmed][no action needed]in section: Technical Architecture: GHOSTDAG and blockDAG
    “A further consensus upgrade, DAGKnight, is planned as a parameterless generalization of GHOSTDAG that adapts confirmation times to real-time network latency rather than requiring a fixed delay parameter; it targets 30,000 TPS and was published as an academic paper in October 2022.”
    reviewerDAGKnight targets 30,000 TPS and was published as an academic paper in October 2022TPS target and publication timing both corroborated.
    citedeprint.iacr.org/2022/1494.pdf
  5. #5[confirmed][no action needed]in section: Founder Background: Yonatan Sompolinsky
    “He earned his undergraduate degree in computer science from the Hebrew University of Jerusalem, where he completed a Ph.D. under the supervision of Prof. Aviv Zohar.”
    reviewerYonatan Sompolinsky earned his undergraduate degree in computer science from Hebrew University and completed a PhD under Aviv ZoharCited source supports the claim; a secondary source describes the undergraduate field slightly differently, a low-stakes biographical detail not treated as disputed.
    citediq.wiki/wiki/yonatan-sompolonsky
  6. #6[confirmed][no action needed]in section: Founder Background: Yonatan Sompolinsky
    “He is a named co-author on the DAGKnight whitepaper alongside Michael Sutton (a core Kaspa developer).”
    reviewerSompolinsky conducted postdoctoral research at Harvard University and is a named co-author on the DAGKnight whitepaper with Michael SuttonCo-authorship independently verified; Harvard postdoc also corroborated by Wikipedia and IQ.wiki.
    citedeprint.iacr.org/2022/1494.pdf
  7. #7[confirmed][no action needed]in section: Fair Launch Claims and Pre-Launch Funding
    “Kaspa launched on November 7, 2021 with no premine, no ICO, no developer token allocation, and no vesting schedule for founders.”
    reviewerKaspa launched November 7, 2021 with no premine, no ICO, no developer token allocation, and no vesting schedule for foundersWell documented and uncontested launch date and distribution structure.
    citedkaspa-lens.com/kaspa/wiki/introduction-t…-and-fair-launch
  8. #8[confirmed][no action needed]in section: Fair Launch Claims and Pre-Launch Funding
    “The R&D company DAGLabs was founded in 2018 by Sompolinsky and received approximately $8 million in investment from Polychain Capital, with smaller contributions from Accomplice and Genesis Mining.”
    reviewerDAGLabs was founded in 2018 by Sompolinsky and received approximately $8 million from Polychain Capital, with smaller contributions from Accomplice and Genesis MiningInvestment amount and investor list corroborated by multiple independent sources even though the primary cited wiki page could not be directly rendered.
    citedwiki.kaspa.org/en/daglabs
  9. #9[confirmed][no action needed]in section: Genesis Reset and Early Transaction History Gap
    “Two weeks after mainnet launch, on approximately November 21–22, 2021, a critical bug caused a complete network split. At the point of the crash, approximately 648 million KAS had already been mined.”
    reviewerTwo weeks after mainnet launch, on approximately November 21–22, 2021, a critical bug caused a complete network split with roughly 648 million KAS already minedDate range, coin count, and technical resolution are all independently corroborated.
    citedmedium.com/@toni.lukkaroinen/the-forgott…sis-c54a35bfb7f4
  10. #11[confirmed][no action needed]in section: Security Incidents and Protocol Vulnerabilities
    “In September 2022, Kaspa developer Ori Newman discovered a consensus vulnerability during the Rust rewrite process.”
    reviewerOri Newman discovered a consensus vulnerability involving sig_op_count during the Rust rewrite process in September 2022Technical description of the vulnerability is accurate and matches the primary source.
    citedmedium.com/@michaelsuttonil/kaspa-securi…022-12da617b0094
  11. #12[confirmed][no action needed]in section: Security Incidents and Protocol Vulnerabilities
    “A permanent fix was deployed via hard fork on September 28, 2022, at DAA score 27,905,000, incorporating sig_op_count into the transaction hashing process.”
    reviewerA permanent fix for the sig_op_count vulnerability was deployed via hard fork on September 28, 2022, at DAA score 27,905,000Date and DAA score independently verified.
    citedmedium.com/@michaelsuttonil/kaspa-securi…022-12da617b0094
  12. #13[confirmed][no action needed]in section: Regulatory Status
    “In March 2026, the SEC and CFTC issued a joint interpretation of federal securities law as applied to crypto assets.”
    reviewerIn March 2026 the SEC and CFTC issued a joint interpretation of federal securities law as applied to crypto assetsRegulatory action date and substance are independently confirmed by primary regulator and law-firm sources.
    citedwww.cftc.gov/PressRoom/PressReleases/9198-26www.ropesgray.com/en/insights/alerts/202…of-crypto-assets
  13. #18[confirmed][no action needed]in section: Smart Contract Roadmap and Current Limitations
    “The Kasplex project, a third-party team, introduced KRC-20 tokens (a fungible token standard analogous to ERC-20) on a Layer 2 in mid-2024, entering closed beta on testnet in May 2024 and launching KRC-20 beta on June 30, 2024.”
    reviewerThe Kasplex project introduced KRC-20 tokens on a Layer 2 in mid-2024, entering closed beta on testnet in May 2024 and launching KRC-20 beta on June 30, 2024Both dates independently corroborated.
    citedkasmedia.com/article/introducing-kasplex…0-krc-721-tokens
  14. #19[confirmed][no action needed]in section: Smart Contract Roadmap and Current Limitations
    “Kasplex subsequently launched a zkEVM Layer-2 mainnet in collaboration with the Kaspa Ecosystem Foundation, bringing Ethereum-compatible smart contracts to Kaspa via ZK rollup technology.”
    reviewerKasplex subsequently launched a zkEVM Layer-2 mainnet in collaboration with the Kaspa Ecosystem Foundation, bringing Ethereum-compatible smart contracts to KaspaIndependently corroborated by industry press covering the same announcement referenced in the cited X post.
    citedx.com/kasplex/status/1971469795317960800
  15. #22[confirmed][no action needed]in section: Community Governance and Development Funding
    “The project operates a community treasury managed as a 2-of-4 multisig wallet, with community-elected treasurers.”
    reviewerThe community treasury is a 2-of-4 multisig wallet with community-elected treasurers, and the Rust rewrite was funded with 100 million KAS via a 3-of-6 multisigGovernance structure independently corroborated even though the primary cited kaspa.org URL is dead (see link_rot findings).
    citedkaspa.org/kaspas-community-governance/
  16. #23[confirmed][no action needed]in section: Tokenomics and Emission Schedule
    “As of late 2025, approximately 95% of total supply had already been mined.”
    reviewerKaspa has a fixed hard-cap total supply of approximately 28.7 billion KAS, with approximately 95% of total supply already mined as of late 2025Supply cap and mined percentage both independently corroborated.
    citedcryptonews.com/news/kaspa-price-prediction-2026-supply/
  17. #24[confirmed][no action needed]in the timeline
    “DAGLabs founded by Yonatan Sompolinsky to commercialize the GHOSTDAG protocol, receiving approximately $8 million from Polychain Capital, Accomplice, and Genesis Mining.”
    reviewerDAGLabs founded 2018 by Sompolinsky, receiving approximately $8 million from Polychain Capital, Accomplice, and Genesis MiningConsistent with sections[2] finding on the same underlying claim; corroborated by independent sources cited there.
    citedwiki.kaspa.org/en/daglabs
  18. #25[confirmed][no action needed]in the timeline
    “Kaspa mainnet launched with no premine, no ICO, and no VC token allocation. Initial block reward set at 440 KAS. Genesis block produced November 8, 2021.”
    reviewerKaspa mainnet launched with no premine/ICO/VC allocation; initial block reward 440 KAS; genesis block produced November 8, 2021Genesis block date and reward figure align with independent reporting (mainnet Nov 7, genesis block Nov 8, 2021).
    citedkaspa-lens.com/kaspa/wiki/introduction-t…-and-fair-launch
  19. #27[confirmed][no action needed]in the timeline
    “Core developer Michael Sutton announced the Rust rewrite initiative (Rusty Kaspa / KIP-001) in the official Kaspa Discord. Community approved and subsequently funded the effort with 100 million KAS.”
    reviewerMichael Sutton announced the Rust rewrite initiative (Rusty Kaspa / KIP-001) in July 2022, subsequently funded with 100 million KASThe cited kasmedia.com URL now 308-redirects to kasmagazine.com but resolves to matching content, so this is not treated as link rot.
    citedkasmedia.com/article/rusty-kaspa-fa-qs
  20. #29[confirmed][no action needed]in the timeline
    “Permanent hard fork activated at DAA score 27,905,000, fixing the sig_op_count consensus vulnerability by including the field in the transaction hashing process.”
    reviewerPermanent hard fork activated at DAA score 27,905,000 on September 28, 2022, fixing the sig_op_count vulnerabilityMatches sections[4] finding on the same underlying event.
    citedmedium.com/@michaelsuttonil/kaspa-securi…022-12da617b0094
  21. #30[confirmed][no action needed]in the timeline
    “DAGKnight whitepaper published by Yonatan Sompolinsky and Michael Sutton on the 14th anniversary of the Bitcoin whitepaper, introducing a parameterless generalization of Nakamoto consensus.”
    reviewerDAGKnight whitepaper published by Sompolinsky and Sutton on the 14th anniversary of the Bitcoin whitepaper (2022-10-31)October 31, 2008 is the Bitcoin whitepaper's publication date, so October 31, 2022 is correctly its 14th anniversary; co-authorship independently confirmed.
    citedeprint.iacr.org/2022/1494.pdf
  22. #31[confirmed][no action needed]in the timeline
    “Marathon Digital Holdings deployed its first Kaspa mining machines, beginning institutional ASIC mining on the network.”
    reviewerMarathon Digital Holdings deployed its first Kaspa mining machines in September 2023Consistent with the primary MARA press release.
    citedir.mara.com/news-events/press-releases/d…ining-operations
  23. #32[confirmed][no action needed]in the timeline
    “Testnet 11 (TN11), the 10 BPS Kaspa testnet, launched for the Crescendo upgrade.”
    reviewerTestnet 11 (TN11), the 10 BPS Kaspa testnet, launched on 2024-01-07Date is independently corroborated even though the page's cited source URL is dead (see link_rot finding for the same URL).
    citedcoinmarketcap.com/academy/article/b8fa98…5d1-dd93c55cb8cc
  24. #33[confirmed][no action needed]in the timeline
    “Rusty Kaspa (Rust implementation) released as stable and recommended as the primary network client.”
    reviewerRusty Kaspa (Rust implementation) released as stable and recommended as the primary network client in May 2024Consistent with sections[0] claim on the same milestone.
    citedmedium.com/@michaelsuttonil/kaspa-on-rus…ase-636938596441
  25. #34[confirmed][no action needed]in the timeline
    “Marathon Digital announced it had mined 93 million KAS (approximately $15 million in value) and was targeting approximately 16% of Kaspa's global hashrate using 60 petahashes of Bitmain ASIC hardware.”
    reviewerMarathon Digital announced it had mined 93 million KAS (~$15 million) and was targeting ~16% of Kaspa's global hashrate using 60 petahashes of Bitmain ASIC hardwareThis timeline entry is accurate and should be used as the reference figure to correct the inconsistent 'sections[6]' passage (see marathon-kaspa-petahash-figure defect group).
    citedcryptoslate.com/marathon-digital-diversi…lobal-hash-rate/
  26. #35[confirmed][no action needed]in the timeline
    “Kasplex KRC-20 beta launched, introducing fungible token standard on Kaspa Layer 2.”
    reviewerKasplex KRC-20 beta launched on 2024-06-30, introducing a fungible token standard on Kaspa Layer 2Matches sections[7] finding on the same event.
    citedkasmedia.com/article/introducing-kasplex…0-krc-721-tokens
  27. #36[confirmed][no action needed]in the timeline
    “Crescendo hard fork activated on mainnet at DAA score 110,165,000, upgrading the network from 1 BPS to 10 BPS and implementing all Kaspa Improvement Proposals KIP1 through KIP15.”
    reviewerCrescendo hard fork activated on mainnet at DAA score 110,165,000 on 2025-05-05, upgrading from 1 BPS to 10 BPS and implementing KIP1-KIP15DAA score and date match independent reporting (CoinCarp, GitHub release notes).
    citedkaspa.org/kaspa-updates-to-crescendo-and-10bps/
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.