.
The Idea
Explains how GetPaid generalizes existing fee-routing patterns into proposed infrastructure for multi-chain, multi-rail, and multi-recipient launchpad distributions.
GetPaid is not a first mover. It generalizes existing fee-routing patterns.
The thesis is not that fee routing is new. Existing products already demonstrate parts of the model: creator fee routing, holder rewards, multi-platform distribution, AI-driven token launches, and stock-token pairing.
Relevant examples include:
- UsePaid for fee routing
- pump.fun for pro rata holder rewards
- Wired Up for a multi-platform concept spanning X, Instagram, TikTok, GitHub, and Fomo beta
- bankr for AI agent launches
- long.xyz for stock-token pairing
Pons is another relevant example of a launchpad fee model. These projects are predecessor references only. They are not GetPaid partners, affiliates, or endorsements.
From product pattern to infrastructure layer
An individual fee-routing product can connect one ecosystem, one chain, or one payout model. GetPaid proposes a generalized layer that could give launchpads a shared routing surface across several dimensions:
| Dimension | Proposed scope |
|---|---|
| Chains | Multiple chains through chain-specific integrations |
| Settlement | Multiple payout rails |
| Recipients | Creators, holders, and protocol or community treasuries |
| Token mechanisms | Burn, buyback, staking, and governance paths |
The distinction is architectural. Rather than defining a single fee destination, GetPaid proposes configurable routing between an integrated launchpad and its recipients or token mechanisms.
This is a design thesis, not evidence of adoption or product-market fit. GetPaid remains a pre-testnet concept. Its proposed scope has not been deployed or production-validated.