<p>That proposed solution is only one possible solution. There might be better ways to solve this problem, and Nate Eldredge comments below <a href="https://bitcoin.stackexchange.com/a/79185/121614">this answer</a> that a solution might not be needed at all.</p>
<p>Realistically, it's completely fine to ignore this problem until say the year 2096. 10 years is more than enough for the community to agree on a solution and schedule a fork. There are more immediate issues requiring community attention for now.</p>

CC BY-SA 4.0
2022-04-23T11:41:55.137Z
Nate's comment ignores the need for timestamps in OP_CTLV. And 10 years sounds like plenty of time, but we should learn from rolling out IPv6 that you are probably drastically underestimating the time needed to upgrade a global network.
Mark H
CC BY-SA 4.0
2022-04-18T13:50:45.280Z
2022-04-18T13:50:45.280Z
Vojtěch Strnad
<p>Following along the 2106 problem solution proposed in <a href="https://bitcoin.stackexchange.com/questions/106783/will-a-hard-fork-be-required-to-change-timestamp-fields">Will a hard fork be required to change timestamp fields?</a> …</p>
<p>Is it possible to start including this logic into newer versions of core (is it already there?), or will this need to be a simultaneous upgrade by everyone?</p>

CC BY-SA 4.0
2022-04-20T02:09:37.953Z
Duplicate of https://bitcoin.stackexchange.com/questions/106783/will-a-hard-fork-be-required-to-change-timestamp-fields
Luke Mlsna
<timestamp>
Softening the 2106 hard fork
Jeffrawesome
# Softening the 2106 hard fork

(Asked by: username_0 on 2022-04-18)

Following along the 2106 problem solution proposed in [Will a hard fork be required to change timestamp fields?](https://bitcoin.stackexchange.com/questions/106783/will-a-hard-fork-be-required-to-change-timestamp-fields) …

Is it possible to start including this logic into newer versions of core (is it already there?), or will this need to be a simultaneous upgrade by everyone?

**Tags:** timestamp

> **Comments:**
> **username_1**: Duplicate of https://bitcoin.stackexchange.com/questions/106783/will-a-hard-fork-be-required-to-change-timestamp-fields  

---

## 1 answers

### Answer by username_2 on 2022-04-18. Score: 0

That proposed solution is only one possible solution. There might be better ways to solve this problem, and Nate Eldredge comments below [this answer](https://bitcoin.stackexchange.com/a/79185/121614) that a solution might not be needed at all.

Realistically, it's completely fine to ignore this problem until say the year 2096. 10 years is more than enough for the community to agree on a solution and schedule a fork. There are more immediate issues requiring community attention for now.

> **Comments:**
> **username_3**: Nate's comment ignores the need for timestamps in OP_CTLV. And 10 years sounds like plenty of time, but we should learn from rolling out IPv6 that you are probably drastically underestimating the time needed to upgrade a global network.  

---

