Olympia Upgrade Guide
Node operators must upgrade before the Olympia activation block. Three independent client implementations are available — choose the one that fits your infrastructure.
Activation Block: TBD
The exact block number will be announced after the Olympia Upgrade core developers call. Upgrade your node as soon as a compatible release is available.
Per-Client Upgrade Steps
Core-Geth
Maintenance · GoRuntime
Go 1.24+
Disk
500 GB+ (full sync)
RAM
8 GB minimum
Stop your running Core-Geth node
Download the Olympia-compatible release from GitHub
Replace the existing binary or update via package manager
Restart your node — it will automatically follow the Olympia fork
Hyperledger Besu
Enterprise · JavaRuntime
JDK 21+
Disk
500 GB+ (full sync)
RAM
8 GB minimum
Stop your running Besu node
Download the Olympia-compatible release from GitHub or update via package manager
Replace the existing binary or JAR file
Restart your node — Besu automatically follows the Olympia fork
Frequently Asked Questions
What happens if I don't upgrade?
If you do not upgrade before the Olympia activation block, your node will stop following the canonical chain. You will need to upgrade and resync from the fork point. Exchanges, wallets, and services running outdated clients will be unable to process transactions on the post-Olympia chain.
Will my miner rewards change?
No. Block rewards and tips remain completely untouched at 2.048 ETC (Era 4). The Olympia upgrade redirects the EIP-1559 basefee, a value set to be destroyed, to the protocol treasury. This is separate from miner rewards.
When is the activation block?
The exact activation block will be announced after the Olympia Upgrade core developers call. All three client implementations will release Olympia-compatible versions well before activation.
Can I roll back if something goes wrong?
You can downgrade to a pre-Olympia client version, but your node will only follow the pre-fork chain. In practice, the network will have moved to the Olympia chain. All three clients have been extensively tested against a cross-client test matrix covering 14 historical forks.