Odaily Planet Daily reports: BNB Chain has announced that the BEP-706 proposal has been incorporated into the Jenner hard fork. By introducing a precompiled contract at address 0x70, smart contracts can now read the current block’s millisecond-level timestamp. Previously, contracts could only access second-level timestamps via block.timestamp, making it impossible to distinguish precise time differences when multiple blocks were produced within the same second. BEP-706 enables developers to obtain the number of milliseconds since the Unix epoch, improving the accuracy of time-sensitive applications such as timed signature bids, auction deadlines, and price oracle update validity checks. This enhancement is implemented as an incremental upgrade and does not affect the existing second-level return mechanism of block.timestamp.
BSC Jenner Hard Fork Introduces Millisecond Timestamps for Smart Contracts
KuCoinFlashShare
BNB Chain has deployed the Jenner hard fork, a significant update that introduces millisecond-level timestamps for smart contracts. The BEP-706 proposal enables contracts to access precise timestamps through a precompiled contract at address 0x70. Previously, contracts relied on second-level timestamps from block.timestamp. This enhancement improves accuracy for time-sensitive functions such as auctions and oracles. The update is backward compatible and does not disrupt existing functionality.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.

