VI. Security

Tydro Docs | Audit Reports

Tydro audit coverage includes the Aave V3 lending base and separate reviews of Tydro-specific components, with each report applying only to the code and scope it actually reviewed.

What this page covers

Tydro audit coverage includes the Aave V3 lending base and separate reviews of Tydro-specific components, with each report applying only to the code and scope it actually reviewed.

How it works

The source documentation lists Tydro V2 reviews including Zellic work in August 2026 and a LlamaRisk parameter review, alongside multiple Aave V3 audits by firms such as OpenZeppelin, Trail of Bits, PeckShield, Sigma Prime and ABDK, plus Certora formal verification.

Reference

ReviewScope / date
ZellicTydro V2 Multiply review, August 2026.
ZellicTydro V2 payload / economic review, August 2026.
LlamaRiskkBTC parameter review, August 2026.
Aave V3 auditorsABDK, OpenZeppelin, Trail of Bits, PeckShield, Sigma Prime and Certora reviews of the base lending code.

Practical usage

When reading an audit, check the date, commit or scope, unresolved findings and whether the audited code matches the deployed contracts. Do not assume a base-protocol audit covers Tydro-specific integrations.

Risks and operational notes

An audit is evidence of review, not a guarantee. New code, configuration changes, dependencies and upgrades can introduce risks outside the scope of an older report.