
BNB Chain has announced that its Jenner hard‑fork will go live at 9:30 p.m. Eastern Time on December 7, which corresponds to 02:30 UTC on December 8. The timing is detailed in the v1.8.2 release of the BNB Smart Chain (BSC) client, and node operators on the mainnet are instructed to upgrade their client binaries and restart before the fork activates. This schedule replaces the late‑November window that The Defiant referenced in its recent testnet report.
The upgrade brings a new precompiled contract that gives developers access to millisecond‑precision timestamps that are already recorded in BSC block headers. The existing block.timestamp variable continues to return seconds, but the new function, located at address 0x70, returns a 32‑byte value representing the timestamp in milliseconds, as defined in BEP‑706.
In a post on the BNB Chain forum, a contributor identified as Zealynx highlighted the sample helper code found in section 4.5 of BEP‑706. Zealynx noted that a Foundry test produced a zero result without reverting when the address 0x70 returned no data. The helper performs a low‑level staticcall, checks only that the call succeeded, and then converts the returned bytes with the expression uint64(uint256(bytes32(data))). Solidity’s documentation confirms that low‑level calls to non‑existent contracts can succeed, and that shorter byte arrays are padded with zeros during conversion. Consequently, an empty response is interpreted as zero rather than causing the call to fail.
The forum analysis warns that this behavior could allow an expiry check such as nowMs <= quote.expiry to succeed even when a quote has already expired, because the empty response from 0x70 before the fork would be treated as a valid timestamp of zero. The same risk would exist on any chain where a call to a precompile succeeds but returns no data. The post does not point to any specific contract that is vulnerable, nor does it describe an actual exploit.
To avoid the problem, the author suggests verifying that the returned data length equals 32 bytes or using abi.decode, which rejects empty payloads. The sample code in the BEP does not include these safeguards. Even after Jenner activates, the millisecond timestamp will still be supplied by validators and will be subject to the same consensus limits as the existing block.timestamp; BEP‑706 notes that the finer granularity does not provide a stronger timing guarantee.
Jenner also adds a feature called Payment Lane, which by default reserves five percent of a block’s gas for payments that meet certain eligibility criteria. The list of contracts that can use this lane starts out empty and will be populated through governance proposals; however, plain BNB transfers that meet the eligibility rules can use the lane without being on the list. The reservation does not guarantee that any particular payment will be included in a block.
Finally, the fork introduces CAS20, a native token standard that includes built‑in transfer policies as well as mint, burn and seizure controls. Deploying the standard does not automatically enable token creation; according to the release notes, a governance‑appointed administrator must explicitly activate the ability to create new CAS20 tokens.
Source: CryptoNews.net