pull down to refresh

Priya Rani wroter an earlier article about how transactions get confirmed in Braidpool #1524022 and here they describe their attempts to build a dashboard that will find whatever mining device you have running connected to your network, pull its telemetry, and show it without the user typing in IP addresses, model numbers, or API ports. Same experience, every user, every device.

I’ve spent the last year and a half contributing to Braidpool under the mentorship of Bob McElrath. This decentralised, peer-to-peer Bitcoin mining pool replaces the usual centralised pool operator with a DAG of shares shared directly between miners. One of the pieces the project needed was simple to describe and stubborn to build: a dashboard that shows a miner’s own device analytics, hashrate, temperature, fan speed, and firmware version, and that works the same way for every user, on every device, with as little manual setup as possible.

Priya describes several different approaches to making this work, including adventures with pyasic:

The next stop was pyasic, a Python library built specifically to provide a single, standardised async interface across many different ASIC brands and firmwares, such as Antminer, WhatsMiner, Innosilicon, Avalon, and others, communicating with them through their native APIs or SSH instead of making the caller learn every miner’s dialect.

I really enjoy these Bitshala articles because inevitably I learn about something I had never heard of before. Today it was pyasic.

Priya didn't end up using pyasic, but did end up building a dashboard that searches for and finds your mining equipment and hooks it up.

I'm gonna get Bob McElrath on here for a AMA one of these days.

Discovery beats registration. Asking users or devices to announce themselves (attempt 1) puts the integration burden on the wrong side. Scanning for what’s already there (attempt 3) puts it where it belongs on the software that’s supposed to be doing the work.

If you can authenticate the device, before you authenticate to the device, yes. Can you though?

Kind opti promises to remove that esp32 that listens for 0.0.0.0:80/cgi-bin/get_system_info.cgi from your network and delete these basic auth credential logs.

reply