Skip to main content
AVOID.NET
← Light Protocolreviewed 2026-09-07 · 30 claims checked

Fact-check findings

What an automated fact-checker found when it re-read Light Protocol 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.

disputed 4unverifiable 2stale 2link rot 4partially supported 2confirmed 1610 corrections pending · 0 applied

disputed

4 claims

The reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.

  1. #8[disputed][awaiting moderator]in the timeline
    “2022-10-17”
    reviewerThe seed round closed on October 17, 2022Two independent funding databases date the seed round close to October 18, 2022, one day later than the page's timeline entry.
    Proposed correction (not yet applied)
    2022-10-18
    citedmedium.com/light-protocol-writings/annou…ise-3f19f5d3f66f
  2. #11[disputed][awaiting moderator]in section: Security Audits and Formal Verification
    “Zellic conducted Programs audit #3 (completed August 28, 2024)”
    reviewerZellic completed Programs audit #3 on August 28, 2024Two independent primary sources (the project's own security page and its audits repository filenames) date the Zellic audit to September 2024, not August 28.
    Proposed correction (not yet applied)
    Zellic conducted Programs audit #3 (completed September 2024)
    citedwww.zkcompression.com/references/security
  3. #17[disputed][awaiting moderator]in the timeline
    “OtterSec completes Zerocopy audit; Accretion and HashCloak complete ZK Compression v2 component reviews.”
    reviewerIn March 2025, OtterSec completed the Zerocopy audit and Accretion and HashCloak completed ZK Compression v2 component reviewsThe audits repository shows Accretion's ZK Compression v2 component review was completed in June 2025, three months after the date this timeline entry attaches to it; HashCloak's and OtterSec's March 2025 audits are correctly dated.
    Proposed correction (not yet applied)
    OtterSec completes Zerocopy audit; HashCloak completes a ZK Compression v2 component review (Accretion's ZK Compression v2 component review follows in June 2025).
    citedwww.zkcompression.com/references/security
  4. #18[disputed][awaiting moderator]in the timeline
    “Light Token Program announced at Breakpoint 2025. OtterSec and Certora conduct audits of CPI Context Refactor and Light Token extension respectively.”
    reviewerIn December 2025, OtterSec and Certora conducted audits of the CPI Context Refactor and Light Token extension respectivelyThis entry conflates two separate Certora engagements: the December 2025 audit was of the base Light Token program, while the 'extension' audit (already correctly dated elsewhere on this page as March 2026, see timeline[11] and sections[3]) was a later, distinct review. As written, this entry contradicts the page's own March 2026 dating of the same-named audit.
    Proposed correction (not yet applied)
    Light Token Program announced at Breakpoint 2025. OtterSec conducts an audit of the CPI Context Refactor; Certora conducts an audit of the base Light Token program (a separate Certora review of Light Token extensions follows in 2026).
    citedwww.zkcompression.com/references/security

unverifiable

2 claims

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

  1. #4[unverifiable][awaiting moderator]in section: Team Transparency
    “The project's public face is co-founder Swen Schäferjohann, who holds the title of Co-Founder and Managing Director at Luminous Labs.”
    reviewerSwen Schäferjohann holds the title of Co-Founder and Managing Director at Luminous LabsSchäferjohann's co-founder role is well corroborated elsewhere, but the specific 'Managing Director' title could not be independently confirmed because the cited LinkedIn profile is not accessible without authentication.
    citedwww.linkedin.com/in/swen-schaeferjohann/
  2. #10[unverifiable][awaiting moderator]in section: Security Audits and Formal Verification
    “Neodyme conducted Programs audit #2 (completed August 15, 2024)”
    reviewerNeodyme completed Programs audit #2 on August 15, 2024The August 2024 month is corroborated by two sources, but neither source confirms the specific day of August 15; the exact date could not be verified either way.
    citedwww.zkcompression.com/references/security

stale

2 claims

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

  1. #3[stale][awaiting moderator]in section: Overview and Background
    “The company operating the project is Luminous Labs Lda, headquartered in Lisbon, Portugal.”
    reviewerLuminous Labs Lda, headquartered in Lisbon, Portugal, is the company currently operating Light ProtocolThe page nowhere mentions that Helius acquired Light Protocol in June 2026, roughly three months before this review; describing Luminous Labs Lda as the current sole operator without qualification is now out of date.
    Proposed correction (not yet applied)
    Light Protocol was operated by Luminous Labs Lda, headquartered in Lisbon, Portugal, until Solana infrastructure firm Helius acquired Light Protocol on June 10, 2026.
    citedlightprotocol.com/
  2. #26[stale][awaiting moderator]in the summary
    “Light Protocol is a Solana-native ZK compression infrastructure layer developed by Luminous Labs Lda, a Portugal-based company co-founded in 2021 by Swen Schäferjohann.”
    reviewerLight Protocol is described as a company developed by Luminous Labs Lda, a Portugal-based company co-founded in 2021The summary presents Luminous Labs Lda as the current independent operator of Light Protocol without noting that Helius acquired the company in June 2026; this is a material, dated omission rather than an outright fabrication.
    Proposed correction (not yet applied)
    Light Protocol is a Solana-native ZK compression infrastructure layer originally developed by Luminous Labs Lda, a Portugal-based company co-founded in 2021 by Swen Schäferjohann; Solana infrastructure firm Helius acquired Light Protocol in June 2026.

partially supported

2 claims

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

  1. #16[partially supported][awaiting moderator]in section: Security Audits and Formal Verification
    “The project operates a live bug bounty program on Immunefi launched September 12, 2024, with a maximum critical bounty of $50,000 (calculated at 10% of funds at risk, minimum $10,000) covering 17 in-scope assets.”
    reviewerImmunefi bug bounty launched September 12, 2024, max critical bounty $50,000 (10% of funds at risk, minimum $10,000), 17 in-scope assets, KYC required for payoutsThe $50,000 critical cap, the 10%-of-funds-affected calculation, and the KYC requirement match Immunefi's generally documented Light Protocol program terms found via search. The specific launch date (Sept 12, 2024), the $10,000 minimum, and the count of 17 in-scope assets could not be independently confirmed because the cited URL now 404s (see linked link_rot findings).
    citedimmunefi.com/bug-bounty/light-protocol/information/
  2. #22[partially supported][awaiting moderator]in section: Controversy: L2 Framing Debate
    “Critics, notably Ethereum investor Ryan Berckmans and ZKsync founder Alex Gluchowski, argued that ZK Compression shares features with Ethereum validity rollups and Ethereum's planned statelessness with Verkle trees, and that marketing it as a native L1 primitive rather than an L2 was misleading.”
    reviewerRyan Berckmans and Alex Gluchowski argued ZK Compression shares features with Ethereum validity rollups and planned Verkle-tree statelessnessGluchowski is confirmed to have publicly criticized the ZK Compression framing on X, but the specific technical argument the page attributes to him (comparison to Ethereum's planned Verkle-tree statelessness) does not match the quote found in independent reporting, and neither of the page's own two cited sources for this section mentions Gluchowski by name.
    citedthedefiant.io/news/blockchains/zk-compre…ites-controversysolanafloor.com/news/light-protocol-brin…-sparking-debate

confirmed

16 claims

The cited evidence supports the claim as written.

  1. #1[confirmed][no action needed]in section: Overview and Background
    “reducing account storage costs by up to 5,000x for token accounts and approximately 160x for program-derived accounts (PDAs) compared to standard Solana accounts”
    reviewerZK Compression reduces token account storage costs by up to 5,000x and PDA costs by approximately 160xBoth figures are corroborated verbatim by the cited article.
    citedwww.theblock.co/post/301368/light-protoc…cale-solana-apps
  2. #2[confirmed][no action needed]in section: Overview and Background
    “ZK Compression was publicly co-developed with Helius Labs and launched on Solana mainnet and devnet in June 2024.”
    reviewerZK Compression was co-developed with Helius Labs and launched on Solana mainnet and devnet in June 2024Multiple independent outlets confirm the June 2024 joint launch.
    citedwww.theblock.co/post/301368/light-protoc…cale-solana-apps
  3. #5[confirmed][no action needed]in section: Team Transparency
    “A second co-founder is referred to informally as 'Joe' in at least one public narrative account and described as a childhood friend of Schäferjohann; this individual's full surname has not been confirmed in Tier 1 or 2 sources reviewed.”
    reviewerA second co-founder, referred to as 'Joe,' is a childhood friend of Schäferjohann whose surname is unconfirmedDirectly corroborated by the cited profile piece.
    citedsolanacompass.com/learn/Lightspeed/the-n…en-schaferjohann
  4. #6[confirmed][no action needed]in section: Controversy: L2 Framing Debate
    “Helius Labs co-founder Mert Mumtaz countered that Solana's decoupling of compute and data is architecturally distinct from Ethereum's approach.”
    reviewerHelius Labs co-founder Mert Mumtaz countered the L2-framing criticismMumtaz's co-founder title and defense of the framing are both corroborated, though independent reporting shows he was not the only defender (Anatoly Yakovenko and Austin Federa also spoke up); see coverage gaps.
    citedthedefiant.io/news/blockchains/zk-compre…ites-controversy
  5. #7[confirmed][no action needed]in section: Funding and Backers
    “Light Protocol has raised a total of $4.2 million USD across two rounds.”
    reviewerLight Protocol has raised a total of $4.2 million USD across two rounds (pre-seed plus seed)No source discloses a separate pre-seed dollar figure; independent aggregators (Tracxn, general web summaries) also describe $4.2M as Light Protocol's total raised, consistent with the page's framing.
    citedmedium.com/light-protocol-writings/annou…ise-3f19f5d3f66f
  6. #9[confirmed][no action needed]in section: Security Audits and Formal Verification
    “OtterSec conducted Programs audit #1”
    reviewerOtterSec conducted Programs audit #1 for ZK Compression v1Confirmed by both the official security page and the audits folder.
    citedwww.zkcompression.com/references/security
  7. #12[confirmed][no action needed]in section: Security Audits and Formal Verification
    “OtterSec reviewed the Zerocopy module (March 2025)”
    reviewerOtterSec reviewed the Zerocopy module in March 2025Confirmed.
    citedwww.zkcompression.com/references/security
  8. #13[confirmed][no action needed]in section: Security Audits and Formal Verification
    “OtterSec reviewed the CPI Context Refactor (December 2025)”
    reviewerOtterSec reviewed the CPI Context Refactor in December 2025Confirmed.
    citedwww.zkcompression.com/references/security
  9. #14[confirmed][no action needed]in section: Security Audits and Formal Verification
    “The Groth16 ZK circuits used by the protocol were formally verified by Reilabs, which provides mathematical-level soundness assurance beyond standard code audit.”
    reviewerGroth16 ZK circuits were formally verified by ReilabsConfirmed by both the official security page and the audits repository.
    citedwww.zkcompression.com/references/security
  10. #15[confirmed][no action needed]in section: Security Audits and Formal Verification
    “Certora conducted a security assessment of the Light Token (CToken) extension in March 2026, identifying security issues that were addressed by the team; the full report is available on Certora's website.”
    reviewerCertora assessed the Light Token (CToken) extension in March 2026, finding issues the team addressedDirectly confirmed by the cited primary source; this is a distinct, later report from the base 'Light Token' Certora audit completed December 2025 (see coverage gaps).
    citedwww.certora.com/reports/light-extension
  11. #19[confirmed][no action needed]in the timeline
    “Version 0.23.0 released for production use with ZK Compression V2.”
    reviewerVersion 0.23.0 was released in March 2026 for production use with ZK Compression V2Exact date (March 24, 2026) and description both confirmed.
    citedgithub.com/Lightprotocol/light-protocol/releases
  12. #20[confirmed][no action needed]in section: ZK and Smart Contract Technical Risk
    “At peak load, this single program accounted for over half of all Geyser streaming traffic across Triton's infrastructure (multiple Gbps).”
    reviewerAt peak load, Light Protocol accounted for over half of all Geyser streaming traffic on Triton's infrastructure (multiple Gbps)Directly and precisely confirmed by the cited blog post.
    citedblog.triton.one/light-protocol-program-e…stone-streaming/
  13. #21[confirmed][no action needed]in section: Controversy: L2 Framing Debate
    “Berckmans called the framing 'unethical BS' in an X post.”
    reviewerRyan Berckmans called the L1/L2 framing 'unethical BS' in an X postQuote confirmed verbatim.
    citedthedefiant.io/news/blockchains/zk-compre…ites-controversy
  14. #23[confirmed][no action needed]in section: Regulatory and Legal Standing
    “No SEC enforcement actions, CFTC proceedings, DOJ indictments, OFAC designations, or civil litigation involving Light Protocol, Luminous Labs Lda, or co-founder Swen Schäferjohann have been identified in available sources.”
    reviewerNo SEC, CFTC, DOJ, or OFAC actions or civil litigation have been identified against Light Protocol, Luminous Labs, or SchäferjohannNo contrary evidence found; absence claim treated as confirmed for the scope of sources searched.
    citedlightprotocol.com/
  15. #24[confirmed][no action needed]in section: Incidents and Security History
    “No hacks, exploits, or fund-loss incidents have been identified for Light Protocol or ZK Compression in reviewed sources as of mid-2026.”
    reviewerNo hacks, exploits, or fund-loss incidents have been identified for Light Protocol or ZK CompressionNo contrary evidence of a hack or exploit found during review.
    citedimmunefi.com/bug-bounty/light-protocol/information/
  16. #25[confirmed][no action needed]in the timeline
    “Light Protocol founded by Swen Schäferjohann and co-founder 'Joe' with initial focus on ZK privacy for Solana.”
    reviewerLight Protocol was founded by Swen Schäferjohann and co-founder 'Joe' in July 2021 with an initial focus on ZK privacy for SolanaConsistent with the cited source; 'summer 2021' reasonably resolves to the stated July 2021 month.
    citedsolanacompass.com/learn/Lightspeed/the-n…en-schaferjohann
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.