Skip to main content
AVOID.NET
← Zorareviewed 2026-10-08 · 13 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Zora 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 1partially supported 3confirmed 90 corrections pending · 0 applied

unverifiable

1 claim

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

  1. #9[unverifiable][awaiting moderator]in the timeline
    “ZORA reported all-time high of about $0.1456.”
    reviewerZORA all-time high of about $0.1456 in August 2025Exchange price page returned 503 and the ATH is not independently corroborated. Tier-3 source; the figure is moving data.

partially supported

3 claims

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

  1. #7[partially supported][awaiting moderator]in section: Chain activity, TVL and technical risk
    “L2BEAT reports Zora's total value secured at about $5.19M (down 11.4% over seven days), almost entirely canonically bridged ETH.”
    reviewerL2BEAT TVS about $5.19M, down 11.4% over seven daysLive figures differ slightly from the page's, which is expected for a live dashboard. Order of magnitude and composition are right. The figures should be dated.
  2. #10[partially supported][awaiting moderator]in section: Token performance
    “Against the August 2025 high this implies a decline of roughly 95%, consistent with the rumour's range of FDV decline, though aggregator data conflict with one another and should be treated as approximate.”
    reviewerZORA around $0.006-0.008 in July 2026 and roughly 95% below the August 2025 highThe arithmetic is sound (0.007 / 0.1456 is about 95% down) and the page hedges. The underlying aggregator prices were not independently verified, and the 'rumour's range' was never retrieved.
  3. #12[partially supported][awaiting moderator]in section: Team, funding and business model
    “Reports also describe a Zora attention market launching on Solana, suggesting strategic focus has moved away from its own L2.”
    reviewerReports describe a Zora attention market on Solana, suggesting focus has moved away from its own L2The Solana launch is supported. The inference about Zora's own L2 is the page's own and is not stated by the source; the article concerns Zora's de-emphasis of Base.

confirmed

9 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Team, funding and business model
    “Per TechFlow, Zora was founded in 2020, had early backing from Coinbase's venture arm, and raised about $60M over three rounds.”
    reviewerZora was founded in 2020, with early Coinbase venture backing and about $60M raised over three roundsMatches the TechFlow article. Single secondary source.
  2. #2[confirmed][no action needed]in section: Token performance
    “The ZORA token launched on Base in April 2025 with a 10 billion supply.”
    reviewerZORA token launched on Base in April 2025 with 10 billion supplySupported by TechFlow. The article does not itself say Base in that sentence, though the July 2025 item references Base.
  3. #3[confirmed][no action needed]in section: Token performance
    “A TechFlow article (October 2025) cited an FDV of about $850M and a Robinhood listing in October 2025.”
    reviewerTechFlow cited FDV of about $850M and a Robinhood listing in October 2025Both figures match the article.
  4. #4[confirmed][no action needed]in section: Team, funding and business model
    “trading fees were reported cut from 3% to 1% in October 2025”
    reviewerTrading fees cut from 3% to 1% in October 2025The article gives October without a stated year; the context implies 2025.
  5. #5[confirmed][no action needed]in the timeline
    “Major update enabled mass creator-coin issuance via Base.”
    reviewerJuly 2025 update enabled mass creator-coin issuance via BaseConsistent with the source.
  6. #6[confirmed][no action needed]in the timeline
    “Zora Network, an OP Stack Ethereum L2, launched.”
    reviewerZora Network launched June 2023 as an OP Stack L2The date is correct. The timeline source label 'Search summary of L2BEAT/industry docs' is vague and could be tidied to 'L2BEAT'.
  7. #8[confirmed][no action needed]in section: Chain activity, TVL and technical risk
    “The page also notes the 2026-07-01 'Karst' upgrade kept permissioned fault proofs and recorded liveness gaps of about three hours on 2026-10-07.”
    reviewerL2BEAT states fault proofs non-functional, permissioned actors, no upgrade delay, no exit window; Karst upgrade 2026-07-01 kept permissioned fault proofs; ~3h liveness gaps 2026-10-07All risk statements match L2BEAT. The permissioned challenger and proposer reliance is also stated.
  8. #11[confirmed][no action needed]in section: Shutdown rumour and official announcements
    “Zero Network, a different Ethereum L2 built by Zerion that announced in May 2026 it would wind down”
    reviewerZero Network (a different L2 by Zerion) announced a wind-down in May 2026Accurate.
  9. #13[confirmed][no action needed]in section: Shutdown rumour and official announcements
    “L2BEAT's Zora page carries no 'archived' or 'deprecated' label.”
    reviewerNo official wind-down announcement found and L2BEAT carries no archived labelConsistent at the time of review. The absence claim is appropriately hedged on the page.
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.