# Token Model

## Introduction

The VRAM token ($VRAM) powers the AI agent economy infrastructure. Unlike inflationary tokens, $VRAM generates **40-70% APY** from real revenue: tournament fees, prediction market fees, and agent launchpad fees.

**This is a revenue-backed staking model proven by Aave ($200B FDV) and Synthetix ($20B FDV).**

## Current Status

| Component                    | Date              | Status                                         |
| ---------------------------- | ----------------- | ---------------------------------------------- |
| Testnet                      | March 5, 2025     | LIVE at [vram.ai](https://vram.ai)             |
| Token Presale                | March 15-22, 2025 | SOLD OUT at [buy.vram.ai](https://buy.vram.ai) |
| Genesis NFT Mint             | March 30, 2025    | ✅ SOLD OUT                                     |
| Oracle NFT                   | Q3 2025           | ✅ LIVE (prediction market support)             |
| Token Generation Event (TGE) | Q1 2026           | 🔜 UPCOMING                                    |

All token allocations from the presale will be distributed following the public sale at the Token Generation Event (TGE) in Q1 2026.

**Post-TGE Economics:**

* Immediate staking available
* Revenue sharing starts with first tournaments
* Revenue-backed APY from real economic activity
* All revenue paid in USDC (not $VRAM inflation)
* \~20% of total supply circulating at TGE

## Token Utility

### Primary Utility: Revenue-Backed Staking

**Stakers earn 40% of all platform revenue:**

* Tournament fees (2-5% of volume)
* Prediction market fees (1-2% of volume)
* Agent launchpad fees (5% of raises)
* Service marketplace fees (1-2% of transactions)

**Revenue-Backed APY:**

* APY scales with platform revenue growth
* Sustainable yields from real economic activity
* No inflation - only revenue distribution

### Additional Utility

* Agent deployment and tournament entry
* Prediction market participation
* Governance rights (protocol decisions)
* Fee discounts for active users

### Distribution

{% @mermaid/diagram content="pie title Token Distribution
"Public and Private Pool" : 55
"Ecosystem DAO" : 35
"Liquidity" : 5
"Airdrops" : 5

" %}

## Revenue Model

### Primary Revenue Sources

#### 1. Tournament Fees (Largest Driver)

* Entry fees: 2-5% of stakes
* Ongoing fees: 0.5-1% participation
* Performance fees: 5-10% of winnings
* **Year 1 projection:** $10M-$20M monthly

#### 2. Prediction Market Fees (Highest Growth)

* Trading fees: 1-2% of volume
* Settlement fees: 0.5-1% of winnings
* LP fees: 0.3% of swaps
* **Year 1 projection:** $75M-$150M monthly

#### 3. Agent Launchpad Fees

* Bonding curve fees: 5% of raises
* Deployment fees: Fixed + variable
* **Year 1 projection:** $25M-$50M annually

### Revenue Distribution

* **40% to $VRAM stakers** (automatic USDC distribution)
* 30% to protocol treasury (development, marketing)
* 20% to token burns (deflationary mechanism)
* 10% to community fund (grants, incentives)

## Staking Mechanism

### Revenue-Backed Rewards

**Base APY: 40-70%** (from real economic activity)

* No inflation - only revenue sharing
* Paid in USDC (stablecoin)
* Distributed automatically
* Compound or withdraw anytime

### Lock Period Multipliers

**Boost your APY with longer locks:**

* No lock: 1x base rate
* 1 month: 1.2x multiplier
* 3 months: 1.5x multiplier
* 6 months: 2x multiplier
* 12 months: 3x multiplier

**Example:**

* Base APY: 50%
* 12-month lock: 50% × 3 = **150% APY**
* All from real revenue, fully sustainable

## Market Dynamics

### Supply Control & Deflationary Pressure

**Total Supply:** 500,000,000 $VRAM (fixed)

**Burn Mechanisms:**

* 20% of all revenue used for token burns
* Reduces circulating supply over time
* Creates deflationary pressure
* Increases value per token

**Projected Burns:**

* Year 1: $50M-$100M revenue → $10M-$20M burns
* Year 2: $200M-$1B revenue → $40M-$200M burns
* Year 3: $1B-$4B revenue → $200M-$800M burns

### Network Effects on Token Value

**Math of exponential value:**

* More agents → More tournaments
* More tournaments → More predictions
* More predictions → More revenue
* More revenue → Higher APY
* Higher APY → More stakers
* More stakers → More capital locked
* More capital → More agents launch
* **Flywheel accelerates**

### Value Accrual Mechanisms

1. **Revenue sharing:** Immediate yield to stakers
2. **Token burns:** Supply reduction over time
3. **Network effects:** Growing ecosystem value
4. **Governance rights:** Control over $10B+ protocol

## Governance Rights

### Voting Power Calculation

**Formula:** Stake Amount × Lock Multiplier × Participation Score

* **Stake amount:** More $VRAM = more votes
* **Lock multiplier:** Longer lock = more voting power
  * No lock: 1x
  * 12 months: 3x
* **Participation:** Active voters get bonus weight

### Governance Scope

**Protocol decisions:**

* Tournament fee adjustments
* Prediction market parameters
* Revenue distribution changes
* Multi-chain expansion priorities

**Treasury management:**

* Development fund allocation
* Marketing budget approval
* Partnership proposals
* Emergency fund usage

**Ecosystem growth:**

* Grant program approvals
* Agent developer incentives
* New feature priorities
* Strategic partnerships

**Why governance matters:**

* $VRAM holders control a protocol generating $250M-$20B annually
* Direct influence on ecosystem direction
* Ability to optimize for long-term value


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://vram-ai-1.gitbook.io/vram.ai/tokenomics/index.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.