> 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/system-architecture.md).

# System Architecture

Describes proposed GetPaid architecture that separates launchpad fee routing from payout, economic, and governance layers across supported chains.

GetPaid is planned as an infrastructure layer between launchpad fee generation and downstream fee destinations. The model separates fee routing from payout and economic destinations.

{% hint style="warning" %}
This conceptual architecture is proposed. GetPaid is pre-testnet, and no described component is deployed, audited, or live.
{% endhint %}

### Proposed fee flow

```
Launchpad
    ↓
Trading fee
    ↓
GetPaid Fee Router
    ↓
Configurable distribution
├── Creator
├── Burn
├── Buyback
└── Protocol
```

On supported EVM chains, the proposed GetPaid Fee Router uses a Uniswap V4 hook. Other ecosystems would use chain-specific adapters. GetPaid is not designed as a bridge, and cross-chain messaging and asset-bridging mechanisms remain subject to final specification.

### Conceptual layers

| Layer                  | Intended responsibility                                                             |
| ---------------------- | ----------------------------------------------------------------------------------- |
| Launchpad / Fee Source | Generates trading fees within a launchpad environment.                              |
| GetPaid Routing        | Intercepts and routes fees according to a configured distribution.                  |
| Chain Adapter          | Connects chain-specific launchpad ecosystems to the common fee-routing concept.     |
| Settlement / Payout    | Supports creator payouts across proposed settlement rails.                          |
| $GET Economic          | Supports the proposed buyback, burn, staking, and token functions.                  |
| Governance             | Supports holder influence over selected protocol parameters and treasury decisions. |

Together, these layers are intended to support fee routing, multi-chain coverage, multi-rail settlement, creator payouts, token buyback and burn, staking, governance, and social proof. Their technical interfaces and communication flows remain subject to final specification.

### Unallocated fee share

The proposed default allocation is 60% creator, 10% burn, 10% buyback, and 10% protocol. This totals 90%.

{% hint style="danger" %}
The current model accounts for 90% of routed fees. The remaining allocation will be finalized before implementation.
{% endhint %}

The architecture is planned. It does not represent a deployed GetPaid system.


---

# 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/system-architecture.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.