If you have been sizing this chain off the registry, it is roughly 226.8 times larger than it looks. The default-launch habit on it is unmapped and unclaimed. This is not an opinion, it is a count of every Initialize event the PoolManager has emitted. The chain is live, so the count climbs: the same read on 2026-07-18 returned 1,174 hooks across 40,038 hooked pools. The largest single hook on the chain runs 64,583 pools by itself.
01KZHH1GPF9ZFYSK4ENRGWVWN0
(query 8266138), which ended 2026-08-08T20:29:31Z. The permission counter is from
execution 01KZHH1HRKT13RZ4BYWS4JGKV6 (query 8266140), which ended
2026-08-08T20:29:31.099352Z. Both count distinct hooks independently and both returned
4,536, which is the read checking itself rather than us asserting it.
Three properties, each one a thing competitors cannot copy without giving up something they are keeping.
UNTOLL is a Uniswap v4 hook that holds the liquidity itself, and the source carries no withdraw, sweep, or rescue function. No address, the deployer's included, has a path to pull it, because the path is not in the code. The source is verified on Blockscout, so that is something you confirm by reading it rather than something we ask you to accept. Pads that promise fair-launch typically keep the keys that make the promise breakable. A contract that structurally cannot betray the pool is a credible commitment none of them can match while they still hold their own optionality.
Fee capture happens at the pool, independent of which interface routes the trade. Any terminal, bot, or aggregator on the chain that routes to an UNTOLL pool does so with no integration, no partnership, no BD call. No interface has to be asked, and none can be prevented from routing to it. The distribution surface is every trading interface on the chain, by default.
The same hook binds an autonomous agent to a scoped, revocable session key the contract enforces at settlement: one action, one recipient, a per-transaction cap, an expiry. A compromised agent can act, but in the demo every attempt to redirect its money reverts on chain, and you check that yourself rather than take it on faith. That converts the agent-with-money problem from a trust game into a verification game, which is the layer the agent-payment standards still lack beneath them.
The hook and the enforcement layer are open source and deployed, source-verified, on Robinhood Chain testnet, where the canonical v4 PoolManager is live at the same address as mainnet. 130 tests pass on a cleared cache.