> 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/liquid-staking-slisbnb/smart-contract.md).

# Smart Contract

slisBNB is Lista's yield-bearing liquid staking token for BNB. BNB is staked through `ListaStakeManager`, which delegates to BSC validators via the native StakeHub system contract and mints slisBNB to the staker. slisBNB can be bridged to Ethereum through LayerZero OFT contracts (lock on BSC, mint on Ethereum). See [Mechanics](/for-developer/liquid-staking-slisbnb/mechanics.md) for the staking flow and [Cross-Chain Bridge](/for-developer/liquid-staking-slisbnb/cross-chain-bridge.md) for the bridge architecture.

## Core Contracts (BNB Chain)

| Contract          | Description                                                              | Address                                                                                                              |
| ----------------- | ------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| slisBNB           | Liquid staking token (ERC-20, name `Staked Lista BNB`, symbol `slisBNB`) | [0xB0b84D294e0C75A6abe60171b70edEb2EFd14A1B](https://bscscan.com/address/0xB0b84D294e0C75A6abe60171b70edEb2EFd14A1B) |
| ListaStakeManager | Stakes BNB through the native StakeHub and mints/burns slisBNB           | [0x1adB950d8bB3dA4bE104211D5AB038628e477fE6](https://bscscan.com/address/0x1adB950d8bB3dA4bE104211D5AB038628e477fE6) |

## Cross-Chain (LayerZero OFT)

slisBNB uses the LayerZero OFT standard. The adapter locks slisBNB on BNB Chain; the OFT mints/burns the equivalent on Ethereum. LayerZero endpoint IDs (EIDs): BNB Chain `30102`, Ethereum `30101`.

| Contract        | Chain                 | Role                                                 | Address                                                                                                               |
| --------------- | --------------------- | ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| ListaOFTAdapter | BNB Chain (EID 30102) | Lock/unlock adapter over the canonical slisBNB token | [0x837CB07f6B8a98731856092457524FF37b25E7B3](https://bscscan.com/address/0x837CB07f6B8a98731856092457524FF37b25E7B3)  |
| ListaOFT        | Ethereum (EID 30101)  | Mint/burn OFT representing slisBNB on Ethereum       | [0xf9B24C9364457Ea85792179D285855753549eBAa](https://etherscan.io/address/0xf9B24C9364457Ea85792179D285855753549eBAa) |

## Native BSC System Contracts

`ListaStakeManager` delegates, redelegates, and undelegates through BSC's built-in staking system contracts. These are fixed protocol addresses on BNB Chain.

| Contract | Description                                                                 | Address                                                                                                              |
| -------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| StakeHub | Native BSC staking hub used for delegation, redelegation, and reward claims | [0x0000000000000000000000000000000000002002](https://bscscan.com/address/0x0000000000000000000000000000000000002002) |
| GovBNB   | Native BSC governance token minted on delegation                            | [0x0000000000000000000000000000000000002005](https://bscscan.com/address/0x0000000000000000000000000000000000002005) |

slisBNB bridges to Ethereum as a LayerZero OFT — see [Cross-Chain Bridge](/for-developer/liquid-staking-slisbnb/cross-chain-bridge.md).


---

# 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/liquid-staking-slisbnb/smart-contract.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.