> For the complete documentation index, see [llms.txt](https://docs.tydro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tydro.com/vi.-security/security-overview/technical-security/smart-contract-security.md).

# Smart Contract Security

Tydro defends its contracts with an audited base, a protective pause, and tightly scoped upgrade powers

### An audited base

Tydro is built on the Aave v3 codebase, deployed across multiple networks and securing a large volume of deposits over several years. Building on reviewed code means Tydro does not reinvent core lending logic, which is where the highest-severity bugs tend to live. Tydro's own additions are reviewed separately. See [Audit Reports](/vi.-security/audit-reports.md).

### Pausing

The Guardian can pause a single market or the protocol as a whole in response to a threat, then lift the pause once it clears. This contains an incident rather than letting it run while a response is organized. The pause power is protective only. It cannot move funds or alter balances.

### Upgrade controls

Tydro markets are mutable, so the protocol can adapt parameters and ship fixes. That power is deliberately constrained.

* Scoped roles. Authority is split. The Risk Steward adjusts parameters within preset bounds. The Guardian can pause but cannot change parameters or move funds. Governance holds the broad powers, including upgrades. See Governance.
* Bounded parameter changes. The Risk Steward can only move parameters inside ranges governance has already approved, so fast adjustments cannot exceed safe limits.
* Separation of duties. No single role holds enough authority to compromise the protocol on its own.<br>

For how these roles work end to end, see [Governance](/ii.-core-concepts/protocol-governance.md). For key custody behind these roles, see [Operational Security](/vi.-security/security-overview/technical-security/operational-security.md).

### Immutable components

Where a component is immutable, it cannot be altered by any key, which removes upgrade risk for that component. The tradeoff is that immutable code cannot be patched if a flaw is found. Tydro applies mutability and immutability deliberately by component.

For the residual risk these controls reduce, see [Smart Contract Risk](/v.-risk/risk-types-and-overview/smart-contract-risk.md).

<br>


---

# 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.tydro.com/vi.-security/security-overview/technical-security/smart-contract-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.