BNB Smart Chain’s Jenner hard fork activated on the Chapel testnet on October 29, 2026, introducing infrastructure for prioritized payment capacity, compliant token issuance and millisecond-precision timestamps. BNB Chain’s published client guidance set the testnet activation for 02:30 UTC, and the project’s subsequent announcement said the upgrade was live.
The development applies to the test environment, not BNB Smart Chain’s production mainnet. Network operators and developers can use the rollout to assess new functionality before a separate mainnet deployment is scheduled.
Payment Lane reserves capacity for eligible transfers
One of Jenner’s principal changes is Payment Lane, introduced through BNB Evolution Proposal 703. It reserves 5% of a block’s gas capacity for eligible payment transactions by default. Governance may adjust the allocation up to a maximum of 10%.
The reserved portion is intended to make transaction inclusion more predictable for certain payment activities when general network demand is high. Eligible transfers include nonzero BNB transfers to accounts without contract code and transactions to payment contracts that governance has approved.
Not every stablecoin transfer automatically qualifies. BNB Chain says the list of eligible payment contracts starts empty and requires governance decisions before particular token contracts are included. Transactions still pay applicable fees, and the reserved capacity is not a guarantee of immediate inclusion.
General transactions cannot consume unused Payment Lane capacity, a tradeoff intended to preserve payment availability during congestion. Developers and businesses will need to consider whether their transactions meet the defined criteria.
CAS20 and millisecond timestamps arrive in Jenner
The upgrade also introduces technical groundwork for CAS20, a compliant-asset standard described in BEP-702. It is designed for programmable policies around certain stablecoins and tokenized real-world assets, including allowlists, blocklists, minting, burning and transfer restrictions.
CAS20 token creation is not necessarily available immediately to everyone after the hard fork. BNB Chain has said that its full enablement requires a separate governance process. The design may be useful for organizations with specific issuance or compliance requirements, but it also involves control features that differ from fully permissionless token models.
A further proposal, BEP-706, lets smart contracts access millisecond-precision block timestamps through a dedicated precompile. The existing Solidity block.timestamp field remains denominated in seconds, avoiding an abrupt change to established contracts that use it.
Mainnet activation remains a separate milestone
BNB Chain’s official v1.8.1 compatibility guidance states that the release targets Chapel testnet node operators, builders and sentry operators. Mainnet nodes are not required to install the testnet release for the Jenner fork.
An earlier upgrade guide dated October 22 described a preliminary testnet schedule, while the actual client release specified October 29 at 02:30 UTC. The release-level timetable is the more precise reference for the event reported here.
BNB Chain has not confirmed a mainnet activation date in the relevant client instructions. A testnet launch therefore does not establish that the new payment allocation, compliant-asset features or transaction behavior are already active for ordinary mainnet users.
Primary sources: BNB Chain v1.8.1 release notes; official testnet timing clarification; Payment Lane technical explainer. BNB Chain’s own October 29 social announcement described the activation as live.
