This DIP proposes to make nodes leverage NTP for constructing and verifying consensus messages timestamps.
Having a reliable timestamp is pre-requisite to enable or support features like:
Autocontracts (eg, have actions triggered by reaching a specific time)
Slashing provisioners working on multiple branches at the same time
Prevent withholding attacks, where ratified blocks are kept hidden and then published at a later time
Possible solution design or implementation
A classic server-based NTP can be used in the first implementation.
In a subsequent version, this should be replaced with a P2P NTP or other distributed protocol.
Summary
This DIP proposes to make nodes leverage NTP for constructing and verifying consensus messages timestamps.
Having a reliable timestamp is pre-requisite to enable or support features like:
Possible solution design or implementation
A classic server-based NTP can be used in the first implementation. In a subsequent version, this should be replaced with a P2P NTP or other distributed protocol.
Additional context
Related Issues:
13
14