> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/jing-ji-mo-xing/di-ba-zhang-btc-fen-hong-chi-wai-bu-jia-zhi-hui-bao.md).

# 第八章 · BTC 分红池：外部价值回报

随流动性动态生长的岩层分配

### 8.1 池的形成：买盘 + 动态注入 + 抽成

* <mark style="color:$warning;">**持续买盘**</mark>：塔晶激活 Gas 的 60% 由合约通过去中心化路由实时市价购入 BTC（或 WBTC），逐笔累入池内——池的每一分厚度都来自真实的激活行为。
* <mark style="color:$warning;">**生态注入**</mark>：BTC 是生态价值的直接体现——协议依据生态发展持续注入流动性分红，生态越繁荣，注入越丰沛，池体的厚度与塔的生长同频共振。
* <mark style="color:$warning;">**生态抽成**</mark>：生态后续各项手续费的清算抽成持续汇入，池体随生态繁荣长期增厚。

### 8.2 分配与结算

BTC 分红与 VITA 分红采用<mark style="color:$warning;">**同一套贡献权重 S**</mark>。塔幂创世堆叠结束后，池内资产按权重一次性加权确权：

<figure><img src="https://3424572652-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoLHhg79LiL5zNwP5HryG%2Fuploads%2F8hnJgRS8sgrxSnsAd2LZ%2Fimage.png?alt=media&amp;token=055054cc-ff07-4910-8121-a6b195ba0011" alt=""><figcaption></figcaption></figure>

* <mark style="color:$warning;">**分配时点**</mark>：塔幂创世堆叠结束后，合约以链上权重快照为依据按 S 加权分配，规则一次确定、全程可验。
* <mark style="color:$warning;">**提现机制**</mark>：用户可随时调用 claimBTC() 接口，将已确权的 WBTC 收益提取至个人非托管钱包，全程无人工审核。

### 8.3 理论规模测算

按当前协议参数测算，若 2,100,000 个塔晶全部完成激活，BTC 分红池理论累计规模预计超过 <mark style="color:$warning;">**4,200,000 USDT 等值资产**</mark>。

该数值属于参数测算值，实际规模取决于激活 Gas 费用、实际激活进度、路由成交价格与 BTC 市场价格，一切以链上余额为准；池地址、实时余额、累计流入与累计分配全程公开。


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vitaprotocol.gitbook.io/vita/vita-protocol/jing-ji-mo-xing/di-ba-zhang-btc-fen-hong-chi-wai-bu-jia-zhi-hui-bao.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.