Skip to main content
AVOID.NET

Fact-check findings

What an automated fact-checker found when it re-read Osmosis (allBTC / Nomic Bridge Double-Spend Exploit, September 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.

unverifiable

3 claims

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

  1. #6[unverifiable][awaiting moderator]in section: The Nomic Double-Spend Exploit and allBTC Freeze
    “the attacker exploited this flaw across roughly 25 inter-network transfers”
    reviewerExploit across roughly 25 inter-network transfersI could not find the 25-transfer figure in the sources I fetched. Forklog was not fetched.
  2. #10[unverifiable][awaiting moderator]in section: Root Cause: Third-Party Bridge Risk, Not a Direct Osmosis Chain Compromise
    “Nomic's own documentation describes nBTC as designed to be backed 'exactly 1:1' by Bitcoin held in a decentralized, validator-controlled multisig custody reserve”
    reviewerNomic documentation: 90% signing threshold, 1:1 backing, circuit breakers; 18 forwarding code pathsI did not fetch docs.nomic.io or Forklog, so the 1:1 wording, circuit breakers and the '18 code paths' detail are unchecked.
  3. #11[unverifiable][awaiting moderator]in section: Broader Context: Prior Osmosis Security History
    “The Osmosis core team and validators halted the chain at block 4,713,064 to stop the exploit”
    reviewer2022 Osmosis exploit: about $5M, chain halted at block 4,713,064, June 2022Not fetched in this review. The page's timeline carries the same block height in its date_evidence field, so internally consistent. The 2023 Levana claim was also not checked.

stale

2 claims

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

  1. #1[stale][awaiting moderator]in the summary
    “but as of the most recent reporting that remediation had not been executed.”
    reviewerRemediation (seizure of 22.65 BTC plus community-pool top-up) had not been executed as of most recent reportingPage relies on Sept 9-10 reporting. A later report (Oct 29) says the governance proposal passed. Single secondary source for the passage; the Osmosis governance record was not directly checked.
    Proposed correction (not yet applied)
    and, according to an October 29, 2026 ChainCatcher report, a governance proposal carrying out that remediation has since passed.
  2. #2[stale][awaiting moderator]in section: Proposed Governance Remediation Remains Unexecuted
    “meaning the proposed fix had not yet been formally submitted, let alone voted on or executed.”
    reviewerProposal not yet submitted, voted on or executedTrue as of Sept 9 per eGamers and CryptoSlate, but superseded.
    Proposed correction (not yet applied)
    meaning the proposed fix had not yet been formally submitted as of that date; ChainCatcher reported on October 29, 2026 that a governance proposal has since passed.

partially supported

3 claims

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

  1. #3[partially supported][awaiting moderator]in section: Proposed Governance Remediation Remains Unexecuted
    “No source reviewed for this report confirms that allBTC minting and redemption have since resumed or that the shortfall has been fully covered”
    reviewerPage says no source confirms the shortfall has been coveredHedge is honest about the review window, but is now outdated given the passed proposal. Resumption of minting and redemption is still unconfirmed.
  2. #4[partially supported][awaiting moderator]in section: Emergency Response and Partial Fund Freeze
    “Researcher Rarma's trace, cited by Forklog and eGamers, indicated that a separate portion of the exploited funds”
    reviewerRoughly 671 ETH sent to Tornado Cash per Forklog and eGamersThe 671 ETH figure is real, but Protos supports it and eGamers does not. The attribution is wrong. The Forklog article was not fetched.
  3. #7[partially supported][awaiting moderator]in section: Disclosure Lag: Roughly 74 Days Between Exploit and Public Notice
    “Protos noted that Nomic's last public social media post predated the incident by roughly two years and its GitHub repository had seen no recent commits”
    reviewerNomic last public social post predated the incident by roughly two years and GitHub had no recent commitsApproximately right, but slightly overstated for the social media account.

confirmed

3 claims

The cited evidence supports the claim as written.

  1. #5[confirmed][no action needed]in section: The Nomic Double-Spend Exploit and allBTC Freeze
    “Reporting from CryptoSlate and Forklog put allBTC circulation at roughly 110.57 tokens against the compromised nBTC making up about 36.03% of the basket's nominal backing, leaving roughly 70.73 BTC-equivalent of other, apparently valid, collateral.”
    reviewerMain minting on June 25, 2026; 39.84 / 40.65 nBTC figures; 22.65 BTC frozen; 36.03%; 110.57 allBTC; 70.73 BTC; 17.19 BTC gapCore figures match. The CryptoSlate text cached for me did not show the 40.65 or '25 transfers' details.
  2. #8[confirmed][no action needed]in section: Disclosure Lag: Roughly 74 Days Between Exploit and Public Notice
    “Osmosis's public disclosure came only after Nomic halted its own protocol and after independent research surfaced the discrepancy”
    reviewerDisclosure followed Nomic halting its protocol; 74-day gap; Osmosis blamed Nomic, not Osmosis or IBCConsistent with the timeline's Sept 7 halt.
  3. #9[confirmed][no action needed]in section: Emergency Response and Partial Fund Freeze
    “allBTC's pause authority rests with a 3-of-6 moderator subDAO empowered to halt the pool or flag a constituent asset”
    reviewer3-of-6 moderator subDAO empowered to pause poolThe page's follow-on clause that the subDAO 'exercised that power to freeze the compromised funds' is only loosely supported. The sources describe the freeze as a validator-coordinated emergency upgrade.
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.