> 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/kr/archive/legacy-products/archived-liquid-staking-integration/wbeth.md).

# WBETH

WBETH 소개

\*\*Wrapped Beacon Ethereum(WBETH)\*\*은 스테이킹된 ETH와 그 보상을 나타내는 리퀴드 스테이킹 파생 토큰입니다. BETH의 래핑 버전으로 1 WBETH가 1 BETH를 나타내며, 사용자가 Ethereum 네트워크의 ETH 스테이킹 보상에 참여할 수 있도록 Binance Earn이 만들었습니다. 래핑된 토큰은 원래 구축된 블록체인이 아닌 다른 블록체인에서 암호화폐를 사용하면서도 기초 자산으로 뒷받침되도록 하는 방식입니다.\
\
WBETH는 또한 2023-04-27 08:00(UTC) 이후 ETH 스테이킹에서 BETH 토큰이 누적한 스테이킹 보상을 나타냅니다. BETH 보유자를 위해 BETH를 WBETH로 1:1 고정 비율로 전환하는 추가 지원이 향후 몇 주 내에 제공될 예정입니다.\
\
WBETH에 대해 자세히 알아보려면 [다음 링크를 방문하세요.](https://www.binance.com/en/support/faq/what-is-wbeth-e252366155174ba6887f6b32e3798273)

Binance ETH 스테이킹에 대해 자세히 알아보려면 [다음 링크를 방문하세요.](https://www.binance.com/en/support/faq/binance-eth-2-0-staking-eecd04618b5042c79f2a5b07f895c498)

ETH 스테이킹 이용 약관에 대해 자세히 알아보려면 [다음 링크를 방문하세요](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/kr/archive/legacy-products/archived-liquid-staking-integration/wbeth.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.
