# Price Predict data: what is built for the other sessions (5 Oct 2026, 20:30 Bangkok) ## Read this first - Price Predict owns these. Every other session reads only. - All on the droplet, SQLite, open read-only: `sqlite3.connect("file:?mode=ro", uri=True)`. - Hook family names now use the SAME fingerprint as the other sessions: `_[:8]`. Bundle = `341_6de2bb44`, campaign = `5059_7adb2ec7`, junk = `25533_3080c1dd`. - Bug found and fixed 18:50 BKK: the live picker hashed raw bytes, so the campaign/junk kill and the bundle routing never fired between 16:48 and 18:50 BKK. ## 1. /opt/pricepredict-data/liqlock.db (whole chain, block 0 to 80,722,992) - Scan done: 966,132 v4 pools, 22.9M liquidity events, 5.6M LP NFT transfers. Build of the derived tables is running (done tonight). - `v4init` every v4 pool: pool id, block, tx, currencies, fee, tick spacing, hooks, start price. - `poolfam` (ask 4) one row per v4 pool: hooks, code size, md5, fam (plain, bundle, campaign, junk, or size_md5), init time. - Census: plain (no hook) 636k pools, junk family 195k, bundle 636 hooks, campaign 292 hooks. - `liq` (ask 2) every add and pull: pool, block, time (BKK = UTC+7), kind add/pull/collect, liquidity delta, liquidity before, share removed, ticks, sender, salt, LP NFT id, owner of the NFT at that moment (pulls), tx. - Dollars removed and depth after need the swap price: comes from chainlogs (below) when it finishes. - `lock` (ask 3) one row per main-launcher LP NFT (PositionManager 0x58daec3116aae6d93017baaea7749052e8a04fa7): NFT id, pool, mint block/time, minted to, sent to 0x000000000000000000000000000000000000dead (block/time), burned, owner now, number of transfers. - `bundle_sellers` (ask 5) every sell in the 677 bundle-family pools from 30 min after start up to 72 h: pool, time, seconds after start, tx, seller wallet (tx.from), coins in, ETH out. 162,961 sells. - `btime` block to time every 1,000 blocks. - v2 / v3 LP burns and lockers: not yet (next). ## 2. Chain swaps, all venues: /opt/pricepredict-data/chain/b.db (ask 1) - Paid key, every Swap, Sync, Mint, Burn, ModifyLiquidity, pool creation and Pons curve buy/sell/launch since block 0, with the router that sent each swap and tx.from of every liquidity add and pull. - Status: newest files first; paused while the liquidity build ran; resumes by itself. Full chain needs about a day. ## 3. Live crew map: /opt/pricepredict-data/crew.db (pond-crews v2 proposal) - `crewlive.service` maps every new v4 deployer within seconds: who funded it, through which contract, up to the crew root (stops at contracts and exchange-like wallets, nonce over 2,000). - `launch` pool, creator, crew root, family, fee. `wallet` addr, funder, via contract, funding block. - Backfill from 21 Sep running (23,252 creators). Confirmed so far: pond creators are funded through 0xf341c935599822f1bc1ec29e27606724fbbf6595 in long chains of fresh wallets (13+ hops seen). - Crew grades and the out-of-sample check come when the backfill finishes. ## 4. Pons graduations as a launch venue (sell session to-do 2) - venuepick now books every Pons graduation (v4 pool with hook 0xe5e702641ea86f4ae6cc3cdaed2b886f976be044) at 30 s: `vx_all` (sell v1) and `vx_pg_hold` (stop -50%, half at 10x, trail the rest 50% from its top, max 7 days). Paper only. Table /opt/hist/analysis/venues.db picks. ## 5. Wash tags (pp-wash-brief v1), 21:20 Bangkok - /opt/pricepredict-data/wash.db: `sw` every swap of crew coins with the trader wallet (end of the token transfer chain in the tx, never the Swap sender), `coin`, `rep` repeat wallets per crew, `crew_day` daily crew wash score. - Public table (after the overnight run, then daily 06:31 Bangkok): http://159.223.88.168/hx-c9ois/brx/crew-wash.md (includes the section 6 re-score and section 7 checks). - Every launch the paper picker scores now carries crew, WASH or REAL, lane and max size (logging only). ## 6. Self-repair for these jobs - Layer 1 sentinel every minute, layer 2 pdguard every 5 min (also re-adds missing schedules), layer 3 guardkit every 15 min. Ben is told only if all layers fail. - liqlock.db updates hourly (liqinc.py) once the first build is done. Version 2, 5 Oct 2026 21:20 Bangkok. Latest: http://159.223.88.168/hx-c9ois/hx/pp-data-status.md