> For the complete documentation index, see [llms.txt](https://hu-die-zhi-ku.gitbook.io/flapaivault/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hu-die-zhi-ku.gitbook.io/flapaivault/xiang-mu-zong-lan/shuang-jin-ku-jie-gou.md).

# 双金库结构

蝴蝶智库采用清晰的双金库结构：

**AI 做市金库负责市场管理，分红金库负责税费分配。**

二者独立运行，互不混用。

***

### 1. AI 做市金库

#### 资金来源

AI 做市金库的资金来源为用户提供的 BNB。

#### 资金性质

用户提供的 BNB 为不可赎回资金。

该资金进入协议后，成为协议 AI 做市金库的一部分。

#### 资金用途

AI 做市金库资金用于协议市场管理，包括但不限于：

* 回购代币；
* 出售部分代币回笼 BNB；
* 销毁代币；
* 活跃市场；
* 保留资金并观望。

#### 核心原则

AI 做市金库的目标不是短期盈利，而是服务于代币市场表现。

其核心价值体现在：

* 维护盘面稳定性；
* 增强持币者信心；
* 提高做市资金使用效率；
* 优化传统机械回购销毁模式；
* 在不同市场阶段选择更合适的市场策略；
* 让有限的做市资金发挥更持续的市场管理作用。

***

### 2. 分红金库

#### 资金来源

分红金库的资金来源为代币交易税费。

#### 资金用途

分红金库专门用于按照仓位权重向参与者分配交易税收入。

#### 分红原则

分红来源为市场交易行为本身，而不是后续用户提供的 BNB。

因此，协议的核心资金原则是：

参与资金进入 AI 做市金库，交易税费进入分红金库，两条资金路径独立运行。

<br>


---

# 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://hu-die-zhi-ku.gitbook.io/flapaivault/xiang-mu-zong-lan/shuang-jin-ku-jie-gou.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.