> For the complete documentation index, see [llms.txt](https://docs.ethraship.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethraship.com/tokenomics/token-allocation.md).

# Token Allocation

SHIP supply is allocated across six categories designed to fund long-term execution, ecosystem growth, community incentives, and market liquidity.

<figure><img src="/files/oBnQp7iTCh1aQOQOlxpz" alt="" width="375"><figcaption></figcaption></figure>

| Category                 | Allocation (SHIP) | Share | TGE Valuation (USD) |
| ------------------------ | ----------------- | ----- | ------------------- |
| Founders (Private round) | 100,000,000       | 10%   | 5,000,000           |
| Team                     | 200,000,000       | 20%   | 10,000,000          |
| Ecosystem                | 100,000,000       | 10%   | 5,000,000           |
| Community                | 350,000,000       | 35%   | 17,500,000          |
| Treasury                 | 150,000,000       | 15%   | 7,500,000           |
| Liquidity and Reserve    | 100,000,000       | 10%   | 5,000,000           |
| Total                    | 1,000,000,000     | 100%  | 200,000,000         |

### Founders (Private round) (10%)

This allocation is designed to compensate early backers and contributors who enabled the project prior to public launch, when execution risk is highest and liquidity is lowest. It reflects the initial risk-taking phase and provides alignment with the long-term performance of the ecosystem. The vesting structure is designed so as to incentivize sustained support through the post-launch buildout.

### Team (20%)

The Team allocation is intended to attract and retain talents required to execute a multi-year roadmap spanning product, engineering, operations, compliance, and growth. The vesting schedule creates long-term alignment, and provides a structured framework for future hiring, performance-based grants, and retention packages, ensuring the project can maintain continuity across market cycles.

### Ecosystem (10%)

The Ecosystem allocation funds the development and expansion of the protocol and its surrounding product surface. Typical uses include technical development, integrations with third-party providers, partnerships, tooling and infrastructure costs, as well as ecosystem programs that increase adoption and utility over time. This bucket is also intended to support strategic initiatives that improve the robustness and reach of the ecosystem, such as audits, security services, and product distribution efforts, subject to governance boundaries and internal controls.

### Community (35%)

The Community allocation is the primary engine for user-facing incentives and participation programs. It is intended to fund staking rewards, user acquisition and community campaigns, and enable the implementation of long-term engagement mechanisms. This bucket is also designed to support community-led initiatives, ecosystem participation programs, and selective grants aligned with the project’s growth strategy.&#x20;

### Treasury (15%)

The Treasury allocation provides long-term strategic flexibility and operational resilience. It is intended to fund multi-year execution, buffer operational volatility, and support strategic opportunities that arise over time. The linear release schedule is designed to make this capital available gradually, matching the long-term nature of execution and reducing short-term supply pressure.

### Liquidity and Reserve (10%)

This allocation is intended to support secondary market functioning at launch and provide operational reserves required for orderly token trading. It is typically used for initial liquidity provisioning, liquidity management operations, and related market infrastructure requirements. Keeping this allocation unlocked at TGE enables immediate market availability, reduces early volatility driven by thin liquidity, and supports basic exchange operations.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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://docs.ethraship.com/tokenomics/token-allocation.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.