Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: prepare for release v1.3.5 #2005

Closed
wants to merge 1 commit into from

Conversation

brilliant-lx
Copy link
Collaborator

@brilliant-lx brilliant-lx commented Nov 27, 2023

Description

Release v1.3.5 is a hard fork release for BSC testnet.
It will enable the Kepler(Shanghai) hard fork on BSC testnet, for details of the hard fork, pls refer: BSC Kepler Hard Fork

The validators and full node operators on testnet should switch their software version to v1.3.2 before ?.

Kepler BEPs

Change Log

FEATURE

  • #1970 core: enable Shanghai EIPs
  • #1973 core/systemcontracts: include BEP-319 on kepler hardfork

BUGFIX

  • #1964 consensus/parlia: hardfork block can be epoch block
  • #1979 fix: upgrade pebble and improve config
  • #1980 internal/ethapi: fix null effectiveGasPrice in GetTransactionReceipt
  • #1986 fix(cmd): check pruneancient when creating db

IMPROVEMENT

  • #1977 doc: add instructions for starting fullnode with pbss
  • #2000 cmd/utils: exit process if txlookuplimit flag is set

Example

NA

Compatibility

NA

@brilliant-lx brilliant-lx marked this pull request as draft November 27, 2023 08:22
@brilliant-lx brilliant-lx deleted the release_v1.3.2 branch December 5, 2023 04:16
@zzzckck zzzckck changed the title release: prepare for release v1.3.2 release: prepare for release v1.3.6 Dec 5, 2023
@zzzckck zzzckck changed the title release: prepare for release v1.3.6 release: prepare for release v1.3.5 Dec 5, 2023
@brilliant-lx brilliant-lx restored the release_v1.3.2 branch December 5, 2023 04:19
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.

1 participant