Integrations · Uniswap v4 hooks
A Uniswap v4 hook on Robinhood Chain
HEY holds this Uniswap v4 hook but does not tie it to a published project.
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
- 0xbf8f3ddec8f35329ffb211c2b3ae17724ff35000
- First pool HEY read
- block 86,107,106 (time not read yet)
Who built it, and why HEY says so
- Tied to
- No published project. HEY’s reading of its creation: created through a launch protocol’s factory; not tied to a published project.
- Why no name
- HEY names a project only when it lists the hook under it — never from a name, a listing or the pools that use it — and never names the account that created a hook.
Callbacks its address declares
Called after a pool is created.
afterInitialize— after a pool is created
Decoded from the address itself: what the PoolManager will call, never what the code does and never whether it is safe.
Source
- Verified source
- 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 13 Oct.
Pools using it
1 pool on tokens HEY tracks use it, initialised between block 86,107,106 and block 86,107,106.
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 |
|---|---|
| 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 | 0 · includes earlier pools read back |
| 5 Oct | 1 |
| 12 Oct (so far) | 0 |
When
- Created
- 11 Oct (block 86,107,106)
- First pool initialised
- block 86,107,106; time not read yet
- Newest pool HEY read
- block 86,107,106
- HEY first decoded it
- 11 Oct
- Creation checked
- 11 Oct
Related ship
- Its deployment
- None: HEY does not list this hook under a project.
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.
- Verified source: not known. Not read: HEY has not read the explorer’s source record for this hook.
- First pool’s time: not known. HEY holds the first pool’s block, not its time.
Evidence
- No standing receipt: HEY stands behind v4hook:4663:0xbf8f3ddec8f35329ffb211c2b3ae17724ff35000 only while it lists the hook under a project.
- The contract on the explorer
- As data:
GET /api/v4-hooks/0xbf8f…5000
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.