feat(bnb): bump BSC Geth to v1.7.7 for Pasteur hardfork - #313
Merged
Conversation
BSC mainnet activates the Pasteur hardfork (BEP-673) on 2026-08-25 02:30 UTC; all mainnet nodes must run v1.7.7 by then. The version is taken from the config filename, so this renames the config plus its package.json/sample references. No blueprint CLI-flag changes are required: the flags removed or deprecated in the Pasteur line (--multidatabase, --fake-beacon*) and the load-breaking [Eth] EnableBAL config.toml field are not used by the blueprint, and config.toml is fetched fresh from the release. Upgrade replaces the instance per the blueprint's upgrade model. Smoke-tested on BSC mainnet (dev account): v1.7.7 binary downloads and SHA-verifies, release config.toml/genesis apply, --db.engine=pebble is accepted, the node service starts, peers connect, and snap-sync targets the chain head. Build (tsc) and jest (473 tests) pass.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
Scan for commit: 🔒 Security Scan ResultsScanned files: 6 ✅ No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BSC mainnet activates the Pasteur hardfork (BEP-673) on 2026-08-25 02:30 UTC; all mainnet nodes must run v1.7.7 by then. The version is taken from the config filename, so this renames the config plus its package.json/sample references.
No blueprint CLI-flag changes are required: the flags removed or deprecated in the Pasteur line (--multidatabase, --fake-beacon*) and the load-breaking [Eth] EnableBAL config.toml field are not used by the blueprint, and config.toml is fetched fresh from the release. Upgrade replaces the instance per the blueprint's upgrade model.
Smoke-tested on BSC mainnet (dev account): v1.7.7 binary downloads and SHA-verifies, release config.toml/genesis apply, --db.engine=pebble is accepted, the node service starts, peers connect, and snap-sync targets the chain head. Build (tsc) and jest (473 tests) pass.
What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction — we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.
Motivation
Type of Change
Testing
npm run buildsuccessfullynpm run testand all tests passnpx cdk synthwith a sample.env(e.g. fromblueprints/dummy/samples/) and it succeedsnpm run run-pre-commitNew Blueprint Checklist (if adding a protocol)
blueprints/dummy/(reference implementation).envfiles are provided for at least one network (mainnet or testnet)blueprints/dummy/)website/docs/blueprints/(.mdx mirror importing README)Documentation
cd website && npm run buildwith no broken links (if docs changed)License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.