Skip to content

Draft release v1.5.9#2989

Merged
brilliant-lx merged 30 commits intomasterfrom
develop
Mar 26, 2025
Merged

Draft release v1.5.9#2989
brilliant-lx merged 30 commits intomasterfrom
develop

Conversation

@zzzckck
Copy link
Collaborator

@zzzckck zzzckck commented Mar 25, 2025

Description

v1.5.9 is for BSC Testnet Lorentz hard fork, which is expected to be enabled at: 2025-04-08 07:33:00 AM UTC, all BSC testnet nodes need to upgrade to v1.5.9 before the hard fork time. For this upgrade, simply binary replacement should be enough.

Besides hard fork setup, v1.5.9 also include one bugfix and some improvements, pls check the change log for detail.

ChangeLog

FEATURE

#2932 BEP-520: Short Block Interval Phase One: 1.5 seconds
#2991 config: update BSC Testnet hardfork time: Lorentz

BUGFIX

#2990 core/state: fix concurrent map read and write for stateUpdate.accounts

IMPROVEMENT

#2933 metrics: add more peer, block/vote metrics
#2938 cmd/geth: add example for geth bls account generate-proof
#2949 metrics: add more block/vote stats;
#2948 go.mod: update crypto to solve CVE-2025-22869
#2960 pool: debug log instead of warn
#2961 metric: add more block monitor metrics;
#2992 core/systemcontracts: update url for lorentz hardfork
#2993 cmd/jsutils: add tool GetMevStatus

galaio and others added 25 commits March 5, 2025 14:24
* BEP-520: Short Block Interval Phase One: 1.5 seconds

* consensus/parlia: revert function backOffTime

* consensus/parlia: change lorentzEpochLength to 500

* consensus/parlia: add a slash systemtx when delay mining happens

* Revert "consensus/parlia: revert function backOffTime"

This reverts commit 24bf9d5.

* consensus/parlia: revert punish for intentional delay mining

* core/systemcontracts: update bytecodes for lorentz

* params: not define DefaultLorentzBlobConfigBSC

* params: remove Lorentz in BlobScheduleConfig

* consensus/parlia: use unit64 to express epochLength and blockInterval

* consensus/parlia: remove unnecessary change in distributeIncoming

* consensus/parlia: fix snapshot recovery

* log: improve debug log

* clear: resolve comments
sometimes "bestBid == nil" does not mean it is the first bid,
if new block was just imported during the bid simulation, the bestBid
will be cleared as well. In this case, the bid is stale and useless.

Keep the SetBestBid right now, as it will be cleared later anyway.
Once we have more confidence, it can be removed
with 3s block interval, if there is a simulating bid and with a short time
left for simulate, then don't interrupt the current simulating bid. The new bid
will be pending and can still run once the current simulating bid completes
Merge branch 'tag v1.5.8' into develop
@zzzckck zzzckck marked this pull request as draft March 25, 2025 08:21
@zzzckck zzzckck changed the title WIP: for v1.5.9 Draft release v1.5.9 Mar 26, 2025
@zzzckck zzzckck marked this pull request as ready for review March 26, 2025 06:13
@brilliant-lx brilliant-lx merged commit 2ccdf1a into master Mar 26, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants