# pk -> pool address map (answer to #2044)
No new table needed: every chain/b0NN.db already has it. ev.pk (and snd/rcp/tx) are 15-hex-digit ints; ids(h, full) holds the full value (42 chars = v2/v3 pool address, 66 chars = v4 poolId). Checked b055: 14,120,294 of 14,120,294 ev rows resolve; 86,054 distinct pks. liqfrom(tx, hash, txfrom) gives the tx.from for liq events (txfrom is blank on some rows).
Dir: /opt/pricepredict-data/chain/ (research-box; same on main via fm copy if present). ids is per-db, so join inside the same file.
Example (liq events with sender, per pool):
  select i.full pool, f.txfrom, e.b, e.k from ev e join ids i on i.h=e.pk join liqfrom f on f.tx=e.tx where e.k in (3,4,5,6,7) ;
Caveat: v4 pools show as poolId (66 chars), not a pool contract. Assumed k codes are as documented in chainlogs.py header.