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

# Auditorías

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

#### Las auditorías son solo parte de la historia

Para cualquier proyecto, las capas de seguridad son cruciales. Las auditorías representan una capa, mientras que los desarrolladores y colaboradores principales trabajan juntos para proporcionar muchas más. Entre los programas, diseños y socios destacados de seguridad más allá de las auditorías se incluyen:

* Investigadores de seguridad integrados [a través de Asymmetric Research](https://stacks.org/asymmetric-joins-stacks-ecosystem) en coordinación con Stacks Labs
* descentralizada de sBTC [red de validadores/firmantes](https://www.stacks.co/sbtc) (eliminando la necesidad de confiar en una sola entidad y mitigando el riesgo de contraparte)
* El diseño subyacente de Stacks que ofrece una finalidad de Bitcoin del 100%, asegurando sBTC a nivel de consenso de una red de 2.500 millones de dólares.
* Soporte en la capa de aplicación a través de [Hypernative](https://hackernoon.com/hypernative-bolsters-bitcoin-l2-security-as-stacks-ecosystem-gets-real-time-protection)
* En curso [programa de recompensas por errores de Immunefi](https://immunefi.com/bug-bounty/stacks/information/) (y programas oportunos de Attackathon)

{% hint style="warning" %}
*Todos los problemas 'graves' o 'críticos' enumerados en las auditorías han sido mitigados o de otro modo quedaron obsoletos, incluso si el informe dice lo contrario.*
{% endhint %}

#### Stacks Core

Auditorías sobre Stacks Core

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

{% file src="/files/77bac96a468d41b6fe4ae22f4e1bdc08521e3c7c" %}

{% file src="/files/8d80dce7a0bf1dfed2810af7e4f0942d27d53c0e" %}

{% file src="/files/0461de83f98ef5b9a7531283836133761a68a58a" %}

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

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

#### Otras auditorías

{% file src="/files/94a78557b1142cd2be1874bcea65a04cd5d1b33e" %}

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

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

Informe de Trail of Bits, Stacks Blockchain (Sin PDF, [Lista de problemas de GitHub proporcionada](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/es/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.