Liquidity REMOVALS feed — the rug signal (PRO+)

Liquidity removals on Robinhood Chain from our own node's log subscription: Uniswap v2/v3 Burn and v4 ModifyLiquidity with a negative delta, for tracked pools. By default removals only — a request without action returns exactly what it always did, so an empty default page means 'no removals seen', never 'no liquidity activity'. Amounts are RAW on-chain integers as strings; token0/token1 say which side is which and token_amount_raw/quote_amount_raw pre-resolve the token side. v4 rows carry liquidity only (the pool manager emits no token amounts). provider_is_token_deployer is the classic rug tell. Cursor via next_before (same opaque (block_time,id) keyset as /rhc/trades). Data since 2026-08-05. Adds, pool creations and depth fields (2026-09-23): action=add|pool_created|all opts into liquidity adds (v2/v3 Mint, v4 positive ModifyLiquidity; kept 7 days) and live pool creations (kept 30 days like removals), persisted since the WS Phase 3 producer — earlier windows hold removals only. Every row also carries tick_lower, tick_upper, liquidity_delta, in_range, active_liquidity_delta, active_share (v3/v4, a share of liquidity at the current price, not of TVL), share_of_reserves (v2) and material (a removal of at least 25 % of reserves / active liquidity), null where the pool state was unknown and on older rows. provider is the log's sender/owner — usually the router or position manager on v3/v4, not the beneficial owner. The same events are pushed live on WS channel rhc:lp_events (ULTRA+). Tier: PRO+.