Slice
Product

Routing: Hold, Autopay, Burn

A recipient decides once where their money goes, and every sweep after that follows the decision without them. Three modes, and a fourth that is the third said out loud.

The modes

ModeWhat happens to each new creditNeeds
HoldIt adds to the balance. You claim when you likeNothing. The default
AutopayIt adds to the balance, and the whole balance is paid to your wallet once it reaches 0.05 SOLA saved wallet address
BurnIt becomes a burn order for the token it came from. The treasury buys that token and burns what it boughtNothing
DeclineThe same as Burn, and your account is marked as declined, publiclyNothing

Routing is set on Claim after signing in with X, and it applies to every token that names you. Until an account signs in for the first time, it is on Hold.

Hold

Credits accumulate and nothing moves until you claim. This is the only mode that can apply to an account that has never signed in, and balances on Hold never expire. See Claiming with X.

Autopay

You save a wallet address once. Each run of the payout job looks for accounts on Autopay whose balance is at least 0.05 SOL and queues a payout of that balance to the saved wallet. It is then sent exactly like a manual claim: one open payout at a time, the network fee on the treasury, and the same wait when payouts are paused or the treasury is near its reserve.

The threshold exists so that a busy token does not turn into a stream of tiny transfers. Below it, the balance waits for the next sweep. You can still claim by hand at any time above the 0.01 SOL claim minimum.

Autopay is for recipients who would rather not come back. Sign in once, save a wallet, and the money keeps arriving there for as long as the token trades, with no request to make each time.

Burn

Burn is for an account that does not want the money and would rather it went back into the token. Every credit made while you are on Burn becomes a burn order for the token that produced it, and leaves your balance at that moment.

  1. Burn orders for one token are pooled, from every recipient on Burn and across sweeps.
  2. Once a token’s pooled orders reach 0.02 SOL, the burn job buys that token with exactly that SOL through Jupiter, with the treasury as the buyer and at most 3% slippage. It never spends the treasury’s reserve or SOL set aside for payouts that are queued or on their way. A buy that fails or expires is tried again, up to three times; after that the run is marked failed and its orders go back to the pool for a later run. The SOL never left.
  3. It reads the amount bought from the confirmed swap and burns exactly that amount in a second transaction, using the token program the mint was created with.
  4. The burn is published in the ledger with its signature, the SOL spent and the tokens burned.

The buy is a trade like any other. It pays pump.fun’s trading fees, including the creator fee, which lands back in the same token’s vault and is split again at the next sweep. Price impact and fees mean the SOL buys somewhat less than its spot value; nothing else is taken from it.

Decline

Declining is Burn with a public statement attached. The token pages and your account page show that you declined, and every credit you would have received is spent buying the token back and burning it. For someone who was named on a token without being asked, it is a way to answer in public that costs holders nothing and takes nothing for yourself.

Declining does not remove your handle from the token, because the recipients are fixed at launch. It changes what happens to the money.

Changing your mind

Routing can be changed at any time, including withdrawing a decline. A change applies to credits made after it, with one deliberate exception: switching to Autopay also pays the balance you already have, on the next payout run once it is above the threshold. Burn orders already made stay orders, and a payout already queued is sent.