1. Platform Fee
Unless changed by the platform owner in writing and in code, the platform fee is 5% of incoming creator reward value handled by the service. The remaining value is routed according to the creator's saved settings, such as holder rewards, buy-and-burn, treasury, and donations. Router Protocol's own ROUTER mint may use an internal zero-fee route so its published holder/treasury split is not reduced by the third-party platform fee.
2. Creator-Fee Signer Models
- New project through the platform: the creator-fee automation path may use a service-controlled signer so rewards can be claimed and routed automatically.
- Existing project import: automatic operation may require importing an existing creator-fee private key into an encrypted vault flow.
- Manual signing model: if supported later, a creator may sign claims manually, but this does not provide fully automatic payouts.
3. Imported Private Keys
Importing a creator-fee private key is sensitive and should be treated as custodial or semi-custodial. The platform should display strong warnings, encrypt the key at rest, restrict access, and avoid exposing private keys in ordinary dashboards. Users should never share private keys in screenshots, support chats, or public messages.
4. Treasury, Burns, and Donations
Creators may configure treasury, burn, and donation percentages where supported. Some settings may be locked or treated as irreversible commitments for holder trust. If Pump.fun itself routes a percentage before the platform receives rewards, creators must disclose that so the platform does not route or charge fees against value it never receives.
5. Payout Dust, Fees, and Failed Transactions
Blockchain fees, minimum payout thresholds, route slippage, token account creation, failed transactions, and dust limits can affect payout timing and amounts. Safety defaults may reserve small amounts for fees and skip payouts that are too small or unsafe to process.