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

Mev Modules

PreviousClankerHookDynamicFeeNextClankerMevModule2BlockDelay

Last updated 1 month ago

CtrlK
  • Functionality
  • Current Mev Modules

Clanker v4.0.0 introduces the ability to modify a pool's behavior at the time of deployment through different MEV modules. The goal of these modules is to lessen the negative impact that snipers have on users.

Functionality

MEV modules are specified on pool deployment and are enabled after a token has finished deploying. This happens after extensions have finished executing to allow extensions to either make swaps or add liquidity to the pool.

MEV Modules are active until they disable themselves or expire after 2 minutes. We have this expiry period as a safeguard in case the pool's underlying sequencer environment changes and the MEV module breaks. Additionally, liquidity adds are restricted during the MEV module's operation, as we want to reserve the ability to use the donate() function to send payments to only the beneficiaries of the original LP position.

Current Mev Modules

Clanker has two mev modules currently written:

  • ClankerMev2BlockDelay: Prevents swaps on freshly deployed pools for 2 blocks to stop snipers from trying to search in the same block of deployment.

  • ClankerSniperAuctionV0: Auctions off the first few swaps for freshly deployed pools, giving the auction proceeds to creators.