Nathan

BEP-341: Validators can produce consecutive blocks

6

BEP: 341 Title: Validators can produce consecutive blocks Status: Draft Type: Standards Created: 2023-09-27 Discussions(optional): https://forum.bnbchain.org/t/bep-idea-validators-can-produce-consecutive-blocks/2052 # BEP-341: Validators can produce consecutive blocks - [BEP-341: Validators can produce consecutive blocks](#bep-341-validators-can-produce-consecutive-blocks)...

### Description Merge master 2 develop ### Rationale sync code 4826b4855a3a290296d45ed30402a8673cc915e9 is the latest commit on master branch ``` git checkout merge_master_2_develop git diff 4826b4855a3a290296d45ed30402a8673cc915e9 ``` no diffs at all...

### Description feat: define turnLength and systemRewardAntiMEVRatio for BEP-341 ### Rationale tell us why we need these changes... ### Example two tests will pass by following command ``` cd contracts...

feat: make validators to produce consecutive blocks defined by BEP-341

5

### Description [BEP-341: Validators can produce consecutive blocks](https://github.com/bnb-chain/BEPs/pull/341) ### Rationale tell us why we need these changes... ### Example add an example CLI or API response... ### Changes Notable changes:...

### Description core/forkchoice: improve stablity when inturn block not generated ### Rationale tell us why we need these changes... ### Example add an example CLI or API response... ### Changes...

memory leak

1

#### System information based a old snapshot (in May) sync against mainnet ``` ./geth --config ./config.toml --datadir data-seed --cache 15000 --rpc.allow-unprotected-txs --history.transactions 0 --syncmode full --metrics --metrics.addr 10.180.41.196 ``` catch...

update checkpoints_bsc_mainnet.json and checkpoints_bsc_chapel.json before releasing

1

# Rationale these two files lags a lot will cause new setup nodes stuck in syncing # Implementation Do you have ideas regarding the implementation of this feature? Are you...

#### System information Geth version: `geth version` OS & Version: Windows/Linux/OSX Commit hash : (735f8ea4b70f52ad3da7282447a099d66083a569) Arguments: #### Description - Expected behaviour ... - Actual behaviour ... #### Backtrace ```` [backtrace]...