The SURGE:LEO liquidity pool launched on Hive-Engine in October 2025 with an initial $30,000 USD seed from @khaleelkazi. It's the third-largest LEO pair on the platform, enabling trading and liquidity provision via Beeswap (https://beeswap.dcity.io/pools?search=LEO) or TribalDEX (https://tribaldex.com/trade/SURGE-LEO).
A cross-chain market maker keeps it active, generating profits for LeoStrategy to buy more LEO. The pool supports SURGE's $1 floor price and 15% annual yield ($0.15 HBD per SURGE, paid weekly).
is there any way I suffer loss if I provide liqudity?
Yes, providing liquidity to the SURGE:LEO pool on Hive-Engine carries risks of loss, like any LP position. Here's what to watch:
Impermanent loss: If SURGE and LEO prices diverge (e.g., SURGE drops below $1 temporarily due to volatility), your LP value could be less than holding tokens separately. SURGE's reflexive design aims to peg it at $1+ with unlimited upside, but early trading has seen fluctuations—expect some in a $30K seeded pool.
Opportunity cost on yields: Liquid SURGE earns 15% annual yield ($0.15 HBD/week per token, paid Mondays). LP'd SURGE also qualifies for yield (via snapshot), but if prices shift, you might miss full gains from holding or converting to LSTR.
Fees and slippage: Trading fees (1% on some pairs) go to LPs, but low volume could mean minimal earnings offsetting losses from volatility.
Platform risks: Hive-Engine smart contract bugs, oracle issues (for cross-chain), or market maker disruptions could impact liquidity. No rug pull risk from LeoStrategy—they seed and maintain via profits buying LEO—but always DYOR.
Start small; the pool's MM helps stability. For details, see @leostrategy's launch post: https://inleo.io/@leostrategy/introducing-surge-on-crosschain-50000-in-liquidity-deployed-1-floor-price-9zm