Posted by Antoine Poinsot
Feb 5, 2026/22:48 UTC
The email from Antoine elaborates on the reasons behind constraining the nSequence of coinbase transactions as part of a Bitcoin Improvement Proposal (BIP). The primary objective of this constraint is to ensure that timelock validation is performed correctly. By setting the nSequence to a final state, represented by the value 0xffffffff, it is possible to bypass timelock validation. This enforcement of timelock validation provides a guarantee that, when validating a block, no previous block in the chain could have the same combination of nLockTime and nSequence, thus ensuring the uniqueness of the transaction ID (txid) of the coinbase transaction within a block, assuming the SHA256 algorithm remains secure.
Antoine further clarifies that after BIP 34's activation, no block had its nLockTime set, which simplifies the validation process for blocks post-BIP 54 activation. This simplification could potentially allow for the disabling of the BIP 30 check beyond a certain height if it gets buried in Bitcoin Core's codebase, eliminating the need to verify against the historical BIP 34 activation block hash.
Additionally, the email addresses a specific critique regarding the enforcement of BIP 30 from the genesis block in Bitcoin Core, except for two specific blocks in the historical chain. Antoine acknowledges the suggestion to expand the BIP and code documentation to clarify this point. He also refers to a direct communication where the suggestion to constrain the nSequence was made, which he later publicly shared in a thread on Delving, thereby incorporating it into the BIP.
The rationale for these decisions is rooted in making all coinbase transactions post-Consensus Cleanup activation non-duplicate by enforcing the timelock. This approach is consistent with the enforcement of nLockTime from the genesis block across various implementations, not just Bitcoin Core. This detailed explanation aims to clarify the motivations behind these technical choices in the BIP, ensuring a better understanding of the proposal's goals and mechanisms.
Thread Summary (14 replies)
Dec 30 - Feb 12, 2026
15 messages • 14 replies
TLDR
We’ll email you summaries of the latest discussions from high signal bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project.
Give Feedback