Token System
Token System: How Value Flows Through Benchmark X
Benchmark X does not use a single token to solve every problem.
Instead, it separates responsibilities into three distinct token roles, each designed for a specific function inside the system.
This separation is intentional. It prevents confusion, reduces incentive conflicts, and keeps the system honest.
Why Three Tokens Instead of One
In many protocols, one token is expected to be:
a utility token
a governance token
a reputation signal
a reward token
This usually results in:
unclear value capture
speculation dominating usage
incentives breaking over time
Benchmark X avoids this by decoupling function from speculation.
Each token answers one clear question.
T1 — Compute & Access Token
T1 exists to pay for work done by the system.
If you consume resources, you use T1.
T1 is required for:
Running Battle Rooms
Executing benchmark sessions
Accessing advanced performance data
Exporting reports
Using developer and enterprise APIs
Creating multi-market or long-horizon evaluations
Think of T1 as:
fuel for computation and measurement
It is not a governance token. It is not a reputation signal.
It represents actual system usage.
T2 — Reputation Staking Token
T2 exists to put skin in the game.
If a strategy wants visibility, credibility, or influence, it must stake T2.
T2 is required for:
Entering public Battle Rooms
Appearing on leaderboards
Participating in high-tier evaluations
Unlocking advanced benchmark exposure
T2 can be:
Increased through consistent performance
Slashed for violations or poor behavior
Lost through inactivity or decay
Think of T2 as:
collateralized trust
It does not improve execution. It does not boost scores.
It only determines how seriously the system treats you.
T3 — Revenue Sharing Token
T3 exists to distribute real economic output.
When the system generates revenue, T3 determines who gets paid.
T3 holders receive rewards sourced from:
Battle Room fees
Marketplace transactions
Compute credit usage
Data subscriptions
Enterprise integrations
On-demand evaluation fees
Rewards are distributed to:
High-performing strategy creators
Reputation stakers
The protocol treasury
Think of T3 as:
a claim on system productivity
It reflects how much value the ecosystem is generating — not promises of future utility.
How the Tokens Work Together
The three-token system forms a clean loop:
T1 is spent to run evaluations
Strategies perform in real markets
Performance updates BX Score
BX Score affects T2 reputation
System usage generates revenue
Revenue flows to T3 holders
Each token has a clear job. No token is overloaded.
What This Design Prevents
This structure explicitly avoids:
Reputation being tradable without accountability
Rewards being farmed without performance
Utility being locked behind speculation
Governance decisions being driven by hype alone
It also ensures that:
Bad strategies cannot hide
Good strategies compound advantage slowly
Economic rewards reflect actual contribution
A Simple Mental Model
T1 → “I want to use the system”
T2 → “I stand behind my strategy”
T3 → “I benefit when the system works”
If you remove any one of them, the system becomes weaker.
Why This Matters Long-Term
Benchmark X is designed to run for years, not hype cycles.
Separating compute, trust, and revenue allows:
Sustainable pricing
Clear incentive alignment
Governance without distortion
Performance-driven growth
This is what allows Benchmark X to act as infrastructure, not a short-term product.
Last updated