Aug 14 - Aug 14, 2026
The core issue revolves around Template Providers not receiving direct feedback or proof of their block templates being utilized by mining operations. In the current setup, while they do receive shares when a block is successfully mined, there is no continuous verification mechanism during the solo-mining process, which could serve as proof that it is indeed their templates being mined.
To resolve this, the proposed extension would modify the existing workflow by routing the work shares—which are ordinarily sent from Mining Devices (ASICs) directly to Pools—also to the Template Provider. This adjustment would enable Template Providers to have immediate confirmation of their contribution to the mining effort, thereby ensuring transparency and reliability in solo-mining scenarios. Implementing such a feature would be particularly beneficial for operations where clients operate both the pools and manage ASIC connections dynamically, as is the case with the individual proposing this extension.
Furthermore, the proposal is designed to be optional, allowing Template Providers to opt-in based on their specific needs and circumstances. This flexibility ensures that the extension can cater to a wide range of use cases without imposing unnecessary changes on those who may not require this feature. For more details or to engage in the discussion surrounding this proposed extension, interested parties are encouraged to visit the ongoing discussion thread on the sv2-spec repository, which can be accessed here. This forum offers an opportunity for community feedback and further refinement of the proposal.
Thread Summary (0 replies)
Aug 14 - Aug 14, 2026
1 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