Integrations · Uniswap v4 hooks
Loom’s Uniswap v4 hook
Loom — HEY ties this Uniswap v4 hook to it: deployed by the account that launched the project’s token, through a deterministic deployer.
What it is
A Uniswap v4 hook contract: the PoolManager calls it at the moments its address declares, in every pool created with it.
- Contract
- 0x4eafa1c72ca13c6a9f93095b686afc7dd5bc60cc
- First pool HEY read
- 29 Sep (block 75,247,269)
Who built it, and why HEY says so
- Tied to
- LoomShipping
- On what basis
- Proven on chain
- How
- Deployed by the account that launched the project’s token, through a deterministic deployer: the account that launched its token created it through a deterministic deployer.
Callbacks its address declares
Called before a pool is created, before each swap and after each swap; may change a swap’s amounts before and after it.
beforeInitialize— before a pool is createdbeforeSwap— before each swapafterSwap— after each swapbeforeSwapReturnDelta— may change a swap’s amounts before itafterSwapReturnDelta— may change a swap’s amounts after it
Decoded from the address itself: what the PoolManager will call, never what the code does and never whether it is safe.
Source
- Verified source
- The explorer holds no verified source for it.
- Proxy
- HEY’s contract read detected no proxy at this address.
Uniswap’s hooklist
Uniswap’s public hooklist, as HEY last read it, does not carry this hook. Read 8 Oct.
Pools using it
1 pool on tokens HEY tracks use it, initialised between block 75,247,269 and block 75,247,269.
Pools initialised with the hook on a token HEY tracks (HEY keeps no other pool): a count, the first and last init block, and the pools HEY recorded per UTC ISO week over the last 12 weeks. Context only: never an order, a score or a leaderboard.
Pools HEY recorded, week by week
Counted by when HEY recorded each pool, not by its block time: HEY keeps no block-time mapping. A week before HEY began recording is not zero — nothing was recorded then — and the week it began also holds every earlier pool it read back from the chain.
| Week | Pools recorded |
|---|---|
| 20 Jul | not recorded yet — before HEY began |
| 27 Jul | not recorded yet — before HEY began |
| 3 Aug | not recorded yet — before HEY began |
| 10 Aug | not recorded yet — before HEY began |
| 17 Aug | not recorded yet — before HEY began |
| 24 Aug | not recorded yet — before HEY began |
| 31 Aug | not recorded yet — before HEY began |
| 7 Sep | not recorded yet — before HEY began |
| 14 Sep | not recorded yet — before HEY began |
| 21 Sep | not recorded yet — before HEY began |
| 28 Sep | 1 · includes earlier pools read back |
| 5 Oct (so far) | 0 |
When
- Created
- 29 Sep (block 75,240,381)
- First pool initialised
- 29 Sep (block 75,247,269)
- Newest pool HEY read
- block 75,247,269
- HEY first decoded it
- 1 Oct
- Creation checked
- 2 Oct
Related ship
- Its deployment
- The follow-up deployment it counts through
- Loom’s latest ship
- Code changes, week of 2026-10-05 – 2026-10-11 · 9 Oct
What HEY does not know
- Routing allowlist: not known. Whether a router or aggregator routes swaps through this hook: HEY reads no routing allowlist.
- Audit: not known. Whether its code was reviewed by an auditor: HEY reads no audit report for this hook, and a callback list is never a safety verdict.
- Dynamic fee, from the chain: not known. Whether its pools use a dynamic fee: HEY does not keep a pool’s fee field.
Evidence
Uniswap is a trademark of Uniswap Labs. HEY Research Lab is not affiliated with or endorsed by Uniswap Labs. HEY reads Uniswap v4 pools from the public chain; this page describes what HEY found, not a partnership, an endorsement or a recommendation.