BDLMiner 2.4.2

BDLMiner V2 2.4.2

Pool statistics and Bitaxe Gamma 601 fixes; settings, pool profiles and mining kernels
are otherwise unchanged from 2.4.1.

• public-pool statistics are back on the dashboard. public-pool.io now serves its
  statistics API (port 40557) over TLS 1.3 only, which the firmware's TLS (1.2)
  cannot use, so Seen by the pool fell back to an estimate. When the miner finds no
  statistics API, the dashboard now asks https://<pool host>:40557/api/client/<address>
  itself, from your browser, at most every 10 minutes, and shows the pool's figures
  marked read by this browser. Only the address is sent, not the worker name. The
  figures appear while the dashboard is open; the miner's screen keeps the estimate.

• No more statistics searches at every share. A fruitless search for the pool's
  API ran again after each accepted share. That rule is meant for a pool that only
  publishes an address after its first share; a Gamma finds shares every minute, so
  all ten probes ran again every 30 minutes. It now follows only a search that found
  an API not knowing the address yet (HTTP 404); other failures wait 6 hours.

• The log says why. Each failed statistics probe is logged with its cause (TLS
  error, HTTP status, timeout), and a pool refusing TLS 1.2 is named as such.

• Bitaxe Gamma 601: core voltage setting and ESP-Miner frequencies. The firmware
  kept the core at 1150 mV for every profile up to 800 MHz, while ESP-Miner raises the
  voltage with the frequency and stops its presets at 690 MHz: a Gamma at 600 MHz and
  1150 mV fell back to 525 MHz. Settings › Safety now offers the core voltage among
  ESP-Miner's BM1370 values (1000, 1060, 1100, 1150 stock, 1200, 1250 mV) and
  frequencies from 525 to 675 MHz in 25 MHz steps, plus 690 MHz. A profile above 690 MHz
  saved earlier returns to 525 MHz. The core-voltage safety stop now follows the chosen
  voltage (0.15 V below to 0.10 V above; unchanged at 1150 mV). More voltage means more
  heat and power: raise it in small steps and watch the temperature.

• Bitaxe Gamma 601: the 525 MHz fallback survives restarts. A higher profile that
  failed fell back to 525 MHz until the next reboot only, so every restart, update or
  power cut went back to the failing profile. The fallback is now kept, with its
  reason, while that profile and voltage stay selected; choosing another frequency or
  voltage clears it.

• ESP32-S3 boards: faster hardware SHA loop. On the S3 every register access
  crosses a slow peripheral bus. Following NerdMiner Modded (MIT), the next header block
  is now written while the engine computes the second hash, and only the words that
  change: NerdMiner Modded measured about 324 instead of 222 kH/s on its S3 loop. At
  boot the miner checks every digest and the exact set of hits against software, then
  times it against the existing kernels and keeps it only if faster; an engine that
  does not behave falls back to them. Not yet measured on our S3 boards (M5Stack S3,
  T-Display-S3, headless S3).

Validation

Browser regressions cover the dashboard's own request to public-pool, its tile, and
its absence when the miner reads the API, and the frequency and voltage menus; host
regressions cover each core voltage written to the regulator, the safety window that
follows it, the new profile list, and the fallback kept across a restart and cleared by
another profile or voltage, with all host, browser and board builds. The voltage
setting follows ESP-Miner's values and has not been tried on a physical Gamma. The public-pool request was checked against a simulated answer, not the live
API. No physical board was used for this validation.

What's Changed

• 2.4.2: public-pool stats via the browser, Gamma core voltage and ESP-Miner frequencies by @bdlglua in #21
• 2.4.2: faster ESP32-S3 SHA loop, after NerdMiner Modded by @bdlglua in #22

Full Changelog: v2.4.1...v2.4.2