bnb chain plain logo
BNB Chain sets Jenner hardfork for testnet on October 28
The upgrade brings a reserved payment lane, a compliant asset standard, and millisecond timestamps to BNB Smart Chain's testnet
BNB Chain has scheduled its next protocol upgrade. The Jenner hardfork goes live on the BNB Smart Chain testnet on October 28, 2026, and node operators have homework to do first.
The upgrade bundles three BNB Evolution Proposals (BEPs). One reserves block space for payments, one creates a standard for regulated assets, and one makes the chain’s clock far more precise.
What Jenner actually changes
The headline feature is BEP-703, which BNB Chain calls the Payment Lane. By default, it sets aside 5% of each block’s gas for qualifying payments. Eligible traffic, such as plain BNB transfers sent to non-contract accounts, gets a guaranteed slice of the block. The rest of the network can still jam up, but simple payments are meant to keep moving.
The second piece is BEP-702, which introduces a standard called CAS20, short for Compliant Assets. It is designed to support issuing stablecoins and tokenized real-world assets (RWAs) with compliance controls built directly into the token. Those controls include governance features such as allowlists and blocklists, giving issuers the ability to decide who is permitted to hold or move a token at the protocol level rather than through custom code.
There is a caveat. The full rollout of CAS20 features depends on future governance decisions, so the standard arriving on testnet does not mean every capability is switched on.
The third change is BEP-706, a precompile at address 0x70 that adds millisecond precision to block timestamps. Today, contracts typically see time in whole seconds. Jenner lets them see it in thousandths of a second. For DeFi oracles, which feed price data into lending protocols and exchanges, that extra precision could make timing-sensitive operations more accurate.
The news moving money, markets, and the world—before your day starts.
Daily. Free. Join 34,000+ readers across crypto, finance, and policy.
The fine print for node operators
Every testnet node must run a compatible client before activation. That means restarting with reth-bsc v0.1.3 or applying the relevant BSC Geth updates. Nodes that skip the upgrade risk falling out of sync with the rest of the network once the fork triggers.
One detail worth flagging: the dates do not perfectly line up. The v1.8.1 client release points to activation on the Chapel testnet on October 29 at 02:30 UTC, while the official announcement says October 28. Operators would be wise to have upgrades done before the earlier date rather than cutting it close.
Background: the road to mainnet
Testnet is the dress rehearsal. If Jenner behaves as intended there, BNB Chain plans to bring it to mainnet in late November 2026, though the exact timing has not yet been announced. Jenner follows earlier upgrades such as Mendel, which expanded the network’s scalability and functionality. The network has also recently conducted a BNB auto-burn event, the mechanism that periodically removes tokens from circulation.
What this means
The Payment Lane addresses a familiar complaint about network congestion by guaranteeing a reserved 5% share of block gas for basic transfers. CAS20 lowers the effort for stablecoin and RWA issuers who would otherwise write bespoke contracts, and gives BNB Chain a pitch to compliance-minded firms, though allowlists and blocklists are features that give issuers power over who can transact. The full rollout of those controls remains contingent on future governance decisions.
The near-term items to watch are whether node operators upgrade cleanly before the October 28 activation given the minor date discrepancy with the v1.8.1 release, whether testnet surfaces any issues with the Payment Lane or timestamp changes, and when BNB Chain locks in the late November mainnet date.