This guide provides a technical overview for developers looking to integrate with Velodrome Finance Official, focusing on its core Velodrome ve(3,3) DEX architecture and how to interact with its liquidity and governance mechanisms on Velodrome on Optimism.
Step 1: Understanding the ve(3,3) Architecture
Velodrome is a powerful DEX built on the "ve(3,3)" model, a game-theoretic design for incentivizing liquidity.
Tokenomics: It uses a dual-token system: VELO Token Staking (the utility token) and veVELO (vote-escrowed VELO).
Mechanism: Users lock VELO to receive veVELO. veVELO holders receive protocol fees, bribes, and the power to direct Velodrome Emissions to specific Velodrome Liquidity Pools through Velodrome Gauge Voting.
Step 2: Providing Liquidity and Earning Emissions
Developers can build interfaces for users to become liquidity providers (LPs).
Deposit: Users deposit an equivalent value of two tokens into a chosen pool.
Receive LP Tokens: They receive LP tokens, which must then be staked in the corresponding "Gauge" contract.
Gauge Rewards: The amount of VELO emissions earned by LPs in a specific pool is directly proportional to the votes (veVELO weight) that pool receives. Your dApp can query the gauge contracts to display current emission rates (APRs).
Step 3: Interacting with veVELO Governance
For developers building governance-focused dApps or analytics tools, veVELO is the key.
Locking VELO: Users lock their VELO for a chosen duration to receive veVELO.
Voting: veVELO holders vote weekly on which gauges should receive VELO emissions. This is the core of the ve(3,3) model, allowing the community to direct liquidity incentives.
Bribes: Protocols can attach "bribes" to gauges to incentivize veVELO holders to vote for their pools. Your dApp can display these bribes to inform voters.
Step 4: Swaps and Security
To Trade on Velodrome, users interact with its AMM router contracts. The security model, a key part of answering "Is Velodrome Safe?", relies on its audited codebase and the transparent, on-chain nature of the ve(3,3) system.
For all smart contract ABIs, gauge addresses, and SDK documentation, refer to the Full Official Documentation.
Top comments (0)