Every Uniswap v4 hook deployed on Robinhood Chain.
Read from chain, not from the registry.

The 2026-07-18 sweep, in four numbers.

If you sized this chain off the registry on 2026-08-17, it was roughly 137.6 times larger than it looked. That is not an opinion. It is a sweep of every Initialize event the PoolManager has ever emitted.

Census of 2026-08-08: 4,536 distinct hooks across 110,487 hooked pools, out of 315,232 pools total (35.0% carrying a hook), latest pool 2026-08-08 20:11:38 UTC. Source: Dune, uniswap_v4_robinhood.poolmanager_evt_initialize, query 8266138, execution 01KZHH1GPF9ZFYSK4ENRGWVWN0. The four numbers above are the fixed 2026-07-18 sweep and are what the per-hook table is built from. The 2026-08-17 read is at /read/; the chain is live, so every total here is a floor, never today's count.

Reproduce it or falsify it.

Every v4 pool emits Initialize from the PoolManager, and that event carries the pool's hook address in its data. So the complete set of hooks is derivable from the complete set of Initialize events. No registry, no index, no API.

The canonical CREATE2 deployer is live at 0x4e59b44847b379578588920cA78FbF26c0B4956C. That matters more than it sounds: v4 encodes hook permissions in the low bits of the hook address, so without a deterministic deployer you cannot land a hook at an address that encodes the callbacks you registered.

The 60 hooks that run 94.5% of the pools.

This file lists 60 of the 1,174 distinct hook contracts counted in the 2026-07-18 sweep. Those 60 account for 37,826 of the 40,038 hooked pools in that sweep. For the chain-wide totals see the census line above. 51 of the 60 have verified source. Full rows in the CSV and the JSON.

What the numbers do and do not say.

• Pool counts are lifetime Initialize events, not active pools. A pool that was initialized and never traded still counts.
• SaturnOmnichainV4Hook appears as 27 separate deployments sharing one codebase. They are counted individually here, 405 pools in aggregate.
• Contract names come from verified source on Blockscout. Entries without it are listed by address only.
• Deployer address is not a useful team signal on this chain, because most hooks are deployed through the shared CREATE2 deployer rather than directly.

Corrections wanted. This is read from chain, but the reading could still be wrong. If a hook's permissions or pool count is wrong here, say so and it gets corrected, particularly if it is one of the entries listed by address alone and you would rather be named. Reach @untolling.