Skip to content

2106#119

Open
Sjors wants to merge 10 commits into
masterfrom
2026/06/merkle
Open

2106#119
Sjors wants to merge 10 commits into
masterfrom
2026/06/merkle

Conversation

@Sjors

@Sjors Sjors commented Jun 22, 2026

Copy link
Copy Markdown
Owner

The future is now.

Related discussion:

(heavily vibe coded prototype)

@Sjors Sjors force-pushed the 2026/06/merkle branch 3 times, most recently from b672104 to d3217e3 Compare June 23, 2026 14:59
Sjors added 10 commits June 23, 2026 19:54
Consensus changes in this draft:

- The first block with nTime >= 2^32 must have a negative nVersion and use the new 84-byte header format.

- Every subsequent block must continue to use the new header format.

- Blocks using the new header format must have nTime >= 2^32.

- Block timestamps, MTP, and timestamp comparisons used by consensus validation are represented as uint64_t, allowing the full uint64_t timestamp range.

Tests added/updated:

- Add feature_y2106_extended_time.py to exercise the post-2106 hardfork behavior against current and previous-release nodes, including the max uint64 timestamp reaching contextual validation.

- Extend interface_ipc_mining.py to cover 64-bit submitSolution timestamps.
Position-tagging extended merkle leaves prevents repeated transactions from
recreating the same duplicated-right-branch root.

Legacy blocks still use the original mutation-detection mitigation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant