Network status and upgrades

Chain versions and upgrade heights change, and any value written into a page goes stale. This page records the current state with a timestamp, and every figure here is one command away from being re-checked.

Check it yourself

These queries are the source of truth. Run them before relying on anything below.

# running version and height
curl -s https://rpc.lumera.io/abci_info | jq -r '.result.response | "\(.version) at height \(.last_block_height)"'

# scheduled upgrade, null when none is on chain
curl -s https://lcd.lumera.io/cosmos/upgrade/v1beta1/current_plan | jq .

curl -s https://lumera-testnet-rpc.polkachu.com/abci_info | jq -r '.result.response | "\(.version) at height \(.last_block_height)"'

curl -s https://lumera-testnet-api.polkachu.com/cosmos/upgrade/v1beta1/current_plan | jq .

From a synced node, lumerad status and lumerad query upgrade plan return the same information.

Current versions

	Mainnet (`lumera-mainnet-1`)	Testnet (`lumera-testnet-2`)
`lumerad`	`v1.12.0`	`v1.20.2-rc1`
Height when checked	7,184,647	6,900,051
Scheduled upgrade	None on chain	None on chain
SuperNode release in widest use	`v2.5.2`	`v2.6.x-testnet`

Checked 2 October 2026. SuperNode versions vary across operators; the live distribution is in the version matrix.

Mainnet runs the v1.12.0 line and testnet runs the v1.20.x line, so testnet carries features mainnet does not yet have, including the EVM. Check a feature’s availability on your target network before building against it.

Next upgrade

Neither network has an upgrade plan on chain. current_plan returns null on both. The mainnet EVM upgrade (Aurora Convergence, the v1.20.x line) was planned for block 6,715,000 and did not execute; mainnet passed that height on v1.12.0. It has been rescheduled and the new date is to be announced. See the EVM upgrade.

Applied upgrades

Heights at which each upgrade handler executed, read from applied_plan. A dash means the upgrade was never applied on that network.

Upgrade	Mainnet	Testnet
`v1.6.1`	434,000	—
`v1.8.0`	—	1,740,000
`v1.8.4`	2,270,000	1,922,000
`v1.9.0`	2,964,000	2,630,000
`v1.10.1`	3,770,000	3,410,000
`v1.11.0`	—	3,763,000
`v1.11.1`	4,218,000	—
`v1.12.0`	5,193,000	4,833,000
`v1.20.0`	—	5,547,000
`v1.20.1`	—	5,615,000
`v1.20.2`	—	6,149,000

Query any one of them directly:

curl -s https://lcd.lumera.io/cosmos/upgrade/v1beta1/applied_plan/v1.12.0 | jq .

Build your node from a tag that carries every handler your target network has already applied. A binary missing a handler halts at that upgrade height and cannot sync past it. Testnet has applied v1.20.2, so a testnet node needs v1.20.2 or newer.

Overview

Get started

The Intelligence Layer

SDKs

Smart contracts

Operate the Network

Interoperability

Applications

Protocol Reference

Network status and upgrades

Check it yourself

Current versions

Next upgrade

Applied upgrades

Next steps

Networks

EVM upgrade

​Check it yourself

​Current versions

​Next upgrade

​Applied upgrades

​Next steps

Networks

EVM upgrade

Check it yourself

Current versions

Next upgrade

Applied upgrades

Next steps