Author: Jorge Timón 2011-11-23 15:38:30
Published on: 2011-11-23T15:38:30+00:00
The discussion revolves around the protocol's deterministic way of accepting or rejecting a block and the possibility of cheating the timestamp while hashing the block. The proposed solution is to make the acceptance window zero, which will prevent miners from wasting their efforts as they know their peers will reject it. In response to the question about the network clock in the chain (in the protocol), it is mentioned that it has nothing to do with the protocol and is an individual miner's choice to accept or reject a block based on the timestamp it claims and the current time. The clients use a community clock as "current" established from the time they receive from peers in the "version" message. However, miners are not bound to use this clock, but if they don't use time that approximates what their peers are using, their blocks would be rejected. It is also stated that NTP is mentioned in the source as an alternative to the imperfect decentralized clock used by the client. Overall, the discussion highlights the importance of a deterministic way to determine whether to accept or reject a block and the role of network clocks in the process.
Updated on: 2023-06-04T21:33:11.284611+00:00