# faq

<details>

<summary>Why do you call them "perp-backed" coins?</summary>

Because every basefun token's price reflects two inputs: bonding-curve trading **and** the live PnL of a real Avantis perpetual position. Buy `$ETH5X-PUMP`, you're effectively long 5× ETH plus whatever the meme momentum gives you.

</details>

<details>

<summary>Is there a team token? An airdrop?</summary>

No. There is no team allocation, no vesting schedule, no airdrop. Treasury revenue funds development and marketing. See [Treasury use](broken://pages/9e6aed11c648e81195a7bda23122721603fcdfc7).

</details>

<details>

<summary>Can the team rug a token after launch?</summary>

No. The factory cannot mint additional supply. The curve has no withdraw function. At graduation the LP tokens are sent to `0x000…dEaD` — the actual zero address — so no entity (team, creator, Uni) can ever pull the post-grad liquidity.

What the team **can** do:

* Rotate `protocolFeeRecipient` on the factory (affects future launches only — existing curves snapshot the recipient at deploy).
* Add or revoke migration whitelist addresses on the factory.
* Transfer factory ownership.

None of these touch existing token supply, balances, fee splits, or LP.

</details>

<details>

<summary>What stops a malicious creator?</summary>

* Supply, fee recipient, curve parameters are immutable per token after deploy.
* The creator's `creatorFeeRecipient` only receives 0.5% of trades — they cannot suddenly take 50%.
* The creator cannot drain the curve. They can buy and sell like anyone else, paying the same 1% fee.
* Pre-grad, the creator's profit comes from the same place as ours: trade volume. We're aligned.

</details>

<details>

<summary>What does the $300 graduation cut fund?</summary>

It's a one-shot top-up of the protocol treasury. Same treasury, same uses (development + marketing). Without it, the swap fee alone wouldn't generate meaningful runway during early-volume periods.

</details>

<details>

<summary>Why is the swap fee 1% and not 0.5% or 2%?</summary>

1% is the sweet spot between:

* High enough to fund a real team operating two off-chain services + audits.
* Low enough that small traders aren't penalized at the margin (per-trade economics work down to \~$20 buys).
* 50/50 split keeps creators meaningfully incentivized to keep their token alive long-term.

</details>

<details>

<summary>Can I change the underlying of my token after launch?</summary>

No. The bonding curve's `pairIndex`, `leverage`, `buyLong` are all `immutable`. If you want a different underlying, launch a new token.

</details>

<details>

<summary>What happens if Avantis liquidates the perp behind my token?</summary>

Bonding curve reserve crashes. Token spot drops toward zero. Holders can still sell into whatever residual reserve remains. See [Liquidation risk](broken://pages/661afc6d42d3c96dde46d5cd29a44b6969e458d1).

</details>

<details>

<summary>What happens if Avantis goes down or rolls out a breaking change?</summary>

Pre-bond functionality (opening new perps for new LT mints) degrades. Existing trades' PnL queries may fail — basefun's `try/catch` treats failed PnL reads as zero, so NAV becomes conservative but never reverts. Once Avantis is back, the keeper resumes opening on the next LT mint. No data loss.

</details>

<details>

<summary>Why doesn't my buy go through?</summary>

Top reasons:

1. **Insufficient ETH for gas.** Top up your wallet.
2. **Slippage too tight on a small-reserve curve.** Bump slippage to 3–5%.
3. **USDC allowance not set or too low.** Re-approve the curve.
4. **Wallet showing "transaction will likely fail" right after approve.** Wait 5–10s for the wallet's RPC to see the approve.

See [Execution fees and slippage](broken://pages/55ab2d317333b721937b9e0a1967aaf5448f8d0e) for the full diagnostic list.

</details>

<details>

<summary>Why can't I sell my token?</summary>

If the sell reverts with `ERC20: transfer amount exceeds allowance`, the LT's USDC allowance from the keeper EOA might not be set yet (one-time per LT). Mention the token in the Telegram group and the team will run the approve. After that, sells work normally.

</details>

<details>

<summary>How fast do I get my creator fees?</summary>

* **Pre-bond**: same transaction as the trade. USDC lands in your `creatorFeeRecipient` wallet instantly.
* **Post-bond (V2 tokens)**: within one keeper tick (sub-minute) of the swap, after the keeper has accumulated enough token balance to cross its $5 sweep threshold. The first few small swaps may sit in the keeper's bag for a few minutes before getting swept together.

</details>

<details>

<summary>What does "FOT" mean?</summary>

Fee-on-transfer. A token where 1% of each transfer is silently routed to a fee collector. basefun's V2 tokens turn FOT on for transfers touching the Uni V2 pair (so swaps pay 1%) but leave wallet-to-wallet transfers fee-free.

</details>

<details>

<summary>Where can I see all the contract addresses?</summary>

[Deployed addresses](broken://pages/6f5a0e4594a2e2ac74823a7dc367365fa6eff377).

</details>

<details>

<summary>Can I integrate basefun from my own app?</summary>

Yes. All contracts are public and verified. The API at <https://basefun.app/api/> is open (no auth required for reads). Hit `GET /api/tokens?limit=100` to enumerate launches, or talk directly to the contracts via standard ERC-20 / Uni V2 / `BondingCurveV2` interfaces.

If you build something useful with it, post in the Telegram and we'll cross-promote.

</details>

<details>

<summary>How do I report a bug or security issue?</summary>

DM in the Telegram group <https://t.me/basefunapp>. For anything potentially exploitable, please go through DM (not the public group) so we can patch before disclosure.

</details>


---

# Agent Instructions: 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://basefun.gitbook.io/basefun-docs/faq.md?ask=<question>
```

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.