Velodrome V3

Identification. The entity is Velodrome Finance V3 / Slipstream, website velodrome.finance; documentation is the Velodrome docs plus the public Slipstream specification. Category: concentrated-liquidity DEX/AMM with gauge-based incentives and Superchain cross-chain reward infrastructure. Velodrome originally launched June 2, 2022 and V2 launched June 22, 2023; a distinct V3/Slipstream production launch date is Not verifiable as of September 4, 2026.

Chains in the supplied scope: OP Mainnet and Ink. Native token: VELO; on the Superchain deployment architecture, xVELO is used for bridged/leaf-chain functionality. Representative V3/Superchain contract addresses. OP Mainnet root deployment: rootPoolFactory 0x31832f2a97Fd20664D76Cc421207669b55CE4BC0, rootPoolImplementation 0x10499d88Bd32AF443Fc936F67DE32bE1c8Bb374C, rootGaugeFactory 0x42e403b73898320f23109708b0ba1Ae85838C445, rootXVelo 0x7f9AdFbd38b669F03d1d11000Bc76b9AaEA28A81.

Ink leaf deployment: leafPoolFactory 0x31832f2a97Fd20664D76Cc421207669b55CE4BC0, leafPoolImplementation 0x10499d88Bd32AF443Fc936F67DE32bE1c8Bb374C, leafGaugeFactory 0x42e403b73898320f23109708b0ba1Ae85838C445, leafXVelo 0x7f9AdFbd38b669F03d1d11000Bc76b9AaEA28A81. Dune MCP was unavailable; therefore the requested ≥2-source cross-check including Dune, on-chain verification, and explorer verification status are Not verifiable as of September 4, 2026. Fork lineage. Yes. Slipstream adapts Uniswap V3 core/periphery, adding staked-liquidity accounting, gauge rewards, reward-growth tracking, custom fee modules, and Velodrome governance/Superchain messaging.

The delta received a Spearbit Slipstream audit and ChainSecurity Superchain Slipstream audit. No confirmed malicious modification of Velodrome’s deployed contracts was identified in reviewed sources. A related Aerodrome Slipstream npm package had a malicious-code advisory in 2026; this is a supply-chain incident, not evidence of a deployed-contract exploit.

Velodrome V3 appears to be a real, productized DeFi app rather than a pure landing page: GitHub shows an active protocol repo set, including a public HTTP API repo used by the app to fetch token/pool data, plus a dev docs repo that covers write functions and on-chain data access via Sugar. The ecosystem also shows a live deployment on OP Mainnet and Ink, with public references to deposits, rewards, voting, and bridging xVELO to LPs on Ink, which is consistent with functional app behavior rather than a template site. However, specific live-function checks like current deposit/withdrawal success, broken-link audit, or UX regression testing are not verifiable as of 2026-09-04 from the available evidence.

The source set does not provide enough independent confirmation to rule out partial failures or stale pages, so those items remain Not verifiable as of 2026-09-04. On API support, the evidence is clear that Velodrome has an open developer-facing API surface: the public GitHub API repository is explicitly described as a Velodrome HTTP API, and the docs repo points integrators to Sugar for on-chain pool data plus a developer SDK guide. That said, the exact current production API endpoints and uptime are Not verifiable as of 2026-09-04.

No strong template-site or fake-metrics signal was confirmed in the gathered sources, but that is also Not verifiable as of 2026-09-04.

Velodrome has an active Immunefi bug bounty program covering its live contracts. The program was live since 29 June 2023, with terms listing a maximum bounty of $100,000. The scope page states PoC is required for critical, high, medium, and low smart-contract reports, and the program requires KYC to receive a reward.

Rewards are paid by the Velodrome Finance team in USD-denominated terms, with payouts made in USDC and OP; the terms also say Optimism matches rewards for the program. Reported results include at least one critical payout of $100,000 mentioned in Optimism governance discussion. The current program page also says the bounty is live and was last updated in July 2026.

As of September 6, 2026: Not verifiable as of 2026-09-06 for contract-level dependency exposure, pool composition, or active-failure status because Dune/on-chain verification was unavailable. Primary dependencies and scenarios

• Host-chain risk — OP Mainnet: Velodrome depends on Optimism sequencer availability, transaction ordering, L1 data publication, fault-proof infrastructure, and the canonical bridge. A sequencer outage/censorship event can impair swaps, liquidations, and withdrawals; bridge or fault-proof failure can delay or impair asset recovery.
• Host-chain risk — Ink: Ink is an OP Stack L2 with Kraken-linked infrastructure. Its documentation states that Ink currently has no native bridging portal and directs users to recognized third-party bridges. This creates additional bridge-counterparty and operational risk for bridged assets.
• Bridges and cross-chain routing: Velodrome’s Superchain documentation states that Superswaps use OpenUSDT as an intermediary stablecoin and rely on bridged-token pricing/oracle data or local liquidity. OpenUSDT depeg, issuer failure, bridge compromise, or insufficient destination liquidity could transmit losses across routes.
• Oracle/manipulation risk: Velodrome’s concentrated-liquidity contracts are adapted from Uniswap V3, while its documentation references on-chain pricing/oracle infrastructure. Thin pools, low-liquidity bridged assets, or sequencer-controlled ordering can make spot/TWAP prices manipulable, especially during bridge or stablecoin stress.
• Stablecoin/LST/restaking exposure: Stablecoin, LST, and restaking dependencies may exist in individual pools, but pool-level composition and percentage exposure are Not verifiable as of 2026-09-06. No verified RWA issuer/SPV, custodian, CEX, or market-maker dependency was identified from the reviewed sources. Cross-check, not on-chain truth: DeFiLlama reports Velodrome-wide TVL of approximately $42.03m, with $27.75m on OP Mainnet and $12.91m on Ink; these figures are aggregated across Velodrome deployments and should not be treated as Velodrome V3-only exposure. Contradiction callout: Previously recorded claims about concentrated stablecoin/LST exposure cannot be confirmed at pool level in this run. The earlier statement that Ink has bridge risk remains directionally supported by Ink’s own terms and FAQ, but exact exposure is unknown.

Velodrome V3 is best described as non-custodial: users interact with smart contracts from their own wallets rather than handing assets to a centralized custodian. Liquidity provider funds are deposited into on-chain pool and gauge contracts, and VELO can be locked into veVELO for governance rights, so custody is organized by function (LP deposits vs. governance locks) rather than by a central intermediary. The available evidence does not show any protocol-level withdrawal freeze, so withdrawal_paused is false only for the protocol’s standard smart-contract flow; there is no verifiable indication of a pause in the sources reviewed.

I could not verify any special segregation structure beyond ordinary per-pool/per-position accounting, so segregated_assets is null; no source reviewed establishes a custodial omnibus account or a formal segregated-custody program.

Historical Velodrome team-wallet theft (not user funds): A separate 2022 incident involved a team wallet theft of about $350,000 by a former team member; the team said no user funds were affected and the funds were recovered. This is a real Velodrome incident, but it predates Velodrome V3 / the Ink deployment and is likely outside the requested scope.

Since launch, I found two publicly reported incidents connected to Velodrome: a team-wallet theft in August 2022 and a front-end/DNS compromise in November 2023. I could not verify any separate incident specific to Velodrome V3 on Ink or OP Mainnet; the available reports are protocol-level incidents affecting Velodrome/Aerodrome domains and operations, not a confirmed V3 smart-contract exploit.

On November 29, 2023, Velodrome and Aerodrome domains were compromised through social engineering against the registrar, DNS hijacking, and deployment of malicious frontend clones. A second compromise was reported on December 1, 2023. Velodrome users on OP Mainnet were prompted to connect wallets and approve malicious transfers; core contracts and protocol liquidity were not reported compromised.

Independent transaction tracing attributes approximately $42,000 to Velodrome users; the protocol’s preliminary post-mortem gave a combined Velodrome/Aerodrome damage estimate of up to $250,000. The domains were restored, then migrated and locked at the TLD level. No recovery or completed reimbursement was verified.

Current status: resolved for the technical incident; restitution: Not verifiable as of 2026-09-06.

On November 21, 2025, attackers hijacked the centralized DNS/frontend infrastructure for velodrome.finance and aerodrome.finance after compromising registrar-side controls, removing DNSSEC protections, and redirecting users to cloned phishing interfaces serving drainer code. The underlying smart contracts, protocol liquidity, and decentralized interfaces were not reported exploited. Security partners contained the attack in under four hours and wallets issued warnings.

Independent reporting attributes approximately $700,000 in stolen funds to the combined Aerodrome/Velodrome event, but no reliable protocol-specific split between Velodrome OP Mainnet and Aerodrome Base was found. Therefore: Not verifiable as of 2026-09-06 for Velodrome-specific loss and attacker proceeds. A grant/compensation program was announced, but completion and amounts paid were not verified.

Current status: technical compromise resolved; reimbursement remediation remains unverified.

OP Mainnet / Ink: I found one relevant incident family for Velodrome V3 since launch: a front-end/domain compromise (DNS hijack / registrar takeover) affecting Velodrome’s web interface, with the earliest incident report dated 2023-11-29 and later reporting of a similar coordinated breach on 2025-11-22; the latter appears to be the most directly relevant multi-chain event for the OP/Mainnet-era deployment, but the retrieved sources do not provide a protocol-specific split for OP Mainnet vs Ink losses.

Velodrome V3’s key management is organized around governance-controlled voting and locked positions, not around a publicly documented cryptographic key custody system. The main visible control points are the Voter, VotingEscrow, and Minter contracts, which together handle emission direction, voting power, and token minting. For user-controlled participation, the protocol uses veNFT-style locks: VELO holders lock tokens to receive veVELO voting power, and those voting rights are used to direct emissions to pools.

That means the effective “keys” to governance are the locked positions and their voting rights, rather than a separate admin-key framework described in the sources. Velodrome also uses Relayer/Relay automation for managing rewards from (m)veNFTs, which suggests some operational handling is automated, but the repository description does not specify a formal key hierarchy, signer scheme, or custody model. For the specific question of who controls admin or upgrade keys on Ink and OP Mainnet, that is Not verifiable as of 2026-09-04 from the provided sources.

The available results do not identify the contract owner multisigs, timelocks, or chain-specific privileged signers for Velodrome V3 on either chain.

Assessment date: September 6, 2026. Scope: Velodrome V3 = Slipstream concentrated-liquidity contracts on OP Mainnet and Ink. Addresses

• OP Mainnet: PoolFactory 0xCc0bDDB707055e04e497aB22a59c2aF4391cd12F; PoolImplementation 0xc28aD28853A547556780BEBF7847628501A3bCbb; GaugeFactory 0x327147eE440252b893A771345025B41A267Ad985; GaugeImplementation 0x7155b84A704F0657975827c65Ff6fe42e3A962bb; NFPM 0x416b433906b1B72FA758e166e239c43d68dC6F29; Router 0x0792a633F0c19c351081CF4B211F68F79bCc9676; fee modules 0x7361…49D5f9 and 0xC565…C59D9.
• Ink: PoolFactory 0x31832f2a97Fd20664D76Cc421207669b55CE4BC0; PoolImplementation 0x10499d88Bd32AF443Fc936F67DE32bE1c8Bb374C; GaugeFactory 0x42e403b73898320f23109708b0ba1Ae85838C445; Router 0x3a63171DD9BebF4D07BC782FECC7eb0b890C2A45; LeafVoter 0x97cD…a1123. Architecture / upgradeability ``text OP governance/Voter ──> FactoryRegistry ──> PoolFactory ──clone──> CLPool └────> GaugeFactory ─clone─> CLGauge NFPM ──> CLPool; CLGauge ──> NFPM + reward token OP root bridges/messages ──> Ink leaf voter/factories `` Pools and gauges are OpenZeppelin minimal clones, initialized once; no UUPS, Transparent Proxy, proxy-admin, or implementation-upgrade function is present in the reviewed source. Implementations are immutable factory references. Admin powers / user exit
• Pool owner can transfer ownership and add tick-spacing/fee pairs.
• Swap-fee and unstaked-fee managers can replace fee modules; unstaked fee is capped in factory logic, but module behavior remains a material governance dependency.
• Gauge-factory admins can set reward notifier, minimum stake time (≤1 week), and penalty rate (≤100%).
• Users can burn/collect LP positions directly; staked NFTs have permissionless owner withdrawal. Gauge killing stops emissions but does not block withdrawal.
• No admin withdrawal of pool principal was identified; a compromised fee/governance key could impose punitive fees, manipulate rewards, or impair incentives, but not directly sweep LP principal. Rug risk: medium; freeze risk: low-to-medium. Unverified live-state items: proxy-admin type/events, current owners/managers, emergency roles, renounced roles, timelock delay, pause state, explorer verification, and current cross-chain message permissions: Not verifiable as of September 6, 2026 (Dune unavailable). Audits: ChainSecurity’s reviewed Superchain Slipstream commit reported 0 open critical/high findings, but current deployed-bytecode equivalence is not established.

ChainSecurity has published several Velodrome-related audits (Superchain interoperability, Superchain diff, Superchain Slipstream), all focused on multi-chain messaging, superchain integration, and Slipstream gauge/liquidity accounting. These relate closely to the infrastructure that Velodrome uses to extend Slipstream/V3 across Optimism and other superchain L2s. However, none of the accessible ChainSecurity summaries explicitly state “Velodrome V3 core AMM on Optimism/Ink” as a named scope, and detailed contract lists and chain IDs are not visible in the snippets.

Bytecode matching for current Ink / OP Mainnet deployments is Not verifiable as of 2026-09-04.

Report: Superchain Slipstream Smart Contracts

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.

Report: Superchain Interoperability Smart Contracts

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.

Multiple sources note Code4rena peer-review contests for Velodrome V1 and V2; some secondary commentary claims V3 components were also covered. However, no dedicated Code4rena report or contest page explicitly labeled “Velodrome V3 / Slipstream” could be located in the retrieved data. Because I cannot check the underlying contest scope or match addresses to current Ink/OP deployments, any assertion that Code4rena formally audited Velodrome V3 would be speculative.

Therefore, Code4rena V3 audit coverage is Not verifiable as of 2026-09-04.

Velodrome security review / contest coverage referenced by DeFiSafety as the audit basis for the original Velodrome codebase.

Report: Velodrome Superchain

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.

According to Velodrome’s own legal disclosures, the Slipstream concentrated-liquidity implementation, which underlies Velodrome V3 CLMM, was audited by Spearbit and completed in December 2023. Scope is described as the Slipstream/V3 core implementation (concentrated liquidity pools/gauges), but the public PDF does not enumerate contracts or chains. As of 2026-09-04, I cannot independently verify bytecode match of the audited commit to currently deployed V3 contracts on Ink or OP Mainnet — on-chain verification is impossible in this run.

Therefore coverage of deployed code vs. audited code is Not verifiable as of 2026-09-04.

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.

Report: Velodrome Slipstream & Universal Router Security Review

Velodrome appears to be a real operating DeFi team, not a purely anonymous web front: Optimism governance records list named authors Alex (alexcutler.eth), Jack, and Tao, and the proposal explicitly names core team members including Alex (@wagmiAlexander), Jack (@jackanorak), Stas, Tao (@taowatts), and others. The team also had a documented prior operation, veDAO, and said it had consulted on ve tokenomics for Redacted Cartel and Boba Network; that is a stronger credibility signal than a brand-new anonymous launch. Alexander Cutler is publicly tied to the project in press coverage and later described as a co-founder and core team member, while the team also launched Aerodrome on Base, showing an operator history beyond a single protocol.

Reality check: the available sources do not verify a real office, onshore/offshore structure, or legal entity jurisdiction, so those items are Not verifiable as of 2026-09-04. The project has also had operational/security incidents: a 2022 insider theft from a team wallet was reported, and a 2023 DNS/front-end compromise affected user interactions but not the AMM contracts themselves; those incidents indicate real operational risk rather than a fake project. For the specific Velodrome V3 presence on Ink and OP Mainnet, the sources show it was launched on Ink and is established on OP Mainnet, but the web material here does not provide chain-by-chain founder or legal-entity evidence, so any claim beyond the team names and prior-project history above is Not verifiable as of 2026-09-04.

Velodrome V3’s reputation is generally strong but not pristine. The project is presented as a continuation of Velodrome Finance on OP Mainnet and Ink, with named co-founders Alexander Cutler and Tao Watts, and a foundation structure that stewards treasury/governance. On security, the public record shows a substantial audit history rather than a single review: Code4rena’s 2022 contest found 6 high and 17 medium issues, with the high/medium issues stated as fixed except one addressed via a wrapped-contract workaround.

Later materials and audit pages reference additional reviews by Spearbit and ChainSecurity, including Superchain-era audits that describe the codebase as having a high level of security after issues were addressed. Sentiment is broadly positive among ecosystem and analytics pages, but that is mostly a reflection of active deployment and audit coverage rather than independent reputation polling. The protocol also appears to have received grants from the Optimism Foundation, which supports legitimacy in the OP ecosystem.

I did not find credible evidence in the retrieved sources of a rug pull, insolvency event, sanctions action, or formal fraud case tied to Velodrome V3. That said, unresolved concerns remain around the normal risks of a complex, upgradeable DeFi system and the fact that some issues in audits were acknowledged rather than fully eliminated. Not verifiable as of 2026-09-04: detailed founder/investor cap-table claims, any live legal disputes, and any sanctions screening specifically for Velodrome V3 on Ink and OP Mainnet.

Economic model — Velodrome V3 (Slipstream). Users deposit ERC-20 pairs into Uniswap-V3-style concentrated-liquidity positions (NFTs), selecting tick ranges. Yield comes from swap fees and, when staked in a gauge, VELO emissions; staked LPs forgo direct fee accrual, with those fees routed to the pool’s fee-voting rewards for veVELO voters. Yield character. Trading-fee yield is organic but volume-dependent. VELO emissions, bribes/incentives, and veVELO-related rewards are subsidized/token-funded rather than organic cash flow.

LP exposure is directional/non-market-neutral because concentrated liquidity experiences impermanent loss and can become out of range; range management is required. No leverage, looping, restaking, lending collateral, or external strategy layer was identified in the reviewed V3 primary materials; positions are exposed to the deposited pool assets, smart contracts, oracle/price movement, and VELO incentives. This is not evidence that no integrations exist. Lock-ups and withdrawals. LP NFT positions can be collected, burned, or withdrawn subject to pool mechanics; gauge NFTs can be unstaked/withdrawn.

Concentrated liquidity rewards can become temporarily stuck when price moves outside staked ranges. veVELO is separate: VELO locks can run up to four years, decay linearly, and withdraw only after expiry; permanent locks are possible. Fees, tick ranges, and unstaked-liquidity charges are governance/module-controlled; the Slipstream specification lists fee caps up to 3% and a default 10% unstaked fee, mutable up to 50%. Current DeFiLlama snapshot (September 6, 2026; aggregator, not on-chain verification): total TVL $25.08m; Ink $12.84m (51.2%), OP Mainnet $10.98m (43.8%); other chains comprise ~$1.26m (5.0%). 30-day fees are $245,366 and DeFiLlama-defined revenue $231,455; this “revenue” is principally the veVELO-voter share, not necessarily treasury cash flow.

Product-level TVL, APY history/volatility, and sustainability decomposition are Not verifiable as of September 6, 2026. Dune-vs-DeFiLlama trend comparison is Not verifiable as of September 6, 2026 because Dune MCP is unavailable. Contradiction: prior notes described only OP Mainnet and Ink; current DeFiLlama lists 10 chains. The two-chain scope therefore omits ~5% of listed TVL.

Protocol-fee activation is also Not verifiable as of September 6, 2026; a repository note marked May 2026 said Slipstream protocol-fee fields were uniformly zero, but that evidence is stale.

Assessment — Velodrome V3 (Ink, OP Mainnet)

• Product classification: Velodrome V3 is a DEX/CLMM, not a stablecoin issuer or redeemable reserve-backed product. Therefore, conventional reserve attestations and liabilities are not applicable. DeFiLlama’s V3 page does not report a V3-specific treasury balance.
• Treasury size/composition: The latest available DeFiLlama figure is for combined Velodrome, not V3 alone: $220.62, comprising $147.61 majors, $18.36 stablecoins, $54.66 others, and $0 own tokens. This is an analytics-platform aggregate, not an on-chain proof and cannot be allocated reliably between V2/V3 or between Ink and OP Mainnet.
• Known address: OP Mainnet Dromos Treasury — 0x2B642c9609f9a174393F5014e34D1fB06e92Bb14. The explorer identifies it as a Gnosis Safe proxy and labels it Velodrome’s Dromos Treasury. No Ink treasury address was independently confirmed.
• Custody/control: Custody appears to be through a Safe-style multisig proxy. Signer identities, quorum/threshold, and whether this wallet is the sole treasury controller are Not verifiable as of September 6, 2026.
• On-chain balances via Dune: Not verifiable as of September 6, 2026. Dune MCP was unavailable for this run; no on-chain balance, chain allocation, or latest-block snapshot is asserted.
• Reserve policy/attestations: Not verifiable as of September 6, 2026. No independent reserve policy or attestation was located. Protocol-owned treasury assets should not be treated as user-redemption reserves. Contradiction / change: The prior recorded DeFiLlama figure of $195.78 has changed to $220.62, but the current figure is still combined Velodrome—not V3-specific. The on-chain number cannot be established in this run. Structured fields:
• liquid_reserves_usd: null
• liabilities_usd: null

Velodrome V3 is a new iteration of the Velodrome DEX; token-related information is mostly inherited from the broader Velodrome ecosystem, but chain-specific and V3-specific data for Ink and OP Mainnet are incomplete. All on-chain details are: Not verifiable as of 2026-09-04. ### 1. Native token

• Token name / ticker: Velodrome’s native token is VELO on Optimism; Velodrome V3 appears to use the same ecosystem token rather than a new V3-specific asset.
• Contracts (OP / Ink): Exact Velodrome V3 token contract addresses on Ink and OP Mainnet are Not verifiable as of 2026-09-04.
• There is no evidence of a separate “V3 token”; absence of a V3-specific token is consistent with Velodrome’s design where VELO and veVELO drive incentives across versions. ### 2. Supply, market cap, FDV
• Total and circulating supply, market cap, and FDV for VELO as used specifically by Velodrome V3 (Ink, OP) are Not verifiable as of 2026-09-04.
• Aggregators track VELO on Optimism generally (e.g., DeFiLlama, CoinGecko), but they do not break out Velodrome V3-specific metrics; using them would conflate protocol-wide with V3-only data. ### 3. Utility, governance, and value accrual
• Utility: VELO is used for liquidity incentives and can be locked into veVELO for voting on gauge weights and directing emissions across pools.
• Governance role: veVELO holders vote on which pools receive VELO emissions and can influence protocol parameters; governance is primarily via veVELO voting, not separate governance token.
• Revenue share: Velodrome charges trading fees; a portion is distributed to veVELO voters in the form of bribes and/or protocol fees, but exact share for V3 on Ink vs OP Mainnet is Not verifiable as of 2026-09-04.
• Buybacks / burns / staking rewards: Public documentation mentions VELO emissions and veVELO rewards but does not clearly state sustained buyback or burn programs tied specifically to V3; Not verifiable as of 2026-09-04. ### 4. Emissions & unlocks
• Velodrome has an emission schedule for VELO on Optimism (decaying emissions to incentivize early liquidity), but chain- and V3-specific emission curves are Not verifiable as of 2026-09-04.
• Unlocks & vesting: Details on team/investor/treasury unlock schedules, and whether announced unlocks executed on-chain, are Not verifiable as of 2026-09-04. ### 5. Allocations & concentration
• Concrete breakdowns (team, investors, treasury, community) and top-holder / insider concentration for Velodrome V3 on Ink and OP are Not verifiable as of 2026-09-04. ### 6. Control functions & listings
• Presence of mint, blacklist, or fee-switch functions in V3 token contracts and who controls them: Not verifiable as of 2026-09-04.
• DEX liquidity depth / listings for VELO on Ink and OP Mainnet specifically via Velodrome V3 are Not verifiable as of 2026-09-04; aggregators only show total VELO liquidity on Optimism generally.

Under a Bitcoin crash below $10,000, Velodrome V3 would most likely face secondary-demand shock rather than direct BTC exposure: lower crypto risk appetite typically reduces DEX trading activity, incentives demand, and LP willingness to keep capital deployed. However, the protocol-specific impact on Ink and OP Mainnet is Not verifiable as of 2026-09-04 from the available sources, so chain-by-chain exposure, TVL concentration, and BTC-linked pool share cannot be confirmed. What can be said from the sources is limited: Velodrome V3 is an AMM/DEX on Optimism, with Slipstream concentrated-liquidity pools as part of the V3 design, and its docs emphasize that liquidity can be added/removed freely while only swaps can be paused in an emergency.

A marketwide BTC shock would therefore primarily matter through liquidity migration, fee compression, and lower volume, not through a protocol-native BTC liability. The available sources also indicate that Velodrome’s economics rely on veVELO voting, LP incentives, and active liquidity provision, which are generally sensitive to broader market stress. I cannot verify any BTC-specific pool composition, reserve exposures, or chain split for Ink versus OP Mainnet from the provided web results.

Any estimate of how much of Velodrome V3’s TVL would be affected by BTC < $10,000 would be speculative, so the correct risk statement is: directionally negative for volume and liquidity depth, but quantitatively Not verifiable as of 2026-09-04.

Velodrome V3 is not a lending protocol, so a “largest collateral depegs 20%” stress test is not directly applicable to protocol solvency in the way it would be for an overcollateralized lending market. The relevant risk is pool-level LP mark-to-market loss and swap fee/impermanent-loss dynamics, not collateral liquidation. The web results available here do not provide a verifiable chain-by-chain TVL split or pool composition for Ink vs OP Mainnet, so the protocol’s exposure to a 20% depeg is Not verifiable as of 2026-09-04.

What can be stated from the sources is that Velodrome V3 (Slipstream) is a concentrated-liquidity AMM on Optimism, with support for liquidity pools as part of the Velodrome model. That means a 20% depeg in the largest underlying asset would primarily stress the affected pool(s) by shifting swaps away from the depegged side, reducing LP value in that pair, and potentially increasing slippage if liquidity thins. A precise loss estimate requires the current pool inventory, the share of TVL in the largest collateral asset, and whether that asset is paired in stable or volatile pools on each chain.

Those inputs are absent from the provided sources, so a numeric stress result cannot be responsibly derived. If you want, I can next produce a conservative scenario framework (e.g., 10%/20%/30% depeg bands) using only the verifiable protocol design facts and explicitly marking the missing exposure data as unknown.

For Velodrome V3 on OP Mainnet and Ink, the top counterparty insolvent stress case is best modeled as a liquidity-provider / pool-asset default rather than a credit exposure: the protocol is an AMM, so the loss path is primarily through pool token value impairment and withdrawal slippage, not a balance-sheet claim against a borrower. Based on the gathered sources, there is no verifiable evidence of a protocol-level credit backstop, insurance fund, or insolvency compensation mechanism specific to Velodrome V3 as of 2026-09-04; therefore, compensation is not verifiable as of 2026-09-04. Expected loss path

• If one side of a pool becomes worthless or illiquid, LPs absorb impermanent-loss realization and direct asset devaluation when they redeem LP positions.
• Fees can partially offset losses only if the pool continues to trade; if trading collapses, fee compensation is minimal.
• Governance/emissions incentives may support participation, but they do not constitute insolvency protection. Who absorbs it
• LPs absorb the first loss through reduced pool share value.
• Traders may face worse execution and higher slippage.
• VELO holders / veVELO voters are indirectly exposed if incentives and emissions are redirected toward impaired pools, reducing the productivity of emissions. Impact path through smart contracts
• The pool contract pricing invariant reflects the insolvent token’s collapse immediately.
• LP positions minted against that pool mark down as reserves reprice.
• Fee accounting continues mechanically, but accrued fees cannot offset a near-zero reserve without external market recovery.
• Gauge/emission contracts can still distribute rewards, but they do not restore principal. Chain split
• OP Mainnet: Velodrome is live and uses the same AMM/gauge model; no chain-specific insolvency protection was verifiable from the gathered sources.
• Ink: Velodrome is also live on Ink, with the same general design; again, no verifiable chain-specific compensation layer was found. Contradiction / gap callout: DefiLlama shows TVL/fees activity for both chains, but that is an analytics snapshot, not evidence of insolvency protection or loss mutualization. The key gap is that on-chain loss absorption mechanics and any compensation policy are not verifiable from the gathered sources; the on-chain answer therefore remains: LPs bear the loss, and compensation is not verifiable as of 2026-09-04.

For committed fraud by the DAO or owners, I found no verifiable evidence that Velodrome V3’s DAO or owners executed a fraud scheme against users or treasury. Available sources instead point to front-end/DNS compromises and phishing incidents, which the protocol and independent reporting describe as external attacks, not DAO- or owner-committed fraud. The strongest protocol-side statement I found is Velodrome’s own security disclosure saying a vulnerability allowed infinite external bribe claims under specific conditions, while explicitly stating that no other protocol TVL was at risk.

That is a security issue, but it is not evidence of committed fraud by the DAO or owners. Independent reporting on the 2025 front-end compromise likewise says the underlying smart contracts remained secure and the issue was a DNS hijack of centralized domains. For governance and code-risk context, audit material shows the protocol has had identified vulnerabilities and design risks, but audits are not evidence of fraud committed by insiders.

The GitHub docs page states that since release in February on Fantom, no security incidents related to Solidly smart contracts were reported, but that is limited to the cited codebase history and does not establish any fraud claim. Assessment: I do not see evidence supporting a stress-case assumption of DAO/owner fraud. The more defensible stress scenario is external compromise/phishing or governance/code risk, not insider fraud. Not verifiable as of 2026-09-04: any allegation that Velodrome V3 DAO members or owners committed fraud, absent a regulator/court finding or directly evidenced on-chain governance abuse.

For Velodrome V3 (Slipstream) on Ink and OP Mainnet, the primary yield source negative 30d status is not verifiable as of 2026-09-04 from the available web results. The only relevant protocol source confirms Slipstream is the concentrated-liquidity contract set, and DeFiLlama shows the protocol page exists, but neither source provides a chain-split 30-day yield breakdown or a verifiable primary-yield-source metric for the two requested chains. What can be said reliably is that Velodrome V3’s public materials describe Slipstream as the concentrated-liquidity product, which implies LP yield depends on pool fees and incentives rather than a single uniformly reported protocol-wide yield stream.

However, the search results do not include an independent, chain-specific 30-day yield series for Ink or OP Mainnet, so a negative-30d primary-yield determination cannot be confirmed. Because the on-chain verification path is unavailable in this run, the stress-scenario answer is:

• Primary yield source negative 30d: Not verifiable as of 2026-09-04.
• Chain split: Not verifiable as of 2026-09-04 for Ink vs. OP Mainnet. No supported evidence in the provided results contradicts this, but no source in the set is sufficient to establish the requested metric with confidence.

Assessment — as of September 13, 2026. Governance is not proven to be fully permissionless for Velodrome V3. The published PERMISSIONS.md is expressly a Velodrome V2 document, so its 3/7 Team multisig and 5/6 EmergencyCouncil cannot be safely attributed to V3 on Ink or OP Mainnet. Contradiction/freshness finding: prior records treated V2 permissions as V3 evidence; this is not supported by the document’s scope. Proposal process. The VeloGovernor code uses veNFT voting, 2-day voting delay, 5-day voting period, 25% quorum, and an initial 1% proposal threshold; the Team can raise that threshold to 5%. A separate vetoer can veto proposals and transfer/renounce that role.

This establishes substantive team veto/configuration power, not purely symbolic governance. However, the source code describes itself as V2 governance, not V3-specific governance. Who controls what. Development and repositories are controlled operationally through the Velodrome Finance GitHub organization; its public profile shows the contracts, slipstream, and superchain-slipstream repositories, but no public organization members. The SEC records identify Perpetual Cyclist Services LLC as a software-development company supporting Velodrome and Aerodrome.

A trademark application for “VELODROME FINANCE” is owned by that LLC. Jurisdiction, registration number, directors, and enforceable frontend ToS are Not verifiable as of September 13, 2026. On-chain concentration / controls. Dune was unavailable in this run; top veVELO/VELO holders, voting concentration, V3 contract owners, upgrade authorities, multisig signers, thresholds, and timelock state are Not verifiable as of September 13, 2026. No V3-specific evidence establishes a timelock or independent signer set.

User-fund drain authority is likewise Not verifiable; do not assume V2 permissions apply to V3. Risk conclusion: DAO governance exists in the V2 architecture but is constrained by Team-controlled proposal settings and veto power; for V3, DAO control over parameters/upgrades is unproven and should be treated as non-permissionless pending contract-level verification.

Velodrome V3 appears to have an associated legal disclosure for the VELO token / Velodrome Foundation stating the foundation is an Exempted Limited Guarantee Foundation Company with a registered address in the Cayman Islands, and that Cayman Islands law and Cayman courts govern disputes arising from or in connection with the VELO tokens. However, for the V3 protocol itself, not all legal-entity details are verifiable from the available sources, so the protocol-level entity structure remains partly unverified as of 2026-09-04. No protocol-level terms of service, KYC/AML program, regulator warning, enforcement action, court case, or sanctions designation was verifiable from the available sources as of 2026-09-04.

The available disclosure is token-level and marketing-oriented in part, including a statement about providing regulated market access under MiCA, which should be treated as an unverified marketing claim unless corroborated by independent sources. On classification and risk, the presence of a Cayman foundation and Cayman governing law suggests a legal wrapper exists, but the actual operating risk for a decentralized yield protocol may still be driven by who controls upgrades, governance, admin keys, interfaces, and treasury flows; those operational facts were not verifiable in this run. Data-protection posture was also not verifiable as of 2026-09-04.

No exact GLEIF LEI record for 'Velodrome Foundation', 'Velodrome V3'. OFAC SDN screening of 'Velodrome Foundation', 'Velodrome V3': no match. SEC litigation and administrative release feeds: no mention.

Velodrome V3 does not appear to issue its own stablecoin; the protocol is a DEX/liquidity hub with VELO as its native token, while the stable assets used on the platform are external tokens such as USDC/USDT. No verifiable evidence was found of any depeg event for a Velodrome-issued stablecoin, because no such native stablecoin is evidenced here. Stablecoin depeg history for the protocol’s used stable assets is not verifiable as of 2026-09-06.

Velodrome V3 combines concentrated-liquidity pools, gauge accounting, emissions, and Superchain messaging, creating material smart-contract and cross-chain dependency risk. OP Mainnet is the root chain and Ink is a leaf chain; current TVL, exposure by chain, and live deployment-to-audited-commit equivalence are Not verifiable as of September 5, 2026 because Dune on-chain verification was unavailable.

Velodrome V3’s top strengths are: (1) liquidity-depth flywheel, because it is designed as a liquidity hub that attracts incentives, trading activity, and projects seeking bootstrapped markets; (2) capital efficiency, since Slipstream adds concentrated liquidity pools and better fee targeting for active pairs; (3) aligned incentives, because the ve(3,3) model ties governance, emissions, and LP rewards toward long-term participation rather than mercenary liquidity; (4) multi-primitive design, combining stable, volatile, and concentrated-liquidity pool types in one protocol; and (5) L2 operating advantages, with low fees and fast execution on Optimism. These strengths are described across independent reviews and analyses of Velodrome and its Slipstream upgrade.