> For the complete documentation index, see [llms.txt](https://docs.revolt.cool/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revolt.cool/how-it-works.md).

# How It Works

## Two modes, one destination

Revolt offers both classic launch models, chosen by the creator at launch:

* **Instant Uniswap** — the token, its Uniswap v3 pool, and its locked liquidity are all created in one transaction. A real DEX pair from its very first second.
* **Bonding Curve** — the token starts on an internal constant-product curve (x·y=k with virtual reserves). 80% of the supply is sold on the curve; when **5 ETH** have been raised, the curve closes and the raised ETH (minus a 2% listing fee) plus the remaining 20% of supply are deposited into a Uniswap v3 pool at the curve's final price. The LP position is locked in the protocol forever.

After graduation, a curve token is **indistinguishable from an instant token**: same 1% pool tier, same locked liquidity, same creator fee share.

## Bonding curve mechanics

* Constant-product pricing (`x · y = k`) with \~1.712 virtual ETH: buys push the price up, sells walk it back down — a vending machine with a sliding price. No order book, no market makers.
* **Curve trading fee: 1%** of each trade (in ETH), split **30% to the creator / 70% to the protocol**. Creator fees accrue in the on-site Fee Vault and are claimable anytime.
* Buys that overshoot the 5 ETH target are capped and the surplus is refunded — graduation lands exactly on target.
* **Graduation (atomic):** curve closes permanently → 4.9 ETH + remaining supply become a full-range Uniswap v3 position at the curve's last price → the LP position is locked (no withdraw function). Post-graduation pool fees are split 30/70 like everything else.

## Instant launch mechanics

When a creator calls `createToken` on the Revolt launcher:

1. **Token deploy.** A minimal ERC-20 is deployed: `1,000,000,000` supply, 18 decimals, fully minted at creation. There is no `mint` function, no owner, no blacklist, no transfer tax. The contract is immutable.
2. **Pool creation.** A Uniswap v3 pool `TOKEN / ETH` is created and initialized at the protocol's fixed starting price (see table below) on the **1% fee tier**.
3. **Single-sided liquidity.** 100% of the supply is deposited into the pool as a single-sided position starting just above the initial price. No ETH is required from the creator — the pool starts with tokens only, and fills with ETH as people buy.
4. **Permanent lock.** The LP position (an NFT) is minted **to the launcher contract itself**, which has no function to withdraw or transfer it. The liquidity is locked for as long as the chain exists.
5. **Optional dev buy.** If the creator attached ETH, it is swapped into the token in the same transaction — the creator gets the first fill on their own pool, at the same price rules as everyone else.

## Starting parameters

| Parameter            | Value                                                           |
| -------------------- | --------------------------------------------------------------- |
| Total supply         | 1,000,000,000 (fixed, immutable)                                |
| Supply in the pool   | 100%                                                            |
| Pool fee tier        | 1% (Uniswap v3 `10000`)                                         |
| Starting price       | \~0.0000000016 ETH per token                                    |
| Starting market cap  | \~1.6 ETH                                                       |
| Creator ETH required | 0 (dev buy optional)                                            |
| LP lock              | Permanent — position held by the protocol, no withdraw function |

Every launch starts identical. The market — not the deployer — decides everything after block one.

## Price discovery

Because the liquidity is a concentrated single-sided range, the pool behaves like a curve: early buys are cheap, and the price climbs as ETH flows in and tokens flow out. Sells walk the price back down the same path. It's the same "vending machine with a sliding price" feel as a bonding curve — except it happens **on Uniswap itself**, so:

* every chart platform and aggregator indexes it natively,
* any router, bot, or wallet can trade it with standard Uniswap calls,
* there is no migration event, no liquidity move, no rug window.

## Fee flow

Each swap on the pool pays the Uniswap 1% fee tier. Those fees accrue to the locked LP position, which the protocol owns — and redistributes:

| Recipient             | Share of pool fees |
| --------------------- | ------------------ |
| **Token creator**     | 30%                |
| **Protocol treasury** | 70%                |

* Fees accrue in **both** assets (ETH side and token side).
* `collectFees(token)` is **permissionless** — anyone can call it; payouts go directly to the creator wallet and the treasury.
* There are no other fees: no launch fee, no Revolt-side buy/sell tax, no graduation fee (there is no graduation).

## Which mode should I pick?

* **Instant Uniswap** if you want your token visible on every tracker (DexScreener, Axiom, GeckoTerminal…) from second one — DEX indexers only see tokens once they have a pool, and this mode gives you one immediately.
* **Bonding Curve** if you want the classic fair-launch race: everyone starts at the same low price, the curve rewards conviction, and graduation is a milestone the community chases. The trade-off: until graduation, the token trades only on Revolt.

## Trust model — what can and cannot happen

* **Liquidity cannot be pulled.** The LP NFT sits in a contract with no exit path for it.
* **Supply cannot be inflated.** The token has no mint function and no owner.
* **The creator has no special powers.** After launch, the creator's only privilege is receiving 30% of pool fees.
* **What remains market risk:** price is set purely by trading. A meme can go to zero — that part is the game.


---

# 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.revolt.cool/how-it-works.md?ask=<question>&goal=<endgoal>
```

`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.