Built on Uniswap v4The first block is now defended.
A programmable Uniswap v4 hook that runs three independent, block-native defense systems inside the pool itself — deterministic, immutable once deployed, and enforced on every swap without asking anyone's permission.
Chain
Robinhood · 4663
Hook model
3 systems, 1 slot
Fee hard cap
5% protocol-wide, immutable
Why this only exists on Uniswap v4
Hooks are the whole reason
Uniswap v3 and earlier gave every pool fixed logic and a fixed fee tier — there was no way to plug custom code into a pool's own execution. v4 introduced hooks: a contract that runs directly inside beforeSwap/afterSwap/beforeInitialize/afterInitialize, in the same transaction as the swap itself. UniGuard is one hook, occupying one pool's one hook slot — there is no earlier Uniswap version this could have been built on.
Dynamic fees are a v4 primitive
Adaptive MEV Defense and Dynamic Anti-Dump both work by having the hook override the pool's LP fee, per swap, in real time. That override mechanism — a hook returning a fee the PoolManager actually applies to that exact swap — is a v4 capability, not a wrapper bolted on top of an unmodified AMM. The pool underneath is still a completely standard Uniswap v4 pool: same PoolManager, same settlement, same router compatibility.
Launch Guard
A staged access-control state machine, tightest in the block your launch is most exposed. Per-transaction and cumulative acquisition caps, wallet-allocation percentages, and cooldowns tighten in the first stage and loosen automatically across up to three stages.
Every stage is configured before deployment, locked into immutable bytecode the instant the pool initializes, and enforced by the hook on every single swap. Sells are never subject to any restriction, at any time.
Adaptive MEV Defense
The fee itself becomes the defense — extraction gets priced in real time, on every block. A dynamic fee composes a base rate with launch-window surcharges and a realized price-impact component, recomputed live from the swap in flight.
Capped by a pool-level maximum and a protocol-wide hard cap of 5% — never uncapped, never discretionary, never silent.
Extraction priced by mathematics, not promised by a team.
Dynamic Anti-Dump
Sell-side only. Rolling buy/sell volume is tracked as an exponentially-decaying accumulator; when net sell pressure relative to current liquidity crosses a configured threshold, a fee band applies — plus a flat surcharge for any single unusually large sell.
Both decay back to baseline automatically as pressure normalizes, with zero admin action, zero off-chain triggers, and zero manual intervention required. A self-healing fee curve: sell pressure spikes cost instantly, then decays back on its own.
Enforced at every block.
Not a promise made in a Discord — a property of the deployed bytecode.
Deterministic hook address
Every hook is deployed via CREATE2 at an address mined before deployment — readable and verifiable before it ever touches a wallet.
Immutable once deployed
No proxy, no upgrade path. Every locked numeric parameter is fixed in bytecode the instant the pool initializes.
Zero custodial risk
The hook never holds funds, never operates a separate order book, and never requires a proprietary front end to trade against.
Protection you can verify
Every configuration parameter locks on-chain at pool initialization. Every swap emits a single event carrying the exact fee it paid.
No off-chain discretion decides what a trade costs after launch. Read a pool's locked configuration, its live protection stage, and its full swap history directly from the contract — see a live example at /pools or the technical breakdown at /docs.
The formula, in the open
fee = min( base + launch + impact + sellPressure, min(poolMaxFee, 5%) )
Every term is a value read from the pool's own locked configuration or computed live from the swap being executed — nothing here is discretionary.
0.50%
effective fee
- Base
- 0.30%
- Launch surcharge
- 0.20%
- Sell-pressure surcharge
- 0.00%
- Pool fee cap
- 4.00%
Illustrative, computed live from UniGuard's documented default policy via the exact same fee-math module the deployed contracts use — not a live pool. Price-impact surcharges require a real pool and are omitted here.
Not another private launchpad
The pool is real
A UniGuard-protected pool is created through the standard Uniswap v4 PoolManager, with standard liquidity, standard settlement, and full compatibility with any v4 router once the Launch Guard window ends. UniGuard never custodies funds, never operates a separate order book, and never requires trading through a proprietary front end — the defense lives inside the pool, not around it.
The logic is verifiable
The three defense systems — Launch Guard, Adaptive MEV Defense, Dynamic Anti-Dump — are deployed once per pool by UniGuard's factory at a deterministic, CREATE2-mined address, with every locked parameter readable directly from on-chain state before you ever touch a wallet. See the full breakdown at /docs.
Every parameter you set becomes a rule no one — including us — can break.