# Introducing Clanker v4

> Clanker v4 will fundamentally alter the way creators, traders, and teams think about liquid markets

**Published by:** [dish](https://paragraph.com/@dish/)
**Published on:** 2025-06-17
**Categories:** clanker
**URL:** https://paragraph.com/@dish/introducing-clanker-v4

## Content

Clanker v4 marks a significant step forward, transitioning from Uniswap v3 to Uniswap v4 and adopting a modular contract system. This upgrade not only boosts overall user configurability and accelerates future feature integrations, but also introduces dynamic fee mechanisms—designed to attract external liquidity providers and sustain creators' liquidity rewards over the long term. Additionally, creators can now utilize multiple LP positions to optimize reward generation, alongside improved visibility into unclaimed fees. These enhancements position Clanker to deliver a more flexible, transparent, and creator-friendly experience, setting the stage for us as we expand our value proposition and strengthen alignment across our ecosystem. The Clanker v4 contracts are audited by Macro & Cantina and integrations with aggregators / routers are actively being completed. Soon, we'll be publishing the technical specifications, updated SDK, and a comprehensive implementation guide.Key FeaturesCustomizable Fee Structures: Configure fee tiers, collect fees in only a specified token, or set dynamic fees based on trading activity Custom Liquidity Distributions: Create your own liquidity distribution curve by placing up to 7 LP positions to make more or fewer tokens available for purchase at specified prices. Available via SDK or direct contract interaction Multiple Reward Recipients: Set up to 7 rewards recipients at launch, each modifiable by a paired “admin” address Streamlined Rewards: Create multiple tokens paired with WETH and claim all the WETH rewards in one transaction, as rewards are claimed on a per-token basis MEV Modules: Modify the initial pool’s behavior at the time of deployment with various MEV modules. Our initial module, which delays trading of deployed pools by two blocks, is the first installment of our sniper-aware technology Clanker Extensions: Vaulting and Creator Buy / Dev Buy functionality are now grouped under Clanker Extensions. Extensions are contracts that can be used to add new functionality to the token deployment process. Up to 90% of the token supply may be allocated to extensions in totalVaulting: Now vault up to 90% of the token supply with a reduced minimum lock of 7 daysCreator Buy / Dev Buy: Any amount of ETH may be used to execute a Dev Buy upon creating a token (remains the same). For non-WETH paired tokens, the paired token must have a WETH <> Paired Token Uniswap v4 pool in order to complete a Dev Buy (updated)Airdrops (coming soon): Set airdrop allocations upon token creation with vesting parameters. Tokens are then allocated to recipients and claimable after a minimum of one day. Contract support is live, frontend and SDK support soon to follow.Fee MechanismsFees can be configured to be either static or dynamic. Static Fees Static fees can be configured on a per-token basis, meaning token creators can decide how much of each input token on the swap is collected as a fee. Full customizability is available via deployments through the SDK.E.g., Clanker token fee = 1%, paired token fee = 2%Swapping the Clanker token in exchange for the paired token incurs a 1% feeSwapping the paired token in exchange for the Clanker token incurs a 2% feeDynamic Fees Dynamic fees are collected in both the Clanker token and paired token. A base fee is set, which is a static fee collected on each swap. A variable fee is added on top of the base fee, based on the price impact of the current swap and the accumulated volatility from previous swaps. Generally, the more a token’s price is moving over a short period of time, the higher the effective fee is that will be collected. Full customizability is available via deployments through the SDK. Additional information on the dynamic fee mechanism will be provided in the technical specifications. Clanker Protocol Fee The Clanker fee is now collected at the pool level, meaning it applies to other LPs that participate in the initial pool. This fee is 20% of the effective fee, which is collected in addition to the static / dynamic fee.Liquidity DistributionUp to 7 LP positions may be added during the token creation process to enable various liquidity distributions in the pool. Previously, all tokens were placed in a single LP position from the starting price to infinity. Now, Clanker token liquidity is able to be more / less concentrated in specific ranges, depending on the liquidity profile that the token creator wishes to set. This is available via deployments through the SDK. Additional detail on placing multiple LP positions to come in the updated SDK documentation.Reward RecipientsToken creators accrue rewards from trading activity that occurs against the tokens that are initially placed in the trading pool during token creation. At least one rewardAdmin + rewardRecipients pair is required to be set. Up to a maximum of 7 of these pairs may be included. For each pair, you must set the % of trading fees the rewardRecipients will receive using rewardBps. rewardBps is denominated in basis points (1 basis point = 0.01%) and the sum of rewardBps across all pairs of recipients must be 10,000 (100%). Can Be ChangedAny given rewardAdmin may change its paired rewardRecipients(e.g. rewardAdmin #1 can change rewardRecipients #1)Cannot Be ChangedAny given rewardAdmin cannot change a rewardRecipients that it is not paired with (e.g. rewardAdmin #1 cannot change rewardRecipients #2)rewardBps cannot be changed post token deploymentReward ClaimingBehind the scenes, Clanker contracts now automatically collect the fees earned on the LP position(s) and send them to a separate fee locker for claim. The rewards claiming process is now on a per-token basis rather than a per-token pair basis (recipients may claim WETH for multiple tokens they created in one transaction, rather than collecting WETH + token #1 in one transaction then WETH + token #2 in another). Claiming rewards for a given token / recipient is still a publicly callable function.MEV ModulesModify the initial pool’s behavior at the time of deployment with various MEV modules. The initial module adds a 2 block delay between token / pool deployment and when it is enabled for trading. This is to prevent snipers from sniping in the same block of deployment. Future MEV module upgrades will explore auctioning off the first swaps on pools for the benefit of creators. For more information, see Lily's (head of protocol) article: Minimal Viable Auction for New Assets on Priority Ordered L2s Additional information on MEV modules will be provided in the technical specifications.ExtensionsVaultingVaulting, a Clanker extension, allows for token creators to set aside tokens before they are placed in the initial liquidity position(s). Up to 90% of the token supply may be vaulted and allocated to extensions in total. lockupDuration refers to the time (in seconds) since token creation before vesting begins. The minimum enforced lockupDuration is 7 days. vestingDuration refers to the time (in seconds) during which vesting occurs. Vesting occurs linearly and begins once lockupDuration ends. Note that the lockup period does not constitute a traditional vesting cliff where vesting starts at the beginning but tokens are locked until the cliff - no tokens are vested until lockupDuration ends. admin can claim tokens anytime once the lockupDuration ends. The amount will vary depending on both the amount of time that has passed since the lockupDuration ended and whether some of the tokens have already been claimed. The claim is a public function (anyone can call the claim function) and can be triggered multiple times, and however many tokens are vested + unclaimed at that time will be available. Upon triggering a claim, vested + unclaimed tokens are sent to the admin address. Can Be ChangedThe admin of the vaulted tokens may designate a new admin address, thus relinquishing their control (e.g. admin at deployment is Team EOA #1, who can then change the admin address to Team Multisig #1)Cannot Be ChangedNeither lockupDuration nor vestingDuration can be changed post-deploymentCreator Buy / Dev BuyAny amount of ETH may be used to execute a Dev Buy upon creating a token (remains the same). For non-WETH paired tokens, the paired token must have a WETH <> Paired Token Uniswap v4 pool in order to complete a Dev Buy (updated).Airdrops (coming soon)Set airdrop allocations upon token creation with vesting parameters. Tokens are then allocated to recipients and claimable after a minimum of one day (lockupDuration minimum is one day). Once available for claim, anyone can initiate the claim process for a given airdrop recipient and the given airdrop recipient will receive the tokens. Lockups / vesting work the same way as they do when vaulting tokens.Beyond v4While our primary focus remains on ensuring a seamless v4 integration and comprehensive post-launch support, we've also begun actively exploring new strategic opportunities for the Clanker token and our role in the ecosystem as a whole. This includes evaluating fresh approaches to tokenomics, incentive structures, and partnerships aimed at deepening our ecosystem's value and sustainability.

## Publication Information

- [dish](https://paragraph.com/@dish/): Publication homepage
- [All Posts](https://paragraph.com/@dish/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@dish): Subscribe to updates

## Optional

- [Collect as NFT](https://paragraph.com/@dish/introducing-clanker-v4): Support the author by collecting this post
- [View Collectors](https://paragraph.com/@dish/introducing-clanker-v4/collectors): See who has collected this post