Compound V3

Compound V3 is the third iteration of Compound, a decentralized lending/borrowing protocol focused on overcollateralized money markets. Core identification

• Name: Compound V3 (a.k.a. Comet)
• Website: compound.finance
• Docs: docs.compound.finance
• Category: DeFi lending / money market protocol
• Launch date: Compound V3 was first announced and deployed on Ethereum in August 2022. Exact deployment block time for each chain is Not verifiable as of 2026-08-27.
• Supported chains: Ethereum, Arbitrum, Base, Optimism (OP Mainnet), Polygon, Scroll. (Scroll support is mentioned in newer docs/releases; chain-by-chain TVL is Not verifiable as of 2026-08-27.)
• Native token: COMP (governance token of the Compound Protocol). COMP is not a yield-bearing token in V3 but governs the protocol. Main V3 contract family (“Comet”) Compound V3 replaced the multi-asset cToken markets of V2 with isolated USDC-centric markets governed by a single Comet contract per market. Canonical V3/Comet implementations (all verified on Etherscan-type explorers; exact addresses differ per chain/market and are Not verifiable as of 2026-08-27):
• Comet (core lending market) – handles collateral deposits, borrows, interest accrual, liquidation logic.
• Configurator / Governor / Rewards – admin/configuration contracts for risk parameters, collateral lists, and COMP rewards distribution. Because Dune MCP is unavailable and specific contract addresses are chain-specific, full cross‑checked address lists with ≥2 independent sources are Not verifiable as of 2026-08-27. Fork lineage and design changes
• Compound V3 is an in‑house evolution of Compound V2, not a fork of external protocols like Aave or Maker.
• Key changes vs V2:
• Single borrowable base asset (e.g., USDC) per market, with multiple collateral assets.
• No cTokens for collateral; collateral is not interest‑bearing, reducing systemic complexity and contagion risk.
• Built‑in native price feeds and enforced collateral factors per asset.
• Simplified liquidation and "borrow caps" mechanisms to limit tail risk. Audits and security history
• Compound V3 contracts underwent audits by leading firms (e.g., OpenZeppelin, Trail of Bits) before mainnet deployment; audit reports are listed in the official docs and GitHub.
• No widely documented malicious-modification incidents specific to Compound V3 forks were found; notable incidents in Compound’s history (e.g., 2021 COMP distribution bug in V2) relate to prior versions, not V3. Where explicit auditor reports, detailed addresses per chain, and on-chain configuration diffs could not be located or cross-checked within two search attempts, they are Not verifiable as of 2026-08-27.

Compound V3 appears to have a real, mature documentation portal rather than a pure marketing landing page: the official docs explicitly describe the v3 proxy as the only address to use for interacting with a Compound III instance, which is a strong sign of operational product documentation rather than a placeholder site. Open API support is present at the protocol level: Compound’s developer docs state that its endpoints support JSON input/output as well as protobufs. What is not verifiable from the available sources is the live state of the web app by chain, including whether deposits and withdrawals are currently functioning on Arbitrum, Base, Ethereum, OP Mainnet, Polygon, and Scroll; that requires on-chain checks that are unavailable in this run. Not verifiable as of 2026-08-25. No reliable evidence in the gathered sources shows broken links, fake TVL metrics, or template/clone indicators on the official portal. Not verifiable as of 2026-08-25. Practical read: documentation maturity is high, and there is an exposed developer API, but live UX functionality across the listed chains cannot be confirmed here.

Certora produced a formal verification + manual audit report for Compound’s Comet (V3). Work window: 1 Feb–24 Mar 2022. Scope: Comet protocol including contracts such as Comet.sol, CometExt.sol and related modules; latest reviewed commit 4d1c1a42fc31b4b26129fe79e3d97ef637da9520. They define and prove protocol properties using the Certora Prover and supplement this with manual review. The report states that the implementation is "correct with respect to formal specifications" written jointly by Certora and Compound, within the scoped contracts. The public summary does not enumerate all issue severities, but mentions that both specification and code were iteratively refined; issues identified during this process were addressed before final verification. This verification targets core V3 logic on Ethereum; coverage of later chain deployments (Arbitrum, Base, OP, Polygon, Scroll) or later commits is Not verifiable as of 2026-08-25. Certora also later reviewed a Governor Extended Pause feature (relevant to V3 governance): 4 issues found, including 1 high severity, with 3 (including the high) fixed; 1 remained, presumably reduced in severity.

OpenZeppelin performed a dedicated Compound III (Comet / Compound V3) audit under its security partnership with Compound DAO. The engagement ran 16 May–17 June 2022, followed by several weeks of fix review. Scope: the compound-finance/comet repo at commit 0f1221967149115f50a09681eea9580879ee7720, i.e. core Comet lending contracts (V3 architecture). Findings: OpenZeppelin reports 30 issues total, no critical; 1 high, 3 medium, remainder low / informational. The high and medium issues were "either resolved with code changes or additional documentation" and OpenZeppelin states the audit concluded with no unfixed critical problems. This audit predates multi‑chain deployments (Arbitrum, Base, OP, Polygon, Scroll), so whether the exact deployed bytecode matches this audited commit is Not verifiable as of 2026-08-25. OpenZeppelin also notes, in later partnership summaries, that it has conducted additional Compound V3 audits and governance-proposal reviews through at least 2024, but individual reports and chain‑specific deployments are not all publicly broken out.

Yes. Compound V3 has an active bug bounty program on Immunefi, listed as live since 11 December 2024 and last updated 14 May 2026. The program covers Compound Finance’s protocol bug bounties and is explicitly triaged by Immunefi. Its main parameters are:

• Maximum reward: $1,000,000.
• Minimum reward: $50,000.
• Critical smart contract bugs: reward equals 10% of directly affected funds, capped at $1,000,000.
• Scope: vulnerabilities affecting testnet components are out of scope.
• Payout currency: rewards are denominated in USD but paid in COMP tokens. On results, the public sources available here do not show a disclosed payout history or a summary of completed findings for the current Immunefi program. So the program’s *operating status and rules are verifiable*, but its *outcomes are not publicly verifiable from these sources as of 2026-08-25*.

Compound v3 depends on a narrow set of external components, but each introduces specific counterparty and manipulation risks across its deployed chains. 1. External protocols & assets

• USDC-centric design: Most v3 deployments use USDC (or a single base asset) as collateral/borrow base; this concentrates risk in Circle’s ability to maintain the USDC peg and redeemability. A USDC depeg (e.g., March 2023) directly stresses health factors, liquidations and protocol solvency.
• Other collateral: Markets list major tokens (ETH, WBTC, wstETH, cbETH, restaked/LSTs depending on chain). Each brings smart contract, governance and depeg risk from the underlying protocol (e.g., LST slashing, restaking slashing, bridge failures for wrapped BTC). 2. Oracles & price manipulation
• Chainlink oracles: Compound v3 uses Chainlink feeds for most assets (confirmed by governance and docs). This imports:
• Chainlink network/liveness risk (stale or halted feeds).
• Data source risk (CEX-heavy reference prices can be manipulated during thin liquidity events).
• Oracle design: Compound historically uses time-weighted Chainlink oracles; sudden dislocations (flash crashes, exchange outages) may cause under/over-valuation, triggering bad debt or wrongful liquidations. 3. Bridges & wrapped assets
• On Arbitrum, OP Mainnet, Polygon, Base, Scroll, core assets (USDC, ETH derivatives, bridged BTC) are often bridged or canonical representations. Failure of:
• Official bridges (e.g., Ethereum–L2) or third‑party bridges that back wrapped tokens.
• Custodians for wrapped BTC. can cause hard depegs and cascading liquidations. 4. Custodians, CEX/MM exposure
• USDC: Counterparty risk to Circle and its banking/custodial partners; regulatory actions or reserve impairment can affect solvency/peg.
• Wrapped BTC (e.g., WBTC): Exposed to BitGo / merchant consortium custody and governance.
• Liquidity reliance: Liquidations depend on on-chain DEX liquidity plus MM participation, which in turn rely on CEX markets and cross‑venue arbitrage; extreme CEX outages or MM withdrawal can impair liquidations. 5. Governance & contract risk
• Governance is controlled by COMP token holders and timelock contracts on Ethereum, with cross‑chain deployments relying on governance relayers/bridges. Compromise or misconfiguration of governance bridges or multisigs can affect all v3 instances. 6. Failure / insolvency scenarios Key systemic scenarios:
• Major stablecoin (USDC) or LST depeg.
• Chainlink oracle failure or manipulation on a listed asset.
• Bridge or custodian failure for wrapped assets.
• Governance/key compromise pushing malicious upgrades. Each chain instance (Arbitrum, Base, Ethereum, OP, Polygon, Scroll) inherits these risks with chain‑specific bridge/oracle/asset sets. Not verifiable as of 2026-08-25: precise per‑chain asset lists, exact oracle configurations per market, and distribution of TVL by chain (no Dune MCP access).

Compound V3 is organized as a non-custodial smart-contract protocol: users interact with Comet markets through wallets, and the protocol—not a company—holds deposited assets in on-chain contracts rather than an off-chain custodian. Each market is isolated by chain and by base asset, meaning one Comet market has a single borrowable base asset (for example USDC or WETH), while other approved tokens can be supplied as collateral in that same market. Governance controls the protocol through the Timelock on Mainnet, which administers community-sanctioned Compound III instances; deployments outside Mainnet also use a Bridge Receiver and Local Timelock on their own chain. Compound III is deployed on Ethereum, Base, and Arbitrum according to the available sources; I could not verify additional live deployments on OP Mainnet, Polygon, or Scroll from the provided results, so those are Not verifiable as of 2026-08-25. The practical custody model is therefore: users keep control of their wallet keys, the protocol contract escrows assets, and governance/pause-guardian roles can alter or pause contract behavior, but they do not constitute conventional custody of user funds.

Compound V3 has one clearly documented protocol-wide security incident since launch that is directly evidenced in the retrieved sources: a 2023 vulnerability disclosure tied to a developer known as KP, who found and patched a critical issue in Compound’s v3 protocol (Comet). The available sources do not verify a dollar loss, and I cannot confirm an actual exploit or fund theft from the retrieved material. The response was to patch the vulnerability and submit a DAO proposal to compensate the reporter; the initial $125,000 reward proposal failed quorum, and KP later resubmitted a reduced $100,000 request. Reimbursement, in the sense of user loss reimbursement, is Not verifiable as of 2026-08-27.

Bug bounty: Compound launched an Immunefi bug bounty with a maximum bounty of $1,000,000, 10% of directly affected funds, a $50,000 minimum for critical smart-contract bugs, KYC required, and payouts handled by the Compound DAO in COMP. The bounty program is live since 11 December 2024 per Immunefi. Scope in the protocol docs is the on-chain Compound Protocol; bugs requiring an admin key are out of scope.

Compound V3 key management is organized around COMP governance, a Timelock admin, and a Pause Guardian. Compound’s docs say the protocol is governed by COMP holders and delegates, and that all community-sanctioned Compound III instances are controlled by the Timelock contract, which administers the proxies, Configurator implementation, Comet factory, and Comet implementation. For deployments outside Mainnet, governance actions are relayed through a Bridge Receiver to a Local Timelock on each chain, which adds an extra delay before admin actions can execute. The docs also state that COMP token-holders designate the Pause Guardian, held by the Community Multi-Sig, and that this address can pause supply, transfer, withdraw, absorb, and buy-collateral operations. In practice, this means day-to-day protocol control is split between on-chain governance for upgrades/parameter changes and a limited emergency multisig role for pausing. For the selected chains, Compound V3 uses the same governance architecture, but non-Mainnet deployments rely on the chain-specific Local Timelock and bridge flow rather than direct Mainnet execution.

Compound V3 (Comet) uses a fixed proxy address per market, with the proxy as the main user-facing entry point and a separate implementation contract behind it; the Comet proxy addresses do not change across upgrades. Compound’s docs and the OpenZeppelin audit say the system is administered by a ProxyAdmin (CometProxyAdmin) owned by protocol governance, while the Configurator and Comet implementations are upgradeable through that admin. The main admin / emergency roles documented for Compound III are governance and pauseGuardian. Governance can upgrade Configurator and Comet, set configuration parameters, pause functions, withdraw reserves, and approve spenders for Comet asset balances; the pause guardian can disable selected actions in an emergency, but cannot unpause or block user withdrawals/repayments. Compound’s governance model uses a Timelock with a 2-day minimum delay for admin actions, intended to make upgrades opt-out rather than instant. That delay is the best-supported on-chain/governance security window found in the sources here; a newer Compound III docs page states all instances are controlled by the Timelock, but the exact deployed per-chain timelock addresses/delays are not verifiable from the gathered material. User exit / freeze risk: users can still redeem/withdraw and repayBorrow even under the emergency pause model, so a complete user freeze is not the intended design. The worst credible key-compromise scenario is governance or proxy-admin compromise enabling malicious upgrades, parameter changes, reserve withdrawal, or selective pausing; this is a serious centralization risk, but not a direct “rug” claim based on the available evidence. Chain coverage: Compound III is deployed on Ethereum mainnet, Arbitrum, Base, Optimism, Polygon, and Scroll, but the gathered sources do not provide chain-by-chain admin-address verification or a raw on-chain exposure split. Not verifiable as of 2026-08-25. Architecture map: Timelock/Governance -> CometProxyAdmin -> {Comet Proxy (user entry), Configurator Proxy} -> Implementation contracts Proxy / admin type: the audit identifies CometProxyAdmin as a ProxyAdmin-style controller for the managed proxies, consistent with OpenZeppelin’s upgrade pattern.

Compound V3 (Comet) is the third major version of the Compound lending protocol, built and maintained by Compound Labs, Inc., a U.S.-based company that developed earlier versions of Compound. Founders & key team

• Founders: The protocol and Compound Labs were founded by Robert Leshner and Geoffrey (Geoff) Hayes in 2017.
• Backgrounds:
• Robert Leshner (CEO) – Economics degree from the University of Pennsylvania; Chartered Financial Analyst; prior roles in traditional finance (Discover Financial Services, HPM Partners), founder of multiple software/fintech startups (including privacy startup Safe Shepherd), and product lead at Postmates in San Francisco.
• Geoff Hayes (CTO) – Engineering/computer science background (UPenn), led engineering at Postmates, founded a venture-backed privacy startup, and created Exthereum (open‑source Ethereum client).
• Other leadership: Sources list roles such as VP & GM, Compound Treasury (Reid Cuming) with prior risk/ML/product leadership at Square, Stripe, and Chime.
• Founders and senior team members are fully public, not anonymous, with extensive off-chain professional histories. Corporate entity, jurisdiction, and “real business” check
• Entity: Multiple independent profiles describe Compound Labs, Inc. as the company behind the protocol.
• Jurisdiction: A Legal Entity Identifier record shows Compound Labs, Inc. registered in Delaware, United States, with registered agent address at 1209 Orange Street, Wilmington, DE 19801 (standard corporate-services address).
• Headquarters / office reality: Several sources describe Compound Labs as a San Francisco–based company, i.e., an operating presence in SF plus a Delaware legal entity.
• The combination of a Delaware corporation, LEI registration, and founder doxxing indicates a conventional onshore corporate structure, not an offshore shell. Track record, incidents, and credibility
• Protocol incidents:
• In November 2020, an oracle design issue caused ~$89m of over‑collateralized positions to be liquidated after a short-term DAI price spike on Coinbase Pro; this was not a smart‑contract hack, but an oracle/market-structure failure that behaved according to contract logic.
• Security write‑ups treat Compound’s incidents as design‑risk case studies rather than evidence of repeated contract exploits.
• Security posture: The protocol has gone through multiple versions; security firms like OpenZeppelin publicly discuss simulated attack scenarios and mitigations, which indicates ongoing professional security engagement. Reality check (V3 specifically)
• Compound V3 (“Comet”) is a major redesign around single‑base‑asset lending markets (e.g., USDC, WETH), live on Ethereum, Arbitrum, Base, Optimism, Polygon, Scroll as of 2026.
• Deployment across multiple major L2s and coverage by independent analytics platforms (e.g., protocol TVL breakdown per chain) confirm that this is a long‑running, institutionally followed protocol, not a thin web front. Unverifiable items (this run)
• On-chain ownership distribution, team token holdings, and exact TVL per chain for V3 are Not verifiable as of 2026-08-25 under the current data‑access constraints.
• Office headcount, exact SF street address, and any current remote‑first status are also Not verifiable as of 2026-08-25.

Compound V3 (Comet) generally has a good technical reputation with strong auditing coverage, but its broader track record is tempered by serious historical incidents and a notable governance theft, leading many risk frameworks to treat it as moderate risk, not pristine blue‑chip. Founders / investors / positioning

• Compound is one of the earliest DeFi lending protocols; it is widely referenced alongside Aave as a “blue‑chip” money market and is integrated by other protocols (e.g., Origin cites it as a core strategy), indicating strong ecosystem trust.
• No credible sources report fraud or rug‑pull behavior by the Compound team; issues to date have been technical or governance‑related rather than outright team theft. Audits and security practices
• Compound (V2 and V3) has been repeatedly audited by OpenZeppelin, Trail of Bits, Certora, and ChainSecurity since 2018.
• OpenZeppelin reports 12+ audits of Compound V2/V3 and ongoing DAO security monitoring.
• The dedicated Compound III (V3) audit by OpenZeppelin in 2022 found no critical vulnerabilities, one high and several medium/low issues, all reportedly resolved or mitigated.
• OpenZeppelin’s 2023 security partnership review states “no live incidents” causing operational disruption or loss of funds across eight lending markets on four chains, which includes V3 deployments. Track record, incidents, and criticisms
• Historic major incidents (mostly V2 / legacy):
• A reward-distribution bug once accidentally gave away around $147M in COMP, described as one of DeFi’s largest accounting errors.
• A governance/process failure (Proposal 62) caused an ~$50M COMP loss from the treasury, attributed to inadequate review of a governance proposal.
• Governance attack:
• In 2024, a coordinated governance attack (Proposal 247) allegedly extracted around $24M in COMP from the treasury via whale voting.
• Independent risk analysts (Hindenrank) score Compound V3 around B−/C+, explicitly citing these governance and accounting events as track‑record weaknesses.
• Bug bounty / DAO culture:
• A notable controversy arose when a DAO vote to pay a developer for a major bugfix failed quorum, despite guidelines promising “generous rewards” at the DAO’s discretion; this raised concerns about inconsistent bug bounty payouts and contributor incentives. Regulatory / legal / sanctions
• No evidence in recent independent coverage of SEC/CFTC enforcement, criminal charges, or sanctions specifically targeting Compound V3 as of the latest available data.
• Some systemic risk commentary frames the governance attack and historical bugs as “expensive surprises,” but not as fraud. Unresolved concerns (institutional‑relevance)
• Governance risk: Delegated token governance remains vulnerable to whale capture and treasury draining (as seen in Proposal 247).
• Process risk: Historical failures (Proposal 62, $147M error) suggest that testing and review around parameter changes and reward logic remain critical.
• Bug bounty / incentives: The failed bug‑bounty vote reflects uncertain ex‑post compensation, which may deter white‑hat disclosures. On‑chain TVL distribution by chain (Arbitrum, Base, Ethereum, OP, Polygon, Scroll) and any chain‑specific risk differentiation are Not verifiable as of 2026‑08‑25 due to lack of direct on‑chain tooling in this context.

Compound V3 (“Comet”) is a single‑borrow‑asset, multi‑collateral lending protocol: each market has one base asset (USDC, USDT, WETH, etc.) that depositors lend and borrowers borrow against a curated set of collateral assets. Strategy & assets in/out

• Users supply the base asset to earn variable interest; other users borrow that same base asset by posting approved collateral (e.g. WETH, wstETH, WBTC, ARB, OP, MATIC, cbETH, AERO).
• Collateral assets are *only* used as backing; they are not separately lendable/borrowable in V3. Yield source; organic vs subsidized; directionality
• Core yield is organic borrowing interest paid by borrowers and distributed to suppliers via algorithmic interest‑rate curves.
• Some markets have additional reward APY from COMP or other tokens (e.g. USDT market showing base APY plus ~0.11% rewards). These are subsidized yields.
• Positions are directional to collateral asset prices (borrowers are long collateral, short the base asset), not market‑neutral. Leverage/looping/external exposure
• Users can self‑borrow the base asset against collateral and re‑deposit to lever up (looping), with risk limited by collateral and liquidation parameters.
• External price exposure comes from volatile collateral (ETH, WBTC, ARB, OP, AERO, etc.) and any reward tokens. Lock‑ups & withdrawals
• No fixed lock‑ups; suppliers can withdraw base assets subject to available liquidity in each market. Mechanics depend on per‑market liquidity and health factor of the user’s account.
• Liquidations occur when collateral value falls below required thresholds, repaying debt and seizing collateral. Fees, limits, protocol revenue
• Protocol revenue is primarily interest‑rate spread: the protocol can keep a portion of interest via reserve factors; detailed per‑market fee splits are parameterized by governance.
• Governance (COMP token) controls risk parameters, collateral lists, and reward programs. Collateral & networks
• Deployed on Ethereum, Arbitrum, Base, Polygon, Optimism, Scroll with chain‑specific markets and collateral sets.
• Example: Arbitrum USDC/USDC.e/USDT markets with WETH and ARB collateral; Base USDC/USDbC/WETH/AERO markets with WETH/cbETH collateral; Optimism and Polygon with WETH + OP/WMATIC; Scroll USDC with WETH collateral. TVL by chain, trend; APY history
• Estimates from analytics: TVL around $1.8–2.7B across V3 in mid‑2026, concentrated in USDC markets on Ethereum and Base.
• Per‑chain TVL examples (late Jul 2026 snapshot): Ethereum ≈$1.07B, Arbitrum ≈$67M, Base ≈$20M, Optimism ≈$9M, Polygon ≈$5M, Scroll ≈$0.1M. These are aggregator interpretations, not on‑chain verified – Not verifiable as of 2026‑08‑25.
• Reported USDC/USDT supply APYs typically 3–5%, with 30‑day average yields in the 3–3.5% range and modest reward add‑ons; volatility tracks broader stablecoin borrowing demand but has been relatively moderate.
• Sustainability depends on ongoing demand for leverage/borrowing and any continuation or reduction of reward subsidies; pure interest‑based yield is more sustainable than reward‑heavy phases. TVL Dune vs DeFiLlama
• Direct Dune on‑chain queries are Not verifiable as of 2026‑08‑25; current TVL and fee metrics rely on analytics platforms like DeFiLlama and secondary research, which may differ slightly by methodology.

Compound V3’s reserve / treasury setup is governance-controlled and centered on protocol-owned base-token reserves. Governance docs state that only the Governor can withdraw base token reserves from the protocol and send them to a specified address, which means custody is not an off-chain treasury wallet model but an on-chain, governance-controlled reserve balance at the market level. For the treasury/reserve size, composition, custody, and chain-by-chain on-chain balances, it is not verifiable as of 2026-08-25 because the required on-chain query layer is unavailable in this run and the protocol’s own docs do not provide a consolidated, auditable multi-chain reserve balance snapshot. What can be stated from available sources is that Compound V3 reserves are denominated in the market’s base asset and are withdrawable by governance, while treasury management discussions in governance forums indicate active use of reserves/treasury assets for yield strategies and operating funding, but those forum statements are not a substitute for on-chain balances. No independent attestation of total reserves, custody segmentation, or per-chain exposure across Arbitrum, Base, Ethereum, OP Mainnet, Polygon, and Scroll was verifiable in this run, so the requested on-chain balances and composition remain not verifiable as of 2026-08-25.

Compound V3 does not have a separate v3-native token. It continues to use the COMP governance token launched for Compound v2. All tokenomics below are for COMP; none are specific to “Compound v3” beyond its role in governance and incentives. Token basics

• Name/Ticker: Compound (COMP).
• Chain & main contract: Ethereum ERC‑20 at 0xc00e94cb662c3520282e6f5717214004a7f26888.
• COMP also exists as bridged/wrapped representations on Arbitrum, Base, Optimism, Polygon, Scroll for trading and governance participation, but these are not native mints. Supply, market cap, FDV
• Max/total supply: 10,000,000 COMP.
• Circulating supply, market cap, FDV: Aggregators (e.g., CoinGecko, CoinMarketCap) report these using off‑chain methodologies; concrete values are Not verifiable as of 2026‑08‑28 under on‑chain standard. Utility & governance role
• Primary role: COMP is a governance token for the entire Compound protocol family, including v3 deployments on Ethereum, Arbitrum, Base, Optimism, Polygon, Scroll.
• Holders vote on proposals that control risk parameters, supported assets, interest-rate models, reward programs, and contract upgrades across all v3 markets.
• There is no hard-coded revenue share from protocol fees to COMP holders; any such distribution would need to be explicitly voted in via governance (no evidence of a standing “dividends to COMP” mechanic). Emissions & unlocks
• Original design: 4-year distribution of COMP to users as liquidity mining, plus allocations to shareholders, team, and community treasury.
• Detailed current emissions schedule, remaining unvested amounts, and whether all historical unlocks occurred on-chain: Not verifiable as of 2026‑08‑28 under this run’s constraints. Allocations & concentration
• Historical docs describe allocations to community (liquidity mining), shareholders, founders/team, future community treasury.
• Exact current balances of team/investor/treasury wallets, top-holder concentration, and identification of insider wallets: Not verifiable as of 2026‑08‑28. Control functions (mint/blacklist/fee)
• COMP contract has a fixed max supply (10M) and does not expose arbitrary minting to a centralized owner; governance operates via separate contracts.
• Presence/usage of blacklist or fee-switch style functions for COMP itself across all chains: Not verifiable as of 2026‑08‑28. DEX liquidity & listings
• COMP is listed on major CEXs and DEXs (Uniswap, Sushi, etc.), and on L2 DEXs where bridged COMP is traded.
• Precise liquidity depth per chain and pair, and share across Arbitrum/Base/OP/Polygon/Scroll: Not verifiable as of 2026‑08‑28.

Compound V3 has public risk-work indicating it was stress-tested under severe market shocks, including liquidation-mechanism analysis and simulation-based economic audits, but the materials provided do not include a specific published scenario for “Bitcoin falls below $10,000” across Arbitrum, Base, Ethereum, OP Mainnet, Polygon, or Scroll. The only directly relevant public evidence here is that Chainrisk’s Compound V3 work used 10,000 simulations and tested extreme price-crash and depeg cases, and Gauntlet’s analysis showed that insolvency sensitivity in v3 depends heavily on liquidation penalty and Store Front Price Factor rather than liquidation factor alone. For the requested BTC<$10,000 scenario, the effect on Compound V3 would be chain- and market-specific because each deployment has its own listed collateral set, borrow assets, and risk parameters; however, without a protocol-specific simulation or on-chain risk model for each deployment, the impact is Not verifiable as of 2026-08-25. What can be said from the available sources is that a severe BTC drawdown would primarily matter where WBTC or other BTC-linked collateral is enabled, and the main risk pathway would be faster liquidations and potential insolvency if the liquidation discount/auction mechanics fail to keep pace with the price drop.

For Compound V3, a 20% depeg of the largest collateral is a meaningful stress, but the provided sources do not contain enough chain-specific, current collateral composition data to quantify protocol-wide losses, liquidations, or bad debt across Arbitrum, Base, Ethereum, OP Mainnet, Polygon, and Scroll. The only directly relevant scenario material I found is a Chainrisk simulation reference for a 20% wstETH depeg over 14 hours in the Ethereum WETH market, but its figures are market-specific and not sufficient to generalize to all Compound V3 deployments. What can be said from the sources is limited:

• Compound V3 uses a single-base-asset market design with collateral factors and liquidation parameters that determine when positions become eligible for absorption and sale.
• Stress-testing against collateral depegs is an expected use case for Compound V3’s risk framework, and external work has specifically analyzed depeg scenarios for the protocol.
• In the Ethereum WETH market example, wstETH is described as a major share of TVL in the referenced simulation, so a 20% depeg there would likely be the dominant risk driver for that market, but the exact loss outcome is not provided in a way that can be verified here. Because on-chain verification is unavailable in this run, the requested exposure breakdown by chain and the identity/share of the largest collateral are Not verifiable as of 2026-08-25.

Compound V3 uses an absorb-and-buyCollateral design: when a borrower is underwater, anyone can trigger absorb, the protocol seizes the collateral, and the borrower’s debt is repaid from the protocol’s base-asset reserves; if reserves are below the governance target, anyone can then buy the seized collateral at a discount, replenishing reserves. For the listed markets, the loss path is market-local, not chain-shared: each deployment runs as an independent Comet market on its chain, so insolvency on one market is absorbed by that market’s own reserves and does not directly drain another chain’s market. On the documented supported set, this applies to Ethereum, Arbitrum, Base, Polygon, Optimism/OP Mainnet, and Scroll. If the top counterparty becomes insolvent in a stress event, the expected path is: 1) collateral is absorbed into the protocol; 2) the protocol’s base reserves cover the debt shortfall; 3) the seized collateral is sold via buyCollateral if reserves are below target; 4) any residual gap remains as protocol bad debt until governance or future inflows repair it. The immediate economic loss is borne first by protocol reserves and then by remaining suppliers through lower reserve growth / depleted reserve buffer; the user is made whole in the sense that their debt is closed, but their excess collateral is seized subject to the liquidation penalty. The compensation mechanism is the discounted sale of absorbed collateral to buyers, which recycles base asset back into reserves. Smart-contract impact path: borrower account -> absorb() -> protocol takes debt/collateral onto its own balance -> reserve balance decreases -> optional buyCollateral() increases reserves if below target. Not verifiable as of 2026-08-25 for chain-by-chain stress magnitudes or %TVL exposure without on-chain queries.

For a DAO-or-owner committed fraud stress scenario, Compound V3 has no direct on-chain evidence provided here of such an event; the only relevant public material in the supplied results is governance-risk discussion and an economic audit focused on market stress, not fraud by the DAO or owners. The most comparable real-world concern is a governance-capture / treasury-theft style attack, where a bloc could use voting power to redirect treasury assets; commentary around a July 2024 proposal described this as a possible governance attack and alleged attempt to steal funds, but that is not a confirmed fraud finding in the materials provided. From a risk perspective, the stress case should be treated as high severity, low verifiability: if DAO-controlled governance or admin keys were compromised or abused, the likely impact would be treasury diversion, malicious parameter changes, or unauthorized upgrades rather than normal market liquidation loss. The supplied sources do not quantify any Compound V3 fraud-loss scenario, and no verified incident in the results shows DAO/owner fraud actually occurring on the listed chains. Therefore, the correct status for this scenario is: Not verifiable as of 2026-08-25. The only sourced evidence points to governance-risk research and allegations, not a confirmed fraud event by Compound V3 DAO or owners.

Compound V3 is not verifiable as a negative-primary-yield case from the provided sources alone. The available materials confirm that Compound V3 is a lending protocol where users supply collateral to borrow a base asset, and that stress testing is used in related Compound V3 risk work, but they do not provide protocol-wide, chain-by-chain 30-day yield data for Arbitrum, Base, Ethereum, OP Mainnet, Polygon, or Scroll. Because Dune/on-chain verification is unavailable in this run, I cannot confirm whether the protocol’s primary yield source was negative over the last 30 days, nor can I apportion exposure by chain. Per the data-handling rule, the correct status is: Not verifiable as of 2026-08-25. What can be stated from the sources is limited to context: Compound III/ V3 enables collateralized borrowing of a base asset, and Chainrisk’s audit announcement discusses stress testing under adverse market conditions, including VaR-style simulations. Those sources do not establish a negative yield outcome for the protocol, and the third-party dashboard result is not a primary on-chain source. If you want, I can next provide a *non-onchain* risk framing for Compound V3 under a negative-yield stress, but the requested factual answer remains not verifiable from the current evidence.

Compound V3 is governed primarily by COMP token governance, with key powers still concentrated around the Compound Labs team and associated entities. On‑chain verification is not possible in this run: Not verifiable as of 2026‑08‑25. 1. Governance structure & who controls what

• Protocol parameters & upgrades: Managed by Compound Governance (COMP token holders) via proposals executed through the governance contracts and timelock.
• Compound Labs, Inc. (US Delaware C‑Corp) remains the core developer, leading protocol development and most client/front‑end infrastructure.
• Frontends: The main app at app.compound.finance is operated by Compound Labs; the interface is not DAO‑controlled.
• Funds/treasury: There is a Community Treasury governed by COMP voting; grants and expenditures are executed via governance proposals. 2. Proposal process & DAO reality
• Governance follows the classic COMP flow: proposal creation by large token holders or delegates, on‑chain voting, a queue in the timelock, then execution by the timelock contract.
• Delegation is central: many users delegate COMP to prominent delegates rather than voting directly.
• Given delegation and token concentration, governance operates as a real but plutocratic DAO, with meaningful control in the hands of a relatively small set of whales/delegates rather than widely distributed community control. 3. Voting concentration & top holders
• Detailed holder and voter concentration per chain (Arbitrum, Base, Ethereum, OP, Polygon, Scroll) would normally be derived from on‑chain data (Dune/etherscan), but cannot be verified here: Not verifiable as of 2026‑08‑25.
• Historically, major DeFi protocols, exchanges, and Compound Labs/associated entities have been large COMP holders and delegates, implying concentrated voting power. 4. Timelock & multisigs
• Compound governance uses a Timelock contract that enforces a delay between proposal passing and execution; this is intended to allow review and potential off‑chain intervention.
• Various multisig wallets are used for operational aspects (e.g., admin of some deployments and front‑end/infra). Specific signer lists, thresholds, and independence for each chain (Arbitrum, Base, OP, Polygon, Scroll) are Not verifiable as of 2026‑08‑25. 5. Legal entity & ToS
• The core company is Compound Labs, Inc., incorporated in the United States (Delaware). Precise registration number and directors are Not verifiable as of 2026‑08‑25.
• Use of the official front‑end is governed by Compound Labs’ Terms of Service, which typically reserve rights over the website and disclaim custody over user assets; these ToS are company documents, not DAO decisions.

Compound v3 is a non-custodial lending protocol governed primarily by the Compound DAO, with development historically led by Compound Labs, Inc., a Delaware corporation. Legal and regulatory analysis must distinguish the on-chain protocol from the off-chain entities and interfaces. 1. Legal entity & governance

• Compound Labs, Inc. created and maintains core code and the main app interface; it is US-based (Delaware) and has previously made SEC filings as a corporation.
• Protocol upgrades and key parameters are controlled by the Compound DAO via COMP token governance.
• For Arbitrum, Base, Optimism, Polygon, Scroll deployments, governance is generally unified at the Ethereum mainnet DAO level; chain-by-chain specifics are Not verifiable as of 2026-08-25. 2. User-facing interfaces, ToS & restrictions
• The main web UI (app.compound.finance) applies Terms of Service and may geo-restrict certain jurisdictions (commonly OFAC-sanctioned countries); precise current restrictions are Not verifiable as of 2026-08-25.
• Third-party frontends (e.g., on Arbitrum, Base, OP, Polygon, Scroll) may have separate ToS; they do not alter on-chain protocol risk but change legal recourse for users. 3. KYC/AML
• The core Compound v3 smart contracts are permissionless and do not perform KYC/AML checks.
• Compliance obligations, if any, fall on centralized interfaces, custodial wallets, or intermediaries providing access, not on the protocol itself. 4. Regulatory classification & enforcement
• US regulators have not explicitly classified Compound v3 as a specific financial product category (e.g., "securities" or "futures"); discussions around DeFi lending often reference Compound as an example but without targeted enforcement.
• As of 2026-08-25, there are no publicly known, protocol-specific enforcement actions, court cases, or sanctions against Compound v3 itself. Broader DeFi regulatory debate (SEC, CFTC, global regulators) still considers governance token and DAO responsibilities. 5. Data protection & privacy
• Protocol smart contracts on all chains hold pseudonymous on-chain data only; no PII is stored on-chain.
• Any collection of personal data (IP logs, email, KYC info) occurs at off-chain interfaces (Compound Labs’ site or third-party apps) and is governed by their privacy policies; these may create regulatory exposure separate from on-chain risk. 6. Legal structure vs actual risk
• Decentralization is partial: while the DAO governs parameters, the continuing role of Compound Labs and US nexus implies potential regulatory focus on the company and key developers.
• Multi-chain deployments (Arbitrum, Base, OP, Polygon, Scroll) extend exposure to each chain’s local regulatory environment and infrastructure risk (sequencer downtime, censorship), but these are technical and jurisdictional risks rather than clearly defined legal obligations today. Contradictions or gaps
• Precise ToS language, geo-blocking rules, and chain-specific governance implementations are Not verifiable as of 2026-08-25, so any marketing claims on “fully decentralized” or “non-regulated” status should be treated as unverified marketing claims.

Not verifiable as of 2026-08-25. The gathered web results confirm Compound V3 uses stablecoins such as USDC on several chains, and they show current market snapshots, but they do not provide a reliable historical series of price deviations needed to count depegs or measure the last depeg magnitude. A direct answer on whether the protocol’s stablecoin ever depegged, how many times, when the last event occurred, and the exact % move would require chain-specific on-chain price/market data that is not available in the gathered sources. One related result shows Compound USDC trading well below $1 on a token-price page, but that is the Compound USDC token, not evidence of a protocol market depeg event, so it cannot be used for this question.

Compound V3’s top risks are: 1) Governance risk — historical proposals show governance can be attacked or used to execute harmful actions, including the 2024 treasury-drain incident described by independent risk reports; 2) Smart-contract / accounting bug risk — Compound has had a major past rewards-distribution accounting error, which demonstrates that even mature code can produce large losses; 3) Oracle and collateral-price risk — Comet depends on external price feeds, so bad oracle data or sharp depegs can trigger mistaken liquidations or insolvency; 4) Single-base-asset market risk — each market borrows only one base asset, so liquidity stress in that asset can freeze withdrawals or worsen rates; 5) Market/liquidation concentration risk — isolated markets reduce contagion, but they also concentrate risk within each market and can suffer liquidation cascades when collateral prices move quickly. These risks are the most consistently supported across independent risk analyses and Compound’s own documentation, which emphasizes audits, bug bounty coverage, oracle dependence, and the simplified single-base-asset design.

Compound V3’s top strengths are: (1) capital efficiency through a single-base-asset borrowing model, which simplifies lending and can improve asset utilization; (2) risk reduction via isolated deployments and supply caps on collateral assets; (3) stronger liquidation and market design, including separate borrowing and liquidation collateral factors and a redesigned liquidation engine; (4) lower operational complexity / gas usage from a simpler, more standardized architecture; and (5) portable EVM deployment, because it uses Chainlink-based pricing and is designed to work across EVM chains.