> For the complete documentation index, see [llms.txt](https://docs.hemi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hemi.xyz/building-bitcoin-apps/hemi-virtual-machine-hvm/feature-summary.md).

# Feature Summary

{% hint style="warning" %}
This documentation page is outdated and may not reflect current information.
{% endhint %}

{% hint style="info" %}

## 📜 **TL;DR:**

* Smart contracts on Hemi can access Bitcoin data by calling the hVM precompile contract.
* Future protocol upgrades will add additional precompile calls to provide additional information.
  {% endhint %}

***

## 🌐 Overview

* Smart contracts on Hemi can access Bitcoin data by calling the hVM precompile contract addresses, which query the deterministic TBC node running inside the EVM. 
* Future protocol upgrades will add additional precompile calls to provide additional information like Bitcoin fee levels, Bitcoin block construction information, and popular metaprotocols like Ordinals, BRC-20s, and Runes.

***

## ℹ️ "Phase 0" Precompile Summary <a href="#hvm-precompile-addresses" id="hvm-precompile-addresses"></a>

<table><thead><tr><th>Name</th><th width="125">Address</th><th>Description</th></tr></thead><tbody><tr><td>BtcBalAddr</td><td>0x40</td><td>Gets the balance of an address in satoshis. Supports all address formats: P2PKH, P2SH, P2WPKH, P2WSH, P2TR.</td></tr><tr><td>BtcUtxosAddrList</td><td>0x41</td><td>Gets the list of Unspent Transaction Outputs (UTXOs) for an address. Supports pagination.</td></tr><tr><td>BtcTxByTxid</td><td>0x42</td><td>Gets parts of a Bitcoin transaction by its TxID. The caller can specify which part(s) of the transaction to return using packed bitflags to increase gas efficiency by dropping unnecessary data.</td></tr><tr><td>BtxTxConfirmations</td><td>0x43</td><td>Gets the number of confirmations a specified transaction by TxID has.</td></tr><tr><td>BtcLastHeader</td><td>0x44</td><td>Gets the most recent Bitcoin header known by hVM.</td></tr><tr><td>BtcHeaderN</td><td>0x45</td><td>Gets the canonical Bitcoin header at height N.</td></tr><tr><td>BtcAddrToScript</td><td>0x46</td><td>Converts a Bitcoin address to its corresponding script representation. Supports all address formats: P2PKH, P2SH, P2WPKH, P2WSH, P2TR.</td></tr></tbody></table>


---

# 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.hemi.xyz/building-bitcoin-apps/hemi-virtual-machine-hvm/feature-summary.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.