Hello Everyone,

I’ve been working on a public mining pool designed to help a community collaborate on solving the Bitcoin Challenge. The goal is to make the pool as transparent as possible while taking steps to secure the private key from misuse if a miner finds the solution.  Please keep in mind that due to this the client and server software ill have to remain closed source as there is no way to get around the clients having to work with the physical private key hex values.

I’ve built a working client/server package that distributes work to clients in a randomized manner from the current puzzle range. The server dynamically adjusts the assigned work so that each client completes its range in approximately 60 seconds, sends back the result, and receives its next random block of work. This ensures consistent and efficient participation across the pool.

While the system is functional, I’d love to hear the community’s thoughts and suggestions on improving the security and functionality of the pool. This includes ways to enhance transparency, protect the private key, and build trust in the process.

At the moment, I have not put together a web interface as I have been focusing on the core client and server software. However, the client software provides updates on the miner's stats, the estimated BTC payout if the solution were found now, and the total search range that the pool has completed.

The client is a modified version of the KeyHunt software, as it was in a format that allowed for relatively easy modification to include the pool functions.

The server code is written in Python, with persistent storage for the work ranges that have been completed, as well as client work and related data.

If the pool does find the solution, the transaction will be generated to distribute the funds among the miners based on their share percentage and submitted via slipstream.mara.com. This is designed to reduce the risk of the transaction being broadcast to the full Bitcoin network mempool, as this could potentially result in the transaction being hijacked.

I am looking for anyone who would be interested in providing feedback or willing to point any GPUs at the server to help continue working through bugs.

Looking forward to your feedback!

Client Output:

Server Output: