Monday, November 2, 2026

BNB Chain Activates Jenner Hardfork on BSC Testnet

Photorealistic close-up of a blockchain hub with a glowing Payment Lane and Jenner icon in a block grid.

BNB Chain Activates Jenner Hardfork on BSC Testnet

BNB Chain has activated the Jenner hardfork on the BNB Smart Chain Chapel testnet, introducing reserved block capacity for payments alongside new infrastructure for compliant assets and higher-precision timing. According to the official BNB Chain release, Jenner went live on October 29 at 02:30 UTC through BSC client version 1.8.1, giving developers and infrastructure providers a live environment for testing the changes before a future mainnet rollout.

The upgrade combines BEP-702, BEP-703 and BEP-706, targeting different parts of BSC’s financial infrastructure rather than delivering a single throughput increase. Jenner adds a Payment Lane, the underlying CAS20 asset framework and millisecond-resolution timing for smart contracts, extending the network’s infrastructure work after the earlier Pasteur hardfork strengthened validator and block-building systems.

Payment Lane Reserves 5% of Block Gas

BEP-703 introduces the Payment Lane, which reserves 5% of each block’s gas limit for qualifying payment transactions. Native BNB transfers to ordinary accounts qualify automatically, while transactions sent directly to approved payment contracts can also use the reserved capacity. General-purpose transactions cannot consume unused Payment Lane capacity, meaning the reserved gas can remain idle when qualifying payments do not use it. Governance can adjust the allocation up to a protocol maximum of 10%.

The eligible-contract list initially starts empty. Stablecoins, CAS20 assets and other token contracts therefore do not gain reserved capacity simply because they are designed for payments. Governance must add each eligible contract to the list. Payment Lane prioritizes access to block capacity during congestion without guaranteeing transaction inclusion, eliminating fees or changing normal priority-fee ordering. That makes it structurally different from BNB Chain’s zero-fee stablecoin campaigns, which subsidize selected transaction routes rather than changing protocol-level block allocation.

Jenner also ships BEP-702, introducing CAS20 as a protocol-native fungible-token standard aimed at stablecoins and tokenized real-world assets. CAS20 supports shared allowlists and blocklists, transfer policies, pausing and separate roles for minting, burning and seizure through stateful precompiled contracts. The hardfork makes the CAS20 code available on testnet, but token creation and PolicyRegistry writes remain behind a separate governance-controlled activation mechanism. Existing BEP-20 tokens are unaffected and do not need to migrate.

Millisecond Timing Arrives Without Faster Blocks

BEP-706 adds a precompile at address 0x70 that lets smart contracts retrieve the executing block’s timestamp with millisecond precision. The existing Solidity block.timestamp value continues to operate in seconds. Applications must explicitly call the new precompile to access sub-second timing, which could support functions such as quote expiration, auction deadlines and price-feed freshness checks without changing BSC’s underlying block speed.

The testnet deployment builds on an infrastructure roadmap increasingly focused on payments and financial assets. BNB Chain has already been expanding stablecoin settlement infrastructure and has seen tokenized assets gain broader distribution across BSC. Jenner adds protocol mechanisms that could support those use cases, but technical availability should not be treated as evidence that CAS20 assets or Payment Lane contracts have already achieved production adoption.

BNB Chain has not yet published the final Jenner mainnet activation time or the corresponding required mainnet client release. Version 1.8.1 specifically targets Chapel testnet, and mainnet operators have been told to wait for a separate upgrade notice. The next material milestone is therefore mainnet scheduling, followed separately by governance decisions determining which token contracts enter Payment Lane and when CAS20 creation becomes operational.

Satoshipick
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.