Fact-check findings
What an automated fact-checker found when it re-read Ionic Protocol 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
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #6[unverifiable][awaiting moderator]in section: ezETH integration and April 2024 depeg
“The ION token reached an all-time high of approximately $0.0694 and has since declined more than 99.9% to trade below $0.0001, with minimal trading volume.”
reviewerION token price, supply and ATH figuresMarket-data pages were not fetched successfully, so this claim was not checked. Prices are volatile and the figure is likely out of date.
stale
1 claimThe claim was accurate when written but events since have overtaken it.
- #5[stale][awaiting moderator]in section: ezETH integration and April 2024 depeg
“whether the protocol remains actively maintained is not clearly established in public sources.”
reviewerPage says no compensation plan and that maintenance status is unclear, while DefiLlama marks the protocol DeprecatedPage's 'as of mid-2025' hedging is stale as of Oct 2026. Correction rests on a search snippet because the page fetch was blocked, so it needs a human check before applying.Proposed correction (not yet applied)DefiLlama lists the protocol as deprecated, with TVL data ending in June 2025, and no compensation plan for users affected by the February 2025 exploit has been publicly announced.
partially supported
2 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in the timeline
“Attacker bridges about 1,204 ETH (roughly $3.2M) from Mode Network to Ethereum and launders it through Tornado Cash.”
reviewerBridged ETH figure and Tornado Cash laundering attributed to HalbornLaundering via Tornado Cash is supported. The 1,204 ETH / $3.2M figure comes from Rekt, not the cited Halborn source, which says about $3.5M. - #4[partially supported][awaiting moderator]in section: Fund flow and Tornado Cash laundering
“Pages differ on where the roughly $3.7 million in outstanding loans sat: one describes Ironclad and Layerbank as on 'Move Protocol', while another describes approximately $3.7 million in MBTC loans remaining on Mode Network”
reviewerIronclad and Layerbank loans placement; Rekt says MBTC loans remain on 'Move'Rekt does say the loans were on 'Move'. The sentence is an internal-conflict note rather than a settled fact, and the 'Move Protocol' wording is not clearly in the source.
confirmed
2 claimsThe cited evidence supports the claim as written.
- #1[confirmed][no action needed]in section: February 2025 exploit: social engineering via fake LBTC collateral
“Halborn and most secondary sources cited $8.6 million”
reviewerHalborn cited approximately $8.6 million as the lossHalborn gives $8.6M, a social-engineering attack posing as Lombard Finance, 250 fake LBTC and a 0.01 ETH starting balance. - #2[confirmed][no action needed]in section: February 2025 exploit: social engineering via fake LBTC collateral
“Rekt News cited approximately $6.9 million”
reviewerRekt News cited approximately $6.9 millionMatches Rekt News.