> For the complete documentation index, see [llms.txt](https://docs.posx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.posx.io/whitepaper/tokenomics/basics.md).

# 4.1 代币基本信息

### 代币概览

| 项目    | 状态                                                                                                                                       |
| ----- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| 代币标准  | CURRENT / 当前已部署：POSX 已公开核验的部署位于 Ethereum Mainnet、Base Mainnet 与 BNB Smart Chain。BNB 部署使用 BEP-20 / ERC-20-compatible、UUPS-upgradeable 标准。 |
| 供应硬顶  | POSX 整体经济总量政策以 5,000,000,000 POSX 为上限。当前可直接核验的合约级 `MAX_SUPPLY()` 证据仅来自 BNB 部署。                                                           |
| 当前供应量 | 请参阅下方链本地 `totalSupply` 快照。它们不是已核验 circulating supply。                                                                                    |
| 铸造与管理 | BNB 部署中，铸造受角色控制，且受合约级硬顶限制。Ethereum 与 Base 的完整权限状态仍待逐项公开核验。                                                                               |
| 独立审计  | Pending / 待完成：当前 POSX 定制实现尚未独立审计。                                                                                                        |

OpenZeppelin 的审计仅涉及上游 Fireblocks ERC20F 模板。该范围不认证 POSX 定制实现、部署配置、特权角色或流动性安排。

### 链本地供应快照

| 网络               | 链本地 `totalSupply` 快照 | 核验边界                                                                                                         |
| ---------------- | -------------------: | ------------------------------------------------------------------------------------------------------------ |
| Ethereum Mainnet |   1,000,000,000 POSX | [Etherscan Token 页面](https://etherscan.io/token/0x8cCC52114917c6dAA1E3245efE9168180B20f9E0) 显示的快照。           |
| Base Mainnet     |      21,000,000 POSX | [BaseScan Token 页面](https://basescan.org/token/0x8cCC52114917c6dAA1E3245efE9168180B20f9E0) 与 Base RPC 显示的快照。 |
| BNB Smart Chain  |     337,974,316 POSX | [`block 119,480,403`](https://bscscan.com/block/119480403) 的快照。                                              |

这些数值均非已核验 circulating supply，且在供应关系未公开确认前不得直接相加。Ethereum、Base 与 BNB 之间的发行关系、统一总量控制、映射或桥接关系及对账机制均为 TBD / 待正式公开验证。

BNB implementation `0xd43b78bCE8FA416F31FC038D0cF81AdCdD4c3B7d` 的 `MAX_SUPPLY()` 为 5,000,000,000 POSX。Ethereum 与 Base 指向 implementation `0x0f25045d15C163478bb67C56c5d9D602628F4F62`；本次未核验到这两条部署公开暴露 `MAX_SUPPLY()` 硬顶。

### 代币分配方案

以下为当前白皮书采用的规划分配草案，合计为 5,000,000,000 POSX；是否作为最终正式分配方案仍须 Founder/Business 批准。分配表不表示代币已铸造、已归属、已解锁或可用。

| 分配类别     |       比例 |                   代币数量 | 状态                |
| -------- | -------: | ---------------------: | ----------------- |
| 消费者奖励池   |      50% |     2,500,000,000 POSX | **PLANNED / 规划中** |
| 一级市场销售   |      10% |       500,000,000 POSX | **TBD / 待确认**     |
| 商户激励池    |      10% |       500,000,000 POSX | **PLANNED / 规划中** |
| 用户增长与推广池 |      10% |       500,000,000 POSX | **PLANNED / 规划中** |
| 流动性支持池   |      10% |       500,000,000 POSX | **PLANNED / 规划中** |
| 团队与顾问    |      10% |       500,000,000 POSX | **TBD / 待确认**     |
| **合计**   | **100%** | **5,000,000,000 POSX** | **硬顶闭合**          |

销售条款及任何执行参数仍为 **TBD / 待确认**；6.1 中的归属与解锁规则仅为 **PROPOSED / Founder & Legal approval required**，尚未部署或生效。

本文档仅供信息披露，不构成投资建议、认购邀请或法律意见。


---

# 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://docs.posx.io/whitepaper/tokenomics/basics.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.