Documentation Index
Fetch the complete documentation index at: https://tech.ramses.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Protocol, Interface, Community
It helps to distinguish the different things people call “Ramses”:- Ramses Protocol: The on-chain contracts for concentrated liquidity, emissions, fee routing, and governance.
- Ramses Interface: The web application used to interact with those contracts.
What is Ramses?
Ramses extends Uniswap V3-style concentrated liquidity with a weekly governance and rewards system built around:- Period-based accounting for CL positions
- Non-custodial gauge rewards
- xRAM governance through
XRam,VoteModule, andVoter - Protocol-fee routing through
FeeCollectorandFeeDistributor - 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
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
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:- When votes become active
- When fee and incentive rewards are queued
- When emissions roll forward
- When cooldown and unlock windows apply
