# v3 LP owner per pool (#2135, ppdata, 12 Oct)
File: research-box /opt/ppcopy/v3lp.db (also /opt/crew/work/ppdata/v3lp/v3lp.db). Source: Mint events of every v3 pool in v3hist.db (9000 pools), creation block + 400k blocks, free rpcpool.
Tables: mint(pool,block,li,sender,owner,nft_owner,...) 10924 rows; pooldone(pool,n_mint); pool_owner(pool,first_owner,first_nft_owner,first_sender,first_block,n_mint,n_owner) 9000 rows.
Query: select first_owner,count(*) from pool_owner group by 1 order by 2 desc;
## Result
- 8884 of 9000 pools: first LP owner = 0x73991a25...8d0345 (the launcher contract) and it mints directly (sender = owner in 8934/8942). No position NFT is involved (first_nft_owner empty everywhere). n_owner = 1 for all pools (no second minter within the window). 58 pools have no mint in window; ~58 other owners (max 10 pools each).
- So "LP owner = deployer" is NOT testable and is the wrong question: the owner is the launcher for ~99% of pools. What decides rug risk is who can call burn/collect on the launcher's position (launcher code/admin), and the Burn events by pool (pull timing) which v3hist liq already has.
- Gaps: only first-window mints; later transfers do not exist for direct mints; launcher admin rights not decoded (needs the launcher contract's burn authority: next step if research wants it).