How to use Bybit Liquidity Mining? (Earning fees)

Understanding Bybit Liquidity Mining Mechanics

1. Liquidity mining on Bybit allows users to supply assets into designated trading pairs on the Bybit Spot Perpetual Liquidity Pool (SPLP) or other supported liquidity pools.

2. Participants deposit matched asset pairs—such as BTC/USDT or ETH/USDT—into a shared pool where market makers and automated strategies execute trades.

3. Every trade executed against the pool generates fee revenue, a portion of which is distributed proportionally to liquidity providers based on their share of total pool depth.

4. Rewards are calculated in real time and settled hourly, denominated in the quote asset of the pair—for example, USDT earnings from BTC/USDT pool activity.

5. The protocol applies dynamic fee allocation: deeper liquidity positions earn more during high-volatility periods due to increased trade volume and slippage-based fee accrual.

Eligible Assets and Pair Requirements

1. Only whitelisted token pairs qualify for liquidity mining, including stablecoin pairs like USDT/USDC and volatile pairs like SOL/USDT or AVAX/USDT.

2. Each pair enforces minimum deposit thresholds—typically 100 USDT equivalent per asset—to prevent fragmentation and ensure meaningful contribution to price stability.

3. Tokens must be native to supported blockchains: ERC-20, BEP-20, or TRC-20 assets only; wrapped or synthetic tokens are excluded unless explicitly approved by Bybit’s risk committee.

4. Deposits undergo on-chain validation before being credited to the pool; failed transactions due to insufficient gas or network congestion do not trigger automatic retries.

5. Withdrawals follow a 24-hour cooldown window after deposit confirmation to mitigate front-running and pool imbalance risks.

Fee Distribution Logic and Real-Time Calculation

1. Trading fees collected from taker orders are split between Bybit’s treasury and liquidity providers at a fixed ratio—commonly 70% to LPs, 30% retained.

2. A user’s reward share equals (their deposited asset value / total pool value) × total fees accrued during the settlement period.

3. Fees are computed using on-chain trade logs verified by Bybit’s internal matching engine—not third-party oracles—ensuring deterministic payout logic.

4. Negative funding rate events or liquidation-driven fills do not contribute to fee accrual; only standard market orders generate distributable income.

5. Real-time dashboards display live APR estimates updated every 60 seconds, factoring in current spread tightness, order book depth, and recent trade count.

Risk Parameters and Capital Protection Measures

1. Impermanent loss is not mitigated by protocol design; LPs bear full exposure to relative price divergence between deposited assets.

2. Pools enforce maximum slippage limits per trade—usually 0.5%—to cap adverse execution impact on provider balances.

3. Emergency withdrawal gates activate automatically if pool health metrics fall below defined thresholds, such as 15% bid-ask spread widening over 5 minutes.

4. No insurance fund backs liquidity positions; losses from smart contract exploits or custodial breaches are not reimbursed under current terms.

5. Bybit does not guarantee minimum returns, and historical APR data is displayed without compound interest assumptions or backtested yield smoothing.

Frequently Asked Questions

Q: Can I provide liquidity with only one side of a pair?A: No. Bybit requires balanced deposits—equal USD-equivalent value of both base and quote tokens. Asymmetric deposits are rejected at the wallet signature stage.

Q: Are rewards taxed at source by Bybit?A: Bybit does not withhold taxes. Users receive gross fee distributions and must report earnings according to local jurisdiction requirements.

Q: Does staking BBT affect liquidity mining rewards?A: Holding BBT grants no multiplier or priority in fee distribution. BBT staking operates independently through Bybit Earn, with separate reward mechanics.

Q: What happens if my wallet disconnects mid-session?A: Liquidity positions remain active on-chain regardless of frontend connection status. Wallet disconnection does not pause or terminate participation.