Fact-check findings
What an automated fact-checker found when it re-read Nomic Chain against the sources the page cites. Only the most recent review is shown.
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.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #5[unverifiable][awaiting moderator]in the timeline
“Nomic ceases producing Bitcoin checkpoints, triggering investigation by Osmosis into its reserves.”
reviewerNomic ceased producing Bitcoin checkpoints on September 6, 2026Source blocked. The Sept 7 halt is corroborated; the Sept 6 checkpoint date is not. - #11[unverifiable][awaiting moderator]in section: Chain Halt and Maintenance Concerns
“The lack of active monitoring and maintenance by the Nomic team is cited by multiple outlets as a contributing factor to the 74-day detection gap.”
reviewerThe unusually specific claim that multiple outlets cite lack of monitoring as a contributing factorThe page presents an interpretation as a multi-outlet finding. Reported sources describe Osmosis's own failure to notice. - #12[unverifiable][awaiting moderator]in the timeline
“Nomic Stakenet launches, releasing NOM staking token via ATOM airdrop and activating the nBTC Bitcoin bridge.”
reviewerNomic Stakenet launched in 2023-01-01, activating the nBTC bridgeNot fetched. The 2023-01-01 date looks like a placeholder, and the Decrypt article on the Bitcoin bridge appears to date from later in 2023. - #13[unverifiable][awaiting moderator]in section: Background and Protocol Overview
“developed since approximately 2018 by Turbofish, a company whose chief executive is Matt Bell”
reviewerDevelopment began around 2018 by Turbofish under CEO Matt BellSource blocked, not scored.
partially supported
3 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in section: Double-Spend Exploit of IBC Forwarding Mechanism (June–September 2026)
“the attacker combined two separate bugs in Nomic's forwarding logic”
reviewerThe attacker combined two separate bugs in Nomic's forwarding logicThe 'two bugs' detail was not found in Blockfence or Protos. CryptoSlate was not checked for this point beyond its partial text, so the claim may come from there. - #7[partially supported][awaiting moderator]in the timeline
“2026-07-17”
reviewerRarma traced about 671.1 ETH to Tornado Cash; the timeline dates this 2026-07-17The fact is supported but the July 17 date is not. The July 17 date appears to be copied from the allBTC conversion entry. This applies to the entry at timeline[5] only; timeline[4] also uses 2026-07-17 and is supported by CryptoSlate for the conversion. - #8[partially supported][awaiting moderator]in the timeline
“An emergency upgrade freezes 22.65 BTC in the attacker's address.”
reviewerEmergency upgrade freezing 22.65 BTC occurred on Sept 9 alongside the Osmosis statementThe page implies the freeze happened Sept 9. A single technical write-up says it was binding Sept 8, so the correction rests on one lower-tier source.
confirmed
6 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: Double-Spend Exploit of IBC Forwarding Mechanism (June–September 2026)
“minting approximately 40.650602 nBTC across an estimated 25 cross-chain transfers to Osmosis”
reviewerAttacker minted about 40.65 unbacked nBTC across about 25 cross-chain transfers to Osmosis on June 25, 2026Amount, transfer count and date are consistent across sources. - #3[confirmed][no action needed]in the summary
“causing an estimated $3.15 million in losses”
reviewerApproximately $3.15 million estimated lossSupported by Blockfence only; CryptoSlate does not contain the figure. - #4[confirmed][no action needed]in section: 74-Day Detection Gap and Disclosure
“The exploit of June 25, 2026 went undetected for approximately 74 days.”
reviewerThe 74-day detection gap, with Nomic halting Sept 7 triggering Osmosis to check backingCryptoTimes returned 403, so the Sept 6 checkpoint detail could not be checked. - #6[confirmed][no action needed]in section: 74-Day Detection Gap and Disclosure
“Protos reported that Nomic's social media account had not posted since 2024 and that the protocol's GitHub had not seen a commit in approximately two years”
reviewerProtos reported Nomic's X account had not posted since 2024 and GitHub had no commit in about two yearsMatches Protos. - #9[confirmed][no action needed]in section: Impact on Osmosis allBTC Reserve Backing
“To restore full 1:1 parity, even if the frozen 22.65 BTC were successfully seized, an additional approximately 17.19 BTC would still be required from Osmosis's community pool.”
reviewer39.84 nBTC is 36.03% of allBTC backing; 110.57 allBTC in circulation; 70.73 BTC valid; 17.19 BTC still neededAll figures match CryptoSlate. - #10[confirmed][no action needed]in section: Recovery Plan and Governance Response
“Osmosis announced it would cancel a pending USDC.noble liquidity redeployment as part of the remediation.”
reviewerRecovery plan includes cancelling a USDC.noble liquidity redeploymentCorroborated through search results only; the cited Crypto Briefing page was not fetched.