← Panoptic V1.1reviewed 2026-10-16 · 22 claims checked
Fact-check findings
What an automated fact-checker found when it re-read Panoptic V1.1 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
8 claimsThe 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 the summary
“A coordinated whitehat rescue secured over 98% of remaining at-risk funds, and ZachXBT flagged the incident, contributing to reduced community trust in the V1.1 deployment.”
reviewerZachXBT flagged the Panoptic incident, contributing to reduced community trustNo citation is given for this claim and extensive searching found zero reporting linking ZachXBT to the Panoptic incident. The authoritative post-mortem lists who was involved in flagging/responding to the incident and does not include him; this appears to be a fabricated or misattributed detail.Proposed correction (not yet applied)A coordinated whitehat rescue secured over 98% of remaining at-risk funds, and the incident contributed to reduced community trust in the V1.1 deployment. - #2[disputed][awaiting moderator]in section: Risk Assessment
“ZachXBT flagged the entity, consistent with community-level concern following the incident disclosure.”
reviewerZachXBT flagged the entity, consistent with community-level concern following the incident disclosureSame unsupported claim repeated in the Risk Assessment section; see summary finding for detail.Proposed correction (not yet applied)Community-level concern followed the incident disclosure. - #3[disputed][awaiting moderator]in section: On-Chain Evidence
“The SemiFungiblePositionManager is documented in Panoptic's canonical deployment references with an Ethereum address of 0x1393ad734EA3c52865b4B541cf049dafd25c23a5.”
reviewerThe SemiFungiblePositionManager's Ethereum address is 0x1393ad734EA3c52865b4B541cf049dafd25c23a5Direct contradiction: the cited Etherscan URL resolves to an unrelated TitanX contract, not Panoptic's SFPM. Panoptic's own deployment-addresses documentation gives a different address entirely.Proposed correction (not yet applied)The SemiFungiblePositionManager is documented in Panoptic's canonical deployment references with an Ethereum address of 0x0000000000000aAbbcfCA8100a9ee78124E97B33. - #4[disputed][awaiting moderator]in section: On-Chain Evidence
“https://etherscan.io/address/0x1393ad734EA3c52865b4B541cf049dafd25c23a5”
reviewerEtherscan source link for the SemiFungiblePositionManager addressSame underlying wrong-address defect reflected in the cited source URL; see sections[3].content finding.Proposed correction (not yet applied)https://etherscan.io/address/0x0000000000000aAbbcfCA8100a9ee78124E97B33 - #5[disputed][awaiting moderator]in the cited sources
“https://etherscan.io/address/0x1393ad734EA3c52865b4B541cf049dafd25c23a5”
reviewerEtherscan source link for the SemiFungiblePositionManager address (sources_used)Same wrong-address defect as it appears in the page-level sources_used list.Proposed correction (not yet applied)https://etherscan.io/address/0x0000000000000aAbbcfCA8100a9ee78124E97B33 - #6[disputed][awaiting moderator]in section: Incident Details — August 2025 Position Spoofing Vulnerability
“Roughly $1.6 million remained at risk by August 27.”
reviewerRoughly $1.6 million remained at risk by August 27 (incident details prose)The page attributes the $1.6M remaining-at-risk figure to August 27, but Panoptic's own post-mortem places that figure on the evening of August 26; by August 27 morning the remaining amount had already dropped to roughly $550k.Proposed correction (not yet applied)Roughly $1.6 million remained at risk by the evening of August 26. - #7[disputed][awaiting moderator]in the timeline
“2025-08-27”
reviewerTimeline: $1.6 million remained at risk, dated 2025-08-27Same underlying date error as the Incident Details prose; the timeline entry's event text (about $1.6M remaining) is itself accurate, but it is filed under the wrong date.Proposed correction (not yet applied)2025-08-26 - #8[disputed][awaiting moderator]in the timeline
“2022-04-28”
reviewerGuillaume Lambert published the Panoptic whitepaper on arXiv in April 2022, dated 2022-04-28 in the timelineOff-by-one-day error against arXiv's own submission-history record. The summary/section prose only says 'April 2022' (correct at month granularity); only the timeline's day-level date is wrong.Proposed correction (not yet applied)2022-04-27
unverifiable
1 claimNo source the reviewer could reach confirms or contradicts the claim.
- #22[unverifiable][awaiting moderator]in section: Team and Background
“Lambert holds a BS in Physics from McGill University (2004–2007) and a PhD in Physics from Princeton University (2007–2011). He subsequently held postdoctoral and visiting scholar positions at the University of Chicago and Harvard's Wyss Institute, before serving as an assistant professor of applied and engineering physics at Cornell University from July 2016.”
reviewerGuillaume Lambert's specific education dates: BS Physics McGill (2004-2007), PhD Physics Princeton (2007-2011), postdoc/visiting scholar at University of Chicago and Harvard's Wyss Institute, assistant professor at Cornell from July 2016Could not independently confirm these specific dates/institutions from the cited source or other searches; the cited theorg.com profile does not contain this information at all, which is a link-support gap even though the underlying facts could not be shown false either.
partially supported
1 claimThe cited evidence supports part of the claim but not all of it.
- #12[partially supported][awaiting moderator]in section: Audit History
“Post-incident, Panoptic announced a V2 protocol with three planned audits: Obsidian (Audit 1), Nethermind (Audit 2), and a competitive audit (Audit 3).”
reviewerPost-incident, Panoptic announced a V2 protocol with three planned audits: Obsidian (Audit 1), Nethermind (Audit 2), and a competitive audit (Audit 3)The page undercounts the V2 audit plan by one (omits the final Obsidian review), likely because that audit was scheduled/completed after the page's sources were gathered.
confirmed
12 claimsThe cited evidence supports the claim as written.
- #9[confirmed][no action needed]in section: Overview
“with DeFiLlama reporting approximately $2,373 in TVL distributed across Base, Unichain, and Ethereum”
reviewerPanoptic V1.1's TVL is approximately $2,373 across Base, Unichain, and EthereumOrder of magnitude and chain distribution match; TVL is inherently a live, moving figure so minor variance is expected and not a defect. - #10[confirmed][no action needed]in section: Audit History
“Code4rena completed an initial audit in April 2024, which identified 2 high-severity and 9 medium-severity findings”
reviewerCode4rena April 2024 audit identified 2 high-severity and 9 medium-severity findingsDirectly confirmed by the cited Code4rena report. - #11[confirmed][no action needed]in section: Audit History
“For V1.1: Cantina completed an initial review on November 7, 2024 and a final review on November 20, 2024. Code4rena conducted a V1.1 review finalized January 28, 2025.”
reviewerCantina completed an initial V1.1 review on November 7, 2024 and a final review on November 20, 2024; Code4rena completed a V1.1 review finalized January 28, 2025 with two independent wardensAll three dates and the warden count are confirmed by Panoptic's own security-audits page. - #13[confirmed][no action needed]in section: On-Chain Evidence
“The CREATE3 factory used for deterministic deployment is at 0x000000000000b361194cfe6312EE3210d53C15AA.”
reviewerThe CREATE3 factory for deterministic deployment is at 0x000000000000b361194cfe6312EE3210d53C15AAConfirmed against Panoptic's own GitHub deployment docs; this is a shared public vanity-CREATE3 tool, not exclusive to Panoptic, but Panoptic's own repo confirms using it. - #14[confirmed][no action needed]in section: On-Chain Evidence
“Base (contract 0xa32b14c4e35d1a1cdd2bbe06213ba90eddb1433c on BaseScan)”
reviewerBase contract 0xa32b14c4e35d1a1cdd2bbe06213ba90eddb1433c is Panoptic's deploymentConfirmed via direct contract verification on BaseScan. - #15[confirmed][no action needed]in section: Overview
“The protocol raised $4.5 million in a December 2022 seed round led by gumi Cryptos Capital, with participation from Uniswap Labs Ventures, Coinbase Ventures, and Jane Street.”
reviewerPanoptic raised $4.5 million in a December 2022 seed round led by gumi Cryptos Capital, with Uniswap Labs Ventures, Coinbase Ventures, and Jane Street participatingConfirmed by The Block's original reporting. - #16[confirmed][no action needed]in section: Overview
“A second $7 million seed round closed in November 2023, led by Greenfield Capital with participation from HashKey, Zee Prime Capital, and others, bringing total disclosed funding to $11.5 million.”
reviewerA second $7 million seed round closed in November 2023, led by Greenfield Capital, bringing total disclosed funding to $11.5 millionConfirmed by The Block's original reporting. - #17[confirmed][no action needed]in section: Incident Details — August 2025 Position Spoofing Vulnerability
“On August 25, 2025, a researcher affiliated with Cantina reported a critical vulnerability to the Panoptic team.”
reviewerAugust 25, 2025 vulnerability disclosure, XOR-based fingerprinting collision flaw, flash-loan exploit path, four-hour confirmation, 72-hour notification windowCore technical narrative of the incident is confirmed by the primary source. - #18[confirmed][no action needed]in section: Incident Details — August 2025 Position Spoofing Vulnerability
“On August 28 at 5:55 PM EDT, the team executed a whitehat rescue on Ethereum mainnet at block 23242436, followed by additional rescues on Base and Unichain.”
reviewerWhitehat rescue executed August 28, 2025 at 5:55 PM EDT at block 23242436, over 98% of remaining at-risk funds (~$550,000) secured, funds sent to vault.panoptic.eth with Merkle-root in-kind redistributionConfirmed in detail against the primary source, including the precise timestamp and block number. - #19[confirmed][no action needed]in section: Incident Details — August 2025 Position Spoofing Vulnerability
“The Cantina researcher who disclosed the vulnerability received the protocol's maximum bug bounty of $250,000.”
reviewerCantina researcher received the protocol's maximum bug bounty of $250,000Confirmed against both the post-mortem and the live bounty program page. - #20[confirmed][no action needed]in section: On-Chain Evidence
“The on-chain forensics were classified by DeFiLlama as a Protocol Logic vulnerability affecting all three deployed chains simultaneously.”
reviewerDeFiLlama classified the on-chain forensics as a Protocol Logic vulnerability affecting all three deployed chains simultaneouslyConfirmed. - #21[confirmed][no action needed]in section: Overview
“The protocol was conceived by Guillaume Lambert, an assistant professor of applied and engineering physics at Cornell University, who observed that concentrated liquidity provisioning in Uniswap V3 is mathematically equivalent to selling options in traditional finance.”
reviewerGuillaume Lambert is an assistant professor of applied and engineering physics at Cornell University who derived the Uniswap V3 LP / options equivalence after becoming an active LPCore narrative confirmed; specific degree years (McGill BS 2004-2007, Princeton PhD 2007-2011) and the Chicago/Harvard Wyss postdoc detail could not be independently verified — the cited theorg.com profile page returned only his current CEO role with no education or prior-career listing visible.
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.