Skip to content

Add Liquid Protocol hook addresses (Base)#1381

Open
moggedcapital wants to merge 1 commit into
Uniswap:mainfrom
moggedcapital:add-liquid-protocol-hooks
Open

Add Liquid Protocol hook addresses (Base)#1381
moggedcapital wants to merge 1 commit into
Uniswap:mainfrom
moggedcapital:add-liquid-protocol-hooks

Conversation

@moggedcapital
Copy link
Copy Markdown

Summary

About Liquid Protocol

Liquid Protocol is a token launch platform on Base built on Uniswap V4. Features include:

  • Dynamic LP fees — volatility-responsive fees (0.5% – 5%) via a custom dynamic fee hook
  • MEV protection — parabolic descending fees (~67% → 5% over 30s) at pool creation
  • Permanent LP — all liquidity locked forever in an LP Locker contract
  • Creator rewards — configurable fee splits to up to 7 recipients
  • Pool extensions — modular per-swap logic (vault, airdrop, dev buy, presale)

Both hooks extend the same base (LiquidHookV2) with beforeInitialize, afterInitialize, beforeAddLiquidity, beforeSwap, afterSwap, and afterSwapReturnsDelta flags.

Verification

  • Both contracts are verified on Basescan (links above)
  • Pools are already indexed in the Uniswap V4 API (e.g., pool 0x58ce3e14d82756224b34f1acaa15e4596d97a4762917a02092d606665e544669)
  • Hook submissions also filed to Uniswap/hooklist

Test plan

  • Confirm hook addresses are lowercase and valid
  • Verify pools with these hooks appear in routing results for Base
  • Confirm no regressions in existing hook routing

🤖 Generated with Claude Code

Add dynamic fee and static fee hook addresses for Liquid Protocol
on Base. These hooks power token launches with volatility-responsive
LP fees (0.5%-5%), MEV protection via descending fee modules, and
per-swap pool extensions.

- Dynamic Fee Hook: 0x80e2f7dc8c2c880bbc4bdf80a5fb0eb8b1db68cc
- Static Fee Hook: 0x9811f10cd549c754fa9e5785989c422a762c28cc

Both contracts are verified on Basescan.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Ponx
Copy link
Copy Markdown
Contributor

Ponx commented Mar 20, 2026

Confirmed this is in our queue and will be actioned in the next ~2 weeks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants