> For the complete documentation index, see [llms.txt](https://cook-protocol.gitbook.io/chinese/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cook-protocol.gitbook.io/chinese/current-features-products/cli.md).

# 主流币指数（CLI）

主流币指数（CLI）包括流通市值最大的两个代币-比特币和以太坊，他们代表了加密货币中最大和最好的代币，是整个行业的基石。

### 目标

主流币指数（CLI）是一个数字资产指数，旨在跟踪加密行业中市值最大的代币的表现。该指数通过对代币流通量进行加权计算得来。

### 计算方法

主流币指数（CLI）用了以下标准来选择代币：

* 上线以太坊主网
* 在任何司法管辖区都不被视为证券
* 在各交易平台上具有充足的流动性
* 在Coingecko和CoinMarketCap上始终位于市值最大的前10名代币之列
* 必须通过主流机构的审计

指数的构成基于每个项目流通市值。

初始分配:

比特币

以太坊

![](/files/-McSh3YRQFLy9P3fedO-)

* 流通量（Circulating\_supply）是市场上流通的代币数量。流通量及市场价格的数据来源为CoinGecko。
* 市场价格（market\_price）是以美元表示的代币的市场价格。
* 指数除数（Index\_divisor）是一个常量，用于计算指数的名义值，其初始值是3093848205 
* 指数价格（Index\_price）是指数代币的现货价值。

### 运作方式

主流币指数（CLI）是加密领域最大的两个项目的通证化表示。

每季度最后一个月的第三周，主流币指数将被评估，用来决定是否调整指数的构成。指数中代币的流通量将基于CoinGecko的数据重新计算。在每个季度的指数调整中，指数权重会变更、代币的增加或删除将在此期间进行调整。


---

# 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://cook-protocol.gitbook.io/chinese/current-features-products/cli.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.