.
Chain Adapters
Explains proposed chain-specific adapters connecting diverse launchpad ecosystems to GetPaid’s common fee-routing model across target networks.
GetPaid proposes chain-specific integrations around a common fee-routing concept. Adapters exist because launchpad ecosystems and execution environments differ by chain.
WARNING
All integrations below are planned. The listed ecosystems are referenced in the proposed design. They do not represent partnerships or live integrations.
Planned coverage
| Chain | Integration model | Reference |
|---|---|---|
| Robinhood Chain | Native target / Uniswap V4 hook | Pons / stock tokens |
| Solana | Solana adapter / program | pump.fun / Stonk |
| Base | Adapter / Uniswap V4 hook | o1 / bankr |
| BSC | Commission receiver | FLAP |
| Ethereum | Uniswap V4 hook | Future expansion |
Chain-specific direction
Robinhood Chain → Native integration
Solana → Adapter
Base → Adapter
BSC → Adapter
Ethereum → Future adapter
Robinhood Chain
Robinhood Chain is the proposed native target. The design uses a Uniswap V4 hook, USDG through EIP-3009, and stock-token support.
Solana
The planned Solana adapter is designed as a Solana program. The proposal references pump.fun and Stonk.
Base
The planned Base adapter uses the Uniswap V4 hook model. The proposal references o1 and bankr.
BSC
The planned BSC integration uses a FLAP commission receiver model.
Ethereum
Ethereum is a planned future expansion path using a Uniswap V4 hook.
Scope boundary
Adapters are intended to provide chain-specific integration while preserving a common fee-routing concept. Adapter interfaces, cross-chain messaging, bridging, wrapped assets, cross-chain settlement routing, and interoperability protocols remain subject to final specification.