> 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-si-zhang-ta-jing-fa-xing-huo-qu-yu-ji-huo.md).

# 第四章 · 塔晶：发行、获取与激活

身份资产的三段生命

### 4.1 发行参数

塔晶采用 ERC-721 / BEP-721 标准发行，总量 <mark style="color:$warning;">**2,100,000 个**</mark>，每一个内封存 <mark style="color:$warning;">**10 枚 VITA**</mark> 激活权益（合计 21,000,000 枚，对应总量的 10%）。塔晶用于确认参与身份、铭刻塔幂网络谱系、记录贡献并形成分红权重。

### 4.2 双通道获取

* <mark style="color:$warning;">**通道一 · 堆叠附带赠送**</mark>：参与创世堆叠的地址每日可领取塔晶，单地址每日领取上限统一为 <mark style="color:$warning;">**200 个**</mark>，用于堆叠自己的塔幂网络。
* <mark style="color:$warning;">**通道二 · 激活附带赠送**</mark>：完成塔晶激活的地址，每个地址可获赠 <mark style="color:$warning;">**10 个塔晶**</mark>，用于堆叠自己的塔幂网络。

两条通道指向同一个方向：<mark style="color:$warning;">**塔幂网络越大——创世堆叠的 VITA 越多、激活的塔晶越多——可瓜分的 BTC 与 VITA 分红就越多**</mark>。建设的规模直接刻度着权重 S 的两个因子，网络的每一寸生长都在分红公式里留下印记。

### 4.3 激活：三态跃迁

塔晶存在三种状态：<mark style="color:$warning;">**待领取**</mark>（记于合约额度内）→ <mark style="color:$warning;">**已领取未激活**</mark>（沉睡于钱包，暂无权重）→ <mark style="color:$warning;">**已激活**</mark>（有效状态）。持有者调用 activateCrystal() 接口并缴纳 Gas 清算费（以 BNB 或 USDT 支付）完成激活，单地址累计最多激活 <mark style="color:$warning;">**10 个塔晶**</mark>；单笔交易内完成三件事：释放塔晶内封存的 10 枚 VITA、身份进入有效状态并计入权重因子 C、Gas 按第五章规则 100% 无留存分流。未激活塔晶始终处于沉睡状态——<mark style="color:$warning;">**塔身上没有虚砖**</mark>。


---

# 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-si-zhang-ta-jing-fa-xing-huo-qu-yu-ji-huo.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.