berachain/beacon-kit v1.1.0

BeaconKit v1.1.0

on GitHub

Summary

BeaconKit v1.1.0 unlocks minting of BERA tokens towards the BGT contract.
The activation must be coordinated across validators, so it requires a hard fork.
Validators are required to upgrade their binaries before start of epoch 2855.

BeaconKit v1.1.0 also introduces a new command, deposit validator-keys, to ease up validators key display.

Update Priority

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

All Changes

• feat(cli): Tool to display all formats of public key (#2426)
• chore(forks): Deneb1 Values (#2425)
• [5/n] refactor(spec): introducing fork version activated specs based on slot (#2424)
• [4/n] refactor(chain-spec): handling values for planned fork upgrades (#2423)
• chore(e2e): Add verification during deposit e2e test (#2398)
• [3/n] refactor(version): Simplify usage of version type (#2427)
• Remove uses of context.Background() (#2376)
• chore(genesis deposit) : Change in local network setup with single node (#2402)
• chore(update deps): update uint256 package v1.3.2 (#2416)
• Revert "update uint256 package"
• update uint256 package
• fix(initchain): Enforce stricter handling on InitChain Requests (#2413)

Binaries

System	Architecture	Binary	PGP Signature
	amd64	beacond-v1.1.0-linux-amd64	Signature
	arm64	beacond-v1.1.0-linux-arm64	Signature
	arm64	beacond-v1.1.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 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>