Summary
For the Pectra hard fork on Bepolia testnet, this release candidate version should be used. The deadline to upgrade to this version is May 7th, 2025 @ 16:00:00 GMT+0000, when the beacon version will fork to Electra and the ELs are configured to fork to Prague.
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 Recommended |
Non-Payload Builders | Required | Not Recommended | Not Recommended |
Binaries
System | Architecture | Binary | PGP Signature |
---|---|---|---|
amd64 | beacond-v1.2.0.rc1-linux-amd64 | Signature | |
arm64 | beacond-v1.2.0.rc1-linux-arm64 | Signature | |
arm64 | beacond-v1.2.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 macapt 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>