Proposal: Use NTP Timestamps in Consensus Messages

[fed-franz]

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:

• 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.

Additional context

Related Issues:

• Proposal: Reject consensus messages with inconsistent timestamp #13
• Proposal: Slash concurrent activity on multiple branches #14

[herr-seppia]

Proposal and Ratification already have a timestamp field

[fed-franz]

Proposal and Ratification already have a timestamp field

I updated the DIP to only make these timestamps based on NTP