> 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/technical-architecture/chain-adapters.md).

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

{% hint style="warning" %}
All integrations below are planned. The listed ecosystems are referenced in the proposed design. They do not represent partnerships or live integrations.
{% endhint %}

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


---

# 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/technical-architecture/chain-adapters.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.