> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/archive/legacy-products/archived-liquid-staking-integration/wbeth.md). # WBETH Introduction to WBETH **Wrapped Beacon Ethereum (WBETH)** is a liquid staking derivative token representing staked ETH and its rewards. It’s a wrapped version of BETH, where 1WBETH represents 1 BETH, and is created by Binance Earn that allows users to participate in ETH staking rewards from the Ethereum network. Wrapped tokens are a way to use cryptocurrencies on blockchains other than the blockchain they were originally built on while being backed by their underlying asset.\ \ WBETH also represents the staking rewards accrued by BETH token on ETH Staking after 2023-04-27 08:00 (UTC). For BETH holders, further support to convert BETH to WBETH at a 1:1 fixed rate will be available in the coming weeks.\ \ To learn more about WBETH, please [visit the following link.](https://www.binance.com/en/support/faq/what-is-wbeth-e252366155174ba6887f6b32e3798273) To learn more about Binance ETH Staking, [visit the following link.](https://www.binance.com/en/support/faq/binance-eth-2-0-staking-eecd04618b5042c79f2a5b07f895c498) To understand more about ETH Staking terms and conditions, [visit the following link](https://www.binance.com/en/support/faq/binance-eth-2-0-staking-terms-and-conditions-74b48ca392874849aba9560e7a8fc11b). --- # 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.pancakeswap.finance/archive/legacy-products/archived-liquid-staking-integration/wbeth.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.