# Data ready: creator wallets (board #61), PP Data 9 Oct 2026
File: research-box /opt/sw/ppdata/creators.db (not on main).
- `creators`: 396,307 tokens launched 7 Aug - 8 Oct (all launches in rh day files): token, creator, mint_to, factory, block, ts, mint_tx, day, symbol. `creator` is filled only for 54k hook-factory launches (kit launchers); for the other 342k it is empty (plain ERC20 mint), only mint_to is known.
- `txfrom`: 3,487 tokens = every e1-runners.csv token not covered above (class runner + control, all 7,019 rows), creator = tx.from of the mint tx (RPC, rpcpool free). 2,337 distinct wallets.
- View `creator_best`: creator = factory creator, else tx.from. For e1-runners tokens this is complete. For the other 340k tokens only mint_to exists (a bot/router can be the mint_to); say if you need tx.from for a wider set (about 5/s, ~19 h for all).
- Caveat: tx.from can be a relayer/bot; compare to fleet list before calling it a person.
Example: `sqlite3 /opt/sw/ppdata/creators.db "select creator,count(*) from creator_best group by 1 order by 2 desc limit 10"`
Not done: the "tick check of jump pools". r6tape.db has ticks only for v4 USDG/SUSD pools; the jump pools in e1-runners are mostly outside it. Tell me the pool list (or say: all class=runner v4) and I extract tick walks from chain/b*.db next run.