BNB Smart Chain activated the Jenner hard fork on its Chapel testnet on October 28, 2026, introducing three protocol-level changes: a gas reservation system for payments (BEP-703), a compliance-native token standard for stablecoins and tokenized assets (BEP-702), and millisecond-precision block t...
"CAS20 token creation is switched off at the fork — a governance-appointed administrator must activate it later." — BNB Chain BEP-702 Specification, GitHub
BNB Smart Chain activated the Jenner hard fork on its Chapel testnet on October 28, 2026, introducing three protocol-level changes: a gas reservation system for payments (BEP-703), a compliance-native token standard for stablecoins and tokenized assets (BEP-702), and millisecond-precision block timestamps (BEP-706). Mainnet deployment is targeted for late November 2026.
The upgrade positions BSC — a chain processing 1.51 billion transactions in Q3 2026 with $14 billion in stablecoin supply — to compete for regulated payment and asset-issuance workloads. The Payment Lane reserves 5% of block gas by default for qualifying transfers, ensuring basic payments clear even during congestion spikes. CAS20 embeds allowlists, blocklists, seizure controls, and role-based administration directly into the protocol layer rather than in application-level smart contracts.
Whether either feature gains adoption depends on governance decisions that have not yet been made. The Payment Lane's contract whitelist launches empty, meaning stablecoin transfers require separate governance approval. CAS20 token creation is disabled at fork activation and awaits an administrator appointment. The fork ships infrastructure; the policy choices follow.
BEP-703 carves out a dedicated slice of each BSC block's gas capacity for payment transactions. The default reservation is 5%, adjustable by governance to a protocol-defined maximum of 10%.
Eligible transactions fall into two categories:
The second category is the one that matters for stablecoin usage, and it starts empty. USDT, USDC, FDUSD, and any future CAS20 tokens must each receive individual governance approval before their transfers qualify for the reserved lane. Until that happens, the Payment Lane covers only native BNB person-to-person transfers.
Mechanics. The reserved gas cannot be claimed by general-purpose transactions. If payment-eligible traffic does not fill its 5% allocation in a given block, that capacity goes unused rather than being released to non-payment transactions. This is a deliberate design choice that trades marginal block utilization for guaranteed payment throughput.
The specification defines transaction classification, quota arithmetic, consensus validation, governance-managed configuration, and the PaymentLane system contract interface. Validators enforce the reservation at the consensus layer, meaning non-compliant blocks are rejected by the network.
BNB Chain processes approximately 15.2 to 18.3 million transactions daily. At 5% reservation, the Payment Lane provides guaranteed capacity for roughly 760,000 to 915,000 payment transactions per day under current throughput, though actual eligible volume will depend on which contracts receive governance approval.
BEP-702 introduces CAS20, a protocol-native fungible token standard implemented as stateful precompiles rather than deployed EVM bytecode. CAS20 tokens occupy deterministic addresses derived through a factory and registry system, with compliance controls embedded at the protocol layer.
The standard targets two asset classes: stablecoins and tokenized real-world assets (RWAs). It retains full BEP-20 selector and event compatibility, meaning existing wallets, DEX interfaces, and analytics tools can interact with CAS20 tokens without modification.
Four-role authority structure. CAS20 separates administrative power across distinct functions:
Activation Administrator — Appointed by GovHub (BSC's governance contract). Controls three network-level switches: asset-variant token creation, stablecoin-variant token creation, and shared policy registry writes. Only GovHub can change this administrator.
Feature Administrator — Manages when new stablecoins and tokenized assets can be created.
Token Role Administrators — Control individual permissions within specific tokens, including minting, burning, seizure, and pausing.
Policy Administrators — Manage shared compliance lists and account eligibility across multiple tokens.
Compliance controls include shared allow/blocklists, transfer policies, pause functionality, and separate mint, burn, and seizure roles. Seizure requires the target account to fail a SEIZE_EXEMPT_POLICY check, authorization of the seizure role, the function to be unpaused, sufficient balance, and a valid destination policy. Transfer restrictions operate independently from seizure eligibility — pausing transfers does not pause seizure.
A critical implementation detail: once the shared policy registry is disabled, existing restrictions persist and cannot be updated. This creates a potential lock-in scenario where compliance lists become immutable if governance revokes registry write access.
Current status. BEP-702 remains labeled "Draft" on GitHub. Token creation is disabled at fork activation. No administrator has been appointed. Existing BEP-20 tokens are unaffected.
BEP-706 deploys a precompile at address 0x70 that returns block timestamps in millisecond precision. The existing block.timestamp Solidity global continues to return whole seconds; the new precompile offers an opt-in upgrade path for applications requiring finer granularity.
Target use cases include quote expiry windows for DeFi protocols, auction cutoff enforcement, and oracle price-feed timing. The change does not alter BSC's block production speed or modify validator timestamp guarantees.
For RPC compatibility, reth-bsc v0.1.3 requires blockOverrides.prevRandao to encode millisecond remainders (0–999) as 32-byte hex values for eth_call, eth_estimateGas, debug_traceCall, and eth_simulateV1.
BNB Smart Chain enters this upgrade as the third-largest smart contract platform by several metrics:
| Metric | Value | Period | |--------|-------|--------| | Transactions | 1.51 billion | Q3 2026 | | Daily active addresses | 2.10 million avg (2.76M peak) | Q3 2026 | | Smart contract deployments | 12.3 million | Q3 2026 (up ~3x QoQ) | | Revenue | $54.2 million | Q3 2026 | | Stablecoin supply | ~$14 billion | October 2026 | | USDT on BSC | ~$9 billion | October 2026 | | TVL | ~$5.5 billion | October 2026 | | Market cap (BNB) | $96.3 billion | October 22, 2026 |
Q3 activity showed divergent trends: contract deployments nearly tripled, driven partly by AI agent applications (Predict.fun alone handled 45.3 million transactions, up from 2.2 million in Q2), while daily active addresses declined 14% quarter over quarter. Revenue rose 54% over the prior period.
BNB Chain holds approximately $14 billion in stablecoin supply, with USDT comprising roughly 60% at ~$9 billion. According to ecosystem data, BSC accounts for approximately 40% of global stablecoin transactions by count, with roughly $60 billion in monthly stablecoin volume. The Payment Lane and CAS20 standard are designed to retain and expand this position.
The Chapel testnet fork activated October 28, 2026 (v1.8.1 release notes specify October 29 at 02:30 UTC for full activation). Mainnet deployment is planned for late November 2026; no specific date has been announced.
All BSC validators and node operators must upgrade to reth-bsc v0.1.3 or apply BSC Geth updates before mainnet activation. Nodes that fail to upgrade will desynchronize from the network. Block builders and application developers are advised to begin testing against the Chapel testnet immediately.
The Jenner fork follows the Pasteur and Mendel upgrades earlier in 2026, continuing a cadence of quarterly protocol-level changes.
The Payment Lane and CAS20 address a specific market gap: no major EVM chain currently offers protocol-level gas reservation for payment transactions or protocol-native compliance token standards.
Ethereum's ERC-20 standard and its compliance-oriented extensions (ERC-3643 for security tokens) operate entirely at the smart contract level, meaning compliance enforcement depends on application logic rather than consensus rules. Solana offers priority fees and compute unit reservations but lacks a payment-specific lane. Base, Arbitrum, and other L2s inherit Ethereum's contract-level compliance model.
Hong Kong's stablecoin regulatory framework, which granted its first two issuer licenses in April 2026 (to HSBC and to Standard Chartered/HKT/Animoca Brands' Anchorpoint), requires features that CAS20 natively supports: allowlists, blocklists, seizure capabilities, and auditable role separation. The U.S. OCC's finalized GENIUS Act rules, effective January 18, 2027, similarly require redemption controls and reserve management that CAS20 can accommodate at the protocol layer.
The question is whether regulated issuers will prefer protocol-level compliance infrastructure managed by BNB Chain governance or self-managed smart contract implementations on networks like Ethereum where the issuer retains full control of compliance logic. HSBC chose a private Hyperledger Besu chain for its RedCoin stablecoin. JPMorgan expanded JPM Coin to Ethereum. Neither selected a public chain with built-in compliance primitives.
BNB Chain's Jenner hard fork activated on testnet October 28, targeting mainnet in late November 2026. Three BEPs ship: Payment Lane (BEP-703), CAS20 compliance tokens (BEP-702), and millisecond timestamps (BEP-706).
The Payment Lane reserves 5% of block gas for payments, but the stablecoin contract whitelist starts empty. Only native BNB transfers qualify until governance lists specific token contracts.
CAS20 offers protocol-native compliance for stablecoins and RWAs — allowlists, blocklists, seizure, and four-role administration — but token creation is disabled at launch. A governance-appointed administrator must activate it.
BSC processes $14 billion in stablecoins and handles an estimated 40% of global stablecoin transactions by count. The upgrades target retention and expansion of this payment-centric positioning.
No major EVM chain currently offers comparable protocol-level payment or compliance infrastructure. Whether regulated issuers adopt it over self-managed smart contract models remains an open question.
BEP-702 remains in "Draft" status on GitHub. Regulated entities will require final specifications and governance clarity before committing to CAS20 issuance.
The Jenner hard fork represents BNB Chain's most explicit move toward regulated financial infrastructure. Rather than adding compliance as an application-layer afterthought, BEP-702 and BEP-703 build payment prioritization and asset controls into the consensus layer itself.
The infrastructure ships without activation. Payment Lane's stablecoin whitelist is empty. CAS20 token creation is off. No administrator has been named. Each feature requires subsequent governance action to become functional — a staged approach that allows testing and institutional evaluation before commitment.
For a chain already carrying $14 billion in stablecoins and processing 1.51 billion quarterly transactions, the economic logic is straightforward: guaranteed payment throughput and protocol-native compliance lower the barrier for regulated issuers who would otherwise build or license these capabilities themselves. The $54.2 million in Q3 revenue demonstrates existing fee capture; the question is whether compliance infrastructure converts into additional issuance volume.
The answer depends less on the technical specifications — which are comprehensive — and more on governance execution: how quickly administrators are appointed, which contracts receive Payment Lane status, and whether regulated issuers in jurisdictions like Hong Kong, the EU, and the U.S. accept BNB Chain governance as a counterparty in their compliance architecture. Mainnet activation in late November will start that clock.