The upgrade date is set: December 8. But someone spotted a potential issue in the sample code.

On November 3, BNB Chain announced that the Jenner hard fork would take place on December 8 at 02:30 UTC (10:30 a.m. Beijing time). The testnet had already gone live at the end of October.

This upgrade includes three practical changes:
1. BEP-703 Payment Channels: By default, 5% of each block’s gas is reserved for compliant payment transactions. Governance can raise this to 10%, so payments won’t have to compete with regular transactions during peak periods.
2. BEP-702 CAS20: A standard for compliant assets, laying the groundwork for stablecoins and RWAs on-chain. However, governance must separately approve the issuance of tokens.
3. BEP-706 Millisecond Timestamps: Smart contracts can read block timestamps with millisecond precision.

All mainnet nodes, validators, and MEV builders must upgrade to v1.8.2 or reth-bsc v0.1.4 and restart before activation. Those who don’t upgrade will fall behind.

Interestingly, someone pointed out on the forum on November 19 that the BEP-706 sample code has a potential issue: if a timestamp call succeeds but returns no data, an expired quote could slip past the freshness check. This is only an issue with the sample code; there’s no conclusion yet about the mainnet consensus code. But the fact that it took a month of testnet operation to catch it shows that audits during upgrade windows need to be more thorough.

This whale’s take: The real value of Jenner lies in its payment channels. BSC wants to make on-chain payments not just possible, but a priority. 5% may look small, but it’s a step in the right direction—stablecoins and RWAs are especially vulnerable to being crowded out during peak periods. CAS20 follows the same logic: compliant assets need certainty. Before December 8, keeping an eye on node upgrade progress and official patches is far more useful than watching the short-term price of $BNB .