On Clanker, deploying a token itself is free, but your real cost is not in deployment—it is in how much of the trading fee share you keep for yourself. Clanker's contract does not charge a creation fee at deployment. It takes a 1% fee from every trade, then splits it among the protocol, you, and the interface party according to the ratio you set at deployment. What you really need to verify before clicking deploy is how much you set for the creatorReward parameter, and who the four recipient addresses point to. If you fill it in wrong, it cannot be changed after going on-chain.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Two Ways to Launch: Social Post or Direct Contract Call
Clanker's original method is to post a cast on Farcaster, tag @clanker, and include the token name, ticker, and image. A backend agent then deploys it for you. This path has the lowest barrier to entry, but it depends on your Farcaster account's Neynar score and has daily deployment limits. If you just want to quickly test launching a meme coin, this is the easiest entry point.
A more controllable way is to directly call the deployToken function on the Clanker contract, or use the official TypeScript SDK. The SDK deployment script requires you to configure your private key, chain (usually Base), and token parameters, then call clanker.deployToken(). This path is suitable if you need to precisely set every parameter before deployment, or for batch deployment scenarios. Both methods ultimately call the same contract logic; the only difference is who helps you fill in the parameters.
Fee Structure: Deployment is Free, Trading Fees Are the Real Cost
Clanker's core cost is not in deployment, but in trading. Every trade generates a 1% fee. The distribution rules are clearly written in the contract documentation: the protocol takes 20%, the creator can take up to 80%, and the remainder goes to the interface party.
But that 80% is not automatically given to you. The creatorReward parameter you set in RewardsConfig determines your upper limit. If you leave it blank or set it low, the protocol and interface party shares will be correspondingly larger. You need to actively set creatorReward close to 80, rather than accepting the default value. The creatorAdmin and creatorRewardRecipient addresses must also be controlled by you—the former manages locked tokens and metadata, while the latter receives the fee share.
There is an early version rule difference to note: tokens deployed before November 2024 used a 60/40 split (protocol 60%, creator 40%), and the creator additionally received 1% of the token supply. The new rule has changed to give creators up to 80%, but there is no longer that 1% extra token allocation. If you see a tutorial that says "launching a token gives you 1% of the supply," that is the old rule and no longer applies.
Permissions You Must Verify Before Deployment
Tokens deployed by Clanker have several permission points that cannot be revoked once on-chain.
Fixed supply of 100 billion tokens. The total supply of tokens deployed by the Clanker contract is fixed at 100,000,000,000 (one hundred billion), with no minting function. You do not need to verify this point, but you need to accept it—if you want a different supply, Clanker is not the right tool.
Vault locking is optional but limited. You can choose to lock a portion of tokens in the ClankerVault contract, with a maximum lock-up ratio of 30% and a minimum lock-up period of 30 days. The creatorAdmin for the lock-up is the address you specify, meaning only this address can manage that portion of tokens. If you do not lock up, the entire supply goes directly into the liquidity pool.
Metadata update rights belong to creatorAdmin. The token's metadata field can be modified by creatorAdmin, but the context field is immutable. If you set creatorAdmin to a multisig or cold wallet, metadata changes need to go through a multisig process; if you set it to a hot wallet, it is more convenient but riskier. This choice must be made at deployment.
The liquidity pool's LP NFT is locked in the LpLockerv2 contract. The LP NFT for the Uniswap V3 pool (1% fee tier) deployed by Clanker is not given to you; it is locked in the contract, and fees are automatically distributed according to the ratios above. You do not need to and cannot manually withdraw LP to remove the pool. This is Clanker's "anti-rug" design, but it also means you cannot exit by removing liquidity.
A Judgment Call: The Interface Party's Share
RewardsConfig has two interface-related addresses: interfaceAdmin and interfaceRewardRecipient. If you deploy through a third-party interface or SDK, the interface party may take a portion of the fees. In the official SDK example, interfaceAdmin is usually set to Clanker's official address. If you call the contract directly yourself, you can set the interface party's share to zero or to another address you control, keeping the 80% creator share and the remaining interface share all under addresses you own.
This judgment depends on which entry point you use to deploy. If you do not care where that share goes, using a ready-made interface is easiest; if you want to maximize your own share, call the contract directly and explicitly set each address.
Completion Criteria
It is not "the transaction succeeded," but rather: you find the token contract address on a block explorer and confirm the total supply is 100 billion; you confirm in Clanker's RewardsConfig that creatorReward is the value you expected (close to 80); creatorAdmin and creatorRewardRecipient are addresses you control; if you set up a Vault, the lock-up ratio and duration match your plan. After deployment, make a small test trade first to confirm the fee split arrives according to your set ratio, then consider whether to invest more effort into community or liquidity operations. Clanker only builds the token and the pool; whether anyone trades the token afterward is not something the contract can decide.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
References
- Clanker Documentation·Clanker (Direct Contract Deployments), page published or updated: 2026-06-30; verified: 2026-10-18.
- The Block·Clanker team earns $13 million in revenue from over 200,000 tokens on Base in just five months, page published or updated: 2025-04-03; verified: 2026-10-18.
- Foresight News·Clanker Technical Brief: How Exactly Do You Use AI to Launch Your Clanker MEME, page published or updated: 2026-09-03; verified: 2026-10-18.
- NPM·prema-sdk, page published or updated: no update date indicated; verified: 2026-10-18.
- NPM·clanker-sdk v3.8.1, page published or updated: 2025-04-25; verified: 2026-10-18.
- GitHub (developerfred/clanker-DOCS)·Clanker Docs, page published or updated: 2024-12-03; verified: 2026-10-18.
