Skip to content

hard fork table for mainnet #435

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2025
Merged

hard fork table for mainnet #435

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions packages/docs/pages/networks/mainnets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,17 @@ With these steps, a user can join the Namada mainnet, allowing for querying and
These beginning steps are necessary for running a full node or a validator node as well.
More details on how to join the network in these cases can be found in [this mainnet guide](https://github.com/anoma/namada-mainnet-genesis/blob/main/MAINNET-GUIDE.md).

### Hard forks
If an operator would like to sync a node from genesis, they must do so by running the appropriate version of the node.
This version historically changes each time there has been a hard-fork of the network.

The following table describes the hard-forks and the corresponding software version needed to sync a block:

| Starting Block Height | Software Version |
|------------------------|------------------|
| 0 | v1.0.0 |
| 894,000 | v1.1.1 |

### Services and infrastructure

The `namada-ecosystem` repository contains data on the available mainnet services and infrastructure in json format in [this directory](https://github.com/Luminara-Hub/namada-ecosystem/tree/main/user-and-dev-tools/mainnet).
Expand Down
Loading