> For the complete documentation index, see [llms.txt](https://docs.synfutures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.synfutures.com/perp-trading/perp-launchpad/overview.md).

# Overview

## What is SynFutures Perp Launchpad?

The SynFutures Perp Launchpad allows projects to launch perpetual futures markets for any native asset on Base. Unlike traditional launchpads that focus on spot markets, our Perp Launchpad pioneers the onchain derivatives space by supporting coin margin perp markets with single token concentrated liquidity, facilitating liquidity optimization to generate consistent yields while managing underlying risks.

## What are the benefits for projects?

Unlock New Trading Opportunities: Enable leveraged speculation and hedging for your token holders.

Access a Vast User Base: Tap into an expansive community behind one of the top perp DEXs in the market.

Increase Visibility and Liquidity: List your token among diverse and trending trading pairs.

## What are the benefits for traders?

Trade Beyond the Ordinary: Be the first to trade new pairs not listed anywhere else.

Leverage Opportunities: Long or short trending emerging tokens, memecoins, and other longtail assets.

Unique Profit Opportunities: Access unique onchain arbitrage opportunities and trading incentives for new listings.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.synfutures.com/perp-trading/perp-launchpad/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
