It can be used to optimize consensus and transaction protocols. Consensus example - check out Nezha (https://arxiv.org/abs/2206.03285 https://arxiv.org/abs/220

It can be used to optimize consensus and transaction protocols. Consensus example - check out Nezha (https://arxiv.org/abs/2206.03285 https://arxiv.org/abs/2206.03285), they came up with an interesting 'Deadline Ordered Multicast' (DOM) primitive > DOM follows Liskov's suggestion of "depending on clock synchronization for performance but not for correctness" Transactions example - look no further than DynamoDB, https://muratbuffalo.blogspot.com/2023/08/distributed-transactions-at-scale-in.html https://muratbuffalo.blogspot.com/2023/08/distributed-transa... > In order to relieve your anxiety before you read further, no, correctness does not depend on timestamps, clock synchronization only helps to improve performance, as more accurate clocks result in more successful transactions and a serialization order that complies with real time.