> 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.md).

# Technical Security

Technical security protects Tydro's code and the data it acts on.

The protocol's technical defenses run at three points. The contracts themselves are built on an audited base and wrapped in protective controls. The markets are parameterized to contain risk before it spreads. The price feeds that the protocol acts on are validated before use. Ink adds monitoring at the network layer.

### This section covers

* Smart contract security. The audited base, the protective pause, and upgrade controls.
* Market and collateral security. Parameters, isolation, and caps as active controls.
* Price feed security. Validated pricing and restriction on bad data.


---

# 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.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.
