> 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/user-guide/liquid-staking-slisbnb/bridging-slisbnb-to-ethereum.md).
# Bridging slisBNB to Ethereum
Bridging slisBNB between BSC and Ethereum does not warrant any bridging fees. Users only need to pay for gas fees to move their slisBNB across the two blockchains.
### Bridging slisBNB between BSC and Ethereum:
1. Head over to [Lista.org](https://lista.org?utm_source=gitbook\&utm_medium=article\&utm_campaign=bridging-slisbnb-to-ethereum), connect your wallet, and head over to the liquid staking section.
2. Once you are at the liquid staking page, click “Go to Bridge” at the bottom.
3\. Once you are at slisBNB’s bridging page, insert the amount of slisBNB that you would like to bridge over.
4\. Bridging slisBNB over to Ethereum will take around 3 to 5 minutes to process. Users can check the status of their transactions on LayerZero scans [here](https://layerzeroscan.com/).
5\. Here is an example of how your transactions will look like if you have multiple bridging transactions queued up.
[ ](https://medium.com/@ListaDAO?source=post_page-----61e6e468074d--------------------------------)
---
# 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/user-guide/liquid-staking-slisbnb/bridging-slisbnb-to-ethereum.md?ask=&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.