Great Consensus Cleanup Revival
Posted by Eric Voskuil
Jun 29, 2024/01:31 UTC
In a recent exchange, the discussion revolved around enhancing the robustness of coinbase size verification post-socket read operations. The conversation specifically questioned the comparison between utilizing a non-null pointer check versus directly assessing the coinbase size for this purpose. Clarification was sought on whether the term "non-null pointer" referred to a conventional C programming pointer or to a transaction input designated as a "null point," characterized by a sequence of 32 repeating 0x00 bytes followed by 4 0xff bytes. The inquiry aimed to understand how the proposed method offers increased reliability in the context of transaction processing and system stability.
TLDR
Join Our Newsletter
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
Explore all Products
We'd love to hear your feedback on this project?
Give Feedback