Skip to content

Releases: bnb-chain/bsc

v1.4.5

10 Apr 13:46
@github-actions github-actions
v1.4.5
a057245
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.5

Description

Release v1.4.5 is a hard fork release for BSC Chapel Testnet, the HF name is: Tycho, it mainly support Cancun EIPs on BSC:

But BSC won’t support “EIP-4788: BeaconRoot”, as there is no CL on BSC.

The target Tycho hard fork time will be:

  • Testnet: 2024-04-17 05:07:22 AM UTC
  • Mainnet: To be determined, could be around Mid of Jun 2024

After Tycho hard fork, BSC will also support Blob Transaction, which will provide similar mechanism as Ethereum EIP-4844. And BSC L2 rollup could take advantage of it to reduce the rollup cost.
If you have any question about it, pls refer: FAQ: About EIP-4844 on BSC

Changelog

FEATURE

  • #2378 config: setup Testnet Tycho(Cancun) hardfork date

IMPROVEMENT

  • #2333 remove code that will not be executed
  • #2369 core: stateDb has no trie and no snap return err

BUGFIX

  • #2359 triedb: do not open state freezer under notries

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux 6345521912693de147aa41eda78837021ce69fccb2391472f2aebb5059247590
geth_mac 9ff72d449c6ee21e6a28c48dcab498ee5d8fb04615ed9e7fff1cd2fddabebe2a
geth_windows c3345c52e9377ae95d146ba2cac7a6482e4a8dc7a18576ac6c628a7160d1418e
geth_linux_arm64 8ad39c6bb30aa52cdd66aef8f34d953c2b27ebe179232af75e1d1edf18af3e88
Assets 8
Loading

v1.4.4-beta

03 Apr 01:55
@github-actions github-actions
v1.4.4-beta
46df9b4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.4-beta Pre-release
Pre-release

Description

Release v1.4.4-beta mainly contains 2 parts:

  • it supports mainnet Feynman hard fork
  • it includes the code of BSC-4844, which will be enabled on Tycho hardfork after Feynman

However, it is still at beta phase, for the upcoming mainnet Feynman hard fork, pls use stable release v1.3.13

Change Log

FEATURE

  • #2279 BlobTx: implement EIP-4844 on BSC
  • #2337 4844: bugfix and improve
  • #2339 fix: missing block asigment WithSidecars
  • #2350 cancun: change empty withdrawHash value of header
  • #2335 upgrade: update system contracts bytes code and hardfork time of Feynman upgrade
  • #2323 feat: export GasCeil in mev_params
  • #2357 feat: add bid fee ceil in mev_params

IMPROVEMENT

  • #2321 test: use full syncmode to run rpc node
  • #2338 cmd: include more node info in metrics
  • #2342 p2p: add metrics for inbound/outbound peers
  • #2334 core: improve chain rewinding mechanism
  • #2352 core: fix block report when chain is not setHead

BUGFIX

  • #2367 fix: don't switch to snapsync for fast node

Example

NA

Compatibility

NA

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux 4b6e02ed25ce93debfe3dc956be19d1431101d687dde7a245201323d5aa76a80
geth_mac 8cc144fe75a4deb3ff8ce23db088af56fe34cd243c85692ead048f32519700d5
geth_windows df0743250903fd30f5eb94307c6b9cd01a6683551f8c991b0a2554aaf4367949
geth_linux_arm64 3fba458cefa9d22cc4ea3c71ea46b864ff1762d64e47b3b3ab5c3eab6fa90f35
Assets 8
Loading

v1.3.13

01 Apr 05:55
@github-actions github-actions
v1.3.13
bae7e6b
Compare
Choose a tag to compare
v1.3.13

Description

This release is going to enable the Feynman upgrade on BSC mainnet. The upgrade is forecasted to occur on 18th April 2024 at 05:49 (UTC). The full node runners on mainnet must switch their software version to the latest version by 18th April.

Feyman upgrade is the most important milestone of BNB Chain Fusion. The BNB Chain Fusion is a strategic shift to migrate the Beacon Chain’s functionalities to BNB Smart Chain (BSC) and retire Beacon Chain. This move aims to streamline the network, improve efficiency, reduce security risks, and align BNB Chain's architecture with the current technological demands and future growth. BEP333 propose to securely and smoothly transit the BNB Beacon Chain and BNB Smart Chain (BSC) from a dual-chain structure into a single chain structure and thus decommission the Beacon Chain.

Due to Feyman's upgrade, it will have a significant impact on the BNB ecosystem. We welcome the community to submit issues on GitHub or Discord. Kindly remind that BNB Chain has a bug bounty program if anyone find any security issues.

For BNB Beacon Chain Asset Holders

After BC Fusion, users will find it either impossible or extremely challenging to access assets on the BNB Beacon Chain. Here is a detailed guide designed to assist digital asset issuers and holders on the BNB Beacon Chain in transferring the value of their assets, like BEP2/BEP8 tokens, both before and after the Beacon Chain Fusion.

Here is an outline of all important milestones in the BNB Chain Fusion roadmap, set to facilitate a smooth transition for the BNB Chain community.

Brief Introduction of Feynman Upgrade

BEP-294, BEP-297 and BEP-299 will be deployed in the BSC Feynman hard fork.

  1. BEP-294 will take effect immediately. Validators created on BSC will receive triple voting power when staking an equal amount of BNB. This encourages the transfer of voting power from the Beacon Chain to BSC.

  2. The BEP-297 governance functionality will not be activated immediately after the hardfork. It will only be automatically enabled once more than 10 million BNB are migrated to BSC.

  3. The smart contract of BEP-299 is not available as the merkel root in the smart contract is still empty at this time. Only after the Beacon Chain comes to a complete halt, the Token Migration feature will be initiated by setting the Merkle root for balance dump through governance.

  4. Cross-chain re-delegation, which allows users to un-delegate their stakes from Beacon Chain and then delegate them on BSC in one Beacon Chain transaction, will be enabled after governance opening the related cross-chain channel.

Changelog

  • #2358 doc: add Feynman upgrade for mainnet
  • #2335 upgrade: update system contracts bytes code and hardfork time of Feynman upgrade

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux e48b613a8da2607fd4ab3f41ec320c8cf56aab975ea4362fc329208d0b90b368
geth_mac 89f248c051296b5a8194b19ded434c6b9940178144bb1517c11a0a812c21e178
geth_windows 4b7e54cb06616d2c620d14d18e3d0ffb93f1f9ca88b711d28c910403b7603d34
geth_linux_arm64 37e990242a2be465bfa007bf1e73d7ce95239933bc3761d7af52304df7d7364d
Assets 8
Loading

v1.4.3-alpha

21 Mar 14:33
@github-actions github-actions
v1.4.3-alpha
7f3f72e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.3-alpha Pre-release
Pre-release

Notice

BSC uses PBSS&PebbleDB as the default and primary mode now, will mainly focus the stability and performance of PBSS&PebbleDB. And for HashBased&LevelDB mode, it still can work, but the support will be limited.
If you are still running BSC with HashBased & LevelDB, you'd better switch to PBSS&PebbleDB mode ASAP.
For more detail, pls refer: FAQ: PBSS & PebbleDB

Description

Release v1.4.3-alpha is a maintenance release, although it includes PR of Testnet FeynmanFix hard fork, but as 1.4.x is still at alpha status, for FeymanFix hard fork, you'd better try v1.3.12

v1.4.3-alpha mainly includes these parts:

  • 1.Use PebbleDB as the default database
  • 2.Use PBSS as the default state scheme
  • 3.Some non-critical changes, like: no snap sync for fastnode; new flag: --instance; new cmd to delete trie state; some bugfix.

Same as previous v1.4.x-alpha, it could have some unknown risks or bugs there. It is not encouraged to run this version in your crucial business, but it would be appreciated if you can help try it in some non-crucial business environment and report bugs that you find.

Change Log

FEATURE

  • #2241 cmd/utils, core/rawdb, triedb/pathdb: flip hash to path scheme
  • #2312 cmd/utils, node: switch to Pebble as the default db if none exists

IMPROVEMENT

  • #2228 core: rephrase TriesInMemory log

  • #2234 cmd/utils: disable snap protocol for fast node

  • #2236 build(deps): bump github.com/quic-go/quic-go from 0.39.3 to 0.39.4

  • #2240 core/state: fix taskResult typo

  • #2280 cmd/utils, core: only full sync for fast nodes

  • #2298 cmd, node: initialize ports with --instance

  • #2302 cmd/geth, core/rawdb: add dbDeleteTrieState

  • #2304 eth/ethconfig: remove overridekepler and overrideshanghai

  • #2307 internal/ethapi: add net_nodeInfo

  • #2311 Port cancun related changes from unreleased v1.14.0

  • #2313 tests/truffle: use hbss to run test

  • #2314 cmd/jsutil: dump MinGasPrice for validator

  • #2317 feat: add mev metrics

BUGFIX

  • #2272 parlia: add state prepare for internal SC transaction
  • #2277 fix: systemTx should be always at the end of block
  • #2299 fix: add FeynmanFix upgrade for a testnet issue
  • #2310 core/vm: fix PrecompiledContractsCancun

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux 1209556f6265d8bd419c385e38b7f80afad7c379b90e00bf834ba5185acf850e
geth_mac d416d679b545186009cef8fd5aeaa0be9f477da4bf8c92ceb96134745ded239a
geth_windows 60ff50823491d03e672984ee1c9411eac2ee4dac4b9416988f2b55b97b4240ce
geth_linux_arm64 b28f217601fbc514021ffbc0dcdba8625769a8746cdf9c68169c825a984e3303
Assets 8
Loading

v1.3.12

19 Mar 06:25
@github-actions github-actions
v1.3.12
280cad3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.3.12

This is a maintenance release that addresses a minor issue.

Changelog

BUGFIX

  • #2305 fix: fix the wrong version number

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux d9d22a943963fd90f49ca4d75d968a49e674eb93b28dee95492841c25985044a
geth_mac 3de70df462a28356013d1307a7389e232ed3d24e526c3caab90a70f78e39b989
geth_windows 7ff9522984bee8dd6265e249c06708b098b0691b55f57bd25528f08440a1d6e2
geth_linux_arm64 8c3d3c9735da037630feb6f5a1dfcac69966242c484f4126af14235a7716ead4
Assets 8
Loading

v1.3.11

18 Mar 03:35
@github-actions github-actions
v1.3.11
9fb0241
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.3.11

This release is going to enable the FeynmanFix upgrade on BSC testnet. This upgrade fix an edge case when the cross chain redelegation failed during the delegation migration. The upgrade is forecasted to occur on 25th March 2024 at 5:00 (UTC). The full node runners on testnet must switch their software version to the latest version by 25th March.

Changelog

BUGFIX

  • #2288 fix: add FeynmanFix upgrade for a testnet issue

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux 314151e17e0788042524d77204106050cf7aaa00bc487f451a8971a08f88e1dd
geth_mac 125aad4c16b0b8408edf15009997cedeb2bed861461dab90f40b273abeb68bd2
geth_windows 615af5aa63f38b41be8b4c03e77539162311cf0cb82a008d0463e807dbbd006a
geth_linux_arm64 4914a77f2c6cd54893eb4099b8d97d9e518d17bd905bdf532c283d70f9bbc894
Assets 8
Loading

v1.4.2-alpha

12 Mar 07:34
@github-actions github-actions
v1.4.2-alpha
cbff319
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.2-alpha Pre-release
Pre-release

Do not use this version on critical business!!!

Description

v1.4.2-alpha is another maintenance release.
It mainly include three parts:

  • 1.the 2nd round of Cancun code sync with upstream go-thereum[v1.13.12, v1.13.14] to include some fix and improvements of EIP-4844. #2267
  • 2.feat: support separate trie database. #2021
  • 3.feat: support MEV. #2224

Same as previous v1.4.0-alpha, it could have some unknown risks or bugs there. It is not encouraged to run this version in your crucial business, but it would be appreciated if you can help try it in some non-crucial business environment and report bugs that you find.

Change Log

Feature

  • #2021 feat: support separate trie database
  • #2224 feat: support MEV

BUGFIX

  • #2268 fix: ensure EIP-4788 not supported with Parlia Engine

2nd CancunCodeMerge

  • #2267 Cancun code merge v1.13.12~v1.13.14

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux f57d9faf1e13646b3bcda5659f684b3869dc15838961ce1dffd169e27755bfa9
geth_mac 6d574fc623335de71c59914b60a124a7d37457dc7798fe17ceac343d8c5c6cce
geth_windows 5ffd620762fd51cc284ec0704a9874800e1430f2d92675cdd9fdd1a40311521b
geth_linux_arm64 be742a7d3123e0a77a19320588152e4927dc7b8ecea396fed3963d3990665335
Assets 8
Loading

v1.4.1-alpha

11 Mar 08:14
@github-actions github-actions
v1.4.1-alpha
1487e46
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.1-alpha Pre-release
Pre-release

Description

Release v1.4.1-alpha is a maintenance release, which only applies 2 fixes based on v1.4.0-alpha.

Changelog

FEATURE

NA

BUGFIX

  • #2258 core: skip checking state root existence when do snapsync by fast node
  • #2252 fix: add missing args of bls account generate-proof cmd (#2252)

IMPROVEMENT

NA

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux 99c45b0c06dd9b70164319ee1ddd144966b6e78ce945cf160e2a428005710827
geth_mac 7ea45077b0765a1df4b895d90942ce589fc2cabe8080697e1b12701fe26a9384
geth_windows 16ed5ca922941523794424083ca398884948df603288d1b40a34b1abb96ae6c8
geth_linux_arm64 11becc00e3a4429db353a290a3fe6a95792880da7a4ae51c608d8af8a073b0ef
Assets 8
Loading

v1.4.0-alpha

08 Mar 07:53
@github-actions github-actions
v1.4.0-alpha
5ccaed1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.4.0-alpha Pre-release
Pre-release

Description

Do not use this version on critical business!!!

v1.4.0-alpha is a big maintenance release. It mainly did another round of big code sync with upstream go-thereum[v1.13.0, v1.13.11] to import new features, bug fix, code clear up from go-ethereum, especially to support several Cancun EIPs on BSC.

Since there are huge code changes on this release, there could have some unknown risks or bugs there. It is not encouraged to run this version in your crucial business, but it would be appreciated if you can help try it in some non-crucial business environment and report bugs that you find.

Change Log

There is a very long change list, including modules like: RPC, Flag, GraphQL, Client, Tracer, Txpool, Sync, P2P, PBSS, Cancun...
For detail pls refer: #2200

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux 8539d41e7d9db2bc1541608a4b746cb3f59adfe8612ee1028665bd00a25e92aa
geth_mac 39d8df6bf086d5e9fc209604481fbfcd727faef012b4cfa6da4e18f0b37c0a21
geth_windows b7afe572395e8d75522a584cd2d04478593dd66eb37adb895ca0a97dd98d3a59
geth_linux_arm64 75ea2928428104018189d2c0acaa14d263de79340335dfe036da63f002e733d8
Assets 8
Loading

v1.3.10

04 Mar 06:43
@github-actions github-actions
v1.3.10
c8cc919
Compare
Choose a tag to compare
v1.3.10

Notice

BSC will switch to PBSS and gradually stop support for hash based mode, if your nodes are still running with hash based mode, pls follow this doc to upgrade to PBSS: https://forum.bnbchain.org/t/faq-pbss-pebbledb/2260/6

Description

This release is going to enable the Feynman upgrade on BSC testnet. The upgrade is forecasted to occur on 11th March 2024 at 6:00 (UTC). The full node runners on testnet must switch their software version to the latest version by 11th March.

Feyman upgrade is the most important milestone of BNB Chain Fusion. The BNB Chain Fusion is a strategic shift to migrate the Beacon Chain’s functionalities to BNB Smart Chain (BSC) and retire Beacon Chain. This move aims to streamline the network, improve efficiency, reduce security risks, and align BNB Chain's architecture with the current technological demands and future growth. BEP333 propose to securely and smoothly transit the BNB Beacon Chain and BNB Smart Chain (BSC) from a dual-chain structure into a single chain structure and thus decommission the Beacon Chain.

Due to Feyman's upgrade, it will have a significant impact on the BNB ecosystem. We welcome the community to submit issues on GitHub or Discord. Kindly remind that BNB Chain has a bug bounty program if anyone find any security issues.

For BNB Beacon Chain Asset Holders

After BC Fusion, users will find it either impossible or extremely challenging to access assets on the BNB Beacon Chain. Here is a detailed guide designed to assist digital asset issuers and holders on the BNB Beacon Chain in transferring the value of their assets, like BEP2/BEP8 tokens, both before and after the Beacon Chain Fusion.

Here is an outline of all important milestones in the BNB Chain Fusion roadmap, set to facilitate a smooth transition for the BNB Chain community.

Brief Introduction of Feynman Upgrade

BEP-294, BEP-297 and BEP-299 will be deployed in the BSC Feynman hard fork.

  1. BEP-294 will take effect immediately. Validators created on BSC will receive triple voting power when staking an equal amount of BNB. This encourages the transfer of voting power from the Beacon Chain to BSC.

  2. The BEP-297 governance functionality will not be activated immediately after the hardfork. It will only be automatically enabled once more than 10 million BNB are migrated to BSC.

  3. The smart contract of BEP-299 is not available as the merkel root in the smart contract is still empty at this time. Only after the Beacon Chain comes to a complete halt, the Token Migration feature will be initiated by setting the Merkle root for balance dump through governance.

  4. Cross-chain re-delegation, which allows users to un-delegate their stakes from Beacon Chain and then delegate them on BSC in one Beacon Chain transaction, will be enabled after governance opening the related cross-chain channel.

Changelog

FEATURE

  • #2047 feat: add new fork block and precompile contract for BEP294 and BEP299
  • #2242 eth/gasprice: fix percentile validation in eth_feeHistory

Assets

Assets Sha256 Checksum
mainnet.zip aeeae3392bd51af57fb1e2eddeefff7e84d58a37f87513495348d82deee5824f
testnet.zip bcb79b8731c50ddaa3a5a2e3e92afa4f04b0c04c72b6b37b8a69ecd776304f15
geth_linux ad893fa61ee41dba05bb20447318ae1521944efba7402d3204a4712aac1e8ca4
geth_mac 73ab0acd0a75f899e649223daa3899555f83f2dde1d951986da272b61b2a59bf
geth_windows 4e162178f84b5a103e29ba1c21ce1e7e3bb7fb735f3a4225158d3244efa2bcc2
geth_linux_arm64 519ce8f6f5e4a31eac4ea71e102f04421407a918f5a103f4337d2e261e3953e7
Assets 8
Loading