RELEASE NOTES

MetaInfo

Mandatory Update Required: YES
Target Audience: all Chapel testnet users
Procedure: simply binary replacement should be good (ensure no 'JournalFileEnabled' field in config file)
Schedule(Timeline): After marked as 'Latest' from 'Pre-release', before 2026-03-24 02:30:00 AM UTC

Changelog

v1.7.1 is for BSC Chapel testnet Osaka/Mendel hardfork,the hard fork time is 2026-03-24 02:30:00 AM UTC

FEATURE

• feat: support bid block size check for BEP-655
• feat: support mev bid gas check of bep 652
• eip4844.go: disable eip-7918 for bsc
• feat: implement BEP-657 - Limit Blob Transaction Inclusion by Block Number

BUGFIX

• core/types: fix typo in vote comparison (#3573)
• Fee history issue
• go.mod: upgrade otel to fix CVE-2026-24051
• fix: fix gaslimit check in trace api (#3580)
• miner: fix missing tcount increment in commitBlobTransaction (#3581)
• fix: superinstruction bad block (#3582)
• core/vm: align super-instruction minStack and maxStack bounds (#3584)
• rlp: finalize listIterator on parse error to prevent non-advancing loops (#3586)
• eth/protocols/snap: restore peers to idle pool on request revert (#3587)

Assets

MetaInfo

Mandatory Update Required: NO
Target Audience: all users
Procedure: simply binary replacement should be good from v1.6.x
Schedule(Timeline): no scheduled upgrade timeline, but we recommend upgrading.

Description

This release ports critical security fixes from go-ethereum v1.16.9, resolving two P2P vulnerabilities.

Changelog

BUGFIX

crypto/secp256k1: fix coordinate check
crypto/ecies: fix ECIES invalid-curve handling

Assets

MetaInfo

• Mandatory Update Required: NO
• Target Audience: alpha release, no target audience
• Procedure: simply binary replacement should be good
• Schedule(Timeline): alpha release, no scheduled upgrade timeline

Description

v1.7.0-alpha is a preview release for upstream code sync, it catches up with go-ethereum release [v1.16.7] and also include several bug fix and improvements.

Changelog

Code Sync

• upstream: merge geth-v1.16.2 ～ geth-v1.16.7
  Key changes from the code sync include:
  • Osaka:
    • Implement EIP-7823 - Set upper bounds for MODEXP
    • Implement EIP-7825 - Transaction Gas Limit Cap.
    • Implement EIP-7883 - ModExp Gas Cost Increase.
    • Implement EIP-7918 - Blob base fee bounded by execution cost.
    • Implement EIP-7934 - RLP Execution Block Size Limit.
    • Implement EIP-7939 - CLZ opcode.
    • Implement EIP-7951 - Precompile for secp256r1 Curve Support.
  • eth_sendRawTransactionSync: Synchronous transaction submission
  • Performance Optimizations: Multiple improvements to enhance overall performance
  • Code Refactoring: Major cleanup and improvements to components including:
    • TriePrefetcher prefetch trie nodes in a account in parallel.
    • Introduced a file-based state journal and refactored state history writes

FEATURE

• internal/ethapi: recover GetDiffAccounts and GetDiffAccountsWithScope
• BEP648: Enhanced Fast Finality via InMemory Voting Pool

IMPROVEMENT

• miner: enable more prefetch threads in local mining mode
• miner/minerconfig: get defaultNoInterruptLeftOver automatically

BUGFIX

• core/state: fix handleDestruction for fast node (#3501,#3517,#3519)
• fix: add back Contract CodeAddr for superinstruction
• fix: fix pruned node init filtermap err

Others

• ci: upgrade github actions to latest versions
• ci: ignore nancy failre of quic-go@v0.49.1

Assets

This release ports critical security fixes from go-ethereum v1.16.8, resolving two P2P vulnerabilities.

While not an emergency patch, we highly recommend all node operators upgrade to ensure long-term network stability and security.

Upgrade Instructions

From v1.6.x: A simple binary replacement is sufficient.
From v1.5.x: Please refer to the v1.6.5 Release Announcement for specific migration steps.

Changelog

BUGFIX

core/txpool: drop peers on invalid KZG proofs
crypto/ecies: use aes blocksize

Assets

v1.6.5 is a maintenance release that introduces an optional gas limit cap for transactions.

Changelog

FEATURE

#3488 miner: optional transaction gas limit cap

IMPROVEMENT

#3483 feat: remove the handshake from the bsc protocol
#3486 feat: update filtermaps checkpoints

Notice regarding upgrade from v1.5.x to v1.6.5

Snapshot Regeneration

The upgrade will trigger snapshot regeneration. Please expect reduced node performance until this process finishes. On our reference hardware (8-core AMD EPYC 7R13, 32GB RAM, SSD), regeneration took approximately 5 hours.

Log Indexing

v1.6.x introduces a new log indexing mechanism. For v1.6.5, the index is constructed starting from block 71,126,721. This operation consumes significant CPU resources, and the node may appear unresponsive during startup. If you do not need the full index, add the flag --history.logs 576000 to limit indexing to the last 3 days, or disable it entirely using --history.logs.disable.

Assets

Description

This is an experimental feature release based on v1.6.4, with binary version: v1.6.102.

This feature release implemented the none consensus based Block-Access-List. It is based on EIP-7928 and using the non-consensus method, which similar to BEP-592
Deviations from EIP-7928:

• Consensus-level changes were removed, include BAL hash in block header.
• BALs now transfer only via the block propagation payload (ETH/BSC P2P messages) to help peers import blocks faster.
• If the BAL-driven parallel execution path fails (missing data, validation mismatch, etc.), the importer falls back to the legacy serial execution pipeline to guarantee correctness, so enabling BAL never jeopardizes block processing.

The feature is disabled by default, to try it, you may add this flag: --experimental.bal.

Kindly note that our current implementation shows an approximate 18.6% performance improvement in average mgas/s within our local test environment. However, the actual benefits are contingent upon the complete upgrade of the entire network to support BAL; otherwise, your node will not receive blocks with BAL, resulting in no performance gain. We believe there is significant potential to further enhance this feature and achieve even greater performance improvements in the future. For more information, pls refer: https://www.bnbchain.org/en/blog/boosting-bnb-smart-chain-performance-with-block-access-list

Change Log

• feature: non-consensus based block-access-list(EIP-7928)

Assets

v1.6.4 is the release for the BSC Mainnet Fermi hard fork, which is expected to be activated at 2026-01-14 02:30:00 AM UTC. All BSC Mainnet nodes must upgrade to v1.6.4 before the hard fork time. Upgrading from v1.6.3 only requires a binary replacement.

v1.6.4 includes two BEPs, primarily aimed at reducing the block interval from 0.75 seconds to 0.45 seconds:

• BEP-619: Short Block Interval Phase Three: 0.45 Seconds
• BEP-590: Extended Voting Rules for Fast Finality Stability

In addition to the block interval reduction, several other key parameters will be updated.
Please refer to BEP-619: Parameter Changes for details.

Beyond the hard-fork-related changes, this release also includes multiple improvements and bug fixes.
For the full list, please refer to the changelog below.

Changelog

FEATURE

• #3466 config: update BSC Mainnet hard fork time: Fermi
• #3454 eth: support fetching commit ID information from extra data

BUGFIX

• #3448 TxPool: revert transaction lifetime back to 3 hours
• #3457 cmd/geth: remove support for the multidatabase flag
• #3467 go.mod: downgrade bls-eth-go-binary to restore Windows compatibility

IMPROVEMENT

• #3445 eth: improve prefetching by using cached reader
• #3459 feat: implement auto-unsubscribe for transactionReceipts
• #3468 metric: add metric for vote count

Notice regarding upgrade from v1.5.x to v1.6.4

Snapshot Regeneration

The upgrade will trigger snapshot regeneration. Please expect reduced node performance until this process finishes. On our reference hardware (8-core AMD EPYC 7R13, 32GB RAM, SSD), regeneration took approximately 5 hours.

Log Indexing

v1.6.x introduces a new log indexing mechanism. For v1.6.4, the index is constructed starting from block 59,484,738. This operation consumes significant CPU resources, and the node may appear unresponsive during startup. If you do not need the full index, add the flag --history.logs 345600 to limit indexing to the last 3 days, or disable it entirely using --history.logs.disable.

Assets

Description

v1.6.3 is a maintenance release, which fixes 2 RPC issues and with several enhancements, pls refer change log for detail.

ChangeLog

FEATURE

NA

BUGFIX

#3429 build(deps): bump github.com/consensys/gnark-crypto
#3433 internal/ethapi: fix eth_simulateV1
#3431 eth/tracers: fix crasher in TraceCall with BlockOverrides

IMPROVEMENT

#3436 revert: revert the nano check in parlia
#3435 eth: fix stuck when handleBlockBroadcast

Assets

Description

v1.6.2 is for BSC testnet Fermi hardfork: Fermi. Fermi hard fork is a critical upgrade to further reduce block interval from 750ms to 450ms, so users will have even better experience. Here is the list of Fermi BEPs:

• BEP-590: Extended Voting Rules for Fast Finality Stability
• BEP-619: Short Block Interval Phase Three: 0.45 Seconds
• BEP-592: Non-Consensus Based Block-Level Access List
• BEP-593: Incremental Snapshot
• BEP-610: Implement EVM Super Instruction

Here is the timeline of BSC Fermi hard fork

• Testnet: 2025-11-10 02:25:00 AM UTC
• Mainnet: TBD

Besides the BEPs, v1.6.2 also include several improvements for miner, MEV and performance, and also includes two new features. Here is the description of the two new features:

• new websocket RPC filter API for transaction receipts. (#3363)
• new configuration "ProxyedNodeIds" to improve block propagation efficiency.(#3417)

Compatibility

• flag --light.** was removed, include: --light.egress, --light.ingress, --light.maxpeers, --light.nopruning, --light.nosyncserve, --light.serve

ChangeLog

FEATURE

#3363 websocket: add transactionReceipts for receipts notification
#3367 BEP-619: Short Block Interval Phase Three: 0.45 Seconds
#3368 BEP-590: Extended Voting Rules for Fast Finality Stability
#3374 Implement BEP-592: Non-Consensus Based Block-Level Access List
#3372 core/systemcontracts: define fermiUpgrade
#3390 feat: implement incremental snapshot
#3395 feat: EVM execution opcode level optimization
#3400 consensus/parlia: set kAncestorGenerationDepth to 3 in BEP-590
#3397 consensus/parlia: fix updateAttestation&improve assembleVoteAttestation
#3417 p2p: define ProxyedNodeIds in Config

BUGFIX

#3373 ethapi: reject oversize storage keys before hex decode

IMPROVEMENT

#3388 miner/minerconfig: update config to adapt 100M gaslimit
#3404 miner: validator not inturn backoff before mining
#3407 fix: change lock to read lock in legacy pool
#3415 eth: broadcast votes to evn peers regardless of deltaTdThreshold
#3416 cmd/geth: improve config for sentry nodes when init network
#3419 miner: use latest block as pending block for simplicity
#3426 eth: increase the delta td threshold to broadcast votes

Assets

Description

This is an experimental feature release based on v1.6.1-beta, with binary version: v1.6.101.

v1.6.1-beta-feature-ScalableDB introduces a multi-database architecture (scalaledb) that divides chaindata into four separate stores which includes BlockDataBase(with meta), TrieDataBase, SnapDataBase and IndexDataBase according to data schema . Scalaledb provides stronger storage scalability. Different DBs can be allocated customized resources and tuned configurations. In particular, databases can compact independently, avoiding interference and improving read performance under heavy I/O.

Run
Run geth from genesis with "multidatabse" flag:
./geth --config config.toml --datadir data-seed init --multidatabase genesis.json

If you run geth from snapshot, you need to use migrate tool to convert an existing snapshot to the scalaledb layout with
./geth -datadir <your-data-dir> db migrate . You can directly start after migration , no additional flags are required if your snapshot has already been migrated.

Performance Test Results:
In large-scale simulated benchmarks, Multi-DB improves Geth block sync performance by ~3.8%. Starting from the same block height, after seven days of syncing, the Multi-DB node was ahead by ~200,000 blocks.

Change Log

• ethdb: support multidb mode with dedicated snapshot DB and index DB

Assets