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 before 2026-08-18 02:00:00 UTC.
docker pull ghcr.io/galxe/gravity_node:v1.9.1Source 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.
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:
There is no dedicated "hardfork missed" message. The failure is the same hash mismatch used for any execution-spec divergence.
See also
Last updated
Was this helpful?