> For the complete documentation index, see [llms.txt](https://docs.bao.la/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bao.la/jiao-yi-yu-fan-yong/fan-yong.md).

# 返佣

#### 1、邀请返佣

<figure><img src="https://638893843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkzpnuiDNuvyW8KThUzVf%2Fuploads%2FFU3NpY1WDS22a4vyUtQ3%2Fimage.png?alt=media&amp;token=6c8c44e6-6fff-4fc2-898f-ad2e66feda6f" alt="" width="375"><figcaption></figcaption></figure>

* 好友成功绑定您的邀请码后：您可获得该好友每笔交易手续费的 30% 作为邀请返佣；好友可获得本人每笔交易手续费的 20% 作为交易返佣。
* 交易手续费率为 1%。按交易手续费的 30% 计算邀请返佣，邀请返佣收入为交易金额的 0.3%。
* 返佣奖励将以好友产生交易手续费所在区块链的主币进行结算和发放。
* 您与好友的交易手续费返佣有效期均为 365 天，自返佣权益生效之日起计算。2025.07.15 前创建的历史钱包，在当前活动页面开放老用户福利入口，限时领 20% 交易手续费返现福利，领取后返现有效期 365 天。
* 若新用户绑定的上级邀请人为代理商，其可获得的交易手续费返佣比例及具体规则，以该代理商指定的方案为准。
* 受法律法规限制，部分司法管辖区可能无法参与本活动。由于市场环境变化，欺诈风险的存在等原因，平台保留随时对返佣规则作出调整的最终解释权。

#### 2、创作者收益

<figure><img src="https://638893843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkzpnuiDNuvyW8KThUzVf%2Fuploads%2FSvdGyVz7CL9qBV7U0fZ1%2Fimage.png?alt=media&amp;token=aff5dd0b-e068-4e4c-8820-db904f5ba83f" alt="" width="375"><figcaption></figcaption></figure>

* **如何获得创作者收益：**&#x7528;户通过你发布的喊单内容完成跟单交易，或已关注你的用户通过你的交易历史完成跟单交易后，即可获得创作者收益。
* **收益如何计算：**&#x8DDF;单用户完成交易并实际产生手续费后，平台将先行扣除邀请返佣，并按一定比例从剩余手续费中向你分配创作者收益。


---

# 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://docs.bao.la/jiao-yi-yu-fan-yong/fan-yong.md?ask=<question>&goal=<user_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.
