Fact-check findings
What an automated fact-checker found when it re-read LayerZero Labs 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.
disputed
1 claimThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in section: Regulatory and Legal Status
“No class-action lawsuits or court filings related to the KelpDAO exploit or ZRO token controversy were found in available sources.”
reviewerNo class-action lawsuits or court filings related to the KelpDAO exploit were foundA court filing related to the exploit exists and predates the page's own 'As of September 2026' framing. The section has no sources and its statement is contradicted.Proposed correction (not yet applied)In September 2026, Evercrest Technologies (the entity behind KelpDAO) filed a civil claim in the Supreme Court of British Columbia against LayerZero Labs Ltd., LayerZero Labs Canada Inc. and Bryan Pellegrino over the KelpDAO exploit, alleging negligent misrepresentation, negligence and defamation; the allegations are unproven and Pellegrino has called the claim meritless.
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #9[unverifiable][awaiting moderator]in section: The April 2026 KelpDAO Exploit: Infrastructure Compromise
“Mandiant, CrowdStrike, and independent security researchers attributed the attack to DPRK threat actor TraderTraitor (also known as UNC4899), a state-sponsored group also linked to the Lazarus Group.”
reviewerMandiant, CrowdStrike and researchers attributed the attack to TraderTraitor/UNC4899Could not read the report body. LayerZero's own April 20 attribution to TraderTraitor is confirmed via CoinDesk.
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #2[partially supported][awaiting moderator]in the summary
“its personnel had previously approved the single-verifier configuration that enabled the attack”
reviewerLayerZero personnel had previously approved the single-verifier configuration (stated as fact)The page's own body attributes this to KelpDAO's assertion. The summary presents a contested allegation as established. LayerZero's admission concerned its DVN acting as 1/1, not a confirmed approval. - #3[partially supported][awaiting moderator]in section: Ecosystem Migration: Approximately $15 Billion in Assets Exited LayerZero
“BitGo's WBTC ($7.4 billion)”
reviewerBitGo's WBTC migration is $7.4 billionThe cited CoinDesk article says about $7.3B and a later CoinDesk piece says $7.7B. $7.4B matches neither, so no single correction is proposed. The figure is likely a valuation difference. - #4[partially supported][awaiting moderator]in the timeline
“BitGo's decision to migrate WBTC ($7.4 billion) pushes publicly announced LayerZero-to-Chainlink migrations to nearly $15 billion.”
reviewerBitGo's WBTC ($7.4 billion) migration pushes the total to nearly $15 billion on 2026-08-04Date and total are right. The BitGo amount differs from the cited source ($7.3B). - #10[partially supported][awaiting moderator]in the timeline
“2024-06-01”
reviewerZRO launch date given as 2024-06-01The month is right, but the article URL indicates the launch and drop occurred around June 20-21, so the day-level date is imprecise. I did not fetch the source.
confirmed
4 claimsThe cited evidence supports the claim as written.
- #5[confirmed][no action needed]in the timeline
“LayerZero Labs issues statement attributing the exploit to KelpDAO's application-level configuration choices, and attributes the attack to North Korea's Lazarus Group.”
reviewerLayerZero attributed the attack to Lazarus Group after blaming KelpDAO's configuration on 2026-04-20Supported. The source calls the attribution preliminary. - #6[confirmed][no action needed]in the timeline
“LayerZero Labs formally admits it 'made a mistake,' acknowledging that its DVN should not have been permitted to act as a single verifier for high-value transactions.”
reviewerOn 2026-05-09 LayerZero Labs admitted it 'made a mistake' and said 'We own that.'Quotes verified. The blog post date may be May 8, but CoinDesk's date is May 9. - #7[confirmed][no action needed]in section: Systemic Risk: 47% of OApp Contracts Used Vulnerable Configuration
“Post-incident analysis based on Dune Analytics data found that 47% of active LayerZero omnichain application (OApp) contracts were operating under a 1-of-1 DVN configuration at the time of the attack”
reviewer47% of OApps used 1-of-1 DVN, over $4.5B exposure, USDT0 about 87%Figures match the source. The page's 'structural and widespread' framing omits the source's caveat on USDT0 2-of-2 usage. - #8[confirmed][no action needed]in the timeline
“The state of Wyoming joins the migration, moving its stablecoin infrastructure away from LayerZero.”
reviewerWyoming moved its stablecoin infrastructure away from LayerZero on 2026-08-18Supported. The scale of the Wyoming move is tiny, which the page does not say.