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

# Gravity Mainnet Hardforks

Gravity Mainnet (L1) hardfork schedule, required node version, and what happens if a node misses an activation.

Mainnet (chain ID `127001`) activation times are compiled into the `gravity_node` release. Editing `genesis.json` does not change them. If genesis disagrees with the binary, the node keeps the binary value.

Validators, VFNs, and public full nodes must all run the required release before the next activation.

## Current required version

Upgrade to [v1.9.1](https://github.com/Galxe/gravity-sdk/releases/tag/v1.9.1) before **2026-08-18 02:00:00 UTC**.

```bash
docker pull ghcr.io/galxe/gravity_node:v1.9.1
```

Source builds must `git checkout v1.9.1` before compiling. See the PFN, VFN, and validator run guides.

## Schedule

Newest first. Only the top row still requires action.

| Hardfork     | Activation (UTC)    | Unix         | First release                                                      |
| ------------ | ------------------- | ------------ | ------------------------------------------------------------------ |
| Beta + Osaka | 2026-08-18 02:00:00 | `1787018400` | [v1.9.1](https://github.com/Galxe/gravity-sdk/releases/tag/v1.9.1) |
| Alpha        | 2026-07-27 05:00:00 | `1785128400` | [v1.8.0](https://github.com/Galxe/gravity-sdk/releases/tag/v1.8.0) |
| Prague       | 2026-06-29 05:00:00 | `1782709200` | [v1.7.3](https://github.com/Galxe/gravity-sdk/releases/tag/v1.7.3) |

## If you miss a hardfork

A node still on the previous rules executes the new schedule differently. The first block whose local execution hash does not match the committed hash stops the process. That block may be the activation block, or a later block.

This is fail-stop: the node does not keep serving a private fork. RPC height stops increasing.

Search logs for:

```
commit_info mismatch
Block hash mismatch
assertion `left == right` failed
```

There is no dedicated "hardfork missed" message. The failure is the same hash mismatch used for any execution-spec divergence.

## See also

* [Gravity Longevity Testnet Hardforks](/gravity-networks/testnet-hardforks.md)
* [Run a Gravity Mainnet Public Full Node](/gravity-networks/run-a-mainnet-pfn.md)
* [Run a Gravity Mainnet Public Full Node With Docker](/gravity-networks/run-a-mainnet-pfn-with-docker.md)
* [Run a Gravity Mainnet VFN](/gravity-networks/run-a-mainnet-vfn.md)
* [Run a Gravity Mainnet Validator (Invite Only)](/gravity-networks/run-a-mainnet-validator.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.gravity.xyz/gravity-networks/mainnet-hardforks.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.