Berachain Balancer Upgrade
This upgrade disrupts the ability for funds dislodged by the Balancer exploit of November 3 to be transferred anywhere except the Berachain Foundation.
WARNING
All node operators, whether hosting an RPC or running a validator, must upgrade their Execution Client to the versions below to continue following the chain.
Upgrade Details
Berachain released stand-alone executables and Docker images for Linux ARM and AMD64 architectures for Bera-Reth and Bera-Geth. All clients are easily compiled for other systems and architectures with a few minutes' time; review their respective READMEs for details.
New genesis files are required for Bera-Reth/Geth.
No configuration changes are required.
Upgrade Instructions
TIP
If you duplicate your installation to test the upgrade — which is recommended — don't duplicate these identity files to avoid interfering with your production node's peering:
- Bera-Reth:
discovery_secret - Bera-Geth:
nodekey - Beacon-Kit:
priv_validator_key.json
WARNING
If you compile your own build, do so against the recommended release branches.
- Stop all clients.
- Install the recommended release version of Bera-Geth or Bera-Reth, linked below, into place.
- Install the new Reth/Geth genesis files linked below into place, and verify the hash with
md5sum <file>. Then:- Bera-Reth: overwrite
$RETH_DATA/genesis.json. - Bera-Geth: no additional steps.
- Bera-Reth: overwrite
- Start all clients.
TIP
Previous instructions specified a geth init step. These are no longer needed.
If you performed a geth init step and obtained a warning "mismatching Prague3 fork", that can safely be ignored.
Download links
| Chain | Github release page | Release date |
|---|---|---|
| Mainnet | Bera-Geth v1.011602.6 | Nov 4 |
| Mainnet | Bera-Reth v1.2.0 | Nov 4 |
| Bera-Reth/Geth Genesis File | Updated | Download link & md5 hash |
|---|---|---|
| Mainnet | Nov 4 | c5060f8dc392192c43d74c5b33b93cde |
| Bepolia | — | No Bepolia update required. |
Confirm upgrade
Bera-Reth and Bera-Geth should log the fork timestamp and details:
Berachain Prague3 configuration: {time=1762164459, blocked_addresses=... rescue_address=0xD276D30592bE512a418f2448e23f9E7F372b32A2]