← Ravencoin Consensus Vulnerability Exploit (August 2026)reviewed 2026-09-07 · 28 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Ravencoin Consensus Vulnerability Exploit (August 2026) 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 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #4[disputed][awaiting moderator]in section: Scope and Timeline of Exploitation
“Exploitation continued undetected for approximately three days before being disclosed publicly on August 11, 2026.”
reviewerExploitation continued undetected for approximately three days before being disclosed publicly on August 11, 2026.The page's own cited CoinDesk source (credibility 1, also listed in sources_used) titles the same event a 'four day' span, and the calendar gap between Aug 7 and Aug 11 is four days, not three. Other sections of the page (Exchange Suspensions) hedge with 'three to four days,' but this specific sentence asserts three days flatly.Proposed correction (not yet applied)Exploitation continued undetected for approximately four days before being disclosed publicly on August 11, 2026. - #16[disputed][awaiting moderator]in section: Market Impact
“CoinTrust noted the token was down approximately 77% over the prior year, establishing that the exploit occurred during a period of extended decline for RVN.”
reviewerCoinTrust noted the token was down approximately 77% over the prior year, establishing that the exploit occurred during a period of extended decline for RVN.The specific attribution to CoinTrust could not be verified -- the cited CoinTrust article does not contain any price-decline percentage. The underlying 77% figure itself is plausible (other outlets independently report RVN down roughly that much over the trailing year), but it should not be sourced to this particular CoinTrust article as written. Proposed correction removes the unverifiable attribution while preserving the substantive (independently plausible) claim; an editor should re-source this to a specific article that actually states it, or drop the attribution to CoinTrust entirely.Proposed correction (not yet applied)The token was down approximately 77% over the prior year, establishing that the exploit occurred during a period of extended decline for RVN.
unverifiable
2 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #17[unverifiable][awaiting moderator]in section: Market Impact
“The token shed approximately 50% from late-May 2026 levels near $0.0055 even before the exploit was publicly disclosed.”
reviewerRVN shed approximately 50% from late-May 2026 levels near $0.0055 even before the exploit was publicly disclosed.No section source is cited for this specific figure; independent price-history data is directionally consistent but not conclusively confirmed via direct fetch. - #24[unverifiable][awaiting moderator]in section: Resolution Status
“As of the date of this investigation (August 14, 2026), the chain reorganization was in progress but no sources confirmed its completion or full network stabilization.”
reviewerAs of the date of this investigation (August 14, 2026), the chain reorganization was in progress but no sources confirmed its completion or full network stabilization.Accurate as of the investigation date given available reporting, but this reviewer -- operating nearly a month later (current date September 7, 2026) -- could not find any newer reporting confirming whether the reorganization has since concluded or exchanges have reopened RVN transfers. This is flagged as a coverage gap requiring a follow-up update rather than a factual dispute, since no source was found either confirming or contradicting resolution.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #26[partially supported][awaiting moderator]in the timeline
“Ravencoin discloses second major consensus failure: attacker exploited coinbase logic to mint approximately 315 million unauthorized RVN tokens over seven weeks. CryptoScope alerted the team; patched at block 1,304,352 on July 4, 2020.”
reviewerRavencoin discloses second major consensus failure in 2020: attacker minted approximately 315 million unauthorized RVN over seven weeks; CryptoScope alerted the team; patched at block 1,304,352 on July 4, 2020.The page's own section 6 (Historical Pattern of Consensus Failures) describes this same 2020 incident as injecting RVN 'into reissuance transactions,' which matches independent technical accounts of an asset-reissue exploit. This timeline entry instead calls it 'coinbase logic,' which is a different and seemingly incorrect technical characterization inconsistent with the rest of the page and with available technical sources.
confirmed
23 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in the summary
“On August 7, 2026, an attacker exploited a critical consensus vulnerability in the Ravencoin (RVN) network by manipulating the nHeight field in KAWPOW block headers to bypass proof-of-work verification.”
reviewerAttacker manipulated the nHeight field in KAWPOW block headers to bypass proof-of-work verification, beginning at block height 4,487,776 on August 7, 2026, causing exchanges to suspend RVN and RVN to fall ~19% to ~$0.00288.Mechanism, block height, and date are corroborated across multiple independently fetched outlets (crypto.news, coinpaper, 2Miners release notes as summarized by press). - #2[confirmed][no action needed]in the summary
“An emergency patch (v4.6.1.1-hf1) was released on August 10, 2026 by mining pool 2Miners rather than Ravencoin's core development team, marking at least the third significant consensus-level failure in the network's history.”
reviewerThe emergency patch v4.6.1.1-hf1 was released on August 10, 2026 by mining pool 2Miners rather than Ravencoin's core team, marking at least the third significant consensus-level failure in the network's history.Fully corroborated by the cited source and independently by search-indexed secondary coverage. - #3[confirmed][no action needed]in section: Exploit Mechanism
“This allowed an attacker to produce invalid blocks at a cost described by 2Miners as 'orders of magnitude cheaper' than legitimate mining.”
reviewerThe nHeight field was not verified against a block's actual position, letting an attacker skip the memory-intensive KAWPOW check, at a cost 2Miners described as 'orders of magnitude cheaper' than legitimate mining.The quoted characterization matches press summaries of 2Miners' own release notes. - #5[confirmed][no action needed]in section: Scope and Timeline of Exploitation
“A sample analysis of blocks between heights 4,489,527 and 4,491,615 identified 96 affected blocks out of 2,089 examined, indicating a meaningful but not total contamination rate in that range.”
reviewerA sample analysis of blocks between heights 4,489,527 and 4,491,615 identified 96 affected blocks out of 2,089 examined.Exact figures confirmed via direct fetch of the cited source. - #6[confirmed][no action needed]in section: Scope and Timeline of Exploitation
“Nodes began reporting database errors as a downstream symptom of the corrupted chain state.”
reviewerNodes began reporting database errors as a downstream symptom of the corrupted chain state.Corroborated by press descriptions of node database-error crashes tied to the corrupted block index. - #7[confirmed][no action needed]in section: Emergency Patch and Recovery Response
“The initial restart following the patch can take several hours because the software replays approximately 4.49 million blocks and 28 million transactions.”
reviewer2Miners patch enforces height validation from block 4,487,776 onward, sets a checkpoint at 4,487,775, and rebuilds chainstate/asset database automatically; initial restart can take hours because it replays ~4.49 million blocks and 28 million transactions.Figures corroborated by press summaries of the 2Miners release notes. - #8[confirmed][no action needed]in section: Emergency Patch and Recovery Response
“Ravencoin's core development team requested that the pools choose a more recent recovery point to minimize the volume of transactions that would be reversed; both pools declined that request and proceeded with the checkpoint at block 4,487,775.”
reviewerRavencoin's core development team requested that the pools choose a more recent recovery point; both pools declined and proceeded with the checkpoint at block 4,487,775.Verified verbatim against a direct fetch of the cited article. - #9[confirmed][no action needed]in section: Emergency Patch and Recovery Response
“The patch was issued by 2Miners rather than Ravencoin's own team, which reporting by cryip.co described as inactive.”
reviewerThe patch was issued by 2Miners rather than Ravencoin's own team, which reporting by cryip.co described as inactive.Exact quote match on direct fetch. - #10[confirmed][no action needed]in section: Emergency Patch and Recovery Response
“RavenMiner stated its nodes are running the emergency fix and committed to covering any payout shortfalls arising from the reorganization; it confirmed that miner earnings from before the attack window are unaffected.”
reviewerRavenMiner stated its nodes are running the emergency fix and committed to covering any payout shortfalls, confirming miner earnings from before the attack window are unaffected.Substance confirmed; minor phrasing difference ('would be restored' vs. page's 'are unaffected') does not change the substantive claim. - #11[confirmed][no action needed]in section: Exchange Suspensions and User Risk
“Upbit (South Korea) suspended RVN deposits and withdrawals on August 10, 2026, and placed an investment warning on RVN trading pairs, citing the exploited vulnerability.”
reviewerUpbit suspended RVN deposits and withdrawals on August 10, 2026 and placed an investment warning on RVN trading pairs.Corroborated by both a news aggregator and Upbit's own official account. - #12[confirmed][no action needed]in section: Exchange Suspensions and User Risk
“Bitget suspended RVN transfers beginning August 10, citing wallet maintenance.”
reviewerBitget suspended RVN transfers beginning August 10, citing wallet maintenance.The cited cryptotimes.io article itself does not mention Bitget; the claim is nonetheless corroborated by other press coverage describing Bitget's suspension as framed as wallet maintenance. Consider adding a source that explicitly names Bitget. - #13[confirmed][no action needed]in section: Exchange Suspensions and User Risk
“Trading remained active on affected exchanges despite transfer suspensions, creating a risk that market prices reflected a chain state that may be rolled back.”
reviewerTrading remained active on affected exchanges despite transfer suspensions.Confirmed for at least Upbit; reasonable generalization to 'affected exchanges.' - #14[confirmed][no action needed]in section: Market Impact
“RVN fell approximately 19.1% within 24 hours of the August 11 public disclosure, trading at around $0.00288, according to crypto.news.”
reviewerRVN fell approximately 19.1% within 24 hours of the August 11 disclosure, trading at around $0.00288; market cap declined to approximately $47.3 million.Verified verbatim against direct fetch. - #15[confirmed][no action needed]in section: Market Impact
“One source (Decrypt) reported a single-day loss of approximately 20.4% on the RVN/USDT pair, and CoinDesk reported a 17% decline to approximately $0.0029.”
reviewerDecrypt reported a single-day loss of approximately 20.4% on the RVN/USDT pair.Both attributions verified against their respective sources. - #18[confirmed][no action needed]in section: Governance and Development Activity Concerns
“Multiple outlets noted that the emergency patch (v4.6.1.1-hf1) was released from a mining pool's GitHub repository rather than from Ravencoin's own core team, with cryip.co reporting that 'upstream Ravencoin development is inactive.'”
reviewerMultiple outlets noted the patch came from a mining pool's GitHub repository rather than Ravencoin's core team, per cryip.co's quote that 'upstream Ravencoin development is inactive.'Verbatim quote confirmed. - #19[confirmed][no action needed]in section: Governance and Development Activity Concerns
“Raptoreum discovered asset-layer vulnerabilities in 2019; CryptoScope identified the 2020 inflation exploit; and 2Miners identified and patched the August 2026 KAWPOW flaw.”
reviewerThe recurrence of consensus-level vulnerabilities across different codebase components (2018 reorg limits, 2020 asset-layer logic, 2026 KAWPOW header validation) is a documented pattern, with Raptoreum (2019), CryptoScope (2020), and 2Miners (2026) each finding bugs discovered/addressed by outside parties.Confirmed via direct fetch of cited source. - #20[confirmed][no action needed]in section: Historical Pattern of Consensus Failures
“In September 2018, a double-spend attack rewrote 22 blocks; the response capped future reorganizations at 60 blocks.”
reviewerIn September 2018, a double-spend attack rewrote 22 Ravencoin blocks; the response capped future reorganizations at 60 blocks.Confirmed via direct fetch. - #21[confirmed][no action needed]in section: Historical Pattern of Consensus Failures
“In 2019, the Raptoreum team discovered four asset-layer bugs, including one enabling unauthorized sub-asset minting; Ravencoin patched the issues and paid bounties, and none were exploited live.”
reviewerIn 2019, the Raptoreum team discovered four asset-layer bugs, including one enabling unauthorized sub-asset minting; Ravencoin patched the issues and paid bounties, and none were exploited live.Confirmed via direct fetch; page's plural 'bounties' vs. source's singular bounty payment is a trivial phrasing difference, not flagged separately. - #22[confirmed][no action needed]in section: Historical Pattern of Consensus Failures
“Between May and July 2020, an attacker exploited a flaw introduced by a community code submission to inject approximately 315 million extra RVN into reissuance transactions over seven weeks, representing approximately 1.5% of the total supply cap.”
reviewerBetween May and July 2020, an attacker injected approximately 315 million extra RVN into reissuance transactions over seven weeks (~1.5% of total supply cap); CryptoScope identified it and Ravencoin patched by block 1,304,352 on July 4, 2020.Note for transparency: some technical retrospectives attributed to CryptoScope's own post-mortem and the lead developer place the final total nearer 301.8 million RVN, slightly below the widely reported 315 million figure; this reviewer could not directly fetch those primary posts (blocked by 403) to confirm the discrepancy, so the 315 million figure -- confirmed by two independently fetched, credible outlets -- is treated as confirmed rather than disputed. - #23[confirmed][no action needed]in section: Historical Pattern of Consensus Failures
“CoinDesk and CryptoPotato covered the 2020 incident at the time.”
reviewerCoinDesk and CryptoPotato covered the 2020 incident at the time.Confirmed via URL dating and content. - #25[confirmed][no action needed]in the timeline
“First invalid KAWPOW block accepted by vulnerable Ravencoin nodes at height 4,487,776 at 15:44:01 UTC. Exploitation begins. Attacker manipulates nHeight header field to bypass proof-of-work verification.”
reviewerFirst confirmed invalid block appeared at height 4,487,776 at 15:44:01 UTC on August 7, 2026, per the official Ravencoin X account.Corroborated by secondary reporting despite inability to directly fetch the primary X post (platform access restriction, not necessarily link rot). - #27[confirmed][no action needed]in the timeline
“Mining pool 2Miners releases emergency patch v4.6.1.1-hf1 from its own GitHub repository, setting a checkpoint at block 4,487,775 and enforcing proper nHeight validation. Upbit and Bitget suspend RVN deposits and withdrawals. Bitvavo follows with a precautionary suspension.”
reviewerMining pool 2Miners releases emergency patch v4.6.1.1-hf1 on August 10, 2026; Upbit and Bitget suspend RVN deposits/withdrawals; Bitvavo follows with a precautionary suspension.Confirmed via direct fetch and cross-referenced with cryptotimes.io coverage of Bitvavo and Upbit. - #28[confirmed][no action needed]in the timeline
“Ravencoin publicly discloses the vulnerability via official X account. 2Miners and RavenMiner begin mining a competing clean chain from block 4,487,775, excluding the exploited branch. Ravencoin's core team requests a gentler rollback point; pools decline. RVN falls approximately 19% to around $0.00288. CoinDesk, Decrypt, and crypto.news publish coverage.”
reviewerOn August 11, 2026, Ravencoin publicly discloses the vulnerability; 2Miners and RavenMiner begin mining a competing clean chain from block 4,487,775; core team requests gentler rollback point and pools decline; RVN falls ~19% to ~$0.00288.All discrete elements of this compound timeline entry independently confirmed across multiple fetched sources.
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.