Creator Rewards

Before migration

On Dumpster, creator fees accumulate in the creator vault PDA:

["creator-vault", creator]

The recipient signs collect_creator_fee to withdraw the vault balance above its rent-exempt minimum. Collection does not require the recipient to remain a token's current creator.

After migration

On DumpsterSwap, creator fees accrue in quote-token accounts controlled by the recipient's creator-vault authority. The recipient signs collect_coin_creator_fee to collect them into a chosen token account for that mint. For Dumpster's migrated pools, the quote token is wrapped GOR.

Creator handovers

Use the curve's transfer_creator for a current-creator-signed handover or set_creator for a designated-authority assignment. After migration, these operations synchronize the curve and validated canonical pool atomically. DumpsterSwap does not accept an independent wallet handover.

A voluntary handover rejects with CreatorMismatch (6024) if the curve and pool name different recipients. The designated authority can reconcile them to an explicitly chosen nondefault recipient, including restoring a canonical zero-recipient state. Historical disagreement requires a review of successful handover history; neither stored recipient automatically wins.

An unchanged target still requires authorization and account validation. It is a no-op only when neither record needs to change. See creator handover events for pool-only administrative repair and no-op semantics.

Handover changes future fee routing when it successfully executes. It does not move, close or sweep the old recipient's vaults, and former recipients retain their existing collection rights. A trade before the handover uses the previous recipient; a trade afterward uses the new one. No mandatory claim is part of a handover.

Integration implications

• Curve rewards and AMM rewards are separate accounting sources.
• A token can have historical curve rewards and ongoing AMM rewards at the same time.
• If you need strict accounting, treat claim history as its own dataset instead of inferring it from balances alone.
• Attribute historical fees using the recipient at execution, not today's creator field. A database approval or a stale UI label is not evidence that an on-chain handover succeeded.