Hydro Inflow

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Hydro Inflow pools ATOM, BTC and USD and delegates allocation across lending, staking, LST arbitrage and funding-rate strategies. Some routes are automated while others require manual team transactions under a governance-replaceable committee, so the holder cannot pin one immutable downstream exposure. The version-1 delegated-allocation dossier is dispositive regardless of the approximately $2.30M observed on Neutron on 2026-08-15.

Kill criteria: the events that revoke this verdict
• A named vault publishes an immutable adviser-approved strategy, venue and counterparty allowlist, per-position caps and a no-substitution rule
• Cosmos Hub migration, committee and team authorities, live positions, accounting and proposed-size multi-route unwind are independently verified

The research file

Mechanism applicability

Hydro Inflow pools ATOM, BTC and USD deposits into vaults that allocate across strategies including lending, staking, liquid-staking-token arbitrage and funding-rate capture. Hydro’s governance proposal describes some strategies as automated and others as requiring manual team transactions, with committee oversight for community-pool capital. That discretionary, multi-protocol position management directly meets the shared v1 delegated-allocation dossier.

Current observation and lifecycle

The DefiLlama protocol API read on 2026-08-15 classified Hydro Inflow as Yield and reported approximately $2.30M entirely on Neutron. The live Hydro interface exposes USD, BTC and ATOM Inflow vault routes. A June 2026 Cosmos Hub update announced migration from Neutron to permissionless CosmWasm on the Hub, but the current survey still attributes all vault TVL to Neutron; the memo therefore records a live transition rather than silently changing the settled perimeter.

Control and exit applicability

Vault users delegate allocation and cross-chain execution rather than holding a single underlying position. Hydro says its committee can be changed by governance, and the community proposal describes a semi-automated vault in which manual team transactions execute some strategies. LST redemption, lending utilization, funding hedges and interchain movements can each delay or impair a withdrawal; aggregate TVL is not executable capacity for one asset vault.

Why the class rule decides

The vault holder delegates both venue selection and execution across materially different lending, staking, arbitrage and funding routes, including manual transactions. The shared v1 delegated-allocation dossier therefore controls before scale. Reopen only after the Hub migration is reconciled and a named vault publishes an immutable adviser-approved strategy and counterparty allowlist, per-position caps, no-substitution rule, deployed committee and team authority map, live positions, independent accounting and proposed-size unwind evidence.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Hydro — live Inflow vault interface · primary · accessed 2026-08-15
  Supports: live lifecycle, ATOM vault, BTC vault, USD vault, deposit interface
• Hydro — protocol user FAQ · primary · accessed 2026-08-15
  Supports: Neutron contracts, Hydro governance, liquidity allocation, staking, lending yield
• Hydro governance proposal — Inflow deployment and controls · primary · accessed 2026-08-15
  Supports: Inflow vault, manual and automated strategies, committee, governance replacement, Cosmos and EVM allocation
• Cosmos Hub Unit — Hydro migration update · primary · accessed 2026-08-15
  Supports: migration announcement, Neutron origin, Cosmos Hub target, Inflow TVL, lifecycle transition
• DefiLlama — Hydro Inflow survey record · secondary · accessed 2026-08-15
  Supports: current TVL, Neutron perimeter, Yield category, survey observation

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.