# Distribution Plan

JuChain's token distribution is designed to balance immediate utility with long-term sustainability. The distribution plan reflects the project's commitment to building a robust and widely-used blockchain ecosystem.

## High-Level Token Allocation

The initial distribution of JU tokens is structured as follows:

| Category                    | Allocation |
| --------------------------- | ---------- |
| Computing power contributor | 97%        |
| Initial Offering            | 3%         |

This distribution structure emphasizes:

1. **Community-Driven Growth**: The vast majority of tokens (97%) are allocated to Computing power contributor, ensuring wide distribution and community participation over time.
2. **Minimal Pre-Sale**: Only a small portion (3%) is allocated to early investors.
3. **Earned Distribution**: Most tokens enter circulation through active participation in network security and operations, rather than through pre-sale allocations.
4. **Long-Term Alignment**: The gradual release of tokens through computing power aligns token distribution with network growth and usage.

## Distribution Rules

This distribution approach is strategically designed to:

* Prevent excessive token concentration in few hands
* Ensure fair opportunity for all participants to acquire JU tokens
* Support gradual, organic price discovery
* Align token distribution with actual network participation and growth
* Create sustainable token economics that can support JuChain's long-term vision as a chain traffic hub


---

# 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://juchain.gitbook.io/juchain-docs/tokenomics/distribution-plan.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.