BNB Chain Jenner Hard Fork on 8 December (02:30 UTC): What BEP20 Users and Node Operators Must Do
BNB Smart Chain's Jenner hard fork activates at 02:30 UTC on 8 December 2026. Users need no action, but node operators must run BSC v1.8.2 and developers should test RPC changes now.
Crypto Support & Research Desk
Quick answer: BNB Chain's Jenner hard fork activates on BNB Smart Chain mainnet at 02:30 UTC on 8 December 2026. Ordinary BNB and BEP20 holders do not need to do anything, but node operators must run BSC v1.8.2 (or a compatible reth-bsc release) before then. Expect possible short exchange pauses for BEP20 deposits and withdrawals around activation.
What is the Jenner hard fork?
Jenner is the next scheduled network upgrade for BNB Smart Chain (BSC). According to the BNB Chain release notes, the v1.8.2 client released on 3 November 2026 sets the mainnet activation time to 2026-12-08 02:30:00 UTC. The fork was already activated on the Chapel testnet on 29 October 2026 at 02:30 UTC, using client v1.8.1.
Because it is a hard fork, nodes that have not upgraded before activation will stop following the canonical chain. For everyday users, though, nothing changes about wallets, balances or token contracts.
What changes with Jenner
The fork is defined in BEP-718 and bundles several proposals, as summarised by Chainstack's Jenner documentation and crypto.news (29 October 2026).
Payment Lane (BEP-703)
A portion of each block's gas, 5% by default, is reserved for simple payments. Governance can raise this to a maximum of 10%.
- It covers nonzero native BNB transfers to accounts without code (normal wallet addresses), plus transactions to payment contracts that governance has approved.
- Legacy, access-list and EIP-1559 transaction types (0x00, 0x01, 0x02) qualify.
- The approved-contract list starts empty, so BEP20 token transfers such as USDT stay in the general lane for now.
- Inclusion is not guaranteed and normal fees still apply.
In practice, plain BNB payments may confirm more reliably during congestion. It is not a free or priority lane for every transaction.
Millisecond timestamp precompile (BEP-706)
A new precompile at address 0x70 returns block time in milliseconds. block.timestamp itself stays in seconds, so existing contracts are unaffected.
Compliant token standard (BEP-702)
Jenner adds CAS20, a standard for compliant tokens. Creating such tokens is switched on later by governance, so nothing changes for users at activation.
Other changes
- The double-sign evidence precompile at
0x68is now charged gas per input byte. - MEV-related changes (BEP-675) ship with the client but do not require the fork.
Who needs to act, by role
Wallet users and BEP20 holders
No action is required. Your BNB and BEP20 tokens stay where they are, at the same addresses. Do not respond to messages telling you to "migrate", "upgrade" or "validate" your wallet for Jenner; that is a classic scam pattern around hard forks.
Exchange users
Exchanges commonly pause BNB and BEP20 deposits and withdrawals for a short time around BSC hard forks. As of 17 November, we had not found exchange pause notices for Jenner. Practical precautions:
1. Avoid sending large BEP20 transfers to or from exchanges from roughly 01:30 to 04:30 UTC on 8 December.
2. Watch your exchange's announcements page in early December for the exact pause window.
3. Always choose the BSC (BEP20) network, not opBNB or ERC20, when depositing BNB Chain assets.
4. If a deposit is delayed after the fork, look up the transaction hash on BscScan before contacting support. If it is confirmed on-chain, the exchange will usually credit it once deposits reopen.
Node operators, validators and MEV builders
1. Upgrade to BSC v1.8.2 well before 02:30 UTC on 8 December. The release is marked "Mandatory Update Required" for mainnet nodes, builders and sentries.
2. If you are upgrading from v1.7.x or v1.8.0-alpha, read the v1.8.0-alpha and v1.8.1 release notes first. They remove some config fields and change RPC and MEV gRPC behaviour.
3. Restart and confirm the version after replacing the binary.
4. reth-bsc users: run the current reth-bsc release that supports Jenner, including the state-root hotfix released on 6 November (v0.1.4-hotfix). BNB Chain said that hotfix needed no hard fork and no action from ordinary users. Check the reth-bsc release page for the minimum version required for Jenner.
5. Monitor peers and block import closely around activation.
Developers, RPC providers and indexers
These changes arrive when nodes upgrade to the new client, which may be before 8 December:
debug_trace*output now follows the Geth format. This can break parsers written for the old format.eth_simulateV1adds amaxUsedGasfield.- A new method,
eth_getStorageValues, reads up to 1,024 storage slots in one call. prevRandaooverrides must be a millisecond remainder between 0 and 999.
Test your tooling on Chapel testnet, where Jenner is already live, before your RPC provider upgrades mainnet nodes.
How to verify the schedule yourself
- Read the v1.8.2 entry on the official BNB Chain releases page.
- Check the bnb-chain/bsc GitHub repository for the v1.8.2 release notes.
- Follow BNB Chain's official blog and governance forum for any change to the activation time.
- Watch exchange announcement pages for deposit and withdrawal pause notices.
For how other networks handled recent upgrades, see our guides on the Cosmos Hub Gaia v29.1.0 upgrade, Injective's Veyra upgrade halt, the Dash v24 hard fork and the Hedera v0.79 mainnet upgrade.
What we could not confirm
- No exchange had published a Jenner pause schedule at the time of writing.
- We did not find a separate BNB Chain blog post announcing the mainnet date; the official source is the release notes.
- The minimum reth-bsc version for Jenner and any effect on opBNB were not stated in the sources we reviewed.
Frequently asked questions
When is the BNB Chain Jenner hard fork?
Jenner activates on BNB Smart Chain mainnet at 02:30 UTC on 8 December 2026 (Unix timestamp 1796697000), according to BNB Chain's v1.8.2 release notes.
Do I need to do anything with my BNB or BEP20 tokens?
No. Balances, addresses and token contracts are unchanged. Ignore anyone telling you to migrate or validate your wallet for the fork.
Will exchanges pause BNB deposits for Jenner?
Exchanges often pause BEP20 deposits and withdrawals briefly around BSC hard forks. No notices had been published as of 17 November, so check your exchange in early December.
Which client version do BSC node operators need?
BSC v1.8.2, released on 3 November 2026, is a mandatory update for mainnet node operators, validators, MEV builders and sentries. reth-bsc users should run the current Jenner-compatible release.
What is the BNB Chain Payment Lane?
It reserves 5% of block gas by default (up to 10% via governance) for plain BNB transfers to normal wallets and approved payment contracts. Fees still apply and inclusion is not guaranteed.
Conclusion
Jenner is a routine but mandatory BNB Smart Chain hard fork scheduled for 02:30 UTC on 8 December 2026. If you only hold BNB or BEP20 tokens, you do not need to do anything except avoid large exchange transfers around activation and ignore "upgrade" scams. If you run nodes or build on BSC, upgrade to v1.8.2 now and test the RPC changes on Chapel before your providers switch over.
This article is for information only and is not financial or technical advice for your specific setup. Blockchain Support USA is an independent publication and is not affiliated with BNB Chain, Binance or any exchange. We will never ask for your seed phrase, private keys, passwords or 2FA codes.
Regulatory & Financial Risk Disclosure
The opinions, research, and analysis expressed in this publication are solely for educational and informational purposes and do not constitute investment, financial, legal, or tax advice. Digital asset markets are speculative and volatile. Past performance does not indicate future results. Always perform independent due diligence.
About the Author
Crypto Support & Research Desk
Crypto Support Desk publishes practical, source-led guides to exchange, wallet, network and on-chain service changes. Information is checked against primary or reputable security sources and is not investment advice.