Skip to main content
Arbitrum-native ve(3,3) DEX with concentrated liquidity support. Features gauge voting, bribes, and protocol-owned liquidity mechanisms. Solidly-fork architecture.

What it offers

  • swap: Swap tokens with route-based routing specifying stable or volatile pool type

Notes

  • Solidly-fork routes contain {from, to, stable} tuples (NO factory field, unlike Velodrome/Aerodrome)
  • Two pool types: stable=true for correlated assets, stable=false for uncorrelated
  • ve(3,3) model: RAM token holders vote-lock to direct gauge emissions and receive bribes
  • Arbitrum-only deployment; competes with Camelot on Arbitrum
  • Ramses also has concentrated liquidity pools (CL) but the SDK currently exposes the V2 Solidly interface
  • LP tokens can be staked in gauges for RAM emissions
  • Input token must be ERC20-approved to the Router

Its names in a program

On Arbitrum One, Ramses is a namespace: its contracts need no import.

Deployments

ABI

RamsesRouterABI

import RamsesRouterABI from "./protocols/ramses/RamsesRouterABI.json"; Speaks for: router.
  • swapExactTokensForTokens(uint256 amountIn, uint256 amountOutMin, (address from, address to, bool stable)[] routes, address to, uint256 deadline) returns (uint256[] amounts)
  • addLiquidity(address tokenA, address tokenB, bool stable, uint256 amountADesired, uint256 amountBDesired, uint256 amountAMin, uint256 amountBMin, address to, uint256 deadline) returns (uint256 amountA, uint256 amountB, uint256 liquidity)

Next steps