Timestamp Manipulation & Timejacking

Because Bitcoin's "clock" is decentralized and depends on peer communication, it is susceptible to specific types of manipulation. Timejacking is a theoretical attack where an adversary attempts to isolate a node and manipulate its perception of time to cause consensus failures.

1. How Timejacking Works

An attacker connects many malicious nodes to a victim node. 1. The malicious nodes all report a consistent, but incorrect, timestamp (e.g., 1 hour in the past). 2. The victim node calculates its Network Adjusted Time based on these peers. 3. The victim node's internal clock is now "dragged" away from the real time.

2. Consequences of Timejacking

If a node's time is successfully manipulated, it might: * Reject valid blocks: It thinks a valid block is too far in the future. * Accept invalid blocks: It might be tricked into following a chain that has been "time-warped" to lower difficulty. * Partitioning: The node is effectively "time-locked" out of the main network, making it vulnerable to Double Spending.

3. Mitigation: The 70-Minute Guard

To prevent a single attacker from easily dragging a node's clock, Bitcoin Core implements a safeguard: * If the median offset from peers is more than 70 minutes, the node will ignore the peer timestamps and revert to its own local system clock. * The node will also issue a Warning to the user.

4. Time-Warp Attack

A more advanced form of manipulation is the "Time-Warp Attack." Miners can manipulate timestamps at the end of a 2016-block window to make the Difficulty Adjustment algorithm think blocks were slower than they actually were. This allows them to mine with lower difficulty than intended. * This was a real problem in early altcoins and was fixed in Bitcoin via the MTP rule.

In the final section, we will build a Python Timestamp Auditor to check block consensus ourselves.