> For the complete documentation index, see [llms.txt](https://docs.antivamp.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.antivamp.io/for-creators/launch-on-pumpfun.md).
# Launch on pump.fun
Launch a Solana token on pump.fun directly from antivamp.io — identity-gated at creation, a 70/30 creator-fee split set on-chain, and automatic ticker protection when your token graduates.
AntiVamp has a native **launch factory** for pump.fun: you create your token from [antivamp.io/reservations](https://antivamp.io/reservations) (the **Launch** tab in the Creator hub), signing with your own Solana wallet. Every launch is checked against the identity index first, so you can never accidentally vamp a protected name — and your own launch starts earning protection the moment it confirms.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
## How a launch works
```mermaid
flowchart LR
M["🖼️ Metadata pinned to IPFS"] --> G["🛡️ Identity check"]
G --> C["✍️ You sign the create transaction"]
C --> F["🤝 You sign the 70/30 fee split"]
F --> W["👁️ Bond watcher"]
W --> L["🔒 Ticker lock at graduation"]
```
1. **Metadata** — your token image (uploaded, or pasted as a URL — either way it is fetched and pinned) and metadata JSON are stored on IPFS, so they outlive any external host. Token images receive the **AntiVamp Launch Mark** (a small circular badge in the lower-left) so traders can see the launch origin — this is not proof of an active reservation. Optional banner, website, X, and Telegram links are included.
2. **Identity gate** — the launch is validated like any partner launch. A name + ticker that is reserved by someone else, or locked by a bond/milestone, is refused before you spend anything.
3. **Create** — you sign one transaction: mint creation on the pump.fun bonding curve, with an optional initial buy.
4. **Fee split** — a second signature sets the **immutable 70/30 creator-fee split** (70% you, 30% AntiVamp). If you skip it, your launched card on [My Reservations](https://antivamp.io/reservations) shows a **Complete fee share** button until it's done.
5. **Protection** — the launch is indexed under your wallet. From then on, the **bond watcher** checks your bonding curve every few minutes.
## Protection at graduation
A pump.fun mint claims **no ticker lock at creation** — most pump.fun tokens never graduate, and locking every attempt would be a griefing vector. Protection fires when your bonding curve **completes** (graduates to the AMM):
Launch
Lock at graduation
Reserved (you held an active AntiVamp reservation for the pair)
60-day network-wide ticker lock
Unreserved
48-hour ticker lock
The lock is applied automatically by the watcher — no report, no button — and is mirrored to the on-chain registry through the same queue partner-reported bonds use. Your card on My Reservations shows the bond state and the lock expiry.
{% hint style="info" %}
🔒 Locks only ever **extend** (longest-lock semantics). If your identity already carries a longer protection window, graduating never shortens it.
{% endhint %}
## Creator fees
pump.fun pays the coin creator a share of trading fees. With the AntiVamp split:
* **You receive 70%**, AntiVamp receives 30% — set once, on-chain, immutable per launch (earlier launches keep the split they were created with).
* Fees **accrue in a vault** and move when a *distribute* instruction runs. Distribution is **permissionless**: AntiVamp's keeper can crank it for everyone, and either shareholder can trigger it — the split itself can't be changed by whoever cranks.
* If you never sign the fee-share transaction, no split exists — you keep 100%, but the launch shows as incomplete in your hub and AntiVamp may prompt you to finish it.
{% hint style="warning" %}
⚠️ Fee amounts depend entirely on trading volume. Neither the split nor this page is a promise of any fee income.
{% endhint %}
## What's recorded
Every launch is logged durably — mint, creator wallet, metadata URI, initial buy, both signatures, fee-share state, and bond state — so your Creator hub shows the full lifecycle and support can reconstruct any launch, including failed or abandoned ones. The **My Launches** tab in the [Creator hub](https://antivamp.io/reservations?tab=launches) lists every token you have launched, with its image, pump.fun and Solscan links, fee-split status, and protection state.
## Try it
1. Open [antivamp.io/reservations](https://antivamp.io/reservations) and pick the **Launch** tab.
2. (Optional, recommended) **Reserve** your name + ticker first for the 60-day graduation lock and launch-window exclusivity — see [Reserve a Name + Ticker](/for-creators/reserve.md).
3. Fill in the token details, connect your wallet, and sign the two transactions.
🔗 Related: [Launch with Protection](/for-creators/launch-with-protection.md) · [Post-Launch Protection](/for-creators/post-launch-protection.md) · [Reservation Tiers](/for-creators/reservation-tiers.md)
---
# 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://docs.antivamp.io/for-creators/launch-on-pumpfun.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.