b077ad7f-9
BNB Chain Schedules Jenner Hardfork for Dec. 7 With Timestamp Risk Flagged
BNB Chain's Jenner hardfork activates Dec. 7 at 9:30 p.m. ET, adding a millisecond precompile at 0x70, Payment Lane and CAS20 — as a forum post warns BEP-706 sample code can let expired quotes pass timing checks.

Outputs
Jenner hardfork scheduled for 9:30 p.m. ET Dec. 7 (02:30 UTC Dec. 8), per BSC client v1.8.2 release
New precompile at address 0x70 returns 32-byte millisecond timestamps under BEP-706
Forum analysis warns BEP-706 sample helper can convert empty responses to zero, passing expired quotes
Payment Lane reserves 5% of block gas by default for eligible payments
CAS20 installs with token creation requiring separate activation by a governance-appointed administrator
BNB Chain has scheduled its Jenner hardfork for 9:30 p.m. ET on Dec. 7 (02:30 UTC on Dec. 8), according to the BNB Smart Chain (BSC) client v1.8.2 release. The release instructs mainnet node operators to replace their client binary and restart before activation. The date supersedes the late-November window cited in earlier testnet reporting.
The fork carries three operational changes for builders on BSC: a millisecond timestamp precompile, a reserved payment lane, and a native token standard. Each arrives with constraints that practitioners should price into contracts before, not after, activation.
What does the timestamp precompile change?
Jenner opens access to millisecond timing already recorded in BSC block headers but unavailable through the existing block.timestamp value, which remains denominated in seconds. The new built-in function sits at address 0x70 and returns a 32-byte millisecond timestamp, per BEP-706. Even after activation, the value remains validator-supplied within consensus limits — the proposal states plainly that finer precision provides no stronger timing guarantee than block.timestamp.
Where is the risk?
A forum contributor posting as Zealynx flagged a defect in the sample helper in section 4.5 of BEP-706. The author reported that a Foundry test returned zero without reverting when 0x70 was empty.
The mechanism is concrete. The helper makes a low-level staticcall, checks only whether it succeeded, then converts the returned bytes with uint64(uint256(bytes32(data))). Solidity's documentation confirms two facts: low-level calls to nonexistent contracts can succeed, and shorter byte arrays are padded with zeros. An empty response therefore becomes zero rather than causing a revert.
The forum analysis warns that an expiry check such as nowMs <= quote.expiry would then pass even for an expired quote. An empty 0x70 without an active precompile — the state of BSC before activation — is one way to produce that successful but empty response, and the same concern applies on any chain where the call succeeds with no data. The post identifies no affected deployed contract and no exploit.
The recommended fix is to check data.length == 32 or to use abi.decode, which rejects empty data. The BEP's sample contains neither safeguard. Any contract that copies the sample verbatim inherits the flaw.
What else ships in the fork?
Jenner also introduces Payment Lane, which reserves 5% of block gas by default for eligible payments. The payment-contract list starts empty; entries are added through governance. Eligible bare BNB transfers can qualify without a listing, but the reservation does not guarantee inclusion for any individual payment.
The fork additionally installs CAS20, a protocol-native token standard with transfer policies and mint, burn and seizure controls. Installing support does not open token creation: the release notes state that a governance-appointed administrator must activate creation separately.
For node operators, the deadline is binary — replace the binary and restart before 02:30 UTC on Dec. 8 or fall off consensus. For contract developers, the practical question is whether any deployed helper against 0x70 validates response length before activation makes the failure mode live.
via cryptonews.net (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,574 articles