Reese Mainnet Upgrade

GOAT Network will activate the Reese mainnet upgrade at consensus block 11,130,000, with activation currently estimated for 2026-03-26 02:20 UTC.

This upgrade delivers a set of important improvements across the network, including consensus-critical fixes, execution-layer security hardening, and a refresh of bootnode connectivity. Together, these changes improve network resilience and help ensure continued mainnet stability as GOAT Network evolves.

What Is Included in the Reese Upgrade

The Reese upgrade introduces improvements across both the consensus and execution layers of GOAT Network.

On the consensus side, the upgrade activates the Reese fork at block 11,130,000 and includes processing-path fixes related to unlock queue handling and beacon root processing.

On the execution side, the recommended release includes upstream critical hardening for DoS-resistance paths, strengthening client security and improving robustness under adverse conditions.

The upgrade also refreshes bootnode lists across both the consensus and execution clients. Older bootnode entries will remain temporarily as deprecated fallback entries to support a smoother transition.

What Node Operators Need To Do

All node operators should complete the required upgrade before the activation block is reached.

The required versions for the Reese upgrade are:

  • Consensus Client: goat v0.4.4
  • Execution Client: goat-geth v0.4.2

We recommend upgrading both layers together within a single maintenance window.

Operators using the official Docker Compose setup can update with:

docker compose -f docker/mainnet.yaml pull

docker compose -f docker/mainnet.yaml up -d

As part of the recommended process, operators should also regenerate the Geth p2p node key before restart:

rm -f /data/geth/geth/nodekey

If your environment uses a different geth data directory, remove the equivalent file under your configured datadir instead.

Regenerating the node key will change the node ID, so operators using static peering should update peer configurations accordingly.

Before activation, operators should verify that:

  • nodes are syncing normally,
  • both consensus and execution clients are healthy,
  • and the correct versions are running across both layers.

Why This Upgrade Matters

Reese is a maintenance and resilience-focused mainnet upgrade. While it does not require manual action from end users, it is an important release for network operators and infrastructure teams.

By combining consensus-critical fixes, execution-client hardening, and network connectivity updates in a single coordinated release, Reese helps keep GOAT Network secure, stable, and ready for the next phase of growth.

Activation Details

  • Network: GOAT Mainnet
  • Consensus activation block: 11,130,000
  • Estimated activation time: 2026-03-26 02:20 UTC

Please note that the activation time is an estimate and may change slightly depending on live block production.

Official References

  • goat v0.4.4 (Reese Hard Fork)
  • goat-geth v0.4.2
  • Reese mainnet fork-height update commit
  • Consensus bootnode

Back to the Blog
Reese Mainnet Upgrade
Mar
24
By
GOAT
SHARE ON
Related Articles