> 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/foundational-topics/the-architecture/gas.md).

# Gas

{% hint style="info" %}

## 📜 TL;DR:

* **Gas fees on Hemi** is paid using ETH, the network's native token.
* This approach is similar to Ethereum Layer 2 rollups like Optimism, where gas fees are in their native bridged tokens.
  {% endhint %}

***

## 🌐 **Overview**

* In cryptocurrency networks, **gas** refers to the tokens used to pay transaction fees. These fees are essential for processing transactions and maintaining network security, compensating network operators for the real-world costs they incur.

***

## 🔧 **Fee Mechanisms: Other Networks**

* For example, in the **Bitcoin network**, transaction fees are paid in BTC. **Ethereum**, on the other hand, uses ETH as gas. These fees serve the same fundamental purpose across different blockchains but are paid in the respective network's native tokens.

***

## ⛽ **Gas Fees on Hemi**

* Hemi adopts a method akin to Ethereum Layer 2 rollups by using ETH as its gas token. This strategy enhances compatibility and user-friendliness, particularly for those accustomed to Ethereum's system.
* To interact with the Hemi Network, users can obtain ETH and **tunnel** to Hemi. This ensures a seamless and efficient means for users to engage with the Hemi Network's services.

🔍 [Explore Network Details](/discover/network-details.md)


---

# 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/foundational-topics/the-architecture/gas.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.