Hydration

• Name: Hydration (formerly HydraDX)
• URL: https://docs.hydration.net/quick_start/hydration/
• Category: appchain DeFi stack / shared-liquidity AMM / hub-asset routing protocol / single-sided liquidity primitive
• Tags: polkadot-ecosystem
• Summary: Hydration is a Polkadot DeFi chain built around one useful mechanism: the Omnipool. Instead of fragmenting liquidity across token pairs, it routes listed assets through an internal hub asset, lets LPs add one asset at a time, and keeps asset admission plus balance-sheet policy under governance. That makes it more useful as a hub-asset AMM and treasury-governed liquidity note than as another all-in-one DeFi app pitch.
• What it does:
  • Runs the Omnipool, a single multi-asset AMM where supported assets trade against one another through an internal hub asset instead of through isolated token pairs
  • Lets LPs provide one asset at a time rather than two-sided pair liquidity, with the protocol minting and burning LRNA/H2O to keep the pool balanced
  • Uses dynamic trading fees, oracle-aware withdrawal protection, liquidity caps, and protocol-owned liquidity to manage manipulation and balance-sheet risk
  • Extends beyond the AMM into stablepools, isolated pools, borrowing, and a native overcollateralized stablecoin, HOLLAR, inside one Substrate runtime
  • Keeps Omnipool asset admission and major treasury/liquidity decisions under onchain governance rather than treating listing as fully permissionless
  • Uses Polkadot-native appchain architecture and XCM connectivity to position the protocol as shared liquidity infrastructure for the wider ecosystem
• Key claims:
  • The most important reusable mechanism is not merely single pool instead of many pools; it is the split between user-facing asset deposits and protocol-managed hub-asset accounting. Hydration turns pair selection and reserve balancing into protocol policy rather than leaving them to separate LP communities.
  • The single-sided LP model matters because it changes where impermanent-loss management sits. Instead of asking LPs to choose and rebalance both legs of a pair, Hydration exposes LPs primarily to their chosen asset versus the hub asset while the protocol absorbs, redistributes, and burns parts of the hub-side imbalance.
  • Hydration’s official Omnipool materials make the internal hub asset more than a routing convenience. LRNA/H2O functions as the common accounting leg for every listed asset, a weighted index-like reserve surface, and the medium through which fees, partial IL mitigation, and imbalance recovery are handled.
  • Governance control over Omnipool listings is analytically important. Hydration is not a fully permissionless list-anything AMM at the core layer; practical power sits in deciding which assets get access to the shared pool, what caps they receive, and what tradability/risk parameters apply.
  • The protocol’s runtime-level integration also matters. Hydration is trying to collapse trading, borrowing, stablecoin issuance, and treasury deployment into one appchain-level control plane, which makes it a better comparison point for vertically integrated DeFi stacks than for ordinary single-product AMMs alone.
  • Hydration belongs in the active corpus because it makes a distinct comparison branch clearer: liquidity concentration can be achieved not only by weighted baskets or routing aggregators, but by a governance-managed single-pool architecture where hub-asset policy, listing policy, and protocol-owned liquidity become the real control surfaces.
• Whitepaper: No single canonical public whitepaper surfaced in this pass. The strongest primary materials were the official docs plus official repository context documents and Omnipool deep-dive notes collected in ../whitepapers/hydration-primary-sources-2026-05-12.md.
• Sources:
  • https://hydration.net/
  • https://docs.hydration.net/quick_start/hydration/
  • https://docs.hydration.net/products/trading/pools/omnipool/
  • https://docs.hydration.net/products/trading/liquidity/single_sided_lp/
  • https://raw.githubusercontent.com/galacticcouncil/hydration/main/README.md
  • https://raw.githubusercontent.com/galacticcouncil/hydration/main/general/hydration.md
  • https://raw.githubusercontent.com/galacticcouncil/hydration/main/general/omnipool.md

Internal linkages

• Strongest liquidity-architecture contrasts: uniswap and curve.
• Keep the note on governance-managed hub-asset routing and single-sided liquidity, not on generic appchain DeFi breadth.

Control surface

• Practical authority sits in Omnipool asset admission, hub-asset accounting policy, liquidity caps, fee logic, protocol-owned-liquidity deployment, and runtime governance over the wider stack.

• That is why the note should stay on shared-liquidity balance-sheet design rather than broaden into a Polkadot DeFi catalog.

• Last reviewed: 2026-06-12 UTC