Posted by conduition
Sep 14, 2026/00:35 UTC
The discussion raises concerns about integrating mining code directly into Bitcoin Core, particularly when it is unlikely that Bitcoin nodes will utilize such code. The suggestion put forth advocates for the development of a specialized library dedicated to the proof system that miners could incorporate as needed. This approach would involve creating a shared library, potentially named libbitzip, which would handle both proving and verifying functionalities. The complexity of the prover-specific code could then be managed through an optional flag, allowing for flexibility depending on the user's requirements.
Further elaboration on this topic reveals that the implementation of such features is still at a preliminary stage, with significant evaluation required in the design trade-off space. Current efforts are focused on designing a SPHINCS verification circuit over GF(2). This circuit design is intended to be batched using a technique known as Flock, which is expected to set a benchmark for prover throughput. Understanding this throughput is essential as it will significantly influence future design decisions regarding the proof system library. These considerations are critical for developing a robust and efficient framework that meets the specific needs of miners without compromising the functionality and integrity of Bitcoin Core.
Thread Summary (9 replies)
Sep 4 - Sep 16, 2026
10 messages
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