• v1.39.0 6aca39cc79

    v1.39.0
    All checks were successful
    CI / Rust clippy (push) Successful in 2m27s
    CI / Rust fmt (push) Successful in 1m19s
    CI / Rust test (push) Successful in 8m8s
    CI / UI (SvelteKit) (push) Successful in 1m22s
    CI / Security Audit (push) Successful in 1m25s
    Release / Docker Multi-Arch (push) Successful in 31m15s
    Release / Binary aarch64-unknown-linux-gnu (push) Successful in 14m8s
    Release / Binary x86_64-unknown-linux-gnu (push) Successful in 12m41s
    docs / build (push) Successful in 34s
    Release / Linux .deb + .rpm (amd64) (push) Successful in 2m10s
    Release / Linux .deb + .rpm (arm64) (push) Successful in 1m54s
    Release / Linux AppImage (aarch64) (push) Successful in 23s
    Release / Linux AppImage (x86_64) (push) Successful in 23s
    Release / Cosign sign artifacts (push) Successful in 27s
    Release / Forgejo Release (push) Successful in 35s
    Stable

    dvb-projekt released this 2026-10-10 15:55:42 +00:00 | 14 commits to main since this release

    Fixed

    • WarpTune: the voltage trial no longer ratchets a voltage up on noise. A
      share vote short of the bar by less than its own noise on the double
      window counts as a deficit only when the chip error rate on the point rose
      by more than one point over the point's baseline (the error rate of its
      last good verdict, or of the next voltage up at that clock) — with the
      chip error trigger off as well. With flat errors and no second witness the
      verdict is "noise, not a deficit": the point is good, the trial goes on
      down toward the lowest good voltage, and a calibrated voltage raised in
      operation steps back on such a vote as on a healthy one. Where the firmware
      reports no error rate, or no baseline is known, the double window decides
      as before. (NerdQAxe++ 2026-10-07 → 10-10: Eco 600 MHz walked 1140 → 1240
      mV in 10 mV steps on votes of 95 % over 400 at a flat 0.2 % error rate,
      +18 % power.) The baselines are read back from the journal at a start.

    Added

    • Devices: WarpTune vs. hand point — a tile above the device cards and a
      line on every WarpTune card show what the Eco setting saves (watts) and
      what the Max setting adds (hashrate) against each miner's hand point: the
      point it would run without WarpTune (stock in warptune.toml, or the point
      seen at the first start). Measured, not modelled: watts from the miner's
      own readings, hashrate from the pool's accepted shares, over every stay on
      the point in the last seven days (dvb-warppool-tune yield's table). A
      point counts from 200 shares and 30 minutes; below that the card says "not
      enough data" with the counts. A point the miner no longer visits (a hand
      point replaced by its calibrated voltage) is estimated from the
      best-measured point at the same clock, power by V², and marked "≈". The
      tooltip carries the hand point, "(= factory setting)" when it is the
      maker's default, the measurement behind each figure (shares, minutes, last
      stay) and the method; "±" is the share noise. The Avalon Q's work modes are
      named as such; work-mode miners are left out of the tile's percentages
      (their kilowatt would dominate them) but stay in its watt and hashrate
      sums, and the tile names the miner left out. Watts and hashrate only — no
      kWh or money figure. The sidecar (savings on the snapshot) recomputes
      every 30 minutes on its own task (a failed run keeps the last figures,
      shows the error and retries after five minutes); no change to
      warptune.toml is needed.

    dvb-WarpPool v1.39.0 — Downloads

    Docker

    git.warppool.org/dvb-projekt/dvb-warppool:v1.39.0 (multi-arch amd64+arm64, ohne v-Präfix)

    Native packages

    • Linux .deb: amd64 + arm64 → apt install ./dvb-warppool_*.deb
    • Linux .rpm: amd64 + arm64 → dnf install ./dvb-warppool-*.rpm
    • Linux AppImage: x86_64 + aarch64 portable
    • Linux tarballs: x86_64 + aarch64 for manual installs
    • macOS .dmg: added shortly after publish (built separately) — or build from source
    • Windows .msi: paused since the forge migration (no Windows runner yet)

    Signatures

    • SHA256SUMS + cosign bundle (SHA256SUMS.bundle, project key)
    • SBOM (SPDX) for all dependencies

    Verify (project public key cosign.pub in the repo root):

    cosign verify-blob \
      --key cosign.pub \
      --bundle SHA256SUMS.bundle \
      SHA256SUMS
    sha256sum --check SHA256SUMS
    

    First-time setup: run dvb-warppool-setup for the first-run wizard.

    Downloads