> 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/network-fundamentals/audits.md).

# Audits

<div data-with-frame="true"><figure><img src="https://2842511454-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>

#### Audits are just part of the story

For any project, layers of security are crucial. Audits represent one layer, while core developers and contributors collaborate to provide many more. Notable security programs, designs, and partners beyond audits include:

* Embedded security researchers [via Asymmetric Research](https://stacks.org/asymmetric-joins-stacks-ecosystem) in coordination with Stacks Labs
* sBTC’s decentralized [network of validators/signers](https://www.stacks.co/sbtc) (removing the need to entrust a single entity and mitigating counterparty risk)
* Stacks’ underlying design that offers 100% Bitcoin finality, securing sBTC at the consensus level of a $2.5 billion network.
* Support at the app layer via [Hypernative](https://hackernoon.com/hypernative-bolsters-bitcoin-l2-security-as-stacks-ecosystem-gets-real-time-protection)
* Ongoing [Immunefi bug bounty program](https://immunefi.com/bug-bounty/stacks/information/) (and timely Attackathon programs)

{% hint style="warning" %}
*All 'high' or 'critical' issues listed in audits have either been mitigated or otherwise made obsolete, even if the report states otherwise.*
{% endhint %}

#### Stacks Core

Audits on Stacks Core

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

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

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

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

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

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

#### Other audits

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

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

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

Trail of Bits Report, Stacks Blockchain (No PDF, [Github Issues List provided](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/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.