UKBNB Chain Jenner hard fork on Chapel testnet
BNB Chain's Jenner hard fork is scheduled to go live on the Chapel testnet of BNB Smart Chain on October 29, 2026, at 02:30 UTC. The upgrade is tied to BNB (BNB) and introduces native CAS20 token support under the draft BEP-702 standard.
What is happening
The v1.8.1 release, published on October 16, schedules the Jenner fork for the Chapel testnet. An earlier announcement gave late-November guidance for mainnet, but the exact mainnet time has not been announced.
The central change is BEP-702, which remains labeled Draft. It defines the CAS20 token family, which moves common token behavior into native chain logic implemented as stateful precompiles. Existing BEP-20 tokens would remain unaffected. CAS20 has two variants, Asset and Stablecoin, and BNB Chain's CAS20 page is seeking early-access issuers.
Feature availability is controlled by governance. Chain governance appoints an activation administrator through GovHub, BSC's governance forwarding contract. That administrator operates separate switches for creating Asset-variant tokens, creating Stablecoin-variant tokens, and writing to a shared policy registry. Only GovHub can change the administrator, and only the stored, nonzero administrator can operate the switches. Within a token, minting, self-burning, seizure, pausing and unpausing use separate roles, and seizure is disabled by default for holders unless the token is configured otherwise.
Why it matters
For issuers, installing Jenner support and activating token creation for a chosen variant are two different milestones. Even after the code is on the network, a launch depends on governance opening the relevant switch. The shared policy registry adds a further dependency: if registry writes are closed, list memberships cannot be changed, and an account already restricted by a policy would remain restricted until writes are reopened.
For holders and traders, the activation switches are not a direct mechanism for moving or freezing balances. Closing a creation feature would stop new tokens of that variant but would not stop existing tokens from minting, transferring or administering roles. Whether a holder is exposed to transfer restrictions or seizure depends on the permissions and policies the issuer configures. The proposal also notes a trade-off of native logic: a client defect could affect multiple CAS20 tokens and require another hard fork to fix.
The testnet fork is the next scheduled step. It is a test environment, and mainnet timing remains separate and unconfirmed in terms of the exact time.
Key details
- Date: October 29, 2026, 02:30 UTC (exact time)
- Project: BNB Chain
- Coins: BNB
- Category: Testnet
- Status: Confirmed
- Source: CryptoSlate