> 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/bai-pi-shu/di-shi-zhang-ta-mi-chuang-shi-dui-die.md). # 第十章 · 塔幂创世堆叠一百层的登塔仪式 ### 10.1 定位：参与的第一道门塔幂创世堆叠是 VITA 的创世发行仪式，也是每一位建设者踏入塔门的第一步。52,500,000 枚 VITA（总量的 25%）沿一条预先写入合约的**绑定曲线（Bonding Curve）**铸造发行：曲线划分为 100 个连续价格层，如同塔的一百级台阶，每一枚 VITA 都由真实资金从曲线上买入而诞生；价格自第 1 层的 0.100 USDT 起沿曲线攀升（曲线参数 0.02，整体近似线性），至第 100 层到达 0.200 USDT——恰为起点的 2 倍。登塔越早，脚下的台阶越低；而曲线对所有人只有同一条。

### 10.2 鱼肚型分布：写进正态曲线的节奏单层发行量采用离散正态分布（均值 μ = 50.5，标准差 σ = 20），形成「前期低价少量、中段集中释放、后期高价收缩」的**鱼肚型结构**：

按该模型：第 1 层价格 0.100 USDT、发行约 49,579 枚；第 50 与第 51 层为峰值，各约 1,060,052 枚；第 100 层价格 0.200 USDT、发行约 49,579 枚；经整数尾差修正后，100 层总和精确等于 52,500,000 枚。这条曲线的每一段都承载明确的设计意图：**前段低价少量**，把最陡的价格优势留给最早的信仰者，同时以有限供给杜绝巨鲸垄断；**中段放量**，在共识升温期敞开承接主力建设者；**尾段收缩**，以稀缺性完成冲刺，让创世以供不应求的姿态收官。 ### 10.3 执行规则：合约即司仪 * **状态全透明**：堆叠合约实时公示当前层价格、剩余数量与累计堆叠状态，每一级台阶的余位全网可查。 * **跨层必拆分**：用户资金跨越多层时，由合约逐层拆分结算——价格阶梯对所有人一视同仁，无人可以整段买穿。 * **售罄即进层**：当前层售罄后自动进入下一层；第 100 层售罄后，塔幂创世堆叠**永久结束**，此后再无第二次创世。 ### 10.4 公平铸造：正规性的第一块基石塔幂创世堆叠在发行方式上恪守区块链行业最正统的公平原则：**无私募、无机构轮、无价格暗箱**——100 层价格曲线自部署之日起完整公开，每一层的价格与数量写死于合约，所有参与者面对同一条曲线、同一套规则、同一个入口。发行的全部过程由合约司仪，团队与任何第三方均无优先通道。创世堆叠同时授予参与者塔晶的获取资格，作为进入塔幂网络的身份凭证；身份体系的哲学与结构详见第四章至第六章。铸造完成的那一刻，协议的创世发行永久闭幕——此后 VITA 的一切流转，都发生在公开市场与公开规则之下。 --- # 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/bai-pi-shu/di-shi-zhang-ta-mi-chuang-shi-dui-die.md?ask=&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.