Integrations · Uniswap v4 hooks
Ripples’s Uniswap v4 hook
Ripples — 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
- 0xba7401628167fbcd8f9db9f6ad2dda72ab41eacc
- First pool HEY read
- 2 Nov (block 104,102,272)
Who built it, and why HEY says so
- Tied to
- RipplesShipping
- 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 liquidity is added, before liquidity is removed, before each swap and after each swap; may change a swap’s amounts before and after it.
beforeInitialize— before a pool is createdbeforeAddLiquidity— before liquidity is addedbeforeRemoveLiquidity— before liquidity is removedbeforeSwap— 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
- Published source code
- Not read — HEY has not read the explorer’s source record for this hook.
- Proxy
- Not read — HEY’s contract watch has not checked this address for a proxy.
Uniswap’s hooklist
Uniswap’s public hooklist, as HEY last read it, does not carry this hook. Read 6 Nov.
Pools using it
17 pools on tokens HEY tracks use it, initialised between block 104,102,272 and block 110,732,268.
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 |
|---|---|
| 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 | 0 · includes earlier pools read back |
| 5 Oct | 0 |
| 12 Oct | 0 |
| 19 Oct | 0 |
| 26 Oct | 0 |
| 2 Nov | 13 |
| 9 Nov (so far) | 4 |
When
- Created
- 2 Nov (block 104,100,633)
- First pool initialised
- 2 Nov (block 104,102,272)
- Newest pool HEY read
- block 110,732,268
- HEY first decoded it
- 2 Nov
- Creation checked
- 10 Nov
Related ship
- Its deployment
- The follow-up deployment it counts through
- Ripples’s latest ship
- Code changes, week of 2026-11-02 – 2026-11-08 · 4 Nov
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.
- Upgradeability: not known. Not read — HEY’s contract watch has not checked this address for a proxy.
- Published source code: not known. Not read — HEY has not read the explorer’s source record for this hook.
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.