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.

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.

For how these roles work end to end, see Governance. For key custody behind these roles, see Operational Security.

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.