Summary
This release accompanies the Osaka1 EL hard fork on bepolia. Osaka1 is EL-only, so no beacond upgrade is required for the fork. Activation details and node upgrade instructions are in the execution client release: bera-reth v1.4.3-rc.0.
This release also updates the network eth-genesis.json files with the Osaka1 schedule, bepolia activates on July 22, 2026 16:00 UTC and mainnet keeps a placeholder time for now. These files live in the repository itself and are not attached as release assets.
Update Priority
This table provides priorities for which classes of users should update particular components.
| User Class | Priority |
|---|---|
| Payload Builders | Optional |
| Non-Payload Builders | Optional |
All Changes
- feat: osaka1 fork to floor the base fee and blob fee (#3141)
- fix(ci): fix failing vulncheck via Go 1.26.5 bump and advisory suppression (#3144)
- fix(ci): pre-build the Go coverage tool to fix flaky coverage test failures (#3143)
- chore(deps): bump go-ethereum to v1.17.4 (#3140)
- ci(nightly): add missing pipeline permissions (#3139)
- ci(nightly): run full pipeline and deps tests nightly against main (#3137)
- fix(vulncheck): build govulncheck against patched x/tools (golang/go#80055) (#3136)
- chore(ci): post to Slack when deps workflow fails (#3135)
- chore (ci): bump actions/checkout to v7.0.0 (pinned) (#3133)
- ci(pipeline): disable fail-fast on ci matrix (#3131)
Binaries
| System | Architecture | Binary | PGP Signature |
|---|---|---|---|
| amd64 | beacond-v1.4.2-rc.0-linux-amd64 | Signature | |
| arm64 | beacond-v1.4.2-rc.0-linux-arm64 | Signature | |
| arm64 | beacond-v1.4.2-rc.0-darwin-arm64 | Signature | |
| System | Option | - | Resource |
| Docker | berachain/beacon-kit |
Verifying signatures
Use gpg to verify the signature on these binary archives. This is important to make sure that the content you've downloaded is legitimate. gpg can be installed with most package managers. For example:
brew install gpgon macapt install gpgon Ubuntu/Debian
Once gpg is installed, import our public key into its database and verify:
- Download signing public key from here.
- Run
gpg --import berachain_release.asc - Verify with
gpg --verify {signature}.sig {binary}.tar.gz - This message is expected:
WARNING: This key is not certified with a trusted signature! - To resolve the warning, trust the key by signing with your own keypair.
gpg --lsign-key <keyid>