> 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

The `slisBNBx` lifecycle is strictly controlled by `SlisBNBxMinter`. Users and external contracts cannot mint directly.

| Step        | Action                                                                                                    | Result                                                      |
| ----------- | --------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- |
| 1. Deposit  | User deposits `slisBNB` or `slisBNB/BNB LP` into Moolah through the related provider/collateral contract. | Collateral is recorded and provider calls `SlisBNBxMinter`. |
| 2. Mint     | Minter calculates `slisBNBx` using BNB-equivalent collateral value and calls `slisBNBx.mint()`.           | `slisBNBx` is credited to user or delegated address.        |
| 3. Hold     | User holds `slisBNBx` (non-transferable).                                                                 | Holder qualifies for Launchpool participation.              |
| 4. Withdraw | User withdraws collateral from Moolah, fully or partially.                                                | `SlisBNBxMinter` is called for proportional burn.           |
| 5. Burn     | Minter burns `slisBNBx` corresponding to collateral removed.                                              | `slisBNBx` supply is reduced and stays collateral-backed.   |

## Notes

* Minting and burning always follow collateral state.
* Partial withdrawals burn only the proportional amount.
* This lifecycle applies to Moolah integration, not legacy CDP.


---

# 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:

```
GET https://docs.bsc.lista.org/for-developer/clisbnb/token-lifecycle.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.