Design Overview
Ramses tokenomics combine flexible participation with supply discipline. Converting RAM to xRAM burns half of the RAM input, xRAM holders direct weekly emissions without a fixed-duration lock, and value retained by MEV backruns can fund RAM buybacks and burns. Protocol fees can also create r33 burial opportunities.
These mechanisms do not guarantee net deflation or a market-price outcome. RAM issuance and every source of supply reduction must be evaluated together.
Distribution
Below is the initial distribution of RAM.
- Ramses community (veRAM)
- 45%
- Hyperliquid community
- 30%
- Treasury
- 23%
- Protocol-owned liquidity
- 2%
Breakdown
The Hyperliquid Community (30%) allocation contains the NFT Airdrop (20%) and Incentives (10%). Within Incentives, RXP receives 3% and Liquidity and Vote Incentives receive 7%. All percentages below are shares of the initial supply.
| Category | % of Initial Supply | Amount |
|---|---|---|
| Ramses Community (veRAM) | 45% | 157,500,000 |
| Hyperliquid Community | 30% | 105,000,000 |
| NFT Airdrop — Hypurr, Hypios, Catbal NFTs, and PiP | 20% | 70,000,000 |
| Incentives | 10% | 35,000,000 |
| RXP | 3% | 10,500,000 |
| Liquidity and Vote Incentives | 7% | 24,500,000 |
| Treasury | 23% | 80,500,000 |
| POL | 2% | 7,000,000 |
| Initial Supply | -- | 350,000,000 |
Emissions
RAM's current supply grows when new RAM is minted and falls when RAM is burned. The live supply composition shows where existing RAM sits, alongside this epoch's emissions and annualized gross inflation. Gross inflation measures issuance before burns; it is not a forecast of net supply growth.
The 1 billion RAM cap limits the total RAM that can exist at one time. It is a safety ceiling, not an emission target or a limit on lifetime cumulative issuance. Burns reduce outstanding supply and restore room below the ceiling, so cumulative issuance can exceed the cap over time without outstanding supply exceeding it.
Each Sarcophagus burial permanently sends r33 to the dead address. Because r33 is liquid-staked xRAM, the burial also retires its liquid claim on the underlying xRAM and RAM backing. That backing remains permanently locked inside r33 and remains part of RAM total supply, so the chart does not treat the same value as a direct RAM-token burn.
The projection below starts from live RAM total supply, the minter's next scheduled emissions, and its current weekly multiplier. It defaults to five years from now and holds the multiplier constant. A 0% weekly emission change means the same amount is emitted each week; a negative percentage means emissions decline each week.
Emissions vs. Supply
- Projected supply starts with existing RAM and adds each future weekly emission, subtracting any assumed burns.
- No future burns shows the supply path without additional burns. This is the default assumption.
- Recent burn pace holds the average RAM burned over the last eight completed epochs constant. It excludes the current partial epoch and the initial supply reconciliation; when fewer completed epochs are available, the chart states how many it uses. The dashed line compares supply without future burns.
- Weekly emissions starts with the minter's exact next-epoch amount and follows the current multiplier thereafter. The supply ceiling is enforced during each simulated mint; burns are applied at each epoch's end.
Elastic Emissions
New weekly RAM emissions are sent to the voter and gauge system; there is no recurring team-emissions allocation. An authorized protocol role can update the emissions multiplier within the contract's maximum allowed change.
The current multiplier and next scheduled emission are available on-chain. The chart projects those settings forward without predicting future authorized updates or guaranteeing a supply outcome.
Multichain Token Architecture
Ramses X is live across HyperEVM, Base, Polygon, and Robinhood Chain. HyperEVM is the current home of RAM and the canonical side of the live LayerZero OFT network. Ethereum Mainnet is configured as an eventual canonical hub, but its route is currently inactive.
RAM and r33 use shared supply accounting across active OFT routes, while execution, liquidity, and governance remain local to each chain. Moving the canonical hub to Ethereum is not required for the current network.