> For the complete documentation index, see [llms.txt](https://docs.eitherway.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eitherway.ai/documentation/launchpad/launch-design.md). # Launch Design Launches on the Eitherway Launchpad continue to use a bonding curve mechanism. That design still serves three functions at the launch layer: * structured initial price discovery * early liquidity formation * a defined path into broader trading access What has changed is the default pairing model for permissionless launches. Rather than pairing every permissionless launch directly against **$EITHER**, the launchpad now follows the native-chain path. On Solana, that means launches default to **SOL pairs**. As the launchpad expands across ecosystems, launches can also use other native-chain pairs, including **Base-native pairs**. This change is intended to make the permissionless system more scalable while reducing the downside that weak launches can create for the main **$EITHER** pair. At the same time, launch activity still feeds back into the wider Eitherway ecosystem. Each permissionless launch carries a **0.5% residual fee on volume**. That residual accrues toward periodic **buyback and burn of $EITHER**, allowing launch activity across the platform to support the main token without requiring every permissionless launch to be paired directly against it. At a high level, the launch sequence now follows this progression: * a project enters launch preparation * the token is configured for launch through the bonding curve * the default pair follows the native-chain route, such as **SOL** on Solana * the bonding curve manages early issuance and price discovery * liquidity depth forms onchain as activity progresses through the curve * routing expands into broader trading access and terminal visibility * a residual fee from launch volume accrues back toward **buyback and burn of $EITHER** The purpose of this architecture is not only to simplify launch mechanics, but to create a cleaner transition from issuance to liquidity, discovery, and market participation while keeping the wider **$EITHER** economy supported over time. --- # 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: ``` GET https://docs.eitherway.ai/documentation/launchpad/launch-design.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.