# Tokenomics & Emissions

Initial distribution, supply schedule and elastic emissions for RAM token

Source: https://www.ramses.xyz/docs/tokenomics

---

## Distribution

Below is the initial distribution of **RAM**.

[Initial token distribution — interactive visualization](https://www.ramses.xyz/docs/tokenomics#distribution)

Initial RAM distribution among the Ramses community, Hyperliquid community, treasury, and protocol-owned liquidity.

| Allocation | Initial supply |
| --- | --- |
| 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** |

> **Token Types**
>
> All allocations are in xRAM except for POL.

---

## Emissions

Below is an illustrative projection of the baseline weekly emission schedule (before elastic emissions) and supply for the first 500 Epochs (~10 years). The burn scenario assumes all emitted RAM is converted to xRAM and, as with every RAM → xRAM conversion, 50% of the converted RAM is burned. Actual burns depend on how much RAM is converted.

### Emissions vs. Supply

[RAM supply and emissions — interactive visualization](https://www.ramses.xyz/docs/tokenomics#emissions-vs-supply)

Illustrative emission schedule. Gross supply approaches 883.75M RAM. Net supply approaches 616.875M only if all emitted RAM is converted to xRAM and 50% of each conversion is burned. Actual burns depend on conversions. Left axis: supply and burns; right axis: weekly emissions.

- Initial supply: 350M tokens
- The **Gross supply** dashed line shows initial supply plus emissions before burns
- Filled supply area shows net supply after subtracting burns under the illustrated conversion assumption
- The **Assumed cumulative burns** line shows cumulative burns under that same assumption

> **Emission Schedule**
>
> - Epoch 0: 7M weekly emissions
> - Epoch 1: 12.5% decrease
> - Epoch 2: 15% decrease
> - Epoch 3+: 1% decay per epoch in perpetuity without intervention

### Elastic Emissions

**Emissions can be modified by up to ±25% per epoch** depending on protocol revenue to maintain sustainable inflation. 100% of ALL emissions go to gauges—**there are no team allocations or other distributions, ensuring fully decentralized emissions.**

Emissions may be increased when **revenue is greater than or equal to emissions** for several consecutive epochs, or when near-term catalysts are expected to increase revenue.

Emissions may be decreased when **revenue remains substantially below emissions** for several consecutive epochs, or when revenue is expected to decline.

*Note: These are approximate projections and actual emission numbers may vary. This model demonstrates our commitment to sustainable, long-term supply growth.*

---

## Multichain Token Architecture

Ramses plans for RAM to exist canonically on **Ethereum Mainnet** and extend to other chains using an **OFT (Omnichain Fungible Token)** model powered by LayerZero. This architecture is a work in progress and is not yet deployed.

### Canonical RAM

| Property | Details |
| --- | --- |
| **Native Chain** | Planned for Ethereum Mainnet |
| **Bridge Technology** | Planned LayerZero OFT |
| **Cross-chain Transfers** | Planned transfers via an OFT adapter |
| **Supply Management** | Intended single canonical supply |

Once deployed, this architecture is intended to keep RAM as a **single canonical asset** with shared supply accounting across deployments. Trading liquidity will remain local to each chain.

### How OFT Works

The planned architecture will use the following components:

| Component | Function |
| --- | --- |
| **Canonical RAM** | Planned native token on Ethereum and source of truth for total supply |
| **OFT Adapter** | Will coordinate cross-chain transfers via LayerZero |
| **Lockbox** | Will hold canonical RAM on Ethereum when RAM moves to a remote chain |
| **RamsesOFT** | Planned chain-specific RAM representation backed by canonical RAM |

> **Unified Supply**
>
> Once deployed, canonical-to-remote transfers will lock RAM and mint the remote representation; remote transfers will burn the source representation before minting or unlocking the destination asset. These operations are intended to preserve one shared total supply.

[Learn more about Ramses X multichain architecture →](https://www.ramses.xyz/docs/ramses-x)