> For the complete documentation index, see [llms.txt](https://docs.unstable.run/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unstable.run/launching-a-coin/after-launch.md).

# After the launch

Your `launchToken` transaction just confirmed. Here's what happens next.

## Immediately

The board on the Unstable homepage refetches within a few seconds and your card appears at the top of "New". A few seconds later, if you did an initial buy, your entry candle shows up on the chart.

You can share your token URL right away:

```
https://unstable.run/token/0xYOUR_TOKEN_ADDRESS
```

That's a **shareable, permanent** link. Post it on X, drop it in your Telegram, whatever — everyone gets the same page you see.

The launch transaction is also permanently visible on [StableScan](https://stablescan.xyz). Your metadata (name, symbol, logo URI, description, socials) is on-chain in the token contract; anyone with an RPC can read it.

## Trading elsewhere

Because Unstable uses **canonical Uniswap V3**, your token trades everywhere V3 is supported on Stable — not just here. Users can also:

* Trade via [swap.stable.xyz](https://swap.stable.xyz) — the official Uniswap V3 UI on Stable.
* Trade via `SwapRouter02` directly — every V3 trading bot and aggregator understands this.
* Add your pool to a portfolio tracker that indexes canonical V3 pools.

The pool address is deterministic — Uniswap V3 Factory `getPool(TOKEN, USDT0, 10000)` returns it.

## Where do fees go?

Every trade on your pool charges a **1% fee**. The V3 pool holds those fees inside the LP position NFT that's locked in the Unstable LP Locker. They accrue until someone triggers a collection.

* **80% of collected fees** → the wallet you set as the **fee recipient** (defaults to your wallet if you didn't set one explicitly).
* **20% of collected fees** → the Unstable platform treasury.

Collections are **permissionless**: anyone can call `collectFees(YOUR_TOKEN)` on the LP Locker contract, and the funds route to the right slots automatically. The caller pays gas; that's their only stake.

See [Fees & creator rewards](/under-the-hood/fees-and-rewards.md) for the full mechanics, and [Claiming fees](/under-the-hood/fees-and-rewards.md#claiming) for the how-to.

## Watching your project grow

The token page shows every metric you'd want:

* **Market cap** — computed from `1B × current price`
* **24h volume** — sum of USDT0 across `Swap` events in the last 24h
* **Holders** — non-zero wallets, updated every minute
* **Chart** — TradingView-style candlesticks, 1m/5m/1h/1d timeframes
* **Recent trades** — last 30 swaps with wallets clickable to StableScan

Refreshes are polling-based, near-realtime (5-30 seconds depending on the surface).

## Should I do anything else?

**Yes** — go promote it. Nothing about the launch itself creates demand. The mechanics guarantee:

* Fair distribution at t=0
* Immutable metadata
* Fees to you forever

But the actual traders are humans you have to reach. Post your token URL, join relevant Telegram groups, engage on X. The launcher builds the market — you build the community.

## Common questions post-launch

| Question                                              | Answer                                                                                                                                                                                                          |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Can I change my token's logo / description / socials? | No. Every metadata slot is `string public` set once in the constructor. This is the trust guarantee — indexers and community can rely on what was set at t=0.                                                   |
| Can I add more liquidity later?                       | Not through Unstable directly, but yes via Uniswap V3 itself. Any wallet can mint a new position on your pool via the NonfungiblePositionManager.                                                               |
| Where's my LP position NFT?                           | It's owned by the Unstable LP Locker contract. See [LP position lock](/under-the-hood/lp-lock.md).                                                                                                              |
| Can I change the fee recipient?                       | Yes. Call `updateCreator(YOUR_TOKEN, newAddress)` on the LP Locker. Only your current fee recipient can call it — see [Fees & creator rewards](/under-the-hood/fees-and-rewards.md#changing-the-fee-recipient). |

## Next

* [Fees & creator rewards](/under-the-hood/fees-and-rewards.md) — how you actually get paid
* [Fair-launch model](/under-the-hood/fair-launch.md) — the trust story
* [LP position lock](/under-the-hood/lp-lock.md) — what "locked" means, exactly


---

# 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.unstable.run/launching-a-coin/after-launch.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.
