> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/learn/zh/network-fundamentals/audits.md).

# 审计

<div data-with-frame="true"><figure><img src="https://629346125-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH74xqoobupBWwBsVMJhK%2Fuploads%2Fgit-blob-5e2e14ea3986509bfcb836fe9be357ca3b56106b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### 审计只是故事的一部分

对于任何项目来说，多层安全至关重要。审计只是其中一层，而核心开发者和贡献者协作提供更多层级。除审计之外，值得注意的安全计划、设计和合作伙伴包括：

* 嵌入式安全研究人员 [由 Asymmetric Research 提供](https://stacks.org/asymmetric-joins-stacks-ecosystem) 与 Stacks Labs 协同进行
* sBTC 的去中心化 [验证者/签名者网络](https://www.stacks.co/sbtc) （无需将信任交给单一实体，并降低对手方风险）
* Stacks 的底层设计提供 100% 的比特币最终性，在一个市值 25 亿美元网络的共识层面保障 sBTC 安全。
* 通过以下方式提供应用层支持： [Hypernative](https://hackernoon.com/hypernative-bolsters-bitcoin-l2-security-as-stacks-ecosystem-gets-real-time-protection)
* 持续进行中 [Immunefi 漏洞赏金计划](https://immunefi.com/bug-bounty/stacks/information/) （以及及时的 Attackathon 活动）

{% hint style="warning" %}
*审计中列出的所有“高”或“严重”问题都已得到缓解，或以其他方式失去效力，即使报告另有说明。*
{% endhint %}

#### Stacks Core

对 Stacks Core 的审计

{% file src="/files/d57ca8485835cb61417081055748d6c41fb9dd44" %}

{% file src="/files/439a509b9fb753b8a7287c229e3eb98c115e5c46" %}

{% file src="/files/07c1d5156d781e7a94ee1ec2a805915691305758" %}

{% file src="/files/592cd8b0df201d02d1c9273b8f72d685671029d3" %}

{% file src="/files/beb8207385bd7ec7ed603c4434db883d6ffbc2eb" %}

{% file src="/files/a1240262a4ca93532e1bd9851360b22d9419305d" %}

#### 其他审计

{% file src="/files/1038001e8d1ac166a21b0104f633d4397408a148" %}

{% file src="/files/4a4680858c4c05fd1dc19dfe82f564aabd97cd3d" %}

{% file src="/files/bc3592c0166d4bb82847d4746ac90f12432709ba" %}

Trail of Bits 报告，Stacks 区块链（无 PDF， [提供了 GitHub 问题列表](https://github.com/diwakergupta/stacks-blockchain-tob-audit/issues))


---

# 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.stacks.co/learn/zh/network-fundamentals/audits.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.