> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/multi-chain-and-multi-rail/multi-chain.md).

# 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.

{% hint style="warning" %}
This is planned adapter architecture only. No listed integration is deployed, audited, or live.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://whitepaper.getpaid.family/multi-chain-and-multi-rail/multi-chain.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.