Fees
What the console charges, on what, and when it is taken.
There are two kinds of cost in every run: what the chain and the protocol charge, and what this console charges. Only the second is ours.
The platform fee
| Action | Fee | Charged on |
|---|---|---|
| Launch | 1% | What the launch spends buying, the creator's own buy included |
| Bundle | 1% | What the bundle spends buying |
| Sell | 1% | The proceeds of the sale, measured from what landed |
| Volume bot | 0.5% | The volume the bot printed, buys and sells added together |
| CEX funding | 1% | The total sent to the exchange order |
Three rules the collection follows, all of them because it runs after real money has already moved:
- A fee never fails a run. The launch landed, the volume printed, the tokens sold. If the fee cannot be taken, the run still reports success and says the fee went uncollected.
- It is one transfer, at the end, from a wallet the run already controls. Charging each wallet separately would double the transaction count and leave a wave of identical transfers into one address, which is the pattern the rest of the console spends its effort avoiding.
- It is charged on what you got, not on what passed through your hands. A volume bot recycles the same capital through wallet after wallet, so billing the funding would charge the same coin many times over for one run.
The volume rate is half the others deliberately: its base is printed volume, which for a bot doing many rounds is a far larger number than the operator's actual outlay.
When nothing is charged
Every one of these is printed in the log rather than passed over in silence, because "you were not charged" and "the fee quietly broke" would otherwise look identical:
| Reason | What the log says |
|---|---|
| The action did not complete | No fee line at all. An unlanded bundle is never charged. |
| An admin account ran it | fee: nothing charged, admin accounts are exempt |
| No recipient configured | fee: nothing charged, this deployment has no fee recipient configured |
| The fee works out to zero | fee: nothing charged, the fee works out to zero |
| No wallet can afford it | The reason, naming the shortfall |
If you are testing the fee path, do it from a user account. An admin account is exempt, so a run from one proves nothing about whether the fee works.
Where it is disclosed
Every page that can charge it says so before you act, in the estimate panel, as its own line. A fee you only discover in the log afterwards is a fee you did not agree to, so the console does not work that way.
What is not ours
- Gas. Paid to the chain, per transaction, by whichever wallet signs it. On a bundle it is also the bid, so a contested block costs more than a quiet one.
- Curve fees. Every launchpad takes a cut of each curve trade: 1% on four.meme, 1% on Flap, and OneMeme's own rate read from its contract.
- Token taxes. A tax token charges on transfer. Flap's own launches on both chains carry a 1% sell tax that goes to the creator. That is you, but it still comes off a sale before you see it.
- Exchange fees. The CEX Funder's provider charges its own withdrawal fee, quoted per recipient before you commit.
Estimates
Cost panels are priced through the same planner the run itself uses, so the estimate and the execution cannot drift apart. They are still estimates: gas is bid rather than fixed, and a curve moves between the quote and the send.