Liquidity — the unified pool

The unified liquidity pool is the piece that makes cross-chain trading feel like same-chain trading. Instead of running a separate pool per chain (fragmented, thin), OmniHood runs one virtual pool that owns inventory across every supported chain and rebalances automatically.

How the unified pool works

• You deposit on any single chain — Base, BNB, or Robinhood Chain today.
• The pool credits you a global share of the whole cross-chain inventory, measured in the token itself, not in any one chain.
• When a user on any chain trades, the pool serves it from the nearest chain that has inventory. If the local chain is short, the keeper bridges from another chain (~1–3 min via LayerZero) and the ledger tracks who owes what.
• Every trade generates fees, which accrue to the pool. Your share grows automatically as fees compound — you don't claim, they raise your NAV.

Providing liquidity

Withdrawing

• Any time, no lockup.
• Withdrawal is paid out of the local chain's inventory. If the local chain is short, the keeper first pulls back from another chain (~1–3 min) and then delivers.
• You always get back your share priced at the signed home price — no impermanent loss from cross-chain mispricing, because the whole pool trades at a single price.

How fees flow to LPs

• Trade fees flow into the pool NAV — your share automatically grows. No claim step.
• The RFQ fee is 1% on every buy and sell of a launched token, with 70% going to LPs and 30% to protocol.
• Fees are denominated in the quote asset (WETH / WBNB) on each chain; the pool's NAV computes them in the token itself using the signed home price.

The RFQ engine under the hood

Trades don't happen against an AMM — they happen against signed prices from the home pool. A keeper reads the home price (Meteora on Solana for ANSEM, for example) and signs quotes for other chains. When a buyer submits a signed quote on their chain:

• If local inventory is enough → instant fill at the signed price (no slippage).
• If not → the gate emits a CrossChainOrder event. A keeper detects it and bridges the tokens over LayerZero from a chain that has them (~1–3 minutes). The user waits, then receives.

The ledger on each gate tracks receivables and payables between chains, so the pool's NAV stays consistent even during multi-chain rebalances.

Coverage today

The unified pool model is live and running against ANSEM across Base + BNB + Robinhood Chain, sourced from Solana. New tokens will get the same treatment as they launch through the omnichain Launcher.

Risks

• Cross-chain latency. If you withdraw when the local chain is short, expect a 1–3 min bridge before you're paid.
• LayerZero dependency. The whole rebalance mechanism uses LZ; a prolonged LZ outage would delay bridges (funds are safe but stuck until it resumes).
• Keeper dependency. The keeper signs prices and executes cross-chain fills. If the keeper is down, trades stall (funds remain safe on-chain).