White PaperToken Allocation, Staking Lockups, and Long-Term Accountability
- White Paper
- 01The Emergence of Global Investment Intelligence Infrastructure
- 02The Evolution of Eonvera Capital, EONVERA ADI, and EADI Token
- 03Why EADI Token Is Needed and the Principles of Protocol Design
- 04EADI Token Issuance Parameters
- 05Mapping EADI Token Rights to ADI's Six Core Modules
- 06EADI Token Staking and Intelligence Access Tiers
- 07Four Individual Service Tiers and EADI Token Use Cases
- 08Three Institutional Service Tiers and EADI Token Use Cases
- 09Compute Scheduling, Priority, and Fair Resource Allocation
- 10Quantum Research Eligibility and Computing Resource Management
- 11Wallet Linking, On-Chain Verification, and Account Entitlement Mapping
- 12Token Allocation, Staking Lockups, and Long-Term Accountability
- 13Incentives, System Contributions, and Long-Term Participation
- 14Ecosystem Governance, Proposals, and Parameter Changes
- 15Protocol Security, Abuse Prevention, and System Safeguards
- 16Leadership and Long-Term Responsibilities
- 17Development Roadmap and Global Commercialization
- 18Long-Term Objectives and the Investment Intelligence Ecosystem
Token Allocation, Staking Lockups, and Long-Term Accountability
- Allocation
- Staking Lockups
- Long-Term Accountability
- 25% · Public Circulation and Foundational Protocol Liquidity
- 30% · Ecosystem Development and Usage Incentives
- 15% · Long-Term Governance and Protocol Reserves
- 20% · Company and Core Management Team (Long-Term Vesting)
- 10% · Strategic Partnerships and Research Nodes
12.1 Principles of Long-Term Token Allocation
The total supply of EADI Token is fixed at 100,000,000 tokens. Allocation is organized around public circulation, ecosystem development, long-term governance, core-team accountability, and technical partnerships. The purpose is to sustain the ecosystem over time, not to stimulate short-term trading through concentrated token releases.
The publicly circulating allocation enables participants to obtain access rights. Ecosystem incentives support genuine usage, research feedback, and investor education. Governance reserves support security maintenance and protocol upgrades. Company and team allocations reflect long-term development responsibilities, while research and partnership allocations support infrastructure and the developer ecosystem. Each allocation category should have a distinct purpose, management authority, and auditable release conditions.
12.2 Overall Allocation
25%
Public Circulation and Foundational Protocol Liquidity
To provide a neutral, accessible source of tokens for staking, governance participation, and system access. This allocation is the primary source of exchange and on-chain liquidity.
30%
Ecosystem Development and Usage Incentives
To reward genuine system use, testing contributions, model feedback, and sustained participation. Tokens are released progressively under established rules rather than in concentrated distributions.
15%
Long-Term Governance and Protocol Reserves
To support system security contingencies, governance upgrades, and responses to extraordinary events. These reserves may be deployed only through governance procedures.
20%
Company and Core Management Team (Long-Term Vesting)
To align long-term responsibility for the system. This allocation is subject to a multiyear lockup and linear vesting arrangement and is excluded from short-term circulation.
10%
Strategic Partnerships and Research Nodes
To support system-level collaboration with research institutions, infrastructure nodes, and long-term partners.
12.3 Allocation Design Principles
- No large-scale, one-time release of tokens;
- All non-circulating allocations are subject to time-based and conditional restrictions;
- The allocation structure prioritizes governance and system security over market stimulation.
12.4 Staking Lockups and Alignment of Responsibilities
User staking and team-token vesting are separate mechanisms. Users stake to obtain service tiers, computing priority, and governance eligibility; team-token vesting aligns management responsibilities with the project's long-term development. These mechanisms must not be conflated, and team holdings must not automatically confer unrestricted priority over computing resources used by clients.
