PancakeSwap AMM V3

PancakeSwap AMM V3 is the v3 DEX/AMM version of PancakeSwap, offering concentrated liquidity and multiple fee tiers, live on Ethereum and opBNB among other chains. Protocol identification

• Name: PancakeSwap V3 (AMM / Exchange V3).
• Category: Decentralized exchange (DEX) / automated market maker (AMM) with concentrated liquidity.
• Website: PancakeSwap main app and docs are referenced in Binance Academy and PancakeSwap docs, but exact URLs are treated as unverified marketing claims.
• Docs: Developer and audit documentation for “Exchange V3” and “PancakeV3Factory” are available under PancakeSwap’s developer and audit sections; content is used only as claims.
• Launch date (v3): V3 launched on BNB Chain and Ethereum in April 2023.
• Chains (focus of this query):
• Ethereum mainnet – supported and live since April 2023.
• opBNB – listed as a supported chain for PancakeSwap V3 in ecosystem descriptions.
• Native token: CAKE (PancakeSwap’s governance/utility token), per ecosystem descriptions. Main contract addresses & verification (Ethereum / opBNB)
• Ethereum PancakeSwap V3 Factory: Etherscan shows a verified contract PancakeSwap V3: Factory at 0x0BFbCF9fa4f9C56B0F40a671Ad40E0805A091865, created in tx 0x157ee3… with verified source and contract name matching v3 factory.
• Developer docs describe the PancakeV3Factory contract (createPool, getPool, poolDeployer, owner functions) as the v3 factory; this is an unverified marketing claim but consistent with the Etherscan-verified factory interface.
• Cross‑check: DefiLlama’s PancakeSwap v3 adapter references PancakeSwap v3 deployments across chains (including Ethereum/opBNB), supporting the identification of v3 as a multi‑chain AMM; specific addresses there are still aggregator-level and not explorer‑verified for this answer.
• opBNB: Specific v3 factory/router addresses on opBNB are referenced in PancakeSwap developer “v3 addresses” page, but without explorer cross‑check here they remain unverified marketing claims.
• On‑chain verification via analytics SQL is Not verifiable as of 2026‑09‑04. Fork lineage & changes
• Binance Academy explicitly notes PancakeSwap V3 introducing concentrated liquidity, customizable price ranges, and multiple fee tiers, describing it as analogous to Uniswap V3‑style concentrated liquidity.
• Public repos “pancake-v3-contracts” indicate a Uniswap‑style v3 design, but exact fork/derivative status vs Uniswap is not independently confirmed, so fork lineage is Not verifiable as of 2026‑09‑04.
• Audits: PancakeSwap’s own audit page lists Exchange V3 security audits by PeckShield and SlowMist (March 2023), plus MasterChef V3 audits (March–April 2023). These are independent auditor reports, but their findings are not detailed here.
• There is no independent evidence in retrieved sources of malicious modifications in PancakeSwap V3 forks; broader “similar forks” risk history is Not verifiable as of 2026‑09‑04.

PancakeSwap AMM V3 appears to be a real, functioning product rather than a pure landing page: the developer docs publish V3 contract addresses for Ethereum and opBNB, and the docs/navigation indicate an active developer-facing portal. Public material also describes live V3 deployment on Ethereum and opBNB and shows step-by-step guides for using the opBNB V3 app, which is consistent with an operational dApp rather than a template site. What is verifiable from the gathered web data is limited on UX quality: the docs are maintained and fairly current, but broken-link checks, fake-metric checks, and live deposit/withdrawal testing are Not verifiable as of 2026-09-04.

Likewise, whether the interface exposes a formal open API is only partially verifiable: the developer docs and third-party SDK references indicate documented contract addresses and programmatic integration points, but a clearly documented public REST API for the AMM itself is Not verifiable as of 2026-09-04. Overall maturity assessment: established DeFi product with working documentation and chain-specific deployments on Ethereum and opBNB, but the evidence gathered here is insufficient to confirm API surface details or to independently validate live user flows and frontend integrity beyond the published docs.

PancakeSwap has an active bug bounty program hosted on Immunefi. It launched on 26 March 2021, after a whitehat disclosure and bugfix review, and remains listed as active on Immunefi’s PancakeSwap bounty page. The program covers smart contracts, websites, and apps; for smart contracts/blockchain, reports must include a proof of concept, and the main reward tier is tied to severity and funds at risk.

Reported results include at least two publicly documented payouts: $7,500 for a content injection issue and $70,000 in CAKE for a logic error bugfix review.

Assessment (as of September 6, 2026): PancakeSwap AMM V3 on Ethereum and opBNB is primarily exposed to its own deployed Factory, Pool, SwapRouter, PositionManager and Smart Router contracts; no custodian, CEX, market-maker, RWA issuer/SPV, or restaking/LST dependency is documented for the core AMM. Deployment addresses are listed separately for ETH and opBNB. External dependencies and scenarios:

• Bridges: Cross-chain activity introduces material third-party dependency risk. PancakeSwap’s bridge interface routes transfers through deBridge, cBridge, LayerZero, Stargate and Meson; CAKE uses OFT-based cross-chain infrastructure, including an opBNB deployment. A provider exploit, message-forgery event, liquidity shortfall, censorship or provider shutdown could strand or impair bridged assets.
• opBNB infrastructure: Trading on opBNB additionally depends on the chain’s sequencer, batcher, proposer and canonical bridge. Official withdrawals have a seven-day challenge period; community bridges are explicitly described as potentially less secure.
• Oracle/manipulation: No external oracle is identified as a required dependency of the documented V3 swap path. Nevertheless, concentrated-liquidity pool prices are manipulable when used as an oracle, especially in thin or narrowly ranged pools; downstream protocols must use robust TWAP/liquidity safeguards. Direct pool-level exposure and oracle-consumer usage are Not verifiable as of September 6, 2026 without Dune/on-chain tracing.
• Bridge-specific evidence: A 2025 audit of PancakeSwap’s swap-and-bridge flow identified an Across integration issue that could divert positive slippage to relayers; it was marked fixed in PR#88. This demonstrates counterparty/integration risk even where contracts are audited. Contradiction callout: No current protocol-claimed exposure, reserve, holder, or dependency concentration figure was located to reconcile against on-chain balances. Not verifiable as of September 6, 2026. Failure scenarios: bridge exploit or depeg; opBNB sequencer/bridge outage; thin-pool price manipulation; stablecoin issuer insolvency/depeg for pools containing USDC/USDT or other third-party assets; token-specific admin or blacklist actions. No active PancakeSwap-specific dependency failure was identified in the reviewed sources as of September 6, 2026.

PancakeSwap AMM V3 is non-custodial for ordinary swaps: users connect their own wallet and trade through smart-contract pools, so assets are not first deposited into a centralized PancakeSwap account. For V3 liquidity provision, custody is organized on-chain through ERC-721 position NFTs in the NonfungiblePositionManager; those NFTs represent ownership of the underlying assets and fees, and can be transferred. If a position is staked in a farm, the NFT is transferred to the farm contract, which then holds custody of that position NFT.

Segregated-assets status is not verifiable as of 2026-09-06, and withdrawal-paused status is not verifiable as of 2026-09-06.

Four.Meme’s migration/liquidity process allowed an attacker to initialize a PancakeSwap V3 SNOWBOARD/WBNB pool at a manipulated price before legitimate liquidity was added, then drain WBNB. Affected: Four.Meme users and LPs in the relevant PancakeSwap V3 pool; no evidence that PancakeSwap V3 core contracts were compromised. Response: Four.Meme paused affected launch functionality and deployed a fix; the launch function was restored after security checks.

Compensation claims were opened and compensation was reported as underway. Exact amount reimbursed and whether all users were reimbursed: Not verifiable as of 2026-09-06. Current status: remediation_in_progress because reimbursement completion is unverified, although the technical issue was reportedly fixed.

No core-contract hack or protocol-wide exploit is publicly evidenced in the provided results for PancakeSwap AMM V3 since launch; the only incident-level claim found is a report of two price-manipulation incidents in V3 pools in Feb 2025 (~$183K) and Mar 2026 (~$679K in BCE/USDT), with the March 2026 event attributed to a third-party token burn-mechanics interaction rather than a core V3 contract bug. Response/reimbursement/fix details are not verifiable as of 2026-08-30 from the available sources.

CORRECTION to the previously recorded March 2026 finding: the available technical description identifies the affected market as a PancakeSwap BCE/USDT pool on BNB Smart Chain and uses PancakeSwap V2-style pair mechanics (including sync/reserve manipulation), not PancakeSwap AMM V3 on Ethereum or opBNB. Cause was a third-party BCE token burn/destruction mechanism that compressed pool reserves after the attacker bypassed trading restrictions. Affected: BCE/USDT LP liquidity and BCE holders.

Response, technical remediation, recovered funds, and reimbursement: Not verifiable as of 2026-09-06. Current status: unknown; no evidence found that PancakeSwap V3 core contracts were exploited.

A second reported V3-pool manipulation event occurred in March 2026 with an estimated loss of ~$679K in the BCE/USDT pool. The available source says this was driven by a third-party token’s burn mechanics interacting with V3 pool mechanics, not a direct compromise of PancakeSwap AMM V3 core contracts. Response/reimbursement/fix details are not verifiable as of 2026-08-30 from the available sources.

PancakeSwap AMM V3’s key management is organized around *user-owned positions* rather than protocol-custodied balances. On Ethereum and opBNB, each liquidity position is an ERC-721 NFT held in the NonfungiblePositionManager; the NFT stores the position parameters and accrued fees, and the owner controls the position by controlling that wallet or NFT custody. The AMM itself is also structured per-pool: PancakeSwap V3 uses separate pool contracts, with the pool identified by a PoolKey and derived PoolId.

For operational control, the protocol separates user key management from contract administration. The available sources indicate PancakeSwap uses multisig administration and timelocks for upgrades or sensitive changes, which means privileged actions are not meant to be controlled by a single hot key. However, the exact signer set, threshold, and current admin addresses for Ethereum and opBNB are Not verifiable as of 2026-09-04 from the provided sources.

In practice, this means:

• Users manage LP positions through their own wallets or NFT custody.
• Protocol administrators manage upgrade/admin rights through multisig + timelock controls rather than a single key.
• Pool state is contract-bound and identified per pool, reducing the need for centralized per-position custody. If you want, I can next map the exact deployed V3 contract addresses for Ethereum and opBNB and identify which admin/owner fields are publicly readable from explorers, subject to verification limits.

Assessment — Ethereum and opBNB Architecture / addresses. V3 is a Uniswap V3–style, multi-contract AMM: Factory → PoolDeployer → permissionless Pools; users interact through SwapRouter, SmartRouter, and NonfungiblePositionManager. Documented deployments are:

• Ethereum: Factory 0x0BFbCF9fa4f9C56B0F40a671Ad40E0805A091865; PoolDeployer 0x41ff9AA7e16B8B1a8a8dc4f0eFacd93D02d071c9; SwapRouter 0x1b81D678ffb9C0263b24A97847620C99d213eB14; PositionManager 0x46A15B0b27311cedF172AB29E4f4766fbE7F4364; SmartRouter 0x13f4EA83D0bd40E75C8222255bc855a974568Dd4.
• opBNB: Factory 0x1BB72E0CbbEA93c08f535fc7856E0338D7F7a8aB; PoolDeployer 0x7f71382044A6a62595D5D357fE75CA8199123aD6; SwapRouter 0xD70C70AD87aa8D45b8D59600342FB3AEe76E3c68; PositionManager 0xa815e2eD7f7d5B0c49fda367F249232a1B9D2883; SmartRouter 0x678Aa4bF4E210cf2166753e054d5b7c31cc7fa86. Verification / audits. Ethereum Factory and Router source are explorer-verified; PancakeSwap lists PeckShield and SlowMist Exchange V3 audits. This supports audited code, but exact audit-to-deployment bytecode matching for both chains is Not verifiable as of September 6, 2026. Admin powers. Factory owner can enable fee tiers, alter protocol-fee settings, collect accrued protocol fees from pools, configure liquidity-mining pools, and manage whitelist/fee metadata. These are fee/configuration powers, not a direct LP-principal sweep. No oracle or strategy module is part of core V3. Core pools are permissionless and LPs can decrease liquidity/collect or burn NFT positions without admin approval. Proxy / timelock / roles. Exact proxy-admin type, upgrade events, role holders, renunciation status, and timelock delay are Not verifiable as of September 6, 2026 because Dune/on-chain verification is unavailable. Explorer heuristics flag the Ethereum Router as potentially proxy-like, but this is not sufficient proof of proxy architecture. Worst case. Compromised factory/admin keys could raise protocol fees, redirect protocol-fee collection, manipulate fee-tier/LM configuration, or impair selected pools; a compromised router/SmartRouter deployment or upgrade authority could cause user-token loss when users approve it. Core pool funds are not generally drainable by factory ownership alone. Freeze risk is mainly operational/configuration- or token-dependent, not a global AMM pause. Conclusion: meaningful admin/configuration risk; lower direct-rug risk for immutable core pools, but router/proxy uncertainty remains material. Timelock protection is unverified.

PeckShield Exchange V3 audit. Publication date: March 28, 2023. Scope: PancakeSwap Exchange V3 / AMM V3 Phase 2 contracts; report is not chain-specific.

Findings: 0 critical, 0 high, 1 medium, 1 low, 1 informational. Fix status: findings reported acknowledged/addressed; no independent remediation re-audit located. Covers deployed Ethereum/opBNB bytecode: Not verifiable as of September 6, 2026.

SlowMist MasterChef V3 audit. Publication: March 2023; exact single publication date is Not verifiable as of September 6, 2026. Scope: MasterChef V3 liquidity-mining/reward-distribution contracts.

Findings: 0 critical, 0 high, 1 medium, 1 low, 1 informational according to the accessible audit table; independent direct-PDF verification was not available. Fix status: reported as passed, with findings addressed or mitigated. Covers Ethereum/opBNB deployed bytecode: Not verifiable as of September 6, 2026.

Corrected: SlowMist Exchange V3 audit. The official PancakeSwap audit index lists the report as March 2023; the accessible secondary audit table gives March 7–13, 2023, not a single publication date. Scope: Exchange V3 / AMM V3 core contracts; chain-specific deployment coverage is not established.

Findings: 0 critical, 0 high, 1 medium, 0 low, 4 informational (corrected from the previously recorded 3 informational). Fix status: the medium excessive-authority/admin-centralization issue was acknowledged with multisig mitigation; informational recommendations were reported fixed or acknowledged. No independent remediation re-audit located.

Covers deployed Ethereum/opBNB bytecode: Not verifiable as of September 6, 2026.

Exchange V3 security audit for PancakeSwap AMM V3 core DEX contracts on BNB Chain (primary deployment), March 2023.

PancakeSwap v3 Exchange V3 security audit; covers the Exchange V3 codebase. The public audit index lists this report, but the available result snippet does not expose critical/high/medium counts, fix status, or a bytecode-to-deployment coverage statement.

MasterChef V3 security audit for PancakeSwap AMM V3 yield‑farming contracts, April 2023.

PancakeSwap MasterChef V3 security audit; relevant to the v3 ecosystem’s incentive contracts. The search results confirm the audit exists, but the accessible snippets do not provide critical/high/medium findings, fix status, or explicit deployed-bytecode coverage.

Exchange V3 Core security audit for PancakeSwap AMM V3, March 2023.

PancakeSwap, including its AMM V3 deployments on Ethereum and opBNB, is founded and operated by a fully anonymous team, with no publicly verifiable legal entity, founders’ real names, or office presence as of 2026. This is a materially anonymous, offshore-style setup rather than a conventional, onshore financial business. ### Founders & Team

• Multiple independent sources agree PancakeSwap was launched in September 2020 by an anonymous developer team on BNB Chain as a fork of Uniswap.
• Team members use pseudonyms and the “Kitchen/Chefs” branding: co-leads Hops and Thumper, technical/lead devs like Chef Jojo, and other “Chefs” for biz dev, frontend, solidity, design, and community.
• One source claims the team is “based in Unoshima, Fukuoka, Japan” and has grown to “over 250 contributors,” but this is not corroborated elsewhere and should be treated as an unverified marketing claim.
• Some articles mention former Binance employees involved, but without real-name disclosure or corporate registration details.
• A roster with real names (e.g., “Henry Cavill – CEO”) appears in one startup database, but this conflicts with all other sources describing a fully anonymous team and is likely inaccurate or non-authoritative. ### Public vs. Anonymous; Credibility
• Founders and core team are non-doxxed; there is no public KYC of the principals, board, or controlling shareholders.
• Long-running operation since 2020, large TVL, multiple audits, and broad chain expansion are positive credibility signals, but they do not substitute for identifiable accountability.
• Several reviews explicitly flag: “team private”, “fully anonymous”, “undisclosed location”. ### Jurisdiction, Offices, Real-World Footprint
• No reliable evidence of a registered operating company, headquarters, or regulated entity responsible for PancakeSwap V2/V3 on any chain. Not verifiable as of 2026-09-04.
• Claims of a Japanese base and large contributor count come from secondary content only and lack independent corporate or regulatory confirmation, so they remain unverified marketing claims. ### Reality Check for Institutional Risk
• Key structural risk: protocol is controlled by an anonymous team with no clear legal recourse or regulatory perimeter.
• From a traditional institutional lens, PancakeSwap V3 on Ethereum/opBNB should be treated as an anon DeFi DEX with uncertain jurisdiction and governance concentration, not as a regulated financial institution.

PancakeSwap AMM V3 on Ethereum and opBNB currently has a strong technical-security reputation, but operates in a high‑risk environment (permissionless BNB/opBNB ecosystem) and faces some regulatory frictions. ### Security, audits, and bug bounties

• V3 Exchange and MasterChef contracts were audited by PeckShield and SlowMist in March–April 2023, as listed on PancakeSwap’s audit page and confirmed by independent overviews.
• Later infra (Infinity Core/Periphery) was audited by Hexens, and other components by Certik, OpenZeppelin, Quantstamp, indicating multi‑firm coverage.
• Independent security briefings describe PancakeSwap as having a “strong security posture” with an extensive multi‑year audit trail and a bug bounty program around $1m.
• Reviews in 2026 note no major core-DEX exploit since launch on BNB Chain, despite many auxiliary products and upgrades. ### Incidents and criticisms
• A 2021 analysis documented an ongoing exploit abusing Uniswap v2‑style pool donation mechanics on PancakeSwap (BNB Chain), extracting “tens of thousands of dollars” from pools where users sent tokens directly without calling sync. This targeted user behavior, not a direct V3‑specific flaw.
• Chain‑level research shows PancakeSwap pools are heavily used by rug‑pull tokens; one 2026 study identified $284M+ in rug pulls on PancakeSwap V2 in 20 weeks, across 100k+ events, highlighting the platform’s role as infrastructure for malicious tokens even if the DEX itself is not the rugger.
• Ecosystem criticism focuses on risk to retail users from unvetted tokens (especially on BNB/opBNB) rather than insolvency or protocol‑level fraud. ### Governance, founders, and investors
• PancakeSwap is presented as a community‑driven project; independent profiles emphasize its status as the leading DEX on BNB Chain but provide limited verifiable detail on founders or equity investors. Founder/investor identities and cap table are Not verifiable as of 2026‑09‑04. ### Legal, regulatory, and sanctions
• In July 2025, Turkey’s Capital Markets Board blocked access to PancakeSwap for Turkish residents, citing unauthorized provision of crypto‑asset services and lack of local licensing; the platform remains globally operational.
• There are no credible reports of protocol‑level fraud, insolvency, or international sanctions against PancakeSwap Not verifiable as of 2026‑09‑04. ### Overall sentiment and unresolved concerns
• Independent reviews in 2026 rate PancakeSwap as a high‑usage, audited DEX with solid core security, but stress elevated counterparty/asset risk due to permissionless listing and the prevalence of scam tokens on BNB/opBNB.
• Key unresolved concerns for institutional use: exposure to rug‑pull tokens, limited transparency on founders/investors, and regulatory uncertainty in specific jurisdictions (e.g., Turkey).

Economic Model — PancakeSwap AMM V3 *(reviewed September 6, 2026)*

• Strategy/assets: Concentrated-liquidity AMM. LPs deposit two ERC-20/BEP-20 assets, select a fee tier and price range, and receive a transferable position NFT. Fees accrue only while the position is in range; fees are not automatically compounded. Supported fee tiers include 0.01%, 0.05%, 0.25% and 1%.
• Yield source: Primarily organic swap fees generated by trading volume. Optional V3 farms add CAKE emissions, making the incremental farm yield subsidized. DefiLlama attributes 15% of fees in the 0.01%/0.05% tiers and 23% in the 0.25%/1% tiers to CAKE buyback/burn.
• Risk profile: Directional, not market-neutral. LPs bear impermanent loss, inventory rebalancing, out-of-range inactivity, token depeg/price risk and smart-contract risk. Farms add CAKE-price and emissions risk. No native leverage, looping, restaking or borrowing mechanism was identified; external exposure is limited to deposited assets, CAKE rewards and the relevant chain.
• Lock-ups/withdrawals: No protocol lock-up identified. LPs can remove all or part of liquidity at any time and receive the two underlying tokens; earned fees must be manually collected/withdrawn. Farm-staked positions can be adjusted without unstaking, although changing the range requires unstaking, full removal and recreation.
• Fees/gates/limits: User pays pool swap fees and network gas; harvesting also incurs gas. Minimum deposit is effectively constrained by the lower-value token contribution and available pool liquidity. No universal withdrawal gate or maturity was identified.
• Protocol revenue: DefiLlama reports V3 revenue of $44,413/24h, $1.97m/30d and $147.83m cumulative in its latest page snapshot; these are analytics-platform figures, not on-chain verification.
• TVL: DefiLlama reports total V3 TVL of $290.22m across all chains; Ethereum $27.27m and opBNB $29,018, or approximately 99.9% and 0.1% of the requested two-chain subtotal ($27.30m). Dune comparison, TVL trend, product decomposition, and on-chain reconciliation: Not verifiable as of September 6, 2026.
• APY sustainability: Latest DefiLlama snapshot shows 93 pools and average APY 17.21%; this is a current aggregate, not a historical series. APY is volume-, price-range-, liquidity-, emissions- and token-price-dependent, so sustainability and volatility are Not verifiable as of September 6, 2026. Structured fields: organic_yield_pct: null; leverage_ratio: null

As of September 6, 2026, treasury/reserve balances for PancakeSwap AMM V3 on Ethereum and opBNB are Not verifiable as of September 6, 2026. Dune MCP was unavailable, so no on-chain reserve query, query ID, execution ID, block height, token composition, custody address, or controller verification could be produced. Explorer pages and DeFiLlama TVL are insufficient to identify protocol treasury assets or distinguish them from user liquidity. Chain exposure context — not treasury reserves: DeFiLlama reports total AMM V3 TVL of $290.22m, including Ethereum $27.27m and opBNB $29,018 in its latest crawled snapshot.

Across only the two requested chains, this is approximately 99.89% Ethereum and 0.11% opBNB. These are user-liquidity figures, not reserve balances. Reserve policy: PancakeSwap documentation states that V3 swap-fee allocations include 84% to LPs, 8% to burn, and 8% to the protocol treasury. This establishes a stated fee-flow policy, not the current treasury balance, custody, or segregation of assets. Control, custody, composition, attestations: Not verifiable as of September 6, 2026.

No directly verified treasury address or current reserve attestation was identified from the reviewed sources. The available audit index confirms published PancakeSwap audits but does not establish treasury solvency, balances, or custody. Contradiction / change vs. prior finding: The previously recorded overall TVL snapshot of $433.8m differs materially from the current DeFiLlama page's $290.22m. This is an aggregator-data change, not evidence of a reserve movement; the on-chain cause cannot be verified without Dune or equivalent direct balance analysis. Structured assessment: liquid reserves USD: unknown; liabilities USD: unknown.

PancakeSwap AMM V3 has a native token: CAKE (PancakeSwap). I could not verify the contract address, total vs. circulating supply, market cap/FDV, top-holder concentration, insider wallets, mint/blacklist/fee-switch controls, or on-chain unlock execution in this run; per your instruction, these are Not verifiable as of 2026-09-04. What is verifiable from non-chain sources is that CAKE is the protocol’s governance and utility token, with Tokenomics 3.0 reducing emissions, retiring veCAKE/gauge voting, and shifting value capture toward deflation via buyback-and-burn.

PancakeSwap’s docs state a target annual deflation rate of at least ~4% and a ~20% total CAKE supply reduction by 2030, funded by fee streams including 15–23% of spot trading fees, 20% of perpetual profits, 100% of CAKE.PAD/IFO fees, and 20% of lottery CAKE played. Community/governance sources indicate veCAKE and staking/revenue-sharing mechanics were unwound in April 2025 and that emissions were cut materially under Tokenomics 3.0, but the exact post-change supply and whether every announced unlock occurred on-chain is Not verifiable as of 2026-09-04. The available sources also point to a later governance change reducing CAKE’s maximum supply cap from 450M to 400M in January 2026, but this remains an off-chain governance claim here rather than an on-chain-verified fact.

For DEX liquidity depth and main listings, DefiLlama shows PancakeSwap AMM V3 TVL and CAKE liquidity figures, but I cannot confirm chain-by-chain exposure or the main venue breakdown from on-chain data in this run.

A Bitcoin move below $10,000 would likely stress PancakeSwap AMM V3 mainly through sharp range exits and impermanent loss, not through a protocol-wide solvency event. Concentrated-liquidity LPs can be pushed fully into one asset as price trends beyond their range, and PancakeSwap’s own docs state LPs earn no trading-fee rewards when price goes out of range. For the Ethereum and opBNB deployments specifically, the user-supplied web results do not provide on-chain pool composition, active liquidity, or chain-level exposure data, so the severity split by chain is Not verifiable as of 2026-09-04.

The safest risk statement is that any BTC-linked pools, wrapped-BTC pairs, or correlated crypto pairs would face the greatest pressure if BTC’s collapse triggered broader market deleveraging, because concentrated liquidity magnifies losses when prices move through narrow ranges. Operationally, the likely failure mode is liquidity thinning: LPs withdraw or fall out of range, spreads widen, and swaps face higher price impact. PancakeSwap guidance on V3 trading agents explicitly anticipates rebalancing when price nears range boundaries, which implies the protocol’s liquidity quality depends heavily on active management rather than passive range holding.

I cannot verify any quantified TVL, pool-share, or chain-exposure estimate from the provided sources, so those figures are Not verifiable as of 2026-09-04.

For PancakeSwap AMM V3, a 20% depeg in the largest collateral is primarily a liquidity-dislocation / price-discovery stress, not a direct smart-contract solvency event. PancakeSwap’s concentrated-liquidity design means LP capital can be highly clustered, so a sharp move can push many positions out of range, sharply reducing executable depth and increasing slippage on the affected chain. What this means in practice:

• Ethereum and opBNB should be evaluated separately, because exposure and liquidity may differ materially by chain; with the current evidence set, chain-level TVL or pool-level depth is Not verifiable as of 2026-09-04.
• A 20% depeg is below the 40%+ flash-crash scenario highlighted in one risk analysis, but still large enough to meaningfully impair concentrated-liquidity pools, especially if liquidity is narrow and clustered near the old peg.
• If the depegged asset is used by downstream protocols as collateral or as an oracle input, the main risk is stale or manipulable pricing during the liquidity vacuum, which can cascade into incorrect liquidations or bad borrow pricing.
• A depeg in a stable pair is explicitly recognized as a case where impermanent loss becomes material rather than muted. Most important limitation: there is no on-chain verification available in this run for the actual largest collateral, its chain split, or the pool-specific depth needed to quantify losses, so any numeric impact estimate would be speculative. Not verifiable as of 2026-09-04.

For PancakeSwap AMM V3 on Ethereum and opBNB, the main “counterparty” risk is LP insolvency in a pool (their position value goes to or below zero). This does not cause protocol‐level insolvency, but it can create losses for traders and other LPs via prices and bad debt. ### 1. Setup: what “top counterparty insolvent” means * AMM design: PancakeSwap V3 is a concentrated‑liquidity Uniswap‑V3‑style AMM: trades execute against pool reserves at a formula price, with LP positions in price ranges. * AMMs are fully collateralized by pool tokens; there is no margin lending in the core AMM. * “Top counterparty insolvent” therefore maps to: * A large LP whose position becomes worthless (e.g., due to extreme price move, impermanent loss, or holding a depegged/failed asset), or * A major token in the pool itself becoming worthless (issuer insolvent or rug).

Not verifiable as of [2026‑09‑04]: exact share of TVL per top LP or per chain; on‑chain breakdown is unavailable here. ### 2. Stress path: Ethereum vs opBNB #### Case A – Token in pool collapses (both chains) * Loss path: * Price on the AMM follows or lags the collapse; arbitrageurs trade until the pool is mostly filled with the worthless token. * LPs in ranges that include the collapse price end up holding almost only the failed token; their position value ≈ 0. * Who absorbs losses: * LPs in the affected pool – they are economically long the pool assets and eat the loss. * Traders who bought the failing token late may also lose ex‑post, but at trade time they receive what the contract promises. * Smart‑contract impact: * Core AMM contracts remain solvent; they only move balances per formula. No native mechanism for socializing losses across pools. * No automatic protocol‑level compensation; any recovery would require governance‑approved treasury action (unverified marketing claim if stated only by PancakeSwap docs). #### Case B – Large LP becomes “insolvent” off‑chain * If LP’s external obligations exceed assets, but their on‑chain LP position stays, users are still paid per contract; off‑chain insolvency does not affect pool solvency. * If LP withdraws and cannot meet some off‑chain obligation, that is not a protocol loss; counterparties to that LP bear it. ### 3.

Chain‑specific notes * Ethereum: More diverse asset set and CEX/DeFi arbitrage; shock transmission is mainly via price and rebalancing, not AMM insolvency. * opBNB: Higher concentration in BNB ecosystem; insolvency of a major BNB‑linked asset could hit multiple opBNB pools, but still via LP losses, not protocol failure. ### 4. Compensation & systemic impact * No built‑in insurance or backstop in V3 AMM; LPs are residual risk‑takers. * Systemic impact is via: * LP capitulation → reduced liquidity → wider spreads & slippage. * Price dislocations if oracles or other protocols use PancakeSwap V3 prices without robust safeguards. Sources: PancakeSwap V3 documentation and architecture descriptions.

For the stress scenario “committed fraud by the DAO or owners”, I found no verifiable evidence that PancakeSwap AMM V3’s DAO or owners committed fraud on Ethereum or opBNB. The available web results include a forum accusation that PancakeSwap “scammed” CakePie SubDao users, but that is an unverified allegation from a community post, not proof of fraud. What is verifiable is that PancakeSwap has had security and governance-risk discussions, including a reported social-media compromise and general owner/admin power risks in third-party analyses, but those do not establish committed fraud by the DAO or owners.

PancakeSwap’s own documentation and audit pages show that the protocol maintains audit disclosures, but protocol-published material alone is not sufficient to substantiate fraud claims. For this stress test, the correct risk classification is:

• Fraud by DAO/owners: Not verifiable as of 2026-09-04.
• Related governance/operational risk: compromised official channels, admin-key concentration, and governance disputes can create fraud-like outcomes or user harm, but this is distinct from proven fraud. Given the absence of on-chain verification in this run, no chain-specific fraud attribution can be made for Ethereum or opBNB.

For PancakeSwap AMM V3, the primary yield source is fee income to LPs, and a negative 30d primary yield means fee income over the last 30 days is insufficient to offset the LP position’s costs and adverse price effects, so the strategy is in a loss state rather than a yield-producing state. In this stress scenario, the main drivers of negative performance are concentrated-liquidity impermanent loss, range exit, and MEV/sandwich extraction, all of which can reduce realized LP returns even when swaps still occur. PancakeSwap’s own docs state that only LPs earn AMM fees, while the fee model routes most swap fees to LPs with smaller portions to burn and treasury, so a drop in trading activity directly compresses LP income.

Because Dune on-chain checks are unavailable in this run, the 30d negative-yield condition is not verifiable as of 2026-09-04 from raw chain data, and I cannot confirm which chain—Ethereum or opBNB—is contributing the loss profile. Operationally, the stress implication is straightforward: if primary yield is negative for 30 days, the position is behaving more like a directional market bet with fee drag than a carry trade, and the LP should be treated as underperforming benchmark cash/yield alternatives rather than providing positive income.

Assessment: team-steered; DAO is not autonomous for PancakeSwap AMM V3 on Ethereum or opBNB. Governance is ecosystem-wide, not chain- or V3-specific. Core proposals may be submitted only by the PancakeSwap Core Team, require a CAKE-holder vote, and—if approved—are implemented by the PancakeSwap team. Community proposals require 100,000 CAKE but are explicitly non-binding; there is no minimum quorum.

Voting is 1 CAKE = 1 vote at the proposal snapshot, with delegation unavailable. Control surface: The Core Team reserves unilateral emergency intervention without a community vote, including temporarily pausing contracts. This is a documented emergency bypass and makes governance partly symbolic for security/operational interventions. The frontend and implementation process are team-controlled by documentation; exact deployer/admin roles for the Ethereum and opBNB V3 contracts are Not verifiable as of September 13, 2026 because Dune/on-chain verification is unavailable in this run. Multisig/timelock: PancakeSwap’s FAQ claims that contracts use multisig and timelocks, but it does not identify the relevant V3 addresses, signers, threshold, independence, or delay; therefore these are treated as unverified marketing claims, not verified controls. Voting concentration/top holders: Not verifiable as of September 13, 2026 (Dune unavailable; no raw on-chain substitute used).

The same applies to whether any admin can drain user funds. No conclusion of safety should be drawn from the absence of evidence. Company angle: PANCAKESWAP LIMITED, UK company no. 13599505, was incorporated in England and Wales and dissolved on October 1, 2024.

Companies House recorded Xingcong Liu as director and person with significant control (>75% shares/votes and director-appointment rights). This establishes a historical corporate control link, not a verified current operating entity. Current applicable Terms of Service, jurisdiction, and operating entity: Not verifiable as of September 13, 2026.

Assessment (as of September 4, 2026). PancakeSwap AMM V3 is a set of non-custodial smart contracts deployed on Ethereum and opBNB, not a separately identified legal person; official documentation lists the V3 factory/router contracts on both chains. No incorporated operator, foundation, registered office, or beneficial owners could be confirmed from reliable public sources. The project has described its developer collective as “The Kitchen,” but this does not establish a legal entity.

ToS / restrictions. The web interface links to Terms of Service. Available third-party captures report Hong Kong governing law, HKIAC arbitration, and class-action/class-arbitration waiver; the current text and any current prohibited-jurisdiction schedule were not independently retrievable. Therefore: Not verifiable as of September 4, 2026 for the current enforceable restrictions. KYC/AML and sanctions. Direct wallet-to-contract V3 swaps are generally non-custodial and no protocol-level user KYC process was verified.

Front-end, fiat on-ramp, market-maker, analytics, or other third-party services may impose separate screening. A current PancakeSwap AML/KYC policy was not verified: Not verifiable as of September 4, 2026. No evidence was found that PancakeSwap or its disclosed project entity is itself designated by OFAC or another sanctions authority; this does not mean every user, token, pool, or address is permissible. Classification / legal risk. No binding ruling classifying PancakeSwap V3 was identified.

Regulators could nevertheless characterize a front-end operator, developers, governance participants, or particular products as operating an exchange, broker, commodities venue, money-transmission, or securities-related activity, depending on facts and jurisdiction. The absence of a disclosed entity increases attribution, service-of-process, licensing, and consumer-remedy uncertainty. Smart-contract decentralization does not eliminate exposure for identifiable developers or interface operators. Warnings, enforcement, litigation. SEC litigation has described PancakeSwap as a venue used for token offerings, but PancakeSwap was not the defendant in the cited complaint.

No regulator enforcement action or court case directly against PancakeSwap AMM V3 or its identified entity was found in the reviewed public sources. Current privacy-law compliance and controller identity: Not verifiable as of September 4, 2026.

GLEIF LEI registry unavailable at scan time. OFAC SDN screening of 'No legal operating entity publicly verified', 'PancakeSwap AMM V3': no match. SEC litigation and administrative release feeds: no mention.

PancakeSwap AMM V3 does not appear to issue its own stablecoin; the supported stablecoins in its documentation are external assets such as USDT, USDC, DAI, and BUSD. A clearly identified depeg event relevant to PancakeSwap was the November 2025 USDX incident, when PancakeSwap said it was monitoring affected vaults; however, a complete count of how many depegs occurred, the last depeg date for the protocol’s supported stablecoin set, and the maximum depeg percentage are not verifiable as of 2026-09-06 from the available sources.

PancakeSwap AMM V3’s principal risks are concentrated-liquidity loss, smart-contract failure, adverse MEV/price execution, privileged-control exposure, and chain-infrastructure dependency. Audits and a live bounty program reduce—but do not eliminate—loss risk; Ethereum and opBNB exposure, TVL, and current administrator configuration are Not verifiable as of September 5, 2026 because Dune on-chain verification was unavailable.

PancakeSwap AMM V3’s top strengths are: (1) capital efficiency, because concentrated liquidity lets LPs deploy funds only in chosen price ranges; (2) lower trader slippage and deeper in-range liquidity, which improves execution on targeted pairs; (3) flexible fee tiers, which allows pricing to match asset volatility and trading demand; (4) gas efficiency from its singleton and flash-accounting design, which reduces pool-deployment and multi-hop transaction costs; and (5) multi-chain reach, with V3 deployed on Ethereum and opBNB, expanding venue access and liquidity distribution.