> 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/earn.md).

# Earn

## 二、赚取 Earn

### 2.1 功能介绍

赚取页面集中展示 Stacks 生态的收益产品，并识别用户的真实协议仓位。

目前支持四个产品：

* StackingDAO
* Zest Protocol
* Hermetica
* Xverse

### 2.2 StackingDAO

支持：

* stSTX
* stSTXbtc
* 原生 Stacking

说明内容：

* 质押资产
* 奖励资产
* 实时 APY
* 产品跳转链接
* 用户现有 StackingDAO 仓位

### 2.3 Zest Protocol

支持展示：

* sBTC
* STX
* stSTX
* stSTXbtc
* USDCx

Zest 仓位通过对应 Vault Position 识别，不把普通钱包余额重复计算为 Zest 仓位。

对于带底层收益的资产，可展示组合收益：

```
总 APY = Zest 借贷 APY + 底层代币收益
```

例如：

```
stSTX 总 APY = Zest APY + StackingDAO stSTX APY
```

### 2.4 Hermetica

展示：

* USDh
* sUSDh
* 实时质押收益率
* 用户真实收益仓位

### 2.5 Xverse

展示：

* STX Stacking
* sBTC Dual Stacking
* BTC / sBTC 奖励
* 实时或区间 APY

### 2.6 风险声明

* APY 会随市场和协议状态变化
* 协议智能合约可能存在风险
* 资产价格可能波动
* Stacks.PET 不托管用户资产
* 最终交易由用户钱包确认


---

# 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/earn.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.