Core concepts
Ramses X
From Governance DEX to DeFi Infrastructure
Ramses has matured beyond a single-chain, governance-heavy DEX. Ramses X describes the planned next phase: automation, fee-first deployments, and a multichain architecture that coordinates RAM supply while each chain retains its own execution and liquidity.
Less effort. More rewards.
Architecture Overview
The planned Ramses X architecture has three core components: canonical RAM supply, chain-specific execution and liquidity, and a shared fee sink.
RAM Token & OFT Connectivity
Canonical RAM on Ethereum Mainnet and its LayerZero OFT connectivity are work in progress. No production Ethereum RAM token or OFT adapter address has been published.
| Component | Planned Function |
|---|---|
| Canonical RAM | Ethereum token intended to be the source of truth for RAM supply |
| OFT Adapter | Intended to lock canonical RAM on Ethereum and coordinate cross-chain messages through LayerZero |
| RamsesOFT | Planned chain-specific representation that debits supply on the source chain and credits it on the destination chain |
| Messaging Fees | Cross-chain transfers require source-chain gas and a quoted LayerZero messaging fee |
If deployed as designed, the OFT architecture would:
- Maintain coordinated RAM supply accounting across connected chains
- Avoid independently issued RAM tokens
- Preserve chain-specific execution, liquidity pools, and governance state
OFT connectivity unifies token supply accounting; it does not unify liquidity across chains.
Chain Structure & Fee Handling
Under the planned rollout model, a new chain begins with governance inactive and fee-only or ungauged liquidity.
Phase 1: Fee-Only Mode
In this initial phase:
| Feature | Status |
|---|---|
| LP fee share | 95% of swap fees |
| Protocol / Sarcophagus share | 5% of swap fees |
| Emissions | Inactive |
| Gauges & Voting | Inactive |
The 5% protocol share can be routed to the Sarcophagus. RAM supply changes only when a caller completes a RAM-for-fee claim and the chain-specific burn or removal mechanism executes. No emissions are distributed during this phase.
Phase 2: Governance Activation
Once a deployment reaches predefined performance and consistency thresholds, governance can be enabled.
At that point:
| Feature | Status |
|---|---|
| LP fee share | 0% by default for gauged pools |
| xRAM voter fee share | 100% by default for gauged pools |
| RAM emissions | Active and directed by gauge votes |
| Voters | Earn fees plus incentives |
| Revenue stream | Backed by real activity |
An optional maker rebate of up to 1% is treasury-funded and additive. It is not deducted from the 95% LP / 5% protocol swap-fee split.
The intended sequence is demand first, incentives second.
Specific parameters including governance activation thresholds will be published alongside each chain deployment.
What This Enables
| Outcome | Benefit |
|---|---|
| Coordinated Supply | Planned Ethereum canonical RAM and OFT connections maintain shared supply accounting |
| Independent Scaling | Chains retain independent execution and liquidity while starting fee-only |
| Earned Governance | Governance can be activated after published requirements are met |
| Explicit Fee States | Fee-only pools use the 95% LP / 5% protocol split; gauged pools default to 100% for voters |
| Automation | AutoVaults remove manual voting while preserving user-controlled claims |
Ramses X is the roadmap for evolving Ramses from a governance-centric DEX into modular DeFi infrastructure.
Ramses X Rollout Status
| Chain | Ramses X Status | Governance Status |
|---|---|---|
| Ethereum | Canonical RAM and OFT adapter in development; no production address published | Not applicable |
| HyperEVM | Ramses DEX live; connection to the planned canonical OFT architecture is not deployed | Active |
| Additional Chains | Announced only when deployment details are published | Deployment-specific |
This table describes the Ramses X rollout, not every chain where a Ramses DEX deployment exists. New production token, OFT, Sarcophagus, and deployment-specific governance addresses will be published in the contract-addresses documentation when available.