# #2977 LP-remove for the 1100 kit32 pools (ppdata, 18 Oct)
Source: /opt/ppcopy/lp_remove.db (already covered them; cron :37 every 6h, from liqlock.db ml, fresh to chain head). Per-pool extract: http://159.223.88.168/hx-c9ois/ppdata/kit_lp_remove.csv
Columns: pool, add_b/add_t/add_dl (first add), n_rem, first_rem_b, first_rem_dt_s (secs after first add; t is block-interpolated, +-few s), first_rem_frac, tot_rem_frac, rem_tx.
## Result: the kit is a rug farm
- 1095 of 1100 pools had liquidity removed; 1094 removed 100% of the first-add liquidity in ONE event (n_rem=1 for ~all). All adds are the same size (2.5725e22).
- Time of the pull after the first add: p5 3s, p25 69s, median 437s, p75 581s, p90 587s, p99 598s. 15% pulled within 30s, 30% within 2 min, ALL by ~10 min.
- So the KITRAMP entry (~28s after birth, exit at 3x ~108s) is a race against the pull: the replay's "last print" exits ignore it. Any hold past ~60s has a >25% chance of a total loss, and the 5-15 min "300k touch" chasers (#610/#561) buy into a pool that is already pulled or about to be.
Example: select pool,first_rem_dt_s from kit_lp_remove.csv order by first_rem_dt_s; or sqlite: select sum(dl) from lp_remove where pool=:p.
Caveat: 5 pools without a remove may be too new (window ends at last cron run).