Velodrome Finance profile: Aero upgrade, legacy Slipstream pools and locked-position migration

Velodrome runs an automated market maker rather than an off-chain central limit order book. The trader submits a blockchain swap against pool liquidity, while LPs can choose how to allocate tokens into pool positions and gauges. In the legacy model, veVELO voting directed emissions and allocated fees/incentives to voters; the Aero transition changes that operating context. These are different economic positions: buying a token, providing liquidity and locking a governance asset have materially different risks.[1][2]

Velodrome V2 and legacy Slipstream use different contract designs, including pool factories and custom fee modules. In the former incentive model, staking an LP position exchanged its fee income for emissions. Those emissions have stopped. Holding or withdrawing an old position does not recreate that incentive stream; liquidity and price-range risk remain.[2][4][7]

Slipstream’s specification lists default tick-spacing combinations such as 1 basis point, 5 basis points, 30 basis points and 100 basis points, while also describing a custom fee module that can set and update swap charges. In the live app, the cost of a route therefore depends on the exact pool/chain combination and whether several pools are traversed. A liquidity provider’s fee share is a separate revenue rule, not an extra charge made by Velodrome to every trader.[4][2]

For a hypothetical direct pool that actually quotes a 0.05% fee, a 2,000 USDC input corresponds to 1 USDC nominal pool fee, *before* price impact, gas and any second hop. That arithmetic is conditional and must not be presented as the fee on all Velodrome markets. A route traversing two pools can incur two pool charges and two sources of price impact.[4]

Velodrome does not publish a general TRY or EUR bank deposit rail in the reviewed material. A trader starts with compatible tokens and a wallet connected to the correct chain. Before the swap, an ERC-20 approval may give a router authority over the token; the transaction then changes balances on-chain if it executes. A token balance on another chain is not available until bridged by a separate supported process.[3][1]

A liquidity provider sends two token sides, or an applicable single-sided workflow, to a selected pool and obtains a position. If a position is locked under the Velo Launch feature, the platform says additional liquidity may be added but price ranges or withdrawals cannot be changed before expiry. This creates a fundamentally different withdrawal timetable from a normal tradable wallet token.[5][4]

A trader controls a self-custody wallet before signing, but tokens submitted to a swap or liquidity pool interact with smart contracts and can be exposed to oracle assumptions, token transfer taxes, smart-contract vulnerabilities and MEV. The protocol describes its code as immutable in key respects, while the broader V2 system has factories and fee modules that can be added or updated. Avoid collapsing “immutable core” into “every deployed address can never change.”[2][4]

Liquidity stakes and veNFT governance locks can leave an economic position that cannot be immediately redeemed like a cash balance. Concentrated pools face range risk: their assets reallocate as the market price moves, and a liquidity provider may end up entirely on one side. The protocol does not provide bank deposit insurance or counterparty reversal of blockchain trades.[4][5]

There is no normal KYC broker account simply because the interface can connect to a wallet, and the protocol’s decentralised pool market is not a guarantee every address can legally interact in every jurisdiction. Country rules about offering crypto assets, taxes and sanctions remain relevant. No comprehensive verified customer acceptance list or institution-specific agreement was established in the reviewed sources.[1][2]

Participants also have practical access tests: the correct EVM chain, token smart contract, wallet signing and enough native gas. LP/gauge participation adds other conditions, such as position ownership or stake state. Inability to use a route may reflect contract or liquidity state, not an account being rejected by a bank.[3][4]

The first source of truth for a blockchain swap is the chain explorer’s transaction receipt and the token balance movements. If a user sees unexpected output, inspect the swap path, tolerance, block time, pool fee, gas and possible token transfer mechanisms. There is no standard off-chain exchange trade ID or central cancellation once an AMM transaction is final.[3][4]

The published documentation and interface support can help with navigation, but neither implies authority to reverse a permissionless contract. Preserve router address, token contracts, spender approvals, chain ID, transaction hash and wallet used. A liquidity gauge dispute additionally requires the position NFT, lock/gauge ID and reward-claim transaction history.[2][5]

Velodrome’s published materials centre on contract design, token governance and user interactions. No regulator-issued exchange authorisation, bank deposit permission or precisely identified general-purpose customer-contract company has been verified. It would be improper to translate a GitHub audit, a launch announcement or a DAO vote into a statutory licence.[2][4]

The exchange directory therefore shows no positive legal permission row. Transaction responsibility is allocated between wallet holder, connected interface, deployed contracts and any bridging or liquidity-provider services, depending on the route. A retail user cannot assume a single ombudsman has jurisdiction over every component.[1]

The official migration guide supersedes the older coming-soon banner. It says the upgrade opened with Aero on 22 October at 00:00 UTC. This is a position migration, not a centralised exchange account transfer. The guide distinguishes liquid VELO, locked veVELO and liquidity deposits; this profile does not assume that one path automatically migrates all three.[6]

Operator

Velodrome decentralised AMM protocol; contracting front-end entity not independently verified

Exchange model

Decentralised

Service scope

Legacy Velodrome pools and locked positions after Aero launched on 22 October 2026. Legacy gauges and emissions stopped; selected chains retain trading without the token economy. veVELO upgrades move from OP Mainnet to Base.

Client types

Retail clients

Pricing publication

Public and quoted pricing

Other names

Velodrome; VELO MetaDEX

Pricing scope

Protocol, pool, bridge and gas costs vary per route; this is not a fixed order-book commission. Always check minimum received and transaction approvals.

Funding scope

No general cash account; requires supported tokens on the appropriate EVM chain plus network gas. Cross-chain transfers are distinct workflows.

Custody and asset handling

Wallet swaps and LP positions interact with AMM contracts. Legacy gauge deposits retain their contract-specific exit requirements, but no longer earn VELO emissions. There is no conventional exchange deposit account.

Client eligibility

Wallet/chain access with token and route availability; permissionless smart contracts do not prove legality or safety for every person and location.

Support

Protocol documentation, official interface support and blockchain traces; no bank-like reversal service or guaranteed regulator-supervised recovery.

Authorisation and registration scope

No definitive licenced exchange company/number verified; governance, audits and token contracts are not a financial-services licence.

Exchange metadata checked 29 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7

For a swap, compare the net destination amount after pool charges, gas and price impact. For a liquidity position, identify its contract generation and range exposure. Legacy gauges no longer pay emissions; migration to Aero introduces a separate reward and fee model. A single platform-wide trading percentage cannot describe all of these positions.[4][7]

The upgrade hub says the old ALM service has wound down and no longer rebalances automatically. It directs withdrawal of Lisk deposits before 31 October 2026. These are position-specific actions; they do not create a general expiry date for every VELO token upgrade.[7]