> For the complete documentation index, see [llms.txt](https://docs.uprotocol.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uprotocol.finance/usdubtc/usdubtc-utility.md).

# $uBTC Utility

* Store of Value: $uBTC allows for decentralized and immutable holding of BTC, acting as a reliable store of value.
* Long Exposure to ETH/BTC Pair: $uBTC provides a means for decentralized long exposure in the ETH/BTC trading pair, allowing users to potentially profit from market fluctuations.
* Decentralized Omnichain DeFi Use Cases: $uBTC opens up a world of decentralized omnichain BTC DeFi use cases, such as providing liquidity and participating in yield farming opportunities.
* Payment and Settlement: $uBTC can be used as a medium of exchange in transactions across various platforms. 
* Collateral: $uBTC can be used as a collateral for minting stablecoins in various DeFi platforms.

  \ <br>

  \ <br>


---

# 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.uprotocol.finance/usdubtc/usdubtc-utility.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.