HALO
Docs
Ethereum
BUILT ON UNISWAP V4

Fair liquidity.
Shared value.

Halo protects long-term liquidity by rewarding time, not just capital.

Read how it works

Your overview

NOT CONNECTED
Total value locked
$0.00
Fees earned (halo protected)
$0.00
Active positions
0

Protection in action

THE CONTRACT'S OWN FORMULA
0 blocksTENURE = 300 blocks (~1 h)
100% of this position's fees go back to the liquidity that stayed
POSITION AGE 0 blocks

Network status

NOT DEPLOYED
Total value locked
$0.00
Fees redistributed (all time)
$0.00
Pools
0

Every figure on this page is a chain read or a formula. Nothing here is illustrative — a protocol with no pools genuinely has none.

How Halo works

1. Liquidity added
2. Time goes by
3. Fees redistributed
4. Long-term wins

The toll is taken from fees only. v4 hands the hook the accrued fees as a value separate from the principal, so a withdrawal returns every wei of capital no matter what the toll says.

Built for Uniswap v4

Halo is a hook that ensures fees belong to the liquidity that stayed.

Transparent. Verifiable. Fair.

Hooknot deployed
Hook flags0x0541
Ownernone
Withdraw functionnone

Your positions

AWAITING DEPLOYMENT
PoolRangeLiquidity TenureToll if you exit nowFees
No pool has been deployed yet Once it is, each position you hold appears as a row above: how long it has been in place, and what share of its fees would go back to the pool if you left right now. Both come from the hook, not from this page.
Tenure counts in blocks and is shown against TENURE_BLOCKS = 300 Toll applies to fees only — never to the capital in the position

Halo pools

AWAITING DEPLOYMENT
PairFee tierTVL Volume 24hFees redistributedTenured share
No pools A pool joins Halo at creation by naming the hook address in its PoolKey. Any pair and any fee tier can — Halo does not change the fee rate, only where the fees end up.
TENURED SHARE—Portion of liquidity past full tenure
JIT ATTEMPTS 24H—Positions exited inside one block
AVG TENURE—Liquidity-weighted, in blocks

Fees redistributed

AWAITING DEPLOYMENT
no TollTaken events to replay
——

This chart is a replay of the hook's own events, so anyone can recompute it from the chain and get the same picture. With no pool there is nothing to replay.

Where it went

TO TENURED LIQUIDITY—
HELD FOR NEXT SWAP—
KEPT BY THE PROTOCOL0.00

The last row is not waiting on a deployment. It is 0 by construction — the contract has no treasury and no withdraw function, so there is no path by which it could ever be anything else.

Tenure distribution

AWAITING DEPLOYMENT
0–1 blk
<10
10–60
60–150
150–300
tenured

How much of the pool's liquidity sits in each tenure band. The leftmost bucket is the one Halo exists for.

There is nothing to govern

TENURE_BLOCKS is a constant in the bytecode. The hook has no owner, no setter, no proxy and no withdraw function, so there is no parameter a vote could move and no treasury a vote could spend. This page exists to say so rather than to pretend otherwise.