Fee splitting for one coin, across every platform
One coin. Everyone gets a cut.
Route a single coin's creator fees to the people who made it move: the X poster, the TikTok editor, the Twitch streamer, the dev on GitHub. You write the cut list and decide what percentage goes to each handle.
How it works
Proposed designCutlist is a concept. Nothing on this page moves money, and no fee routing is live. Below is how we would build it.
- 01
Write the cut list
When you launch a coin, you add handles from any platform and give each one a percentage. The cuts have to add up to exactly 100%.
- 02
Lock it on-chain
The list is stored as the coin's fee config. Each handle gets its own claim account, keyed by platform and user ID, not by the display name. Anyone can read it.
- 03
Fees pile up
Each trade pays a creator fee, and that fee is divided by the cut list right away. Each handle's share builds up in its own claim account.
- 04
Handles claim
The account owner proves they own the handle by signing in with the platform (OAuth) or by posting a signed code, then connects a Solana wallet and withdraws.
Prior art, stated plainly
pump.fun already has native fee sharing with up to 10 wallets and GitHub accounts. Bags splits royalties between X, GitHub and wallet claimers. Kickback and lunchpad send a coin's fees to one creator on a single platform. Cutlist's proposal is one list that covers every platform, with a cut you set for each handle.
Split builder
Runs in your browserAdd platforms and handles and set each cut. Nothing is saved or sent anywhere.
| # | Flight | Destination | Cut | Example payout |
|---|
These numbers are illustrative only. They aren't a forecast, a quote, or a real balance. A real system would also take out network and platform fees.
Platforms
Proposed verification| Code | Platform | Handle format | How a handle would prove ownership |
|---|
FAQ
How does a handle claim its fees?
Under the proposed design, the owner signs in with the platform through OAuth, which proves they control the account. Platforms without a usable OAuth flow would use a signed post instead: you publish a one-time code from the handle, and Cutlist checks it. After that you connect a Solana wallet and withdraw. The claim account is tied to the platform's permanent user ID, so changing your handle wouldn't lose your cut.
Does the person need to sign up first?
No. Their cut starts building up from the first trade, whether or not they know about the coin. They can claim it whenever they get around to it.
What happens to cuts nobody claims?
That's an open design question. Our current proposal is that unclaimed cuts wait in their claim account for a fixed period and are then shared out among the handles that did claim, according to the list. The coin's page would show this rule before anyone trades.
Can the cut list change after launch?
We propose that the creator can change it, but each change is logged on-chain and only applies to fees going forward. Fees that have already built up stay with the handle that earned them.
How many handles can one coin have?
The builder lets you add up to 20. The real limit would depend on the fee program underneath. pump.fun's native sharing currently allows 10 recipients.
Is this live? Is there a token?
No to both. Cutlist is a concept site and doesn't route any fees. No official coin yet. Anyone posting a CA for us is not us.