> For the complete documentation index, see [llms.txt](https://hoodstrategy.gitbook.io/hoodstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hoodstrategy.gitbook.io/hoodstrategy/security.md).

# Security

## Audit

The v4 hook is a **high attack-surface** contract: a single bug can cause catastrophic losses for LPs and holders. An **audit by a reputable firm** (Uniswap v4 hook specialist) is **mandatory before any mainnet deployment**. Also plan for exhaustive Foundry testing (fuzzing, invariants) and a full testnet deployment.

## Code verification and transparency

* contracts **verified** on the explorer (public source code);
* public GitHub repository;
* audit report(s) published in full.

## Governance and ownership

* ownership under a **Timelock** (public delay) + **multisig** (e.g. 3/5);
* ownership renounced for parameters that must be immutable;
* no "backdoor" function (fund withdrawal, mint, arbitrary blacklist).

## Liquidity

* $HOODSTR/ETH LP **locked or burned**, with public proof of the lock;
* HOODX/ETH liquidity managed by a transparent treasury.

## Bug bounty

A public bug bounty program (e.g. via Immunefi) is recommended after the audit, to cover residual vulnerabilities.

## Pre-launch checklist

* [ ] Contracts tested (Foundry, ≥ 95% coverage, invariants)
* [ ] Full external audit, findings fixed
* [ ] End-to-end testnet deployment validated
* [ ] HOODX confirmed bridgeable to the target chain
* [ ] HOODX/ETH pool seeded, depth measured
* [ ] Chainlink HOOD oracle configured and tested
* [ ] $HOODSTR/ETH LP locked
* [ ] Ownership under Timelock + multisig
* [ ] Contracts verified on the explorer
* [ ] Public dashboard live
* [ ] Legal disclaimers published
* [ ] Legal counsel obtained


---

# 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://hoodstrategy.gitbook.io/hoodstrategy/security.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.