Skip to content

Releases: bnb-chain/node

v0.10.24

18 Oct 01:42
a7722bf
Compare
Choose a tag to compare

Changelog

This is the release for the Final Sunset of BNB Beacon Chain Mainnet.

The BNB Beacon Chain mainnet is expected to have a scheduled hard fork upgrade at block height 384544850. Based on the current block generation speed, the hard fork is forecasted to occur on 19th Nov 2024 at 6:00 (UTC). The mainnet full node runners must switch their software version to v0.10.24 with the correct settings of app.toml by 19th Nov or change the app.toml:

[upgrade]
FinalSunsetHeight = 384544850

Important Notes

Action Required for Users:

  • Migrate BEP2 Assets to BSC: We urge all users to migrate their BEP2 assets from the BNB Beacon Chain to the BNB Smart Chain (BSC) as soon as possible. While the majority of assets have been migrated, we still observe some BEP2 assets remaining on the Beacon Chain. To ensure continued access to your assets, please initiate the migration process immediately. You can do this through various platforms, including centralized exchanges, decentralized exchanges, and wallets like Trust Wallet.

https://docs.bnbchain.org/bc-fusion/users/assets/#before-bc-fusion

Action Required for Centralized Exchanges (CEXs):

  • Halt Beacon Chain Deposits: CEXs are requested to disable all deposit functions to the BNB Beacon Chain as soon as possible.
  • Consolidate BEP2 Assets: To maximize security, CEXs should consolidate all remaining BEP2 assets into a few cold storage wallets and transfer to BSC.

Post BC Fusion Historical Data Access

After Final Sunset, cross-chain communication between the Beacon Chain and BSC will be completely stopped.

  • Blockchain Data Access: Even after the fusion, blockchain data will remain accessible through several BC RPC nodes and snapshots uploaded to platforms like Greenfield. The mainnet explorer will also be maintained for viewing historical data.

  • Balance Snapshots: A snapshot of users' balances will be taken at a specific block height after the fusion. Users can access and verify their balances through the provided links and tools.

  • Token Migration: A token recovery tool will be available for users to migrate their BEP2/BEP8 assets from the Beacon Chain to the BSC after BNB Beacon Chain sunset. For tokens without cross-chain feature enabled, the asset will be lost permanently

For details, community and users can refer to the BEP333.

Assets

Assets Sha256 Checksum
mainnet_config.zip fe2f58f1d82312d5c17076b26c989af5cbc73b134a82d6d3d905dd797b82241f
testnet_config.zip 7ebaada1e71407c3499411b5e0a93d0b381b7a9226120fd20c322f56beaea4b4
linux_binary.zip 26ebaf8f4ea579ea14989992015b259c9165e7f6259a5f344e639bb708b35849
macos_binary.zip 0eb0c13f49e18646e34303559022a8316f6817320b11fce3313c9dbd81184134
windows_binary.zip 98906cbca26f9636c0b6d86f20553828f346e7d74cf0df60cc53abcf7b531fa0

v0.10.23

17 Jul 03:49
01cc677
Compare
Choose a tag to compare

Changelog

This is the release for the Final Sunset of BNB Beacon Chain testnet.

The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 56,218,686. Based on the current block generation speed, the hard fork is forecasted to occur on 1th Aug 2024 at 6:00 (UTC). The testnet full node runners must switch their software version to v0.10.23 by 1th Aug.

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The first sunset upgrade is the first milestone of BEP333.

Assets

Assets Sha256 Checksum
mainnet_config.zip 1502aecfdcf0816f7909f3a7c5b1674ae3a5113dba0909506ecc4b625cbe4036
testnet_config.zip 99cf9ccc6e00cac23b02d5d0123dc109fedb6dcea98b45de282eb17ec53ca9bf
linux_binary.zip f2d90c81707cfaf512ec091d28b71a94df7e6567f4aec19a3dd5f8ce867aa5a0
macos_binary.zip 7bc5a706cb689c4fdae0d5fcaa63244fbe941eb3d75e5d7dee32b7e58e737007
windows_binary.zip 2df6c6d57f609f290c8676d9e098fa56dd333b3496925b767809c40d6a5c1398

v0.10.22

26 Jun 12:17
6fbf551
Compare
Choose a tag to compare

Changelog

This is the release for the Second Sunset of BNB Beacon Chain Mainnet.

The BNB Beacon Chain mainnet is expected to have a scheduled hard fork upgrade at block height 378062790. Based on the current block generation speed, the hard fork is forecasted to occur on 14th July 2024 at 6:00 (UTC). The mainnet full node runners must switch their software version to v0.10.22 with the correct settings of app.toml by 14th July or change the app.toml:

[upgrade]
SecondSunsetHeight = 378062790

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The second sunset upgrade is the second milestone of BEP333.

Assets

Assets Sha256 Checksum
mainnet_config.zip ab7afaa18126983a75225b48b1f92e3f37b5b0de7b4671153f83bec86ecb62c1
testnet_config.zip 70a863a0eb094d69811690b5a370dd734eaa9f9becba74a09a272a255707601a
linux_binary.zip 0ee84f7896297f60e4e51ed8890834e7a45a4a0531b52d85e1038e6d2cb8f807
macos_binary.zip 689755b12b5c680d2255cd67dd1061166b8861b0350330e4508705dde57ce4b5
windows_binary.zip bbeca3c6874968b52b4b7f331851da11bbe428c60f56e31a9442d1a2ee40d3a2

v0.10.21

12 Jun 08:58
b09b565
Compare
Choose a tag to compare

Changelog

This is the release for the Second Sunset of BNB Beacon Chain testnet.

The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 54554742. Based on the current block generation speed, the hard fork is forecasted to occur on 21th June 2024 at 6:00 (UTC). The testnet full node runners must switch their software version to v0.10.21 by 21th June.

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The first sunset upgrade is the first milestone of BEP333.

Assets

Assets Sha256 Checksum
mainnet_config.zip a13cba413b173acc71eb1ed89d1debaae32e4ea1e92bb96a629e27f9075b4042
testnet_config.zip ef876d8f49b49b39a8a6adca9a1978a631fff503b4ba782f3570a83392a26273
linux_binary.zip 5a3d9c08a53e28df46fc6aa225ab13ae22a8d52018061eff894a3d64cf3b1bae
macos_binary.zip 9d5032fc04b38a9fe20970f537bc3296960dec0f38f1b78cf8203760ae57a89d
windows_binary.zip 572830445935d15ec880b0a4531945207fa0458a69726ed6ecbbb95f6a55b747

v0.10.20

01 Apr 06:05
20d3c87
Compare
Choose a tag to compare

Changelog

This is the release to enable the first sunset upgrade of BNB Beacon Chain mainnet.

The BNB Beacon Chain mainnet is expected to have a scheduled hard fork upgrade at block height 373,526,985. Based on the current block generation speed, the hard fork is forecasted to occur on 15th April 2024 at 6:00 (UTC). The full node runners must switch their software version to v0.10.20 by 15th April.

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The first sunset upgrade is the first milestone of BEP333.

FEATURES

  • #1016 [BEP] feat: enable FirstSunset on mainnet

Assets

Assets Sha256 Checksum
mainnet_config.zip 7263031416319cfe5944564d132c486e9a24b630397a28527f4c4b6f7228873c
testnet_config.zip ddc2a3655f8aaf15d40bd5d0104511b00dcd8de47890dbf366b5ccea3a31d4e0
linux_binary.zip b26e112f5355605cf244952a0ac5c1e7f03e2fb7d16c232dfed4bf72d8e75b6d
macos_binary.zip c2781878f91689b6d151784c5b5edfbe75201f16406e71a0eb09d8166af872dc
windows_binary.zip 4dc8f12b9ee00ecc64b09379eddc9244b9fb60b95b0fc6ad49a57556c406559b

v0.10.19

05 Mar 03:19
911507e
Compare
Choose a tag to compare

Changelog

This is the release to enable the first sunset upgrade of BNB Beacon Chain testnet.

The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 50,121,232. Based on the current block generation speed, the hard fork is forecasted to occur on 4th March 2024. at 6:00 (UTC). The full node runners on testnet must switch their software version to v0.10.19 by 4th March.

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The first sunset upgrade is the first milestone of BEP333.

FEATURES

  • #977 [BEP] feat: implement BEP-333(BNB Chain Fusion)

BUGFIX

  • #1014 [fix] fix: publish completed UnbondingDelegation events to kafka in EndBlock
  • #1015 [fix] fix: publish ChainUndelegate event and ledger sig issue

Assets

Assets Sha256 Checksum
mainnet_config.zip ae6f1444547d678865d2275a688fd5113a4a8b48fa16af2304ec45d067539c52
testnet_config.zip a670936f33bab2059790b9195946f919d95e325c49d0ea84e171825315077e54
linux_binary.zip f06d584a9604c77dc7db90ba7b2fa7b198969af951192fc6b875bf33b837b661
macos_binary.zip 0e7f30618537ae52688c401818b534fadfb86a86cd94a3180e3658857009d4d2
windows_binary.zip 77734320b3cd88e89356ead9ecb5bfc9f1ff297ee781e586e688a17292847d67

v0.10.18

29 Feb 10:31
3c72c85
Compare
Choose a tag to compare

Changelog

This is the release to enable the first sunset upgrade of BNB Beacon Chain testnet.

The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 50,121,232. Based on the current block generation speed, the hard fork is forecasted to occur on 4th March 2024. at 6:00 (UTC). The full node runners on testnet must switch their software version to v0.10.18 by 4th March.

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The first sunset upgrade is the first milestone of BEP333.

FEATURES

  • #977 [BEP] feat: implement BEP-333(BNB Chain Fusion)

BUGFIX

  • #1014 [fix] fix: publish completed UnbondingDelegation events to kafka in EndBlock

Assets

Assets Sha256 Checksum
mainnet_config.zip b17b9e86b1c025b718963e312927fcc42b0d84c9cbcae34c4665f58ff0a5e075
testnet_config.zip f98e4666cd5f9a11ce632d04c22cc33b81d3bd6f1b6a10082e2a6f93028637ab
linux_binary.zip d9e20f47b37c9318cbb87a63c4fa434199baf0adfa6d933c137a7201f72f78b5
macos_binary.zip 104be1bf902247ba0d1beb5b6c215587b26e67a6df6d4b486960afa7631601e7
windows_binary.zip 67affce0fc448728c08ff29d85f60991170b99d7722b83bcbdccd05507d6ba40

v0.10.17

28 Feb 02:55
f9792ca
Compare
Choose a tag to compare

Changelog

This is the release to enable the first sunset upgrade of BNB Beacon Chain testnet.

The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 50,121,232. Based on the current block generation speed, the hard fork is forecasted to occur on 4th March 2024. at 6:00 (UTC). The full node runners on testnet must switch their software version to v0.10.17 by 4th March.

Background of BC Sunset

With the quick evolution of BSC, the Beacon Chain has become a burden. The cross-chain bridge that connects the two chains slows down the development iteration and always exposes BNB to a certain level of security vulnerabilities. BEP333 proposes to migrate the functionality of Beacon Chain to BSC, allowing Beacon Chain to retire.

The Beacon Chain Sunset is divided into multiple stages: first sunset upgrade, second sunset upgrade and final sunset upgrade. The first sunset upgrade is the first milestone of BEP333.

FEATURES

  • #977 [BEP] feat: implement BEP-333(BNB Chain Fusion)

Assets

Assets Sha256 Checksum
mainnet_config.zip 1b943d93e76dc07efa24f0b171f814199e0b05f2d1c8615a3c146d4d82e3fd00
testnet_config.zip eb77d477ff55ad2c37cfa4feca37d298dde0e4c8dc6fade66f0cbaa487363119
linux_binary.zip 60d6836ecd252cb2b52f4935d5c98f063ee6c7878abc91797e30b13a9c12f862
macos_binary.zip 4130dadede6857588e726bec2ba3716050a08fd541cf2def2507d5b7043d4f71
windows_binary.zip 566c7ecea7c9a8962fd315deb4f38b213c20672ca9619dd06b1aa22d54236a0d

v0.10.16

12 Jul 10:58
13bb81c
Compare
Choose a tag to compare

This is a hard fork release on mainnet, with new features.

The BNB Beacon Chain mainnet is expected to have a scheduled hard fork upgrade at block height 328088888. Based on the current block generation speed, the hard fork is forecasted to occur on 19th Jul. at 6:00 (UTC). The full node runners on mainnet must switch their software version to v0.10.16 before the height. Please replace the app.toml with the latest version or add BEP255Height = 328088888 under the [upgrade] module of app.toml.

All BSC validators are required to update the vote key after the hard fork.

Changelog since v0.10.14

FEATURES

  • #977 [BEP] asset: add bep255 upgrade height for mainnet
  • #956 [BEP] feat: implement bep255
  • #964 [fix] fix: clear side vote addresses

Dependency (GLIBC) issue when running node

image

The problem is caused by the CI runner using a higher `GLIBC` tool chain. If you get the same problem, please try the following tips:
  1. Build binaries on your machine.
git clone https://github.com/bnb-chain/node.git
cd node && make build

Then you will get binaries in ./build/ folder.

  1. Try to update OS on your machine and make sure it can upgrade glibc to 2.34+.
  2. Try https://github.com/matrix1001/glibc-all-in-one to install a higher version of glibc. (It may not works on any machine)
  3. If you are running a node on AWS EC2, please upgrade the OS image up to Amazon linux 2022

Assets

Assets Sha256 Checksum
mainnet_config.zip 33d3d741c2ba1b95b7a51b7e3a89315e16fea4e8d377104621c517d9ef96a5cc
testnet_config.zip d500ca11f1a3a31ad7ea9f469de60f2f85d34dd2ad9191c9fd94d540e0bc8ed3
linux_binary.zip 777f840dc1f1bc1ed47563ea8ebfc711802ae14976c7ec714a2b842dff0a5144
macos_binary.zip 633abd17d813373921372776d73f13ce2faa00e4ddfb13fafd6fd5451bd1a8cd
windows_binary.zip b197a4ccaf226df067e2404b77cf195c98359851e483c6c6696403677ff9b4d5

v0.10.15

07 Jul 11:35
3195e6b
Compare
Choose a tag to compare

This is a hard fork release on testnet with new features.

The BNB Beacon Chain testnet is expected to have a scheduled hard fork upgrade at block height 41650000. Based on the current block generation speed, the hard fork is forecasted to occur on 11th Jul. at 6:00 (UTC). The full node runners on testnet must switch their software version to v0.10.15 before the height.

Changelog

FEATURES

  • #956 [BEP] feat: implement bep255
  • #964 [fix] fix: clear side vote addresses

Assets

Assets Sha256 Checksum
mainnet_config.zip 305ab0e9c6984e61fe7e3dc79a2914ec2300c44afd076653cc6343e6772f3228
testnet_config.zip e2bbf453a75aa57c8880829ee2c3c9cff6b1e1d0070f6f70aae600ddf6683496
linux_binary.zip d7bab775c2e34f801e3cf0379ae3c431671f817472b380c70289426843dd9078
macos_binary.zip 9cf175d06420167803ffe2b1511187a9ec661f274aaed42d90222e49bd07b70e
windows_binary.zip b35973c998fdd50879c35cb643f54d50a9092c12e09ee0cf409a0e7923aa078d