> For the complete documentation index, see [llms.txt](https://whitepaper.surge.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.surge.xyz/business-model/launch-protocol-fees.md).

# Launch Protocol Fees

Surge’s business model is designed for **sustainability**, **scalability**, and **tokenholder** **alignment**. Every part of the platform - launch protocols, incubation, AI Foundry, and reputation systems - creates revenue while reinforcing the long-term value of the $SURGE token.

Launches are the primary revenue driver. Each launch format has its own commission structure.

* **Fairlaunch Launch (Bonding Curve):**

  * **One-time Deployment Fee (Bonding Curve Creation):**

    * **Base:** 0.005 ETH
    * **Solana:**
      * **Fairlaunch SOL fee structure:**
        * Token creation fee: 0.15 SOL (one time)
        * **Bonding Curve trading fee**: 1.3% of trading volume, where
          * 0.05% goes to Creator
          *  0.25% goes to Raydium
          * 1% goes to Surge
        * **Raydium trading fee**: 0.3% of trading volume, where 
          * 0.05% goes to Creator
          * 0.04% goes to Raydium
          * 0.21% goes to Surge
    * **BNB Chain:** 0.02 BNB

    **Trading Fee (within Bonding Curve):**

    * **1% fee** applies to all buy and sell transactions across every chain

  All fees are transparently displayed before token deployment.

* **Ignition Launch: TBA**

* **Gated Launch: TBA**


---

# 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.surge.xyz/business-model/launch-protocol-fees.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.