Yes, a corrupt operator can slightly manipulate the timestamps for a marginal benefit.
Doing a it would in a big way would require a significant 51% attack where considerable amounts of history were rewritten in order to achieve a moderate benefit. It is theoretically a problem, but the risk/cost/reward is poor. As such I don't think anyone has ever bothered.
Topic: How do bitcoin clients agree on what time it is? (Read 996 times)
Does this mean that a large miner or a pool op could timestamp blocks either at the minimum or maximum variance allowed to manipulate the difficulty?
I read a paper once, posted here on these forums, about this being a potential attack vector.
Probably here:
- https://bitcointalksearch.org/topic/m.521772
I read a paper once, posted here on these forums, about this being a potential attack vector.
https://en.bitcoin.it/wiki/Block_timestamp
Timestamps are checked against network time and your local time. Nodes refuse to relay if the block's time is too far off.
Timestamps are checked against network time and your local time. Nodes refuse to relay if the block's time is too far off.
In order for the difficulty to be changed every 2016 blocks, the clients need to know how long it has been since the last retarget. Clocks aren't perfect, though, and there could be malicious clients. How do nodes agree?
Jump to: