BNB Chain said proposal BEP-706 has been included in the Jenner hard fork, adding a precompiled contract at address 0x70 that lets smart contracts read the current block timestamp with millisecond precision. Before this change, contracts could only access second-level time through block.timestamp, which made it impossible to tell apart blocks produced within the same second. Under BEP-706, developers can retrieve the number of milliseconds since the Unix epoch. BNB Chain said the feature can improve precision for time-limited signed quotes, auction deadlines, and timeliness checks for price oracle updates. The change is described as an incremental upgrade and does not alter the existing second-based return behavior of block.timestamp.
BNB Chain said BEP-706 has been included in the Jenner hard fork, adding a precompiled contract at address 0x70 so smart contracts can read the current block timestamp with millisecond precision.
Before the change, contracts could only access second-level time through block.timestamp. If multiple blocks were produced within the same second, contracts could not distinguish the exact time difference between them.
BEP-706 adds millisecond-level time access
The proposal allows developers to retrieve the number of milliseconds since the Unix epoch. According to BNB Chain, that can improve precision for time-limited signed quotes, auction deadlines, and timeliness checks for price oracle updates.
BNB Chain said the feature is an incremental upgrade and does not affect the existing second-based return mechanism of block.timestamp.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
