SliceFee flow
Follow one lamport from the trade that pays it to the wallet or the burn it ends in. It passes through three places, and knowing who controls each one answers most questions about the product.
Three places, three owners
| Place | What it is | Who can move it |
|---|---|---|
| Token vault | pump.fun’s creator vault for this token’s creator address, plus the PumpSwap vault after migration. Accounts of pump.fun’s programs | Only pump.fun’s collect instructions. Anyone can run them, and they pay out to the creator address and nowhere else |
| Treasury | One Solana wallet we operate | Whoever holds its key: us |
| Your wallet | Wherever you asked to be paid | You |
The first and the last are protected by keys and programs that are not ours to override. The middle one is protected by us, and checked in public on the proof page. That is the custody model, in one table.
The path, hop by hop
- Trade. Someone buys or sells the token on pump.fun’s bonding curve, or on PumpSwap after it migrates. pump.fun charges its fees on the trade, and the creator fee part goes to the vault of the token’s creator address. On the curve that is 0.30% of the trade at the time of writing; on PumpSwap it is whatever pump.fun sets there. We set neither.
- Token vault. The fee accumulates as SOL in the bonding-curve creator vault, or as wrapped SOL in the PumpSwap creator vault. Because the creator address is this token’s alone, the vault holds this token’s fees and nothing else. See Per-token vaults.
- Sweep. When the vaults hold at least 0.01 SOL, a scheduled job collects both into the treasury in one transaction. If somebody else already ran pump.fun’s collect for the token, those fees are waiting in its creator address, and the same transaction moves them too. See Sweeps.
- Split. Once the sweep confirms, what it collected is divided: the amounts in pump.fun’s collect events plus any fees found waiting in the creator address. 80% goes to the recipients by their shares and the remainder to the platform, which is 20% plus rounding dust. See Recipients & shares.
- Balance. Each credit adds to the balance of the X account pinned to that handle. The SOL stays in the treasury, and the proof page counts it as owed.
- Routing. The account’s owner claims it to a wallet, has it sent automatically, or has it spent buying and burning the token. See Routing.
One trade, followed through
A 10 SOL buy on the bonding curve, at the 0.30% creator fee, with a platform share of 20% and two recipients on 70% and 30%:
| Step | Lamports | SOL |
|---|---|---|
| Creator fee into the token vault | 30000000 | 0.03 |
| Swept into the treasury | 30000000 | 0.03 |
| First recipient, 70% of 80% | 16800000 | 0.0168 |
| Second recipient, 30% of 80% | 7200000 | 0.0072 |
| Platform | 6000000 | 0.006 |
In practice a sweep rarely carries one trade. Sweeps run on a schedule and collect everything the vault has gathered since the last one, and a vault holding less than 0.01 SOL waits for more. The combined amount is split the same way.
Who pays for each transaction
| Transaction | Signed by | Network fee paid by |
|---|---|---|
| Launch | Your wallet and the new mint key, in your browser | You, with pump.fun’s account rent and any first buy |
| Sweep | The treasury and the token’s creator key | The platform share, with any rent top-up of the creator address |
| Payout | The treasury | The platform share. The recipient receives the full amount |
| Buy and burn | The treasury | The platform share. The SOL of the burn orders goes into the buy whole; swap fees and price impact reduce what it buys |
What never happens
A launcher’s wallet never receives creator fees, unless its owner named their own X account as a recipient and claimed. Nobody is credited from a token that does not name them: every credit points at the sweep it came from, and every sweep at one token. And the platform never takes more than its share plus dust, because the recipients are credited first and the platform keeps only what is left.