> For the complete documentation index, see [llms.txt](https://docs.div.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.div.fun/for-creators/after-launch.md). # After launch Once your token is deployed, the protocol does the mechanical work — pricing, graduation, conversion, and distribution all run on their own. Your job shifts to the one thing the protocol cannot do for you: give the token a reason to be traded. ### What runs automatically You do not operate any of this: * **Curve and graduation.** If you launched on a [curve](/core-concepts/the-bonding-curve.md), it prices the token and [graduates](/core-concepts/graduation.md) it when the target is reached, with LP tokens burned automatically, permanently locking the liquidity. * **Dividend conversion.** Each trade's [dividend share](/core-concepts/dividend-distribution.md) is converted into the reward asset on-chain — from the very first trade, whether on the curve or the open market. * **Distribution.** The [keeper](/protocol/the-keeper.md) pushes dividends to holders. You do not run it, fund it, or trigger it. There is no admin panel you must attend to keep dividends flowing. There is also, by design, no lever for you to pull to change the token's terms — they were fixed at launch. ### Burn LP (direct-liquidity launches) If you launched with direct liquidity, you received the LP tokens at launch. You can burn them — send them permanently to the dead address — in one click from the token page. Once burned, the pool is locked forever and no one can remove the liquidity. Every token page shows a public **"Liquidity X% burned"** badge. For bonding-curve tokens, LP is burned automatically at graduation (\~100%). For direct-liquidity tokens, the badge reflects however much of the LP has been burned by the creator. Burning LP is optional, but many holders treat it as a signal that the pool is permanent. ### What depends on you Dividends come from **volume**. A token that is not traded pays its holders — and you — nothing, no matter how it is configured. So the work after launch is the work of any token: give people a reason to hold and to trade it. * **Tell the truth about what it pays.** Your token's dividend history is public and on-chain. The most credible thing you can say is "look at what it has paid", and the interface already shows it. Let the record do the selling. * **Reach the holders your reward asset suits.** A stock-paying token speaks to people who want that exposure; a stablecoin-paying token speaks to people who want legible yield. Reach the audience the [reward asset](/for-creators/choosing-a-reward-asset.md) implies. * **Sustain trading.** Volume is what pays everyone. A token with a reason to be traded keeps paying; one without fades. ### Your income You earn the creator's share of every trade, in the reward asset, for as long as the token trades. It arrives the same way holders' dividends do — converted and distributed automatically. See [economics](/for-creators/economics-and-fees.md) for the full flow. ### What you cannot do * You cannot change the **reward asset**, the **dividend tax**, or the **creator/holders split**. They are immutable. * You cannot withdraw **burned liquidity** — LP burned at graduation (bonding curve) or by your own action (direct liquidity) is gone permanently. * You cannot pause or alter holders' dividends. * You **can** burn your LP tokens if you launched with direct liquidity — see [Burn LP](#burn-lp-direct-liquidity-launches) above. These constraints are features. They are what let a holder trust your token without trusting you. The most successful thing you can do as a creator on div.fun is launch a token whose on-chain record speaks for itself, and then keep it worth trading. Once your token is deployed, the protocol does the mechanical work — pricing, graduation, conversion, and distribution all run on their own. Your job shifts to the one thing the protocol cannot do for you: give the token a reason to be traded. ### What runs automatically You do not operate any of this: * **Curve and graduation.** If you launched on a [curve](/core-concepts/the-bonding-curve.md), it prices the token and [graduates](/core-concepts/graduation.md) it when the target is reached, with LP tokens burned automatically, permanently locking the liquidity. * **Dividend conversion.** Each trade's [dividend share](/core-concepts/dividend-distribution.md) is converted into the reward asset on-chain — from the very first trade, whether on the curve or the open market. * **Distribution.** The [keeper](/protocol/the-keeper.md) pushes dividends to holders. You do not run it, fund it, or trigger it. There is no admin panel you must attend to keep dividends flowing. There is also, by design, no lever for you to pull to change the token's terms — they were fixed at launch. ### Burn LP (direct-liquidity launches) If you launched with direct liquidity, you received the LP tokens at launch. You can burn them — send them permanently to the dead address — in one click from the token page. Once burned, the pool is locked forever and no one can remove the liquidity. Every token page shows a public **"Liquidity X% burned"** badge. For bonding-curve tokens, LP is burned automatically at graduation (\~100%). For direct-liquidity tokens, the badge reflects however much of the LP has been burned by the creator. Burning LP is optional, but many holders treat it as a signal that the pool is permanent. ### What depends on you Dividends come from **volume**. A token that is not traded pays its holders — and you — nothing, no matter how it is configured. So the work after launch is the work of any token: give people a reason to hold and to trade it. * **Tell the truth about what it pays.** Your token's dividend history is public and on-chain. The most credible thing you can say is "look at what it has paid", and the interface already shows it. Let the record do the selling. * **Reach the holders your reward asset suits.** A stock-paying token speaks to people who want that exposure; a stablecoin-paying token speaks to people who want legible yield. Reach the audience the [reward asset](/for-creators/choosing-a-reward-asset.md) implies. * **Sustain trading.** Volume is what pays everyone. A token with a reason to be traded keeps paying; one without fades. ### Your income You earn the creator's share of every trade, in the reward asset, for as long as the token trades. It arrives the same way holders' dividends do — converted and distributed automatically. See [economics](/for-creators/economics-and-fees.md) for the full flow. ### What you cannot do * You cannot change the **reward asset**, the **dividend tax**, or the **creator/holders split**. They are immutable. * You cannot withdraw **burned liquidity** — LP burned at graduation (bonding curve) or by your own action (direct liquidity) is gone permanently. * You cannot pause or alter holders' dividends. * You **can** burn your LP tokens if you launched with direct liquidity — see [Burn LP](#burn-lp-direct-liquidity-launches) above. These constraints are features. They are what let a holder trust your token without trusting you. The most successful thing you can do as a creator on div.fun is launch a token whose on-chain record speaks for itself, and then keep it worth trading. --- # 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.div.fun/for-creators/after-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.