> 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/eitherway-launchpad.md). # Eitherway Launchpad The Eitherway Launchpad is the native token launch layer within the Eitherway ecosystem. It supports both product-first and token-first launches. Teams can use it to launch tokens for applications built on Eitherway, for products developed externally, or for token-led ecosystems that plan to build the product layer over time. Eitherway’s preferred path is product first, then token. The reasoning is simple: launches tend to be stronger when there is already a real product, use case, or user flow behind them. That said, it is a preference, not a restriction. The launchpad is designed to support different paths to market. ### Strategic Rationale Most launchpads are built around issuance. Eitherway is built around execution. The launchpad is not just a standalone token listing surface. It sits inside a broader system that includes application creation, deployment, monetization, routing, indexing, and ecosystem expansion. That matters because it reduces the fragmentation teams usually face when moving from concept to launch. Instead of building in one environment, coordinating liquidity in another, and depending on separate tools for discovery and trading, teams can move through a more unified launch path. In practical terms, the launchpad connects three layers that are often disconnected: * product creation * tokenized coordination * market access That structure gives teams a clearer route from idea to launch and creates stronger alignment between the asset, the product, and the wider ecosystem. The launch model continues to use a bonding curve structure, but the default pairing model for permissionless launches has evolved. Rather than pairing every launch directly against **$EITHER**, permissionless launches now follow the native-chain path, beginning with **SOL pairs** and expanding into other chain-native pairs such as **Base** as the launchpad grows across ecosystems. This change is intended to keep the launchpad open and scalable while reducing the downside that weak permissionless launches can create for the main **$EITHER** pair. At the same time, launch activity continues to support the wider ecosystem through a **0.5% residual fee on volume**, which accrues toward periodic **buyback and burn of $EITHER**. In that model, **$EITHER** remains central to the launchpad economy, not as the default pair for every permissionless launch, but as the core value-capture layer of the ecosystem. Curated and vetted launches can still use **$EITHER** more directly under stronger market and liquidity conditions, while the broader permissionless system is designed to route value back into the main token in a more sustainable way. That is the core logic behind the updated model: keep the bonding curve, shift permissionless launches toward native-chain pairs, and make sure launch activity still strengthens the **$EITHER** economy 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/eitherway-launchpad.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.