Security Overview
Security overview
Security at Tydro is layered. Technical, economic, and operational controls work together, on top of an audited lending base, a monitored network, and qualified custody. This page maps the layers and how they address the protocol's risks.
A layered model
No single control secures a lending protocol. Tydro runs defense in depth, so a failure in one layer is met by others.
Technical security protects the code and the data it depends on: the audited contract base, the protective pause, market parameterization, and price feed integrity. See Technical security.
Economic security protects capital with underwriting, first-loss coverage, insurance, and quantitative risk modeling. See Economic security.
Operational security protects the keys and people who operate the protocol. See Operational security.
The stack reinforces all three. The Aave V3 codebase brings a security history measured in years and large deposits across networks. Ink adds monitoring at the network layer. Kraken qualified custody removes a large share of the self-custody risk institutions carry elsewhere. See The Tydro stack.
How controls map to risks
Every risk in the Risk section is met by specific controls here. This table is the map.
Smart contract risk
Audited base, protective pause, scoped upgrade roles
Smart contract security
Market and collateral risk
LTV and liquidation thresholds, caps, market isolation, underwriting
Market and collateral security, Asset underwriting
Liquidation risk
Conservative parameters, the liquidation engine, bounded parameter changes
Market and collateral security
Oracle risk
Chainlink feeds, staleness and deviation checks, the PriceOracleSentinel, Guardian pause
Price feed security
Tranche risk
First-loss capital, asset underwriting
Economic security
Custody and counterparty risk
Qualified custody, key management, operational controls
Operational security
RWA and permissioned-asset risk
Asset underwriting, access controls
Asset underwriting
Last updated
