> 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-liu-zhang-ta-mi-wang-luo-fen-xing-jie-gou-yu-gong-xian-quan-zhong.md).
# 第六章 · 塔幂网络：分形结构与贡献权重
分形生长：网络的幂次骨架
### 6.1 分形生长结构
塔幂网络采用分形生长结构展开，支持无限纵深、不设代数限制：每个塔晶最多延伸 **10 条分支**；分支上的塔晶再各自延伸 10 条，以10N 几何级数在链上生长出无限层级的塔幂网体——如同树木的枝杈、河流的支系，同一条简单规则逐层重复。所有谱系关系由智能合约记录，仅依赖钱包地址、拒绝任何 KYC 信息采集。
### 6.2 贡献权重函数
建设者 i 的加权分红权重 S 由两个维度等权合成——个人已激活塔晶数量 C 与个人有效堆叠 VITA 数量 V：
C 度量身份建设（激活了多少块砖），V 度量资金建设（堆叠了多少能量）。权重按 **1 : 3** 配比——堆叠为主、激活为辅，同时强制参与者兼为出资者与建设者：缺失任一因子，权重都将大幅折损，从计量层面杜绝纯资金投机与纯身份刷量两种失衡。
### 6.3 均衡建设额：网络维度的公平标尺
在等级评定中，网络贡献的计量采用**均衡建设额 E**：剔除该建设者塔晶谱系中累计堆叠金额最大的单一分支后，其余全部分支的累计有效堆叠金额之和（USDT 计）。该定义使依附单一强大分支的搭便车结构在数学上自动归零，只有多路径的均衡生长才能推高 E 值——公平由代码逐块执行，无申诉、无例外、无人情。
---
# 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-liu-zhang-ta-mi-wang-luo-fen-xing-jie-gou-yu-gong-xian-quan-zhong.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.
