Multi-Chain

Explains a proposed chain-aware architecture that connects launchpad fee flows across target networks to shared routing and distribution logic.

GetPaid’s proposed design uses a chain-aware fee layer with common routing logic. Chain-specific integrations would connect launchpad fee flows to that shared model.

Launchpad
    ↓
Chain-specific integration
    ↓
GetPaid Fee Layer
    ↓
Common routing logic
    ↓
Creator / Burn / Buyback / Protocol

Planned network coverage

Network	Proposed role	Reference basis
Robinhood Chain	Native target	Uniswap V4 hook, USDG through EIP-3009, stock-token support
Solana	Planned adapter	Solana program, pump.fun, Stonk
Base	Planned adapter	Uniswap V4 hook, o1, bankr
BSC	Planned adapter	FLAP commission receiver
Ethereum	Future expansion	Uniswap V4 hook

Robinhood Chain is the proposed native target. All other networks are planned adapters or expansion paths.

Architectural purpose

The model intends to separate fee-routing logic from the chain where a launchpad operates. A chain-specific integration would deliver fee activity to the GetPaid layer, which would then apply common distribution logic.

Bridge design, cross-chain messaging, canonical asset representation, cross-chain settlement, interoperability protocols, and adapter interfaces remain subject to final specification.

WARNING
This is planned adapter architecture only. No listed integration is deployed, audited, or live.