Every token launch creates a creator fee stream, and each launchpad models it differently. This draft is one interface for a launched token’s creator fee stream: who receives it (feeRecipient), what it has earned since launch (accruedTotal), what is claimable, a claim anyone can trigger that always pays the recipient, and a recipient that only the current recipient can change (ERC-173’s rule, applied per token). No administrator, upgrade or launchpad setting may redirect a launched token’s recipient or lower its creator share, and fees are accounted where they accrue, one event per credit, so anyone can recount the history. Together these make the stream pledgeable: pointed at a repay-first payee, only the payee can hand it back.
Questions for launchpad builders:
- Is “no admin path to a launched token’s recipient or share” acceptable for your contracts, or does it need an escape hatch (and what would keep a pledge safe then)?
- Lowering the pool’s fee rate is only a SHOULD NOT today; should it be a MUST NOT?
- An ERC-721 form of the right brings approvals and operators, which a pledge cannot allow; is a wrapper the right place for it?