Clanker Documentation
  • Introduction to Clanker
  • Changelog
  • General
    • FAQ
    • Token Deployments
      • Farcaster Bot Deployments
      • Clanker.world Deployments
      • Preclank Deployments
      • Alternative Interface Deployments
    • Creator Rewards & Fees
    • Clanker.world Warning Tags
  • SDK
    • Quick Start
    • v4.0.0
    • v3.1.0
    • CLI
  • API
  • Quick Start
  • Public
    • Get Tokens
    • [PLANNED EOL] Get Tokens (Search)
  • Authenticated
    • Deploy Token (v4.0.0)
    • Get Token by Address
    • Get Tokens Deployed by Address
    • Get Estimated Rewards
    • Get Uncollected Fees
    • Deploy Token (v3.1.0)
    • Deploy Token w/Splits (v3.1.0)
  • References
    • Core Contracts
      • v4.0.0
        • Deployment Config
        • Fee Management Contracts
          • ClankerFeeLocker
          • ClankerLpLockerMultiple [Deprecated]
          • ClankerLpLockerFeeConversion
        • Extensions
          • ClankerVault
          • ClankerAirdrop
          • ClankerUniv4EthDevBuy
        • ClankerHook
          • ClankerHookStaticFee
          • ClankerHookDynamicFee
        • Mev Modules
          • ClankerMevModule2BlockDelay
          • ClankerSniperAuctionV0
        • ClankerToken
        • Administrative Permissions
      • v3.1.0
        • Clanker (Direct Contract Deployments)
        • LpLockerv2
        • ClankerVault
      • ClankerToken v3.1.0 and v4.0.0
    • Brand Assets
    • Audits
    • Compatible Trading Platforms
    • Deployed Contracts
    • Supported Quote Tokens
    • Core Team
    • Contact
Powered by GitBook
On this page
  1. References
  2. Core Contracts
  3. v4.0.0
  4. ClankerHook

ClankerHookStaticFee

Documentation for Clanker's Static Fee Hook

PreviousClankerHookNextClankerHookDynamicFee

Last updated 1 month ago

CtrlK

The ClankerHookStaticFee hook inherits from the ClankerHook and is used to set a static fee for both the deployed token and the paired token. The fees are able to be different from each other and have a max of 30%.

The fee unit is in Uniswap BPS, where 1 = 1/100th of a basis point. A fee of 1% is represented by 10_000, and a fee of 30% by 300_000.

The expected PoolConfig.poolData is in the form of:

struct PoolStaticConfigVars {
    // the fee taken on the deployed token when it's the input token
    uint24 clankerFee; 
    // the fee taken on the paired token when it's the input token
    uint24 pairedFee;
}

These fees are not changeable post deployment.