Skip to main content

​
Protocol, Interface, Community

It helps to distinguish the different things people call “Ramses”:
  • Ramses Protocol: The on-chain contracts for concentrated and discrete liquidity, emissions, fee routing, and governance.
  • Ramses Interface: The web application used to interact with those contracts.

​
What is Ramses?

Ramses combines two pool models with a shared fee and governance stack:
  1. Concentrated liquidity with period-based accounting for CL positions
  2. DLMM with fixed-price bins, per-bin LP shares, and on-chain variable fees
  3. Non-custodial gauge and optional rewarder systems
  4. xRAM governance through XRam, VoteModule, and Voter
  5. Protocol-fee routing through pool-specific collectors and FeeDistributor
  6. Liquid governance exposure through R33 / hyperRAM

​
Protocol Architecture

​
Concentrated-liquidity core

  • RamsesV3Factory: Creates and configures CL pools
  • RamsesV3Pool: Handles swaps, liquidity, oracle state, and protocol fee accrual
  • RamsesV3PositionManager: Manages NFT positions and reward-claim integrations

​
DLMM core

  • DLMMFactory: Creates pools and manages bin-step presets, fees, quote assets, and hooks
  • DLMMPool / DLMMToken: Handles swaps, bin reserves, oracle state, and per-bin LP shares
  • DLMMRouter / DLMMQuoter: User transactions and route discovery
  • DLMMFeeCollector: Pulls the configured protocol share from DLMM pools
  • DLMMRewarder: Optional RAM emission hook for eligible bins

​
Emissions and fee routing

  • GaugeV3: Reward distribution for active CL markets
  • ClGaugeFactory: Gauge deployment and implementation management
  • FeeCollector: Pulls protocol fees from CL pools and routes them onward
  • FeeDistributor: Stores per-period voter rewards for a single market
At the Robinhood snapshot at block 22,674,244, DLMM is fee-only, its factory is not connected to Voter, and its optional rewarder path is not live.

​
Governance and token stack

  • XRam: Transfer-restricted governance token created from RAM
  • VoteModule: Staked xRAM balances, delegation, admin permissions, cooldowns
  • Voter: Vote accounting, gauge registry, emissions routing, reward claims
  • Minter: Weekly emission controller with capped total supply
  • AccessHub: Role, multisig, and timelock control plane
  • R33 / hyperRAM: ERC4626 liquid governance wrapper

​
Weekly Period Model

The contracts use:
That weekly clock drives:
  • When votes become active
  • When fee and incentive rewards are queued
  • When emissions roll forward
  • When cooldown and unlock windows apply
See Token Contracts & Emissions for the contract-level flow. See DLMM & Liquidity Bins for the discrete-liquidity model.