Velodrome V3

Velodrome V3 is a concentrated-liquidity DEX / ve(3,3) AMM deployment of Velodrome on OP Mainnet and the OP Stack Ink L2. Identification

• Name: Velodrome V3 (often “Velodrome v3 CL”)
• Category: Decentralized exchange (DEX), ve(3,3) model with Uniswap‑v3–style CL pools and gauge system.
• Website: velodrome.finance (core app entry).
• Docs: Velodrome Docs (hosted under docs.velodrome.finance, includes v3 section).
• Chains:
• OP Mainnet (Optimism) – primary deployment.
• Ink – OP Stack L2 where Velodrome is the “native DEX”; v3 contracts are deployed there as well.
• Launch timing: Velodrome v3 was announced and rolled out on Optimism in Q2 2024 (public comms around May–June 2024).
• Native token: VELO (Velodrome’s governance and ve-token) on Optimism; used for gauges, bribes, and fee distribution. Main contracts & verification status Because Dune/on‑chain tools are unavailable in this run, all contract data is from explorers/analytics only.
• OP Mainnet:
• A dedicated V3 router and factory set for Velodrome v3 is referenced by Optimism ecosystem docs and DeFiLlama’s “velodrome-v3” listing as the canonical v3 deployment on Optimism.
• These contracts are verified on Optimistic Etherscan as Velodrome v3 factory/router implementations.
• Ink:
• Ink explorer and OP Stack docs list a Velodrome v3 factory and router as the primary CL DEX contracts on Ink, with contract names matching Velodrome v3 and marked verified in the Ink explorer. Important limitation: Exact contract addresses and cross‑checking with Dune raw tables are Not verifiable as of 2026‑08‑29 per constraints; only explorer/aggregator confirmation is used. Fork lineage & design
• Velodrome v3 is described as a custom concentrated‑liquidity AMM drawing on Uniswap v3–style ticks with the legacy Solidly / ve(3,3) gauge and bribe design from Velodrome v2.
• Multiple sources characterize Velodrome v2 as a fork/evolution of Solidly (Andre Cronje’s design) with significant governance and tokenomics changes; v3 extends this with CL pools rather than plain constant‑product pools.
• Public docs and coverage describe v3 as inspired by Uniswap v3, but not a straight byte‑for‑byte fork; instead, Velodrome claims bespoke implementations and integrations with existing ve‑gauges. Audits & fork‑risk history
• Velodrome lists v2/v3 smart contracts as audited by independent firms (e.g., OpenZeppelin / external auditors mentioned in docs), but underlying reports and exact v3 coverage could not be independently located beyond aggregator references.
• Therefore: detailed v3 audit scope is Not verifiable as of 2026‑08‑29.
• No documented history of malicious modifications in Velodrome v3 forks or clones was found in independent media or major exploit trackers.
• Absence of evidence is not proof of safety; it simply means no major reported malicious-fork incidents surfaced in the research window.

Velodrome V3 appears to have a real product surface, not just a landing page: the GitHub docs repo says its content is used for contextual help across the web app, and the GitHub API repo says the HTTP API is used by the app to fetch tokens and liquidity pool pairs. There is also a public on-chain-oriented SDK called Sugar for fetching pool data directly, which supports the existence of developer-facing integration surfaces. Open API: yes, but with an important distinction. An official HTTP API repo exists for app data, and the project also publishes an on-chain SDK/API layer for developers; however, the web evidence does not verify a stable public API specification, authentication model, or current endpoint availability as of 2026-08-29. Live deposits/withdrawals, broken links, fake metrics, and template signs are not verifiable as of 2026-08-29 from the available evidence. The sources confirm active documentation and app-related backend components, but they do not by themselves prove current deposit/withdrawal flows on Ink or OP Mainnet. Overall maturity assessment: moderate-to-advanced product maturity, with real docs and an app-linked API, but specific runtime UX health and chain-by-chain live functionality remain not verifiable as of 2026-08-29.

Superchain interoperability audit, relevant to Velodrome’s cross-chain components for Ink and OP Mainnet. The source says the audit focused on multi-chain state consistency, functional correctness, Hyperlane integration, and frontrunning resistance, and that issues such as voting-period bypass via poke() and metadata misuse in bridges were resolved. It also says a second version relaxed message-ordering constraints and the addressed issue could temporarily create accounting inconsistency; however, specific critical/high/medium counts are not given in the provided results. The source describes the codebase as providing a high level of security and states that the issue was addressed. Coverage of deployed code is supported by the repository/audit-context linkage, but a literal bytecode-match assertion is Not verifiable as of 2026-08-29 from the provided results.

Velodrome V1 security review / contest audit. The available sources do not provide a complete public issue table for the original contest in the search results, so specific critical/high/medium counts and fix-status breakdown are Not verifiable as of 2026-08-29 from the provided results. The source does indicate the protocol later described V1 additions as audited before launch.

Velodrome V2 full audit. The legal-disclosure source states the review identified 119 issues across all severities, including 1 critical risk and 8 high risks, and says all critical and high-risk issues were fixed before deployment; it also says the follow-up audit verified the fixes. The provided results do not include the original report text itself, so medium-severity counts and full fix-status detail are only partially verifiable from the search results. The audit is described as covering deployed protocol code.

Slipstream audit (Velodrome V3 concentrated-liquidity contracts). The available results do not provide the report’s issue counts or severity breakdown for Velodrome V3 itself. The only verifiable items here are the completion/publication dates and that the review covered Slipstream smart contracts; specific critical/high/medium findings and fix status are Not verifiable as of 2026-08-29 from the provided results. The GitHub repository indicates this is the Slipstream contract codebase, supporting a deployed-code match for the repository-level source, but the exact bytecode-match for the audited commit is Not verifiable as of 2026-08-29 from the provided results alone.

Yes — Velodrome V3 has an active bug bounty program on Immunefi. Immunefi lists it as live since 29 June 2023 and last updated 05 July 2026. The launch announcement also states that Velodrome launched a $200,000 Immunefi bug bounty on 29 June 2023. The currently visible payout parameters are summarized in Velodrome’s GitHub security page: Severe: $20,000-$200,000, High: $5,000-$20,000, Medium: $1,000-$5,000, Low: $100-$1,000, with rewards paid in the USD equivalent of USDC, DAI, or ETH. Immunefi’s program page also indicates PoC required. The scope appears to have been expanded for new Slipstream contracts: Velodrome said on 23 January 2024 that its new Slipstream contracts were added to the $100,000 bug bounty program on Immunefi. This creates a small contradiction with the earlier $200,000 launch figure, so the exact current cap is not fully verifiable as of 2026-08-29 from the available sources alone. The safest interpretation is that the program is active, but the precise maximum reward depends on the current Immunefi scope/version. On results: the sources provided do not show any confirmed bounty payouts, disclosed reports, or total funds paid. So the result of the program is Not verifiable as of 2026-08-29 from the available sources.

Velodrome V3 on Ink and Optimism (OP Mainnet) is a concentrated‑liquidity AMM whose main external risks come from the assets it routes, its oracle choices (when any), and cross‑chain/bridge dependencies. On‑chain verification is not possible in this run: Not verifiable as of 2026‑08‑29. ### 1. External protocol & oracle dependencies

• Core design: Velodrome is primarily a swap AMM; pricing is set by pool reserves, not Chainlink or other oracles, so classic oracle manipulation risk is lower than in lending protocols.
• However, any protocol integrating Velodrome LP prices as “oracle” (for collateral, RWAs, etc.) inherits AMM price‑manipulation risk: thin liquidity pools can be swung with relatively small capital, especially on smaller chains like Ink.
• Gauge voting & rewards depend on external token emissions (e.g., veVELO, partner projects). If those counterparties fail or halt emissions, LP incentive structures can change abruptly, causing liquidity flight and slippage spikes. ### 2. Bridges & multi‑chain exposure
• Velodrome operates on Optimism and is expanding to Ink, which itself is part of a Superchain / OP Stack ecosystem.
• Liquidity on each chain is economically separate; but users often move assets via bridges (Optimism Gateway, third‑party bridges like Across, Hop, etc.).
• Bridge failures (smart‑contract exploit, custodian failure, governance attack) can create:
• “Unbacked” bridged assets on one side.
• Sudden depegs vs canonical L1 assets.
• Liquidity drain from Velodrome pools as users rush to exit. ### 3. Stablecoins, LSTs, restaking & RWA exposure
• Velodrome pools commonly include major stablecoins (USDC, USDT, DAI), LSTs (e.g., wstETH), and restaking tokens on OP Mainnet.
• Counterparty risk is dominated by issuer/SPV risk (USDC, USDT), protocol risk (Maker for DAI, Lido/RWA issuers), and restaking protocol failure.
• Failure scenarios:
• Stablecoin depeg/issuer insolvency: pools with that asset become toxic; LPs suffer losses; traders may arbitrage aggressively, amplifying volatility.
• LST/restaking slashing or oracle failure: LSTs can trade at discount, causing impermanent loss for LPs and skewing prices for downstream protocols using Velodrome swaps. ### 4. CEX/MM & liquidity concentration
• Major pools on OP rely on MM activity by funds/DAOs and CEX‑connected desks.
• If a key MM or CEX account withdraws, liquidity can collapse locally, increasing execution risk and price impact for large trades. Overall, Velodrome V3’s primary counterparty risks are underlying asset issuers and protocols, bridges, and large liquidity providers/MMs; smart‑contract risk is more protocol‑specific and outside this question’s scope.

Velodrome V3 is non-custodial: users deposit liquidity into smart contracts, but the protocol does not take possession of user funds in the way a centralized exchange would. TokenTerminal describes Velodrome as a “non-custodial exchange protocol,” and its V3 repository states that Slipstream is implemented as smart contracts for concentrated liquidity pools, with core and periphery contracts adapted from Uniswap V3. For custody organization, this means assets are held in protocol contracts on the supported chains rather than by an intermediary custodian. On the chains in scope, DeFiLlama shows Velodrome V3 TVL split across Ink and OP Mainnet among other chains, indicating that custody exposure is distributed by chain deployment rather than pooled under a single off-chain custodian. There is also a governance layer that influences how incentives and fees are directed, but that is not the same as custodial control over user assets. The protocol’s fee and voting mechanics route trading fees and emissions through veVELO/voting logic, while the underlying liquidity remains in the smart contracts. What is *not verifiable as of 2026-08-29* from the available sources is any chain-specific breakdown of upgrade-admin keys, multisig controls, or emergency-pauser authority for Velodrome V3 on Ink or OP Mainnet. Those details would require contract-level verification or an auditor/governance source not present in the provided results.

Since launch, the clearly documented incidents tied to Velodrome are a team-wallet theft in August 2022, where a former team member (“Gabagool” / _proxystudio) drained about $350,000 from a team-operated wallet used for operational/salary funds; Velodrome said user funds were not affected, severed ties with the individual, and worked with legal counsel. A later report said the stolen funds were ultimately recovered, and the earlier estimated losses were repaid/returned. The cause was insider theft/key access abuse rather than a protocol smart-contract exploit.

A separate front-end/domain incident occurred in late November/early December 2023, when Velodrome and Aerodrome reported their interfaces had been compromised via social engineering against their domain provider. Reported user impact was limited/unclear, but some reporting said users may have lost funds despite warnings and that Velodrome’s TVL fell by more than $10 million during the episode. The response was to warn users not to interact, investigate, restore the domains, and plan a provider change; the protocols also created an intel bounty on Arkham Intelligence.

Velodrome V3’s key management is organized as a layered access model rather than a single shared admin key. The only directly verifiable source in the provided results is the Relay component repository, which says privileges are split among Public, Keepers, Allowed callers, Relay Admins, and the Velodrome team; it also states that the Velodrome team authorizes addresses to claim rewards (and compound for autocompounders), while keepers are trusted to perform swaps using approved routes. The Relay design further describes time-based controls: the first hour after an epoch flip is reserved for the admin, the next five days are reserved for keepers, and the last 24 hours open to everyone, which limits how long any one privileged role can act. It also notes that the governor role within Voter can create an (m)veNFT, indicating governance-based control over some sensitive actions. For the named chains, the provided sources do not give chain-specific key-management details for Ink or OP Mainnet, so that part is Not verifiable as of 2026-08-29. The safest interpretation is that Velodrome V3 relies on role-based operational keys for automation and reward management, while governance keys control protocol-level permissions; however, a fuller answer would require contract-level verification or a security disclosure beyond the provided results.

Smart-contract and admin risks for Velodrome V3 on OP / Ink are only partially assessable from public info; key on-chain details are *Not verifiable as of 2026‑08‑30* due to lack of direct contract / event inspection. ### 1. Contract set & verification

• Public GitHub shows Velodrome v2 / Superchain contracts, not an explicit v3 package, suggesting v3 may be an evolutionary deployment of the same AMM stack on Optimism and Superchain (Ink as a leaf L3).
• GitHub repos state contracts are open-source, but individual v3 core contract addresses, verification status and exact Ink deployment set are Not verifiable as of 2026‑08‑30.
• Known v2 contracts include PairFactory, BribeFactory, Voter, VELO token, veNFT, etc., so v3 likely reuses a similar factory‑based architecture. ### 2. Upgradeability / proxy architecture
• No independent source describes v3’s proxy pattern, admin type, or upgrade logic.
• Whether AMM pairs, factories, Voter, and governance contracts are upgradeable or immutable is Not verifiable as of 2026‑08‑30. ### 3. Admin / owner / emergency roles
• Governance of Velodrome overall is driven by veVELO (veNFT) voting, with VELO lockers controlling emissions and fees, but this does *not* prove they control contract-level admin roles.
• Existence and permissions of:
• Proxy admin / contract owner
• Pause / emergency / guardian roles
• Fee‑setter, oracle‑setter, strategy‑setter are Not verifiable as of 2026‑08‑30.
• Renounced roles, timelock contracts and delays cannot be confirmed. ### 4. User exit, rug/freeze scenarios
• As an AMM, users *normally* can exit by removing liquidity and swapping through pools without governance approval, assuming pools are not pausable or censored; however this is inference, not on-chain verified.
• Worst case if privileged keys are compromised (typical DeFi risk, inference):
• If factories / pairs are upgradeable: attacker could upgrade logic to steal funds or block withdrawals.
• If a global pause or fee function exists: attacker could freeze trading or set confiscatory fees.
• If gauges / bribes are controllable: attacker could redirect emissions and incentives. ### 5. Architecture map (high-level, inferred)
• VELO token + veVELO NFT → governance & emissions.
• Voter / gauges → route VELO emissions to AMM pools.
• PairFactory → deploys pools (stable/volatile) used by traders and LPs.
• BribeFactory → bribe contracts paying veVELO voters.
• Superchain contracts → cross-chain message passing / xERC20 for OP↔Ink and other L3s. Given the missing direct contract data, institution‑grade assessment of v3 smart‑contract and admin risk on OP / Ink is incomplete, and any operational decisions should assume *non‑zero upgrade / admin capture risk* until addresses and roles are independently verified.

Velodrome V3 is an iteration of the broader Velodrome ecosystem (launched on Optimism) rather than a fresh, separately branded startup; most public “founder” and team information is about Velodrome as a whole, not a chain-specific V3. 1. Founders and core contributors

• Velodrome is generally described as being built and maintained by “Velodrome Labs” / the Velodrome core contributors, not a classic VC-style C‑corp with a CEO frontman.
• Public-facing leads include long-time DeFi figures using pseudonyms (e.g., community/governance representatives on forums and Twitter/X) rather than a fully doxxed C‑suite.
• No credible independent source (audits, analytics platforms, or mainstream media) provides a clear list of real names, prior employers, or formal founder biographies for Velodrome V3 specifically. Not verifiable as of 2026‑08‑29. 2. Prior projects, track record, and hacks
• Velodrome itself (V1/V2) has been live on Optimism since mid‑2022 and has operated as a major Optimism DEX/ve(3,3) protocol without a widely reported catastrophic protocol-level hack.
• There were historical issues around team wallet key compromise and fund mismanagement in early Velodrome history, publicly acknowledged in governance and community posts; mitigations included changes in operational security and multisig processes.
• No evidence in independent analytics or audit writeups of a distinct, separate prior protocol built by a clearly identified Velodrome V3 founding team. Not verifiable as of 2026‑08‑29. 3. Public vs. anonymous and credibility
• The operating structure is closer to a pseudonymous DeFi collective with some semi‑doxxed contributors than a fully transparent, KYC’d corporate founder team.
• Credibility is largely performance-based: sustained TVL/volume on Optimism, integrations with other protocols, and continued upgrades (e.g., V3 deployment) rather than personal reputations of named founders. 4. Jurisdiction, office, and business reality check
• No independently verifiable information on:
• A registered company entity clearly tied to “Velodrome V3”.
• A physical office location or onshore regulatory domicile (e.g., US/EU‑registered corporate filings).
• Velodrome is therefore best categorized as a web-native DeFi protocol with an online contributor organization; any claims of specific legal domicile or offices coming solely from protocol materials would be unverified marketing claims. Not verifiable as of 2026‑08‑29. Risk analyst takeaway For institutional exposure, Velodrome V3 should be treated as a pseudonymous, web-front DeFi protocol with operational track record on Optimism but no on-chain–verified or regulator-filed founder identity disclosures. Governance, security process, and multisig structure matter more than founder pedigree here.

Velodrome V3 (Slipstream) currently has a strong technical-security track record and no public fraud/rug/insolvency or sanctions allegations, but carries typical DeFi and ve(3,3) governance/incentive risks that some commentators criticize. ### Protocol & team reputation

• Velodrome is widely described as the dominant DEX on Optimism and a core liquidity hub for the OP Superchain, which is generally positive for protocol reputation.
• It was launched by the team behind veDAO, inspired by Andre Cronje’s Solidly design, placing it in a known but experimental ve(3,3) lineage.
• Velodrome is now part of the unified “Aero protocol” stack across Superchain L2s, indicating alignment with the broader Optimism ecosystem. ### Security audits, reviews, and bug bounties
• Early Velodrome codebase underwent a security audit and peer review as part of a Code4rena contest; all high/medium-risk issues from that round were reportedly resolved before deployment (unverified marketing claim).
• A Velodrome legal/risk disclosure states:
• V2 received a comprehensive audit by Spearbit (Feb–Mar 2023), with 1 critical and 8 high-risk issues found and fixed before deployment; medium/low findings mostly fixed or formally acknowledged.
• A follow‑up Spearbit review (May–Jun 2023) verified fixes, and post‑engagement reviews confirmed resolution of critical issues.
• The Superchain release (which underpins V3/Slipstream) was audited by ChainSecurity and Sherlock in 2024.
• An active bug bounty on Immunefi offers up to $200k for critical findings, matched by Optimism Foundation support (still a protocol‑originating claim, so “unverified marketing claim”).
• Earlier bug bounty via Code4rena (May 2022) reportedly attracted no successful claims for up to $200,000 in rewards, suggesting no publicly disclosed severe vulnerabilities in scope at that time. ### Legal, regulatory, and sanctions
• The VELO token whitepaper is governed under Cayman Islands law, indicating an offshore, fund‑style legal structuring.
• No evidence in retrieved sources of regulatory enforcement actions, insolvency proceedings, or sanctions listings specifically targeting Velodrome, its core team, or investors as of the latest available data (Not verifiable as of 2026‑08‑29). ### Criticisms, sentiment, and unresolved concerns
• Commentary focuses mainly on mechanism risk: the ve(3,3) model and bribes/emissions flywheel can create complex governance incentives and centralization of voting power, which are standard concerns for this design pattern rather than Velodrome‑specific misconduct.
• The design of veVELO as NFTs addresses transferability but secondary‑market liquidity for those governance positions is noted as limited, which may affect exit flexibility for large holders.
• No major public controversies, rug‑pull accusations, or widely reported security incidents specific to Velodrome V3 on Ink or OP Mainnet were identified in the gathered data (Not verifiable as of 2026‑08‑29). From an institutional risk perspective, the main reputation factors are: strong audit coverage and ecosystem integration on the positive side, versus complex tokenomics and governance incentives as ongoing structural concerns.

Velodrome V3 is a ve(3,3-style AMM on Optimism (OP Mainnet) and Ink L2 focused on incentivized liquidity for governance-selected pairs, with yields primarily from trading fees plus voting bribe markets, and secondarily from subsidized emissions. ### Strategy & Assets

• Core design: vote-escrowed governance token (VELO / vVELO); liquidity providers earn fees and incentives on selected pools; voters earn bribes and protocol incentives.
• Assets in: volatile tokens and stablecoins on Optimism and now Ink, with concentration in major ecosystem pairs (OP, ETH, stablecoins).
• Assets out: LP positions (AMM shares), voting power, and emissions/bribes paid in VELO or partner tokens. ### Yield Sources & Nature of Returns
• Organic yield: swap/trading fees from pool volume.
• Subsidized yield: VELO emissions plus external token bribes directed to gauges; this is material and central to the model.
• Risk profile: LPs are directional (impermanent loss), while vote/bribe strategies are closer to market-neutral but exposed to VELO price and governance risk.
• No native leverage or restaking at AMM level; leverage appears only via external protocols using Velodrome LP or VELO as collateral (Not verifiable as of 2026-08-29). ### Lock-ups, Withdrawals, Collateral
• Governance token is locked as veVELO/vVELO for voting power; lock durations and boost schedules vary by version (exact parameters Not verifiable as of 2026-08-29).
• LP capital is unlocked, withdrawable subject to normal AMM liquidity removal mechanics; no protocol-level withdrawal gates identified (Not verifiable as of 2026-08-29).
• Collateral use (e.g., VELO or LPs in money markets) depends on external protocols, not Velodrome core (Not verifiable as of 2026-08-29). ### Fees, Limits, Protocol Revenue
• Revenue streams:
• Swap fees (percentage of volume, pool-specific).
• Bribe and incentive-related flows to veVELO voters and treasury.
• Detailed fee tiers, protocol cut vs LP share, and any hard deposit/TVL limits are Not verifiable as of 2026-08-29. ### TVL & APY
• TVL by chain/product and trend comparison (Dune vs DeFiLlama) is Not verifiable as of 2026-08-29 in this run.
• APY history, volatility, and sustainability for Velodrome V3 pools are Not verifiable as of 2026-08-29; high dependency on emissions/bribes implies structurally volatile and regime-dependent yields. ### Model Summary Velodrome V3’s economic model is a governance-directed liquidity marketplace where veVELO holders steer emissions and bribes to pools, extracting value from fees and incentives, with LPs bearing market and IL risk and voters monetizing governance power.

Not verifiable as of 2026-08-29. I could not confirm a reserve or treasury address set, on-chain balance, custody arrangement, or reserve policy for Velodrome V3 on Ink or OP Mainnet from the available web results. The only directly relevant web evidence found is a third-party TVL snapshot showing protocol liquidity by chain—Ink about $13.24m and OP Mainnet about $7.09m—but TVL is not the same as treasury/reserves and does not identify controlled treasury assets. No attestation or audited reserve statement was available in the retrieved sources, and without Dune/on-chain verification the requested composition and controller addresses remain unverified. If you want, I can next compile a source-checked list of likely treasury-related contracts and governance-controlled addresses from explorer or docs material, but I cannot present those as verified balances here.

Velodrome V3 is the new version of Velodrome on OP Mainnet and Ink, but as of 2026‑08‑29 there is no clearly separate, widely‑documented “Velodrome V3 token”. All information below pertains to the existing VELO token used across Velodrome deployments. On‑chain verification is not possible in this run: Not verifiable as of 2026‑08‑29. 1. Native token & contracts

• Token name/ticker: Velodrome, VELO (sometimes wrapped as veVELO for locked voting positions).
• Chain coverage: Confirmed on OP Mainnet; Ink deployment references using the same governance/ve-token model, but contract addresses for Ink are not consistently documented across independent sources.
• Exact token contract addresses, Ink-specific contracts and any V3‑specific token contracts: Not verifiable as of 2026‑08‑29 (no consistent cross‑checked sources beyond protocol self‑docs and UIs). 2. Supply, market cap, FDV Public aggregators track VELO on Optimism with total and circulating supply plus market cap/FDV, but figures differ between platforms and move with emissions and price.
• Because they conflict and cannot be cross‑checked against raw chain data in this run: Authoritative total supply, circulating supply, market cap and FDV are Not verifiable as of 2026‑08‑29. 3. Token utility & governance role Independent docs and analyses agree on the core vote‑escrowed veVELO model:
• Lock VELO → veVELO for governance voting on gauge weights (which pools receive emissions).
• Bribes: external incentives paid to veVELO voters directing emissions to specific pools.
• Revenue share: protocol fees (swap fees, potentially other revenues) are distributed to veVELO lockers, typically via weekly epochs.
• Governance: veVELO holders vote on gauges and potentially protocol parameters (depending on multisig/DAO setup). 4. Emissions, unlocks, allocations
• Velodrome is described as using ongoing emissions of VELO to LP gauges following a ve(3,3)‑style design inspired by Solidly.
• High‑level allocations (team, investors, treasury, community) are described in protocol‑provided docs and secondary writeups, but exact percentages and cliffs/vesting schedules differ between sources and cannot be chain‑verified here: Not verifiable as of 2026‑08‑29.
• Whether announced vesting/unlock events actually executed on‑chain for V3/VELO: Not verifiable as of 2026‑08‑29. 5. Holder concentration & controls
• Top‑holder concentration (whales, team, investors, treasury): relies on explorer or Dune‑style holder breakdowns, which cannot be reliably reproduced or verified in this run: Not verifiable as of 2026‑08‑29.
• Admin/mint/blacklist/fee‑switch roles: protocol docs and code comments indicate upgradability/multisig governance around emissions and parameters, but concrete admin addresses, their powers (minting, pausing, blacklisting, fee switch) and any changes for V3 are Not verifiable as of 2026‑08‑29. 6. Liquidity & listings
• VELO trades primarily on Velodrome itself on OP Mainnet and on a few centralized or other DEX listings tracked by aggregators.
• Depth by venue, pair and chain (including Ink): Not verifiable as of 2026‑08‑29 without on‑chain or consistent orderbook data. Overall, from an institutional risk lens, all quantitative tokenomics for Velodrome V3/VELO (supply, caps, unlocks, allocations, holder concentration, exact admin powers and DEX depth) remain Not verifiable as of 2026‑08‑29 under the current tooling constraints and should be treated as such.

For Velodrome V3 on Ink and OP Mainnet, a Bitcoin drop below $10,000 would most likely matter indirectly: it would signal severe crypto-wide risk-off conditions, which typically compress DEX trading volumes, reduce LP incentives, and weaken fee generation. The provided web results do not contain protocol- or chain-specific stress metrics for Velodrome V3, so the precise impact on TVL, pool composition, emissions, or treasury is Not verifiable as of 2026-08-29. The most defensible stress read-through is that a BTC collapse of that magnitude would likely increase downside pressure on altcoins and DeFi liquidity generally, and VELO-linked activity would probably be hit through lower risk appetite rather than any BTC-collateral liquidation channel, since Velodrome is a DEX and not a BTC lending protocol. That transmission mechanism is an inference from the market context, not a protocol-specific measured result. What can be stated from the results is limited: one source frames $10,000 BTC as an extreme downside scenario and another describes a broad market spectrum of bearish BTC targets, but neither provides evidence about Velodrome V3’s actual resilience or loss rates under that shock. For an institutional risk memo, the key unanswered items are: chain-by-chain TVL exposure, stablecoin share, volatile-asset concentration, incentive dependency, and historical volume sensitivity on Ink versus OP Mainnet. Those remain Not verifiable as of 2026-08-29 from the supplied material.

Not verifiable as of 2026-08-29. The provided web results do not contain the protocol’s on-chain collateral composition, chain-by-chain exposure, or a liquidation model for Velodrome V3 on Ink and OP Mainnet, so the effect of a 20% depeg of the largest collateral cannot be quantified from these sources. The only potentially relevant material is an Aave governance thread discussing sUSD risk on Optimism V3, which is about a different protocol and does not establish Velodrome V3’s own exposure. If you want, I can still give a conservative qualitative stress framework, but the numerical loss estimate is not verifiable from the supplied evidence.

For Velodrome V3 on Ink and OP Mainnet, a top-counterparty insolvency stress is mostly a reward/fee-collection problem, not a balance-sheet loss problem. The protocol’s documented mechanics route swap fees and emissions through pool/gauge/reward contracts, and bribes/fees are paid to voters proportionally; if an external counterparty supplying bribes or incentive rewards becomes insolvent, the direct loss is borne by the unpaid reward recipient class (voters/LPs expecting those incentives), while the protocol itself does not appear to underwrite the obligation. The expected loss path is: counterparty fails to deliver promised incentives → the relevant BribeVotingReward / fees distribution contracts do not receive the external deposit → claimable rewards for that epoch are smaller or zero → affected voters/LPs receive less. Because the contracts described in the repository only distribute what has actually been deposited, there is no indicated compensation layer, insurance fund, or protocol backstop in the available sources. Who absorbs it:

• Primary absorber: voters/LPs tied to the specific pool/gauge with the failed incentive stream.
• Secondary absorber: the sponsor/issuer of the bribe or incentive, if any recovery is possible outside the protocol.
• Protocol treasury / veVELO holders: not verifiably shown to absorb the loss from these sources. Not verifiable as of 2026-08-29. Compensation: no independent source found showing a formal compensation mechanism for failed external rewards. Not verifiable as of 2026-08-29. Impact path through smart contracts: external rewards/bribes are deposited into reward contracts for a specific epoch; the contracts then distribute only available balances to eligible voters, so insolvency upstream propagates as reduced or absent claimable rewards rather than a contract-level insolvency event. On the two chains, the same logic applies independently to Ink and OP Mainnet; chain-specific TVL/exposure split is Not verifiable as of 2026-08-29 from the gathered sources.

For the fraud by DAO or owners stress scenario, I found no verifiable evidence that Velodrome V3’s DAO or owners committed fraud on Ink or OP Mainnet. The available sources instead show security incidents and a team-member theft/confession, which are different from an on-governance fraud allegation and do not prove DAO-wide or owner-directed fraud. Relevant context: Velodrome disclosed a DNS attack that redirected users to malicious clone sites and caused an estimated loss/damage of up to $250,000 to users who interacted with the attacker’s sites; the report attributes this to external social engineering against the domain registrar, not to DAO or owner fraud. The project also disclosed a bribe-reward vulnerability that it treated as a white-hat event and said was isolated to external bribes, again not framed as DAO or owner fraud. Separately, media coverage reported that a team member admitted to taking more than $400,000 from a team-operated wallet and later returned the funds; this is an internal theft incident, but it is not evidence that the DAO or owners collectively committed fraud. Assessment: committed fraud by the DAO or owners = Not verifiable as of 2026-08-29.

For Velodrome V3, the primary yield source is not verifiable as positive over the last 30 days from the provided web results. The only protocol-specific evidence available here is a DeFiLlama protocol page for Velodrome V3 that mentions Slipstream and shows pool/activity metadata, but it does not provide a 30-day yield breakdown by chain or an audited on-chain source for yield composition. Given your stress scenario requirement, the defensible answer is:

• Primary yield source negative (30d): Not verifiable as of 2026-08-29.
• Chain split (Ink, OP Mainnet): Not verifiable as of 2026-08-29.
• On-chain confirmation: unavailable in this run because Dune/on-chain tools are not available, so I cannot verify fees, emissions, or pool-level yield contributions. If you need a strict risk memo, the correct treatment is to flag the yield assumption as unsupported rather than positive. In a stress case, that means any underwriting based on recent realized yield should be discounted until chain-level data is checked independently.

Velodrome V3’s governance is only partially verifiable from the gathered web sources. On Optimism, Velodrome’s launch materials say veVELO holders can create gauge proposals at 0.1% of veVELO supply and vote to approve/reject them, with quorum-based default pass behavior if quorum is not met; ChainSecurity’s audit also describes two governance paths: a trusted EOA/multisig can change emission rates via a simple governor, while an EpochGovernor lets veVELO stakers vote on emission changes. The Optimism governance forum further indicates that core protocol upgrades are subject to a 72-hour timelock and that core contracts are owned by secure multisigs, but the exact signer set, threshold, and signer independence are not verifiable as of 2026-08-29. The DAO is therefore real for emissions and gauge direction, but the extent of its control over contracts, frontend, and funds is not fully verifiable from the available sources; for non-emission upgrades, multisig/timelock custody appears to remain material. For chain exposure, DeFiLlama shows Velodrome V3 TVL split across Ink at $13.24m and OP Mainnet at $7.09m, but on-chain verification of the share by chain is not verifiable as of 2026-08-29. Voting concentration, top holders, and proposal power via Dune are not verifiable as of 2026-08-29. The company-control question is also not verifiable as of 2026-08-29: no reliable source in the gathered set established a controlling legal entity, jurisdiction, registration number, directors, or terms of service for Velodrome V3 itself.

Velodrome V3 operates in a legally grey DeFi environment with no protocol‑specific enforcement actions identified as of 2026‑08‑30. Most legal/regulatory signals come from Velodrome’s broader ecosystem and the Optimism/Ink chains, not Velodrome V3 itself. 1. Entity, jurisdiction, legal structure

• Velodrome is closely tied to the Optimism ecosystem; Optimism is governed by the Optimism Foundation (Cayman Islands) and an on‑chain governance system, but Velodrome’s own corporate entity is not clearly disclosed in public docs.
• No clear, independently verified corporate registration for “Velodrome V3” or “Velodrome Finance” surfaced via public searches. As of 2026‑08‑30, the precise legal entity and jurisdiction are Not verifiable as of 2026‑08‑30. 2. Terms of Service, user restrictions
• The primary Velodrome app interface hosts a “Terms of Use”/disclaimer emphasizing non‑custodial smart contracts, no guarantee of returns, and that users bear risk of loss; these are published via the website/app (unverified marketing claim).
• Common DeFi practice on Optimism includes geo‑blocking or discouraging use from OFAC‑sanctioned jurisdictions or restricted countries, but explicit country bans for Velodrome V3 cannot be confirmed independently. Not verifiable as of 2026‑08‑30. 3. KYC / AML practices
• Velodrome V3 contracts are permissionless AMM pools on Optimism and Ink; no evidence of on‑chain KYC (e.g., whitelisting contracts or identity‑gated pools).
• No public statements or independent documentation of transaction monitoring, AML screening, or reporting obligations specific to Velodrome V3 were found. Practically, Velodrome should be treated as non‑KYC, non‑custodial infrastructure. 4. Regulatory classification & risk
• As an AMM DEX distributing liquidity incentives, Velodrome V3 sits in categories regulators have associated with: unregistered securities offerings (if reward tokens are deemed securities), operating an unlicensed trading venue, and potential facilitation of money laundering.
• Global regulators (e.g., U.S. SEC, CFTC, EU authorities) have signaled that DeFi protocols and their “control persons” may face enforcement if they effectively run trading platforms or provide market‑making in tokens that qualify as securities or derivatives.
• No public enforcement actions, court cases, or sanctions lists currently naming Velodrome, Velodrome Finance, or Velodrome V3 were found. Not verifiable as of 2026‑08‑30. 5. Data protection / privacy
• As a non‑custodial AMM, Velodrome V3 primarily processes pseudonymous blockchain addresses; there is no evidence of user PII collection on‑chain.
• Any web‑based interface may collect normal web analytics or wallet metadata; however, a GDPR/CCPA‑style privacy policy specific to Velodrome V3 is Not verifiable as of 2026‑08‑30. Risk takeaway for institutions
• Treat Velodrome V3 as a non‑KYC, non‑custodial DeFi AMM on Optimism/Ink with unclear corporate entity, operating in a regulatory environment where DEX/DeFi enforcement is increasing but protocol‑specific action is not yet evident.
• Institutional use raises potential exposure to securities‑law, market‑venue, and AML/money‑laundering theories of liability, especially if any controlling team or governance participants are identifiable in a regulated jurisdiction.

I could not verify, from the available web results, which *specific stablecoin* Velodrome V3 used on Ink and OP Mainnet, so the depeg history is Not verifiable as of 2026-08-29. The search results only show Velodrome V3 venue pages and one unrelated historical price snippet for ALUSD on Velodrome (Optimism), which is not enough to establish the protocol’s stablecoin exposure on the two requested chains. If you mean ALUSD specifically, the only result I found shows at least one observed trade at $0.8985 on Velodrome (Optimism) on 2022-10-05, which is a 10.15% discount to the $1 peg; however, that single data point does not prove how many depeg events occurred, when the last one was, or whether this was the protocol’s actual stablecoin used across Ink and OP Mainnet. So the honest answer is:

• Did a depeg ever happen? Not verifiable as of 2026-08-29.
• How many times? Not verifiable as of 2026-08-29.
• Last time? Not verifiable as of 2026-08-29.
• % of depeg? If referring to the ALUSD quote above, the observed low was ~10.15% below peg.

Top 5 risks for Velodrome V3 on Ink and OP Mainnet are: 1. Governance concentration / vote centralization — ve-model DEXs can concentrate voting power; one review says the top 100 wallets control about 63% of voting power, which can skew gauge emissions and governance outcomes. 2. Smart contract / accounting complexity — Velodrome’s ve(3,3) and gauge/reward mechanics are complex, increasing the attack surface and the chance of reward, liquidity, or checkpoint accounting bugs. 3. Cross-chain / migration / integration risk — ChainSecurity’s Superchain Slipstream audit highlights cross-chain compatibility, deployment, and address-collision issues as important risk areas; these are especially relevant when protocols span multiple networks. 4. Network-level dependency risk on L2s — the protocol depends on the underlying L2 environments; for Ink specifically, external reviewers cite centralized sequencer risk, limited network maturity, and thin liquidity/pricing infrastructure. 5. Liquidity and market-structure fragility — on Ink, liquidity is described as highly concentrated in Velodrome, with large pairs sometimes dominated by a single address, which can worsen slippage, liquidity flight, and collateral/liquidation risk. Additional notable risk: audits identified edge cases such as incorrect reward calculations at epoch boundaries, DOS vectors around delegation, and pool/gauge accounting problems, showing that operational correctness remains a live risk even in audited codebases.

Velodrome V3’s main strengths are its capital-efficient concentrated liquidity, low-friction fee structure, multi-pool design, ve(3,3)-based incentive alignment, and role as a liquidity hub for the Superchain ecosystem. Slipstream adds concentrated liquidity pools to improve swap efficiency and reduce slippage, while the protocol emphasizes that it charges zero fees for incentives, relay/compounder functions, voting, and Slipstream itself. The protocol also combines multiple liquidity structures—AMM-style pools, concentrated liquidity, and stable-style pools—so it can serve different trading and liquidity needs within one system. Its ve(3,3) model is designed to align LPs, lockers, and protocols through voting and incentives, supporting self-sustaining liquidity programs rather than one-off mercenary liquidity. Finally, it is positioned as a central liquidity marketplace for Optimism/Superchain-style ecosystems, which supports deep routing and ecosystem adoption.