Skip to content

Releases: chainstack/bsc-docker

v1.5.11

21 Apr 15:49
e053dc7

Choose a tag to compare

v1.5.10

14 Apr 20:02
1a2e9c7

Choose a tag to compare

v1.5.9

08 Apr 04:34
6ea10c3

Choose a tag to compare

BSC LOrentz hard fork on testnet

v1.5.7

10 Mar 14:04
d0328c2

Choose a tag to compare

v1.5.6

17 Feb 12:34
ff2d757

Choose a tag to compare

v1.14.17

30 Jan 16:05
6a0f6f9

Choose a tag to compare

Security release

v1.4.16

28 Nov 21:05
bb87cb6

Choose a tag to compare

v1.4.15

26 Sep 01:02
a3081c8

Choose a tag to compare

v1.4.15 is a maintenance release, which mainly has some enhancement on P2P and TxPool module, it also provides some Restful API for L2 and support customized token on BSC faucet.

v1.4.14

30 Aug 03:34
5bddd2b

Choose a tag to compare

Merge pull request #78 from chainstack/feature/v1.4.14

OPS-3909 v1.4.14

v1.4.13

15 Aug 03:12
4485e2d

Choose a tag to compare

Important Announcement:

HashSchema&LevelDB mode will be discontinued after September 30, 2024, will be replaced by PathSchema&PebbleDB mode
If you are still running with HashSchema or LevelDB, you need to reinstall your node with the latest bsc-snapshot.
How to check the running mode and the steps to do the migration, pls refer: bnb-chain/bsc-snapshots#379.

Description

Release v1.4.13 is a hard fork release for BSC Testnet, the HF name is: Bohr.
The target Bohr hard fork time will be:

Testnet: 2024-08-20 01:23:16 AM UTC
Mainnet: it is not determined yet, target Later Sep 2024
There are 4 BEPs in Bohr:

BEP-341: Validators can produce consecutive blocks
BEP-402: Complete missing fields in Block Header to generate Signature
BEP-404: Clear Miner History when Switching Validators Set
bnb-chain/BEPs#410
Among these BEPs, BEP-341 holds the most significance as it proposes a change to the block production protocol. However, BEP-341 will only come into effect after the affirmative outcome of a governance vote.
And BEP-402 updates the block header signature logic, please pay special attention if your product involves the logic of block header verification.
The other 2 BEPs, BEP-404 and BEP-410 are for some enhancement and unlikely to have compatibility issue.