> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/for-developer/clisbnb/token-lifecycle.md).

# Token Lifecycle

`slisBNBx` is minted and burned by `SlisBNBxMinter` as a consequence of a collateral movement in Moolah. There is no user-callable mint. `SlisBNBxMinter` is not the only live minter, though — the legacy CDP's `HelioProvider` still holds minter rights too; see the note below.

| Step        | What you do                                                                     | What happens on-chain                                                                                                               |
| ----------- | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| 1. Deposit  | Supply `slisBNB` or a `slisBNB/BNB` LP position to Moolah through its provider. | Collateral is recorded and the provider calls `SlisBNBxMinter`.                                                                     |
| 2. Mint     | —                                                                               | The minter derives the `slisBNBx` amount from the BNB-equivalent value of the collateral and mints it to you, or to your delegatee. |
| 3. Hold     | Hold the certificate. It is non-transferable.                                   | The holder qualifies for Binance Launchpool.                                                                                        |
| 4. Withdraw | Withdraw collateral from Moolah, in full or in part.                            | The provider calls the minter to burn.                                                                                              |
| 5. Burn     | —                                                                               | The minter burns the share of `slisBNBx` matching the collateral removed, so supply stays fully collateral-backed.                  |

Plan around three consequences:

* **A partial withdrawal burns only the proportional amount** — the rest of the certificate stays minted. Whether the remaining balance still qualifies for a given Launchpool is decided by that campaign's own rules, not by this contract.
* **You cannot hold `slisBNBx` without the backing collateral.** Any path that removes collateral removes the certificate with it.
* **This lifecycle is the Moolah integration.** The legacy CDP is a separate, still-live mint/burn path through its own `HelioProvider` — not something this page documents. See [Delegation](/for-developer/clisbnb/delegation.md) for how the two paths differ.

See [Delegation](/for-developer/clisbnb/delegation.md) for directing the mint to another address, and [Minting Ratio Logic](/for-developer/clisbnb/minting-ratio-logic.md) for how the amount is derived.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsc.lista.org/for-developer/clisbnb/token-lifecycle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.