Coin listings
All coin listings| # | Coins | | |||
|---|---|---|---|---|---|
| | |||||
| | 1 | | $ | Swap | |
| | 2 | | $ | Swap | |
| | 3 | | $ | Swap | |
| | 4 | | $ | Swap | |
| | 5 | | $ | Swap | |
| All coins | |||||
New coin listings
| Coins | | | ||
|---|---|---|---|---|
| | | $ | 3 months ago | Swap |
| | | $ | 3 months ago | Swap |
| | | $ | 3 months ago | Swap |
| | | $ | 3 months ago | Swap |
| | | $ | 3 months ago | Swap |
| All new coins | ||||
Markets
| Markets | Price | ||
|---|---|---|---|
| | $ | Swap | |
| | $ | Swap | |
| | $ | Swap | |
| | $ | Swap | |
| All markets | |||
About Retro
Retro is a decentralized exchange (DEX) on the Polygon network that uses a concentrated-liquidity AMM and ve(3,3) tokenomics. It’s positioned as a liquidity-incentive and revenue solution for protocols on Polygon, and as a yield-oriented DEX for users. The team describes Retro as a “friendly fork” of Thena, inheriting the vote-escrow model while adding its own tweaks.
Key Features
- Concentrated-liquidity AMM on Polygon: Optimized pools intended to improve pricing and capital efficiency.
- ve(3,3) governance & incentives: Lock RETRO to get veRETRO, vote on pools, and earn trading-fee distributions and bribe rewards.
- Integrations & emissions: Support for “auto-bribes” to voters and emissions distribution via external partners.
- ALM marketplace: LPs can choose among automated liquidity managers to optimize position management.
- Security posture: Public docs reference audits and list multisig/timelock details.
Key Takeaways
- Purpose-built for Polygon: Aims to help protocols bootstrap/retain liquidity while rewarding voters and LPs.
- Yield-mechanics heavy: Best suited to users comfortable with lock-vote-earn flows (veRETRO).
- Mind venue size: Check pool depth and slippage on specific pairs before large trades.
- Audits help but don’t remove risk: Standard DeFi cautions still apply.
Final Thoughts
If you’re on Polygon and want to play the ve(3,3) model with concentrated-liquidity pools, Retro targets that niche well. For routine swaps it can be fine on supported pairs; for larger moves, compare routes and slippage.