Skip to content

BeaconKit v1.3.0-rc1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 29 Jul 22:41
· 177 commits to main since this release
v1.3.0-rc1
6d7de25
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

image

Summary

For the Pectra11 hard fork on Bepolia testnet, this release candidate version should be used. It includes Electra1 support for BRIP-0003 and BRIP-0004. The deadline to upgrade to this version is August 5th, 2025, when stable block time will take effect. A day later on August 6th, 2025 @ 16:00:00 UTC is when the beacon chain will fork to Electra1 and the ELs are configured to fork to Prague1.

Update Priority

This table provides priorities for which classes of users should update particular components.

User Class Bepolia Mainnet General
Payload Builders Required Not recommended Not required
Non-Payload Builders Required Not recommended Not required

Binaries

System Architecture Binary PGP Signature
amd64 beacond-v1.3.0-rc1-linux-amd64 Signature
arm64 beacond-v1.3.0-rc1-linux-arm64 Signature
arm64 beacond-v1.3.0-rc1-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 gpg on mac
  • apt install gpg on 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>
Assets 8
Loading