Tydro
A non-custodial liquidity protocol on Ink, built to let capital move without friction. The team behind Tydro thinks DeFi should be simple, transparent, and genuinely useful.
Our Mission
Capital should flow. That is the whole idea. Tydro was created to remove the barriers that prevent people from putting their assets to work — whether that means supplying liquidity to earn yield or borrowing against holdings without selling them.
The protocol launched on Ink, a network designed for speed and low cost. We chose Ink deliberately. Most users do not want to pay $30 in gas to open a position; they want a protocol that works at the pace of their decisions.
The mission is not to add features endlessly. It is to do a small number of things well: supply, borrow, manage risk, earn rewards. The Tydro platform keeps that scope tight so every part of it can be audited, understood, and trusted.
Technology
Tydro is powered by Aave v3 smart contract architecture — one of the most tested lending codebases in DeFi, securing billions of dollars across multiple networks since its v1 release in 2020. The team did not reinvent the core; it adapted battle-hardened logic to Ink and tuned the risk parameters for the assets available there.
The contracts are non-custodial. Nobody holds your funds. Positions are governed by on-chain collateral ratios and liquidation logic, not by a company's back-end database.
Supply positions are tokenized as aTokens. These accrue interest in real time — the balance in your wallet grows every block. Borrow positions carry variable rates that adjust to utilisation. When a pool is heavily used, the rate rises to attract more supply; when it is quiet, borrowing becomes cheaper. This is straightforward mechanism design, not novelty.
The Tydro platform integrates Ink points rewards on top of base APY, giving suppliers and borrowers an additional reason to participate during the protocol's growth phase. Reward calculations are transparent and verifiable on-chain.
Our Approach
Risk management is not an afterthought. Every asset listed on Tydro's markets goes through a review of oracle reliability, liquidity depth, and historical volatility before a supply or borrow cap is set. Caps limit the maximum damage a single asset can cause if something goes wrong.
The team publishes risk parameter changes before they go on-chain. Transparency here is not optional — users need to understand the conditions they are operating in. An unexpected cap reduction or liquidation threshold change can hurt active positions, so the protocol gives advance notice.
We also believe in incremental deployment. New asset listings start with conservative parameters. If the market performs well and oracle feeds prove stable, parameters can be loosened over time. Starting tight and relaxing is far safer than starting loose and scrambling to tighten after a problem.
The interface at the Tydro app is designed to show what matters: your health factor, your current APY, the liquidation price. Everything else is secondary. Clutter in a lending UI is a safety problem, not just a design problem.
Assets & Markets
At launch Tydro supports over ten assets across the Ink network. The list includes kBTC (Kraken Wrapped Bitcoin), USD₮0, USDC, GHO, ezETH, weETH, USDe, sUSDe, USDG, and SolvBTC. Total market size has grown past $400 million — a signal that the Ink ecosystem has real demand for on-chain lending.
Stablecoin markets are the backbone of any lending protocol. USD₮0 and USDC pools regularly see utilisation above 90%, which drives the variable borrow rate up and rewards suppliers with competitive yields. At times USDG supply APY has exceeded 13%. These are not promotional rates — they reflect genuine borrow demand.
Wrapped Bitcoin variants (kBTC, SolvBTC) serve users who want Bitcoin exposure on Ink without giving up yield optionality. These assets are primarily used as collateral rather than borrowed. Liquid restaking tokens like ezETH and weETH follow a similar pattern: good collateral, limited borrow demand, near-zero supply APY from the protocol itself, but meaningful as part of a broader position strategy.
New assets are considered quarterly. If you want to suggest a listing, the support page explains how to reach the team.
Values
Honesty about risk is the first value. DeFi has a track record of downplaying what can go wrong. Tydro's documentation does not do that. The health factor system, the liquidation mechanics, the oracle dependencies — all of it is described plainly, including the edge cases.
Open infrastructure is the second. The protocol's contracts are public, the code is open source, and the Aave v3 foundation it builds on has been reviewed by multiple independent firms. You do not have to take the team's word for it.
Accessibility is the third. The team behind Tydro wants people in different countries, with different technical backgrounds, to be able to use the protocol. That means supporting multiple languages in the interface, writing documentation that assumes curiosity rather than expertise, and keeping gas costs low enough that small positions are viable.
The fourth value is patience. Building on Ink means building inside a young ecosystem. Volume will not peak on day one. The team is here for a multi-year project, not a sprint to TVL numbers.
The Team
The people behind Tydro come from backgrounds in protocol engineering, smart contract security, product design, and DeFi operations. The group is small and distributed. Small teams move faster, make cleaner decisions, and carry less overhead than large ones — though they also require everyone to carry more.
Several team members have prior experience with Aave deployments on other networks, which is a practical reason the protocol inherited that architecture. Knowing a codebase deeply is a risk-reduction measure, not a lack of imagination.
The team does not maintain a public list of individual names or LinkedIn profiles. This is a deliberate choice, not evasiveness. In practice, the relevant transparency is on-chain: the contracts, the transactions, the parameter changes, the reserve data. Those are verifiable by anyone.
If you have questions about the team, the protocol, or want to discuss a potential integration, use the official channels listed in the footer or visit the support section.