> For the complete documentation index, see [llms.txt](https://docs.fractalbitcoin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fractalbitcoin.io/for-developers/developer-overview/runes-on-fractal.md).

# Runes on Fractal

Runes on Fractal follows the same set of rules as the Bitcoin mainnet. If you're familiar with the runes protocol on Bitcoin, you'll find that the structure and functionalities on Fractal are fully aligned with it. Here's what you need to know:

#### 1. **Same Rules as Bitcoin Mainnet**

The Runes protocol on Fractal follows the same fundamental rules as on Bitcoin, with all phases completed within one halving cycle (it takes 4 years on Bitcoin, and takes 2 years on Fractal)

There are 12 phases on both networks. Therefore, any single phase takes 120 days on Bitcoin, and 60 days on Fractal.

#### 2. **Ticker Names on Fractal**

On the Fractal mainnet, all Runes tickers are displayed in **lowercase** letters. 

For more detailed information on the Runes protocol, you can refer to the official documentation here: [Runes Protocol Documentation](https://docs.ordinals.com/runes.html).


---

# 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:

```
GET https://docs.fractalbitcoin.io/for-developers/developer-overview/runes-on-fractal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.