Fees and splits
The fee a creator types is a request, not an outcome. This page is what a swap really charges, who keeps which share, and the three places the typed number and the charged number differ.
Try it
The calculator below implements the same rules the launcher does, transcribed from the deployed fee libraries. Change the tier and the fee and watch what the pool would actually charge.
It applies the protocol's fee rules to a volume figure you invent. It does not know your pool's depth, the slippage a trade takes, or what price your coin will be. The authoritative numbers are always the ones read from the contracts at launch time in the Studio.
The fee map
Three constants decide everything. All three come from the deployed libraries.
| Tier | Fee you may choose | What the pool charges | Creator | Protocol |
|---|---|---|---|---|
| Custom · V4 | 0% | 0.15% floor | 0% | 100% |
| 0.01% – 5.00% | exactly what you chose | 80% | 20% | |
| Pro · V3 | any | nearest of 0.05 / 0.3 / 1% | 80% | 20% |
The break point is inclusive
There is no tier break any more. The protocol takes 20% of any fee above 0%, so you keep 80% whether you chose 0.5%, 2.5% or 5%. Raising your fee raises your take only through the fee itself. A coin launched before this rate changed keeps the split it launched with — the split is fixed at launch and never re-read.
The three places the typed number is not the charged number
1. A 0% fee is not free
Choosing 0% on a Custom launch does not create a fee-free pool. It creates a pool charging a 0.15% floor, and the protocol keeps 100% of it. Any interface that renders a 0% coin as "free" or "no fee" is stating something false. If you are building one: show the true 0.15%.
The reason is simple — a pool with genuinely zero fee is a pool the protocol cannot sustain, and a zero-fee memecoin is an attractive place to route unrelated volume through. The floor prices that.
2. Pro snaps to an enabled tier
Uniswap V3 on Robinhood Chain enables exactly three fee tiers, and a pool's tier can never be changed once it exists. Type 2% on a Pro launch and you get a 1% pool. Type 0.2% and you get 0.3%. The Studio prints the snap at the point of decision, and the summary shows the snapped number.
10000 units is 1%, so a percentage converts with × 10000. Using × 100 collapses the entire 0–5% range onto the 500 (0.05%) tier — you would have to type 17.5% to reach 0.3%. That is a twentyfold under-charge on both the creator's and the protocol's income, and because a pool's tier is immutable it cannot be repaired after the fact.
3. On BNB the tier table is different again
PancakeSwap V3 enables {0.01%, 0.05%, 0.25%, 1%} and disables 0.3%, which reverts. Uniswap's {0.05%, 0.3%, 1%} table is simply invalid there. See Networks.
What currency the fee is paid in
| Tier | Fee accrues as | Where it sits until collected |
|---|---|---|
| Pro · V3 | Both legs of the pair — wrapped gas token and your coin | In the LP position, uncollected |
| Custom · V4 | Always the wrapped gas token | On the hook |
A dashboard that reads only a fee-splitter contract will report zero for a Pro coin that has earned real money, because the fees have not been collected out of the position yet. Preview the uncollected position fees, not just the splitter balance.
Collecting
Fee collection is permissionless on every tier. Anyone can call it; the money always goes to the creator's recipient and the protocol treasury, never to the caller. That is deliberate: a stalled keeper must never be able to strand a creator's earnings.
Two invariants hold on every collection, on every tier:
creator + treasury == collected, for every leg. The remainder from integer division goes deterministically to the treasury; nothing is left dangling.- The recipients are fixed at launch and cannot be re-pointed afterwards.
Fees on trades made through Ultra
Separately from the pool fee, swaps executed through NASDANK's own Ultra interface pay a 1% routing fee in the wrapped gas token, taken as a PAY_PORTION command inside the UniversalRouter call. This is what funds the referral programme. It is not charged if you trade the same pool through any other router — the pool fee is, of course, charged either way.
Ultra swap shows exactly where in the command sequence the fee is taken.