> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/zh-cn/an-quan/bug-bounty-immunefi.md).

# 漏洞赏金 (Immunefi)

Lista DAO 与 **Immunefi** 合作 —— 这是一个领先的区块链安全漏洞赏金平台 —— 以主动识别和修复漏洞。该计划邀请道德黑客和安全研究人员报告关键问题以换取奖励，帮助我们维护一个安全稳固的生态系统。

💰 **报告漏洞或了解更多关于我们活跃的赏金计划**

您可以在 [这里](https://immunefi.com/bug-bounty/listadao/) 找到我们的 Immunefi 漏洞赏金计划并报告任何问题。


---

# 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.bsc.lista.org/zh-cn/an-quan/bug-bounty-immunefi.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.