> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/earn/cakepad/faq-partners.md). # FAQ (Partners) {% hint style="success" %} For more information visit: 👉 [Apply to launch now!](https://docs.google.com/forms/d/e/1FAIpQLScmZu87SG41J_eGfzlbyJ_olFohlGOXfOJer04Dr1yCEJy2NA/viewform) {% endhint %} ### 1. Who can apply to launch an CAKE.PAD event? Eligible projects must: * Have a functioning product or MVP. * Be ready to launch a token and liquidity on PancakeSwap (BNB Chain, Base, Monad). * Allow 3–4 weeks of lead time before TGE. * Demonstrate strong community growth potential. * Pass PancakeSwap’s due diligence review. **How to apply:** * Fill out the [application form](https://docs.google.com/forms/d/e/1FAIpQLScmZu87SG41J_eGfzlbyJ_olFohlGOXfOJer04Dr1yCEJy2NA/viewform). * If suitable, PancakeSwap will contact you for further due diligence. * Once approved, the team will align on tokenomics, marketing, and launch timeline. * Marketing and community onboarding begins. * Launch CAKE.PAD event. ### 2. What are the launch fees? * Launching a CAKE.PAD event on PancakeSwap is **completely free**. * PancakeSwap does not charge any fees to projects. ### 3. Do CAKE.PAD events support lockups or cliffing schedules? * Yes, but current CAKE.PAD event launches are conducted **without any lockups**. ### 4. How PancakeSwap Supports CAKE.PAD Partner Projects {% hint style="success" %} See stats and past performance of CAKE.PAD partner projects launched with PancakeSwap: {% endhint %} #### Co-Marketing * Access to >400k DAUs and >2M social media followers. * PancakeSwap provides co-marketing support **before, during, and after** the CAKE.PAD event. * Could include social media announcements, KOL marketing, ads on PCS home page, and incentives for users to try your product. * Projects should allocate a marketing budget for these activities. 🔗 [Example social media announcement](https://x.com/PancakeSwap/status/1879107402752245982) #### LP Incentives * Reward users providing liquidity (e.g., XYZ-BNB or XYZ-USDT). * Builds deep liquidity for your token pair on a DEX with >$2B TVL and >$3B daily volume. * Improves trading experience with low slippage. * Boosts token visibility and market traction. #### Syrup Pool Campaign * Launch a **“Stake XYZ, Earn CAKE”** staking campaign to increase token utility and encourage user acquisition and retention. * Typically attracts **4,500 to 6,000 unique wallet address**. #### Trading Contests * Post-CAKE.PAD event trading contests amplify trading activity and visibility. * Historically, campaigns see **5x to 10x boost in trading volume**. **Note:** PancakeSwap reserves the final right to decide which campaigns to support based on oversubscription and raise amount. --- # 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.pancakeswap.finance/earn/cakepad/faq-partners.md?ask=&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.