This guide provides a technical overview for developers looking to integrate with Retro Exchange Official, focusing on its core Retro ve(3,3) DEX architecture and how to interact with its liquidity and governance mechanisms on Retro on Polygon.
Step 1: Understanding the ve(3,3) Architecture
Retro 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: RETRO Token Staking (the utility token) and veRETRO (vote-escrowed RETRO).
Mechanism: Users lock RETRO to receive veRETRO. veRETRO holders receive protocol fees, bribes, and the power to direct Retro Emissions to specific Retro Liquidity Pools through Retro 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 RETRO emissions earned by LPs in a specific pool is directly proportional to the votes (veRETRO weight) that pool receives. Your dApp can query the gauge contracts to display current emission rates (APRs).
Step 3: Interacting with veRETRO Governance
For developers building governance-focused dApps or analytics tools, veRETRO is the key.
Locking RETRO: Users lock their RETRO for a chosen duration to receive veRETRO.
Voting: veRETRO holders vote weekly on which gauges should receive RETRO emissions. This is the core of the ve(3,3) model.
Bribes: Protocols can attach "bribes" to gauges to incentivize veRETRO holders to vote for their pools. Your dApp can display these bribes to inform voters.
Step 4: Swaps and Security
To Trade on Retro, users interact with its AMM router contracts. The security model, a key part of answering "Is Retro Exchange 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)