invpe / gridman

🤖 GRIDMAN

A software legacy spanning a decade, originally designed for distributed computing with Raspberry Pis, has been refurbished, modernized, and repurposed to harness the computational power of all available machines in my possession. This isn't merely a source code repository; rather, it comprises pages that provide real-time insights into the ongoing computational tasks across the network of nodes.

🧙 WHAT's cracking

1. To revive this nearly dormant project, I've developed a BTC Lottery miner task. It operates through solo.ckpool.org and utilizes connected nodes to search for nonce, extranonce2, and ntime combinations that produce a double hash (256) of a block header lower than the target. It's a familiar tale of odds, but despite the slim chances of success, it serves as an excellent benchmarking and stress-testing exercise for this decade-old code. Numerous contributors have pooled their resources, often leveraging solar-powered nodes, in hopes of claiming a share of the rewards should fortune smile upon us 🤞 As is customary with such endeavors, the more nodes involved, the broader the scope of our search. A dedicated git page is here that renders the last status of the search game.

2. Another stress testing endeavor involves trying our luck in Dogecoin / Litecoin mining through the litesolo pool. This process closely resembles the one described above, but instead of double SHA256 hashing, we're employing Scrypt hashing. Given the free time slots in execution caused by the completion of one batch (such as BTC) and the subsequent wait for new mining notifications, we can utilize idling nodes for other tasks. For this purpose, a separate page is hosted here.

3. More to come for sure.

❔ DETAILS of the page

The GridMan GitHub page showcases the latest update of the project's status, providing clarity on several key aspects:

Epoch: Represents the timestamp of the most recent project update.
BatchTasks: Denotes the number of tasks included in the current batch.
BatchTasksCompleted: Indicates the number of tasks completed within the current batch.
TotalBatches: Reflects the total number of batches processed since the last project initialization.
TotalTasksCompleted: Specifies the total count of tasks completed since the project's last initialization.
TaskIterations: Represents the number of combinations attempted per task.
Total Iterations made: Illustrates the cumulative count of combinations processed since the project's last initialization.
Found: Reports the number of block header hashes discovered.

In the context of this lottery, a batch refers to a collection of jobs (tasks) initiated whenever a pool provides a new dataset. Upon receipt of new data, any existing jobs are terminated, and a fresh batch of tasks is distributed containing the latest mining details.

📜 INSIDE

A dump of a task being executed on one of the nodes:

2024-05-01 15:03:30 [INF] Accepted and Starting Task 6051 Binary size 51952 Payload size 1588
2024-05-01 15:03:30 [INF] Starting binary GM_1714469720bin with argument GM_1714469720payload
Started with payload: /tmp/GM_1714469720payload
[INFO] Going 3000000 combinations, fingers crossed.
[INFO] We're doing 309717 combinations per second
[INFO] We're doing 562883 combinations per second
[INFO] We're doing 500924 combinations per second
[INFO] We're doing 499022 combinations per second
[INFO] We're doing 497139 combinations per second
[INFO] We're doing 502230 combinations per second
2024-05-01 15:03:42 [INF] Task Completed with code 0
2024-05-01 15:03:42 [INF] Finished Task
2024-05-01 15:03:42 [INF] Sending Payload back to Server