> For the complete documentation index, see [llms.txt](https://docs.bedrock.technology/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bedrock.technology/multi-asset-liquid-staking/unibtc/introduction/btc-staking-mechanism.md).

# BTC staking mechanism

{% hint style="info" %}
This section of document is still in development.
{% endhint %}

When a wBTC token is deposited into Bedrock, an actual BTC token will be staked to the Babylon network in real-time. This process can occur through one of two approaches currently in development:

1. **Proxy Staking:** a proxy mechanism can be used, where wBTC tokens are staked on the Ethereum network, and a corresponding amount of BTC tokens are staked on the Babylon network by a trusted party. This approach allows for flexibility and interoperability between the two networks.
2. **Direct Conversion:** Alternatively, wBTC tokens are instantly redeemed into BTC tokens, which are then staked directly onto the Babylon network. This approach ensures seamless and immediate conversion and staking, without involving the centralised custodial wallet.

Both approaches aim to facilitate the smooth transition of assets between the Ethereum and Babylon networks, enabling efficient and secure staking operations.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.bedrock.technology/multi-asset-liquid-staking/unibtc/introduction/btc-staking-mechanism.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.