Fees hit the rails.

Distribution is what happens when the fees sitting in your vault get split up and sent to your destinations. It happens automatically, on-chain, with no action from you.

How it works

As your coin earns creator fees, they collect in your vault. On a regular schedule, a public program checks each vault. If the balance is above a small threshold, it triggers a distribution: your fees are split into the percentages you set, sent to every destination, and the transaction is recorded on the Solana network.

All of this is public. Anyone can see when a distribution happened and where every lamport went.

Why a threshold?

Every Solana transaction costs something to submit. If we distributed every time a single lamport arrived, most of it would go to transaction fees. The threshold makes sure a distribution is worth doing before we trigger one. Reroute picks a default that keeps the payout well ahead of the fees.

Where you see it

• On your Dashboard, under Distribution history. Every distribution is listed with a timestamp and a link to the on-chain transaction.
• On any Solana explorer (Solscan, Solana FM, Solana Explorer). Reroute is fully public on-chain state.
• On your destination wallets. Fees show up as regular transfers you can track like any other Solana income.

What the LP rail does with its slice

If you enabled the LP rail, its share of a distribution does not land in a wallet. It lands in a system-owned PDA reserved for LP activity on your mint. A separate public bot watches that PDA on its own schedule (about once an hour on mainnet). Once the balance clears a small threshold, the bot fires a single atomic transaction that:

1. Wraps the accumulated SOL.
2. Buys half the position in your token on PumpSwap.
3. Deposits both sides as liquidity into your pool.
4. Burns the LP tokens the deposit produced.
5. Reimburses itself for the tx fee out of the same PDA.

Every step is on-chain and lamport-conserving. If any leg fails, the whole zap reverts and the SOL stays in the PDA for the next attempt. Because the bot reimburses itself from the rail's own balance, the LP rail self-funds and never relies on an operator subsidy.

You can watch every zap on the /token/[mint] accountability page, or on any Solana explorer.

What the staking rail does with its slice

Staking-rail fees accumulate in a rewards pool tied to your mint. Eligible holders (those who have held for long enough and have not sold in between) share the pool in proportion to their held-token-time. The staking page for each mint shows the current pool size, the count of eligible wallets, and a projected share for wallets that are on their way to eligibility but not there yet.

Until the first holders cross the eligibility threshold, the pool grows and the eligible count sits at zero on purpose. The page shows the first-unlock date so early holders know when the pool starts paying.

What if a destination is invalid?

Distributions are all-or-nothing. If any leg of the split would fail (say a destination is somehow invalid), the whole distribution reverts and the fees stay in your vault.

A partial distribution would leave your split out of balance, so the program refuses to do one. Better to hold and retry than to send one destination too much.

How long does it take?

The public crank runs every few minutes on mainnet. Once your vault crosses the threshold, expect a distribution within a few minutes at most.

Can I force a distribution?

Not necessary. Distributions are automatic and gasless from your side. The public crank handles it. If you truly need to push a distribution right now, you can call the on-chain program yourself using the SDK, but it is almost never worth the effort.

What about the transaction fee?

Whoever triggers the distribution pays the network fee upfront. The router reimburses that cost from your vault, so you always pay for your own activity. Reroute never fronts your costs.

Next

• Security and trust model
• Back to overview