Utility & Value Accrual
This section describes how the WANNA token is utilized within the protocol and how long-term value can accrue to holders as the ecosystem grows.
Core Design Philosophy WANNA is not a direct claim on reserves nor a revenue-sharing security. Instead, its value emerges from:
its role in governance and coordination
a structured link between protocol net revenue and Buy-back & Burn (B&B) under clear guardrails
1. Token Utility
The WANNA token has three core utility dimensions.
1.1 Governance & Parameter Control
WANNA is the primary asset for governing the infrastructure. Holders (directly or via delegation) influence:
Risk Parameters: Target collateral ratios (CR), safety margins (σ), liquidity thresholds (LCR).
Economic Parameters: Revenue allocation ratios (Buffers vs. Incentives vs. Buy-back & Burn).
Configuration: Whitelisting collateral assets, RWA partners, and oracle/bridge providers.
Network Policies: Fee schedules and upgrade paths for the G-Series Mainnet (Phase 5).
1.2 Staking & Alignment (Conceptual)
To mitigate short-term speculation, governance weight is tied to commitment:
Staked / Locked WANNA: Higher voting weight for longer lock durations (e.g., ve-style model).
Slashing Risks: Certain governance roles (e.g., guardians) may require staking, with penalties for clearly malicious actions.
Principle: Greater commitment → greater influence.
1.3 Ecosystem Incentives
WANNA serves as a strategic incentive layer:
Integrators: Rewards for wallets, exchanges, and partners achieving usage or volume milestones.
Liquidity: Targeted incentives for critical G-Series / GUSD pools and markets.
Goal: Amplify durable network effects, not just temporary yield farming.
2. Protocol Revenue: Where Value Comes From
The ecosystem generates Net Protocol Revenue from multiple layers:
Reserve & Yield Layer (Phase 2): Yield from L2 reserves (e.g., institutional staking, short-term RWAs).
Brokerage Layer (Phase 3): Fees and spreads from routing flows into RWA and lending venues.
Trading Layer (Phase 4): Revenue from derivatives integrations and smart routing.
Payments Layer (Phase 5): Transaction fees and FX settlement flows on the G-Series Mainnet.
3. Revenue Allocation & Value Accrual Framework
Revenue is not distributed directly to holders. Instead, it flows through a prioritized allocation waterfall:
Risk & Buffer Reserves (Priority #1) Refilling FX buffers and safety cushions to ensure peg stability and solvency. Value is built on safety first.
Operational & Ecosystem Growth Funding development, audits, security, and ecosystem grants.
WANNA Buy-back & Burn (Value Accrual) A governance-defined portion of the Net Surplus is used to purchase WANNA on the open market and burn it.
4. Buy-back & Burn Mechanics
The Buy-back & Burn (B&B) mechanism is the primary engine translating protocol growth into token value.
Mechanism: The protocol accumulates surplus (e.g., GUSD / USDC) → buys WANNA on open markets → sends it to a verifiable burn address.
Effect: Reduces circulating supply over time, linking token scarcity to real protocol usage.
Constraints: Executed under transparent schedules and conditions to avoid market destabilization and to preserve safety buffers when needed.
5. Value Accrual Scenario (Simplified)
Phase 2: Modest reserve yield generates a small surplus → gradual supply reduction via B&B.
Phase 3–4: RWA, lending, and derivatives volume scales up → revenue grows faster than any new issuance → B&B volume increases.
Phase 5: Recurring payment revenues from the G-Series Mainnet → sustained deflationary pressure over time.
Long term: Token value reflects both:
the scale of the underlying infrastructure
the cumulative reduction in circulating supply
6. Safeguards & Disclaimers
To maintain safety and regulatory compliance:
No Direct Claim: WANNA holders have no claim on GUSD or G-Series reserves.
No Guaranteed Yield: Buy-backs depend on protocol surplus; no specific price, yield, or return is promised.
Safety First: In stress scenarios, governance may suspend or reduce B&B to prioritize system solvency and rebuilding buffers.
Last updated