> 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/solution/three-layer-architecture.md).

# System Detailed Logic

## 3-Layer Architecture

BANA has adopted a **3-Layer structure (CASH, COIN, POWER)** with subdivided roles to maximize system scalability and security. This is a "Fault-tolerant" architecture designed to ensure that the entire system does not collapse under any shock.

***

#### Detailed Mechanism by Layer

**Layer 1. CASH (The Liquidity Layer)**

> "A liquidity layer that guarantees the stability of returns"

* **Role**: Responsible for the settlement and payment of actual generated revenue.
* **Function**: Manages user returns by pegging them 1:1 with the value of stablecoins such as USDT.
* **Purpose**: Safely preserves the user's actual profit even in situations of rapid token price volatility and maintains a liquidity pool that can be cashed out at any time.

**Layer 2. COIN (The Growth Layer)**

> "A growth layer that represents the value of the ecosystem"

* **Role**: Manages the value appreciation and deflation of the BANA token.
* **Function**: Execution of the appreciation in real-world asset value and the buy-back/burn policy occurs in this layer.
* **Mechanism**: A core engine that forcibly increases the intrinsic value per token by absorbing BANA tokens from the market with incoming real-world profits to reduce the circulating supply.

**Layer 3. POWER (The Governance Layer)**

> "An authority layer that executes the trust of the ecosystem"

* **Role**: Manages decision-making voting and asset acquisition policies.
* **Function**: Executes major decisions regarding asset management (e.g., purchasing new assets, adjusting yield rates) through on-chain governance.
* **Security**: Prevents artificial fund leakage through Multi-sig wallets and smart contract audits, recording all processes transparently.

***

#### Architecture Comparison

| **Layer** | **Core Function**              | **Value Backing**                 | **Asset Type**            |
| --------- | ------------------------------ | --------------------------------- | ------------------------- |
| CASH      | Revenue settlement and payment | Actual generated operating profit | Stablecoins (USDT, etc.)  |
| COIN      | Value upward management        | BANA token burn and scarcity      | BANA Token                |
| POWER     | Governance and security        | Real-world asset operation rights | Governance Token / Rights |

***

{% hint style="info" %}
**BANA's 3-Layer structure completes the essential financial values of "Profitability-Stability-Transparency" by being independent yet organically combined.**
{% endhint %}


---

# 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/solution/three-layer-architecture.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.