> For the complete documentation index, see [llms.txt](https://bana.gitbook.io/bana-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bana.gitbook.io/bana-docs/en/sale-listing/sale-schedule.md).

# PRICING BY PHASE

#### Phased Valuation & Sale Roadmap

BANA's sale price is linked to the project's real-world asset acquisition stages, moving upward across four phases to provide early participants with the most powerful opportunities for asset growth.

#### **1. Pricing Tiers by Phase**

| **Phase**          | **Price** | **Target**         | **Benefits**                               |
| ------------------ | --------- | ------------------ | ------------------------------------------ |
| Phase 1 (Seed)     | $0.08     | Strategic Partners | Lowest entry price and profit maximization |
| Phase 2 (Private)  | $0.10     | Community Builders | Securing stable initial volume             |
| Phase 3 (Pre-sale) | $0.20     | 1st Public Sale    | Market participation opportunity           |
| Phase 4 (Public)   | $0.30     | Final Public Sale  | Final entry opportunity before listing     |

{% hint style="warning" %}
**Target Listing Price: $0.50**

**Participation in Phase 1 is designed to offer a potential value appreciation of approximately 625% by the time of listing.**
{% endhint %}

#### **2. Asset Protection & Circulation Management**

* 80:20 Split Principle: Reward profits are separated into CASH (liquidity) and ASSET (reinvestment) to prevent sudden market sell pressure.
* Weekday Payout System: Rewards are distributed from Monday to Friday based on actual real-world business operating profits to ensure the permanence of the ecosystem.


---

# 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, and the optional `goal` query parameter:

```
GET https://bana.gitbook.io/bana-docs/en/sale-listing/sale-schedule.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.