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

# Overview

## 一、总览 Portfolio

### 1.1 功能介绍

总览页面用于展示连接 Stacks 钱包后的真实链上资产与收益仓位，包括：

* STX、sBTC、USDCx 等钱包余额
* StackingDAO、Zest、Hermetica 等协议仓位
* CoinGecko 实时价格
* 资产美元价值
* 24 小时价格变化
* 资产配置比例
* 小额资产隐藏
* AI 资产集中度分析

### 1.2 数据口径

需要明确区分两类资产：

#### 钱包资产

用户钱包直接持有、尚未投入收益协议的代币。

例如：

* 闲置 STX
* 闲置 sBTC
* 钱包中的 USDCx

#### 已产生收益仓位

只有已经进入收益协议的资产才计入：

* 已产生收益仓位价值
* 预估收益
* 预估年化

目前包含：

* Zest Position
* StackingDAO 流动性质押代币
* Hermetica 收益仓位
* 后续接入的 Xverse 收益仓位

闲置 STX 不参与收益和加权年化计算。

### 1.3 计算公式

已产生收益仓位价值：

```
总仓位价值 = Σ（协议仓位代币数量 × 对应代币价格）
```

年度预估收益：

```
年度预估收益 = Σ（仓位价值 × 该仓位 APY）
```

加权预估年化：

```
加权 APY = 年度预估收益 ÷ 总仓位价值
```

总仓位余额价值：

```
总余额（USD） = Σ（代币余额 × 代币当前价格）
```

组合 24h 涨跌幅：

```
组合 24h 涨跌幅 = Σ（资产 USD 价值 × 资产 24h 涨跌幅）÷ Σ（资产 USD 价值）
```


---

# 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.stacks.pet/stackspet/overview.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.