Transparency
Every value on this page is read live from the chain. Nothing here is hardcoded.
Fixed hook fee — written into the hook’s immutable at deploy time, with no setter
| Applies to | Hook fee | Creator 90% | Platform 10% |
|---|---|---|---|
| Every pool of this deployment, buys and sells alike | … | … | … |
The fee is charged on the quote side, at the same rate in both directions. It does not vary with market cap, price, block or time, and there are no volume tiers — so there is no such thing as “push the price past a threshold to pay less”. The creator signs this rate into their launch config and the chain checks it matches the hook. Changing it would require redeploying an entire Factory / Hook / Vault set; pools already launched never move over.
Uniswap protocol fee — not part of this project’s hook fee
Uniswap v4’s PoolManager lets a governance-appointed controller switch on a protocol fee for any pool, capped at 0.1% per direction, taken from the input side first. It goes to Uniswap — not to the creator, not to this platform — and we cannot control whether it changes.
Each pool shows its current value for buys and sells separately on its own page. So what we promise is that this project’s hook fee cannot change — not that your total trading cost is fixed forever, and certainly not that the execution price is fixed.
Risk disclosure
- The beneficiary is permanent after launch. There is no rotation or recovery path in the contracts — that is the price of “the platform cannot change your payout address”. If the address is frozen by the quote issuer or its key is lost, that pool’s share can never be claimed. Use a multisig whose signers you can rotate.
- Quote freezes. Issuers of USDC and equity tokens can freeze addresses; a freeze also affects redeeming FeeVault claims. Native ETH carries no such risk.
- A hook bug freezes the pool. The initial position is held unconditionally and forever by PermanentPositionLock, with no rescue path. This is the single largest residual risk in the design.
- Ordinary MEV. This protocol does not remove sandwiching, front-running or the price impact of large sells. A fixed fee only removes the incentive to move the price in order to get a different fee; execution price still moves with pool supply and demand.
- Rounding. Fees round down, so splitting one trade into n trades saves at most n−1 of the quote’s smallest unit. That is not a volume discount, and it does not make every route cost exactly the same.
- Protocol fee. See the section above — Uniswap governance can change it.
- Pilot parameters. Early launches use pilot M₀ values, and M₀ is written into that pool’s record at launch.
Quote assets — M₀ is the opening FDV, the minimum first buy includes the hook fee
This list comes entirely from the chain: addresses are collected from the Factory’s QuoteConfigSet events, then the current quoteConfigs is read back for each one. Symbols and decimals are read from the token contracts. There is no hardcoded quote list in this page.
Reading the on-chain quote whitelist…
Constants and permissions
Contract addresses (chainId 4663)
No upgrades, no pause, no setter that touches a launched pool. The fee is a constructor argument — governance cannot change it even for future launches, and can only adjust the quote whitelist, M₀, the minimum first buy, and the platform recipient for future launches (behind a ≥ 48h timelock). The underlying V4 protocol fee is set by Uniswap governance; it is listed separately and is not part of this protocol’s fee promise.