Wallet cluster: devnet · keeper defaults to simulation-only
Sentient
← Engines

HYDRA

Liquidity with more than one head.

HYDRA maintains up to three DLMM positions — a concentrated core and wings on either side — and repositions each head independently as price, flow and volatility change. Quiet markets grow wings; accelerating markets pull heads toward flow; stressed markets widen and reduce exposure.

v2.0Meteora DLMMExecutable · gatedby protocol
Illustration

Liquidity under management

—

Value in engine-owned DLMM positions. Summed across installations with a connected treasury.

Installations

0

Confirmed transactions: 0 · LP fees earned 0.00 SOL

Execution status

Plans, simulates and (when the execution gate allows) submits through the Meteora DLMM SDK. Simulation-only by default.

Modes

  1. OBSERVEReading the market. No liquidity action proposed.
  2. TRACKHeads moving toward active flow.
  3. SPREADWings deployed on both sides of price.
  4. DEFENDRanges widened, exposure reduced, reserve raised.
  5. IDLEMarket dormant. Preserving resources.

Observes · proposes

Market inputs
PriceVolumeVolatilityBuy/sell imbalanceLiquidity depthLP fee generation
Actions it may propose (everything else is rejected by the risk engine)
CREATE_POSITIONADD_LIQUIDITYREMOVE_LIQUIDITYREBALANCE_LIQUIDITYCLAIM_FEESLOCK_LIQUIDITYHOLD

What is enforced

  • ✓Positions are owned by the installation's engine treasury and are withdrawable; nothing is locked.
  • ✓Every action passes the risk engine and an RPC simulation before it can be submitted.

What it does not do

  • ✕Concentrated liquidity is exposed to impermanent loss.
  • ✕Repositioning liquidity is not price support and does not prevent declines.

Default config

HYDRA v2.0 · SPOT
● editable at install
● Range width24
● Concentration60%
● Reserve floor30%
● Deployment per epoch18%
● Rebalance trigger8
● Volatility response85%
● Max positions3
● Rebalance cooldown40m
● Max slippage50bp
Evaluation interval3m
Fee claim threshold0.020 SOL
● Fee redeployment50%
Retention during activity0%

Bars show each value within its protocol bound. Every config is validated against these bounds before it can operate.

Running HYDRA

No installations yet.