Rewards

Fee allocation

Where the fees go and how the creator milestone reserve is funded.

Which fees are shared?

The allocation uses creator-fee revenue actually received by Rallypad. Protocol fees, liquidity fees and trading volume are outside this calculation.

Accrued but uncollected fees are not yet available to pay rewards. Pool and protocol integrations must account for fee collection before and after migration.

How collected fees are shared

Default allocation from 100 SOL receivedAllocation
70 SOLCommunity rewards for the originating coin.
20 SOL$RALLY buyback and burn.
5 SOLThat coin’s creator milestone reserve.
5 SOLPlatform operations.

This is the default program for future fees from existing coins, including $RALLY, and for new launches without a custom program. New custom programs use their published allocation with exactly 5% operations. Existing earned allocations are preserved. Non-SOL community and creator rewards stay in their quote token.

Available reward estimates

The displayed dollar estimate combines the coin’s collected, unreserved community balance with attributable unclaimed fees awaiting collection. Amounts are approximate and depend on the reward asset’s current display price.

Uncollected fees cannot fund a reward round. Reserved or paid awards are not available again, and a displayed estimate is not a promised payout.

Each coin’s reserve

Each coin’s creator-milestone contributions stay in its own reserve. At a new milestone, its entire available reserve is set aside for the registered creator payout address. Later fees accumulate toward the next milestone.

The promoter allocation remains coin-specific. Once money is reserved for a funded milestone award, it cannot also back another award or a promoter payout.

Shared account, separate records

Every coin uses Rallypad’s shared launch account, but fee attribution is tracked per coin. A wallet’s total balance alone cannot establish how much each coin contributed.

The backend records fee receipts, allocations, milestone evidence and payout transactions. Repeated events or retries must not credit or pay a reward twice.

Operational limits

  • Each new milestone reserves that coin’s entire available creator balance. Several milestones crossed together reserve it once.
  • A milestone with an empty reserve still earns its achievement, without a cash award.
  • Market-cap milestones use backend Jupiter responses no older than 30 minutes, at least $1,000 of pool liquidity and separate qualifying observations. Browser-submitted metrics never grant awards.
  • Tiny payouts to an empty wallet stay queued until the destination can receive them under Solana’s rent rules.
  • The payout address cannot be changed after the launch draft is created. Check the destination before paying.

Protocol references