> For the complete documentation index, see [llms.txt](https://smol404.gitbook.io/smol404-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smol404.gitbook.io/smol404-docs/launchpad/how-to-launch.md).
# How to Launch
#### How to Launch
Launching an agent ecosystem through SMOL404 requires minimal technical knowledge.
Creators do not need to deploy contracts manually, seed initial liquidity, create an AMM pair or handle migration. The launchpad manages the full process from deployment to PancakeSwap graduation.
#### 1. Configure your token
Choose the core parameters of your SMOL404 token:
Name\
Symbol\
Total supply, from 1 to 10,000 whole tokens
Supply is fixed at launch and cannot be increased later.
Each whole token unit corresponds to one BAP-578 NFA.
Fractional balances remain fully fungible.
For example:
`0.7 TOKEN = 0 NFA`\
`1.2 TOKEN = 1 NFA`\
`3.4 TOKEN = 3 NFAs`
#### 2. Configure your agents
Define the default BAP-578 configuration used by the ecosystem.
Creators can provide:
Agent identity metadata\
Associated resources\
Default Agent Logic contract
The Agent Logic defines how an NFA behaves and what actions it can perform.
Creators may choose a logic already supported by the SMOL404 interface or provide their own compatible Agent Logic contract.
The selected logic becomes the default for newly created NFAs.
Individual NFA owners may later change the logic attached to the agents they own.
#### 3. Launch
Once configuration is complete, the creator submits the launch and pays a **0.01 BNB launch fee**.
SMOL404 automatically deploys and connects:
**SMOL404 Token**\
**BAP-578 NFA Collection**\
**Bonding Market**\
**Official PancakeSwap V2 Pair**
No initial liquidity is required from the creator.
The entire token supply is allocated automatically:
**80% → Bonding Market**\
**20% → Reserved for PancakeSwap V2 liquidity**
The creator receives no pre-minted token allocation.
#### 4. Bonding phase
The token becomes immediately tradable through the SMOL404 bonding market.
Users can both buy and sell during this phase.
The bonding market uses a virtual-reserve constant-product curve. Tokens begin at a lower price and become progressively more expensive as the market approaches graduation.
BAP-578 synchronization is active from launch.
Holding complete token units automatically creates corresponding NFAs.
If a holder later falls below a whole-unit threshold, the corresponding NFA is terminated according to the protocol’s synchronization rules.
Trading during the bonding phase carries a **1% fee**:
**50% → SMOL404 Treasury**\
**50% → Token Creator**
Treasury fees are distributed directly.
Creator fees accumulate onchain and can be claimed by the creator.
#### 5. Graduation
The bonding phase ends once the market reaches **18 BNB of net bonded liquidity**.
At graduation, the token is migrated automatically to its official PancakeSwap V2 market.
Under normal conditions:
**17 BNB + 20% of total supply → PancakeSwap V2 liquidity**
The bonding curve is calibrated so that its final marginal price is as close as possible to the initial PancakeSwap liquidity price.
The remaining **1 BNB** is used as the graduation fee:
**70% → SMOL404 Treasury**\
**30% → Token Creator**
The creator share is added to the creator’s claimable fee balance.
#### 6. Permanent PancakeSwap liquidity
Once migration is complete, the resulting PancakeSwap V2 LP tokens are permanently burned.
Neither the creator nor the SMOL404 team can withdraw the initial liquidity.
The bonding market closes and the token becomes freely tradable through PancakeSwap.
Tokens acquired during the bonding phase remain unchanged after migration.
Holders can keep them, transfer them or sell them through PancakeSwap.
The SMOL404 synchronization mechanism continues operating normally after graduation.
#### Full launch flow
`Configure Token → Configure Agent → Launch → Bonding Market → 18 BNB Graduation → PancakeSwap V2 → LP Burned Permanently`
No manual liquidity seeding, AMM deployment or migration is required.
[
](https://four-meme.gitbook.io/four.meme)
---
# 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://smol404.gitbook.io/smol404-docs/launchpad/how-to-launch.md?ask=&goal=
```
`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.