A Uniswap v4 hook contract whose address declares 3 callbacks, first read initialising a pool at block 49,777,833. HEY attributes it to Cache Flow: an address linked to the project — the account that launched its token — created it; listed, not counted as a follow-up deployment.

What it is

Uniswap v4 hook

Callbacks its address declares

beforeAddLiquidity, beforeSwap, afterSwap. What the PoolManager will call, not what the hook does.

First pool HEY read

Block 49,777,833

Attributed to

Cache Flow: an address linked to the project — the account that launched its token — created it; listed, not counted as a follow-up deployment

How it is tied

Created by an address linked to the project (the account that deployed its token or a contract it lists). Read from the chain’s creation record and the project’s own record of the address; listed, never counted as a deployment.

Uniswap’s hooklist

Listed in Uniswap’s hooklist as CacheTollHook · listed as dynamic fee, swap access: governance. A third-party listing, shown as context: it does not tie the hook to a project.

The hook’s page

Who built this hook, its pools and what HEY does not know

Where HEY read it

The Robinhood Chain explorer · View at the source ↗

When it happened

2026-08-30, dated by the source to the minute

HEY first saw it

2026-10-01 (10d ago)These are two different clocks: when the work happened, as the source dates it, and when HEY first read it.

Counts toward building

No. It is context: it does not change activity status or Build Momentum.

What it does not say

A contract record says what the chain shows about a contract. It is not a safety check, and it does not say who runs the contract.