> 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="/files/c18eb2bb29274c91b487c026c6dcf2680ff29e66" 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 principales y los colaboradores trabajan juntos para proporcionar muchas más. Entre los programas, diseños y socios de seguridad notables 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)
* Programas Attackathon en colaboración con Immunefi
* la 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 al nivel de consenso de una red de 2.500 millones de dólares.
* Soporte en la capa de la aplicación a través de [Hypernative](https://hackernoon.com/hypernative-bolsters-bitcoin-l2-security-as-stacks-ecosystem-gets-real-time-protection)
* de Bitcoin L2 Labs [programa de seguridad whitehat](https://bitcoinl2-labs.github.io/2024/06/04/orange-hats.html)
* la asociación de Stacks Foundation con Staking Defense League
* en curso de Stacks Founation [programa de recompensas por errores de Immunefi](https://immunefi.com/bug-bounty/stacks/information/)
* Residentes dedicados de Stacks Foundation centrados exclusivamente en pruebas de fuzzing y de penetración (creado [Rendezvous](https://stx-labs.github.io/rendezvous/))

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

#### Stacks Core

Auditorías en 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 incidencias 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stacks.co/learn/es/network-fundamentals/audits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.