Check a hook
Nine checks on any deployed Uniswap v4 hook, run against the chain at one block. The verifier signs the result so anyone can check it, and rerun it.
What is checked
Each check reads the deployed code and calls the hook at a pinned block. The same address and block give the same result for anyone. A pass is evidence about one property at one block, not an audit.
npm install -g @probecli/cli
probe check 0xYourHook
probe check 0xYourHook --publishContract code at the address
There is code at the address, followed through a proxy when there is one.
Permission flags are valid
The flags encoded in the address are a combination the PoolManager accepts.
Every enabled callback is implemented
Each callback the flags turn on exists in the code, so pool actions do not revert.
Bound to the canonical PoolManager
poolManager() returns the Uniswap v4 PoolManager on this chain.
Callbacks refuse other callers
Each enabled callback is called from an outside address and must revert. The same call from the PoolManager is tried for comparison.
Code cannot be replaced
The hook is not an upgradeable proxy whose behaviour can change later.
No single key controls the hook
Ownership is renounced, absent, or held by a contract rather than one key.
No self-destruct or delegatecall
Neither opcode appears in the code that runs.
Source code is verified
Sourcify has a matching source, so anyone can read what the hook does.
Recently checked
Loading checked hooks…
The standard checks catch setup mistakes, not logic bugs. For tests written against your hook's own behaviour, fund a job and operators are paid for each case the verifier reproduces.