Launch a pump.fun coin and split its creator fees between up to five X accounts, in the shares you set. Paid in dollars through X Money. Nobody has to sign up to be paid.
The builder below is live: it validates every handle, keeps the shares at exactly 100%, and writes the description line the indexer reads. Launching signs two transactions, one to create the coin and one to point its fees at Cut.
Paid proved a coin can pay one X handle in dollars. Cut keeps the whole mechanism and changes one thing: the description names up to five handles with shares, and every claim is divided before it is paid.
In pump.fun fee sharing, add the Cut treasury as the only shareholder and revoke the config. That is permanent and on chain. There is no approval step.
One line: "Fees to @a 50 @b 30 @c 20 via Cut". Leave the shares out for an even split. The indexer reads the line and registers the coin.
Cut claims the accrued fees on a schedule. 20% buys and burns $CUT. The other 80% is divided by share, in whole lamports, so the pieces always add up to the claim.
When a recipient's balance crosses a payout milestone it is sold for dollars and sent through X Money. A public reply from Cut confirms every payout.
After the coin exists, open pump.fun's fee-sharing screen, add the Cut treasury at 100%, and revoke the config's authority. Cut watches the Pump Fees program for sharing configs that name its treasury. A coin is detected when the config exists and becomes payable once the revoke flag is set. The config account is laid out like this:
| OFF | LEN | FIELD |
|---|---|---|
| 0 | 8 | discriminator |
| 11 | 32 | token mint |
| 43 | 32 | admin |
| 75 | 1 | revoke flag |
| 76 | 4 | shareholder count |
| 80 | N×40 | shareholders |
One line, anywhere in the description. Handles are looked up on X at registration and stored by numeric ID, so a later username change never redirects a payout.
Fees to @a 50 @b 30 @c 20 via Cut Fees to @a @b @c via Cut (even: 33.34 / 33.33 / 33.33)
One to five unique handles. Shares to two decimals that total exactly 100, or no shares at all. A line that breaks any of those rules is ignored and the coin is not registered.
Claims run on a schedule and skip vaults under 0.01 SOL, where the transaction would cost more than it collects. Each claim is keyed on its signature so it can never be counted twice. It is divided at that moment: the $CUT cut first, then the pool by share, with any leftover lamports going to the first recipients so the pieces always sum to the claim.
The split maths is one file, lib/split.js, shared by this page and the indexer, with its tests in tools/split-test.mjs.
Each recipient has a balance in lamports. When its dollar value crosses a milestone ($5, $10, $20, $50, $100, $250, $500, $1,000, then every $1,000) the whole balance is sold for dollars and sent through X Money from Cut's pre-funded float. The float is refilled from those sales, so a payout never waits on an off-ramp.
X Money is a consumer app with no API and daily limits, so it is the part that can fail. If a payout cannot be sent, the balance stays on the ledger and the recipient can claim it on chain instead. Nothing is ever forfeited to Cut.
20% of every claim on every coin buys $CUT on the open market and burns it. $CUT's own creator fees buy and burn too, all of them. Holding $CUT gates nothing and changes no split.
Not launched
Paid pays one handle per coin. Cut pays up to five, in the shares the creator sets. Paid keeps expired payouts; Cut holds them for the handle to claim on chain.
No. If the handle has X Money, dollars land. If not, the payment waits as a claimable X Money payment, and after that as an on-chain balance they can claim by signing in with X.
No. Cut is not affiliated with, endorsed by, or connected to X Corp, X Money, pump.fun, or UsePaid.
No. $CUT is a memecoin with one burn rule. There is no yield, no insurance, and no promise of value.