> 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/i.-introduction/overview/tech-stack.md). # Tech Stack Overview of the components of the Tydro Protocol ### Lending Engine Tydro is built on the Aave V3 codebase. Aave V3 is open source, audited, and has over $10B of deposits across multiple networks. Tydro inherits a battle-tested lending implementation without new core logic. Markets, rate models, liquidation flows, and position accounting all follow Aave V3. For how the markets are configured, see [Markets](/ii.-core-concepts/markets.md) and [Interest Rates](/ii.-core-concepts/interest-rates.md). ### Network Tydro runs on Ink, an Ethereum Layer 2 built on the OP Stack and part of the Optimism Superchain. Ink is deployed by Kraken, providing the settlement layer for the protocol and adds chain-level monitoring and security tooling. Tydro's security stack includes real-time monitoring and threat response from [Hypernative](https://www.hypernative.io), alongside best practices in risk modeling, frontend, smart contract, operational security, and external audits. ### Qualified Custodian Tydro integrates with Kraken custody, allowing eligible users to borrow, lend, and hold assets within a qualified custodian. See [Qualified Custody](/iv.-tydro-institutional/institutional-overview/qualified-custody.md). ### Asset Managers & Vaults External managers can run strategies and deploy capital through vaults. A manager can also post first-loss capital where a strategy provides coverage for its depositors. Vaults are planned. See [Vaults](/vii.-developers/developer-overview/smart-contracts/vaults.md) and [Institutional Overview](/iv.-tydro-institutional/institutional-overview.md). --- # 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/i.-introduction/overview/tech-stack.md?ask=&goal= ``` `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.