.

The Problem

Outlines fee-routing constraints and GetPaid’s proposed responses through multi-rail settlement, adapters, flexible recipients, token mechanisms, and anti-vamping.

GetPaid is designed to address five constraints common to fee-routing systems.

1. Single-rail payouts

Some payout systems depend on one rail, such as X Money or crypto worker wallets. That dependency can limit how recipients receive value.

GetPaid proposes a multi-rail architecture so an integrated launchpad could support more than one settlement path. The final rails and their operating constraints remain undefined.

2. Single-chain scope

Fee-routing systems can be bound to one chain or ecosystem. This fragments routing logic when launchpad activity spans different networks.

GetPaid proposes a multi-chain adapter architecture. The aim is to provide a common routing layer while accommodating chain-specific integrations. No adapters are deployed.

3. Single-recipient routing

Some models primarily route fees to a single creator. That approach does not inherently express holder participation or treasury allocation.

GetPaid proposes configurable destinations that may include:

  • A creator
  • Token holders
  • A protocol or community treasury

Recipient rules, allocation logic, and eligibility criteria will be finalized before deployment.

4. Burn-only token utility

Burn-only models provide one path for fee-linked token activity. The GetPaid design considers a broader set of mechanisms:

  • Burn
  • Buyback
  • Staking
  • Governance

This utility model is proposed. It does not establish token performance or investment outcomes.

5. Fee-recipient flexibility

Recipient configuration creates a tradeoff. Permanent locks can prevent legitimate changes. Unlimited flexibility can enable fee recipients to be changed too easily.

GetPaid proposes an anti-vamping approach with limited early changes, seven-day cooldowns, and later LOCK or FLEXIBLE modes. The design balances predictable recipient rights with controlled configuration changes.

These mechanisms are proposed. GetPaid has not deployed or validated them in production.