• v1.34.0 9b3c13f682

    v1.34.0
    All checks were successful
    Release / Docker Multi-Arch (push) Successful in 22m31s
    Release / Binary aarch64-unknown-linux-gnu (push) Successful in 11m22s
    Release / Binary x86_64-unknown-linux-gnu (push) Successful in 10m6s
    CI / Rust clippy (push) Successful in 1m48s
    CI / Rust fmt (push) Successful in 1m12s
    CI / Rust test (push) Successful in 5m48s
    CI / UI (SvelteKit) (push) Successful in 1m15s
    CI / Security Audit (push) Successful in 1m21s
    docs / build (push) Successful in 37s
    Release / Linux .deb + .rpm (amd64) (push) Successful in 2m0s
    Release / Linux .deb + .rpm (arm64) (push) Successful in 1m51s
    Release / Linux AppImage (aarch64) (push) Successful in 28s
    Release / Linux AppImage (x86_64) (push) Successful in 27s
    Release / Cosign sign artifacts (push) Successful in 25s
    Release / Forgejo Release (push) Successful in 37s
    Stable

    dvb-projekt released this 2026-09-27 12:10:44 +00:00 | 209 commits to main since this release

    Fixed

    • dvb-WarpTune energy mode: without the pool's energy feed a miner holds
      Eco, not Balanced — at a service start until the first reading, and
      when the feed goes stale. Without a reading the tariff may be the
      grid's; Balanced has no Eco cap, and after a start on 2026-09-27 an
      Avalon Q stepped up to Standard (~1370 W) in the three minutes before
      the feed arrived. The provisional start while surplus entry is being
      debounced is Eco as well.
    • dvb-WarpTune: a device that says its chips are off is held, not judged.
      The WarpAxe firmware can switch the chips off from its UI and reports it
      (shutdown, chainStopped, chainPhase other than READY); the zero
      draw and 0 mV core output looked exactly like a dead chip, which marks
      the step and everything above it for an hour and steps down. While any
      of these signals, overheat mode, a fault flag or a mining pause is set,
      nothing is marked or written, and once the device hashes again the
      point is judged from scratch. A chain in FAILED is not a stop on
      purpose and stays with the dead-chip guard, whose restart recovers it.
    • dvb-WarpTune on the Avalon Q: a work-mode switch is written as
      ascset|0,workmode,set,<n>. The MM firmware takes a verb after
      workmode (get reads, set writes) and refused the bare
      0,workmode,<n> with "workmode unknown argument", so no live switch
      had ever reached the device. Found on the first live write, 2026-09-26.
    • Stratum V1 and Sv2: a share on a job from before a block change is
      checked and booked for 60 s instead of being rejected as stale. A miner
      finishes the work it holds when the new block's notify arrives and hands
      in the results a few seconds later; that is real work, and dropping it
      showed up as a steady 1–3 % stale rate (a Bitaxe Gamma: one or two shares
      per block change, 2.7 % over 16 h). A block solution on such a job still
      goes to the node, which decides between the two blocks. After 60 s the
      job is stale as before. V1's duplicate check no longer resets on a block
      change, so a share handed in before and after the change still counts
      once (the set stays capped).
    • dvb-WarpTune voltage trial: the share vote now reaches back far enough
      to hold the 200 shares a verdict needs. VarDiff keeps every miner near
      four shares a minute, so the 30-minute window topped out around 130 and
      a voltage between 85 and 95 % of the expected rate waited for good (a
      NerdAxe Gaia at 420 MHz / 960 mV, 2026-09-26). The window is 30 minutes
      or 200 shares, whichever reaches further back.
    • dvb-WarpTune voltage trial: the pool's accepted shares decide a voltage
      verdict, not the firmware's hashrate reading. NerdOS does not see an
      undervolted chip: a NerdAxe Gaia read 103 % at 420 MHz / 940 mV and the
      trial walked on to 930 while the pool booked 70 % of the expected rate
      over 1739 shares (2026-09-25); the old rule called a point good when
      either vote said so. Where shares are counted, a voltage is good on 200
      shares at ≥ 95 %, short of good on 200 below it or on 40 when clearly
      short (under 85 %), and the point waits until the shares are in. A miner
      without a share counter is judged on the reading alone, as before.
    • dvb-WarpTune voltage trial: only failures at rising voltages count
      towards "more voltage does not help this frequency". A floor probed
      again is a floor: 930 mV failing three times at 420 MHz marked the
      frequency unstable although 940 and 960 hashed, and the miner spent the
      evening at 400 MHz. A good verdict resets the count.

    Added

    • dvb-WarpTune: dvb-warppool-tune yield --host <miner>, the yield table.
      For every ladder point the miner visited in the last week it lists the
      minutes, the pool's accepted shares and their difficulty (turned into a
      share-derived TH/s with its 1/√shares error), the firmware's expected
      hashrate, the mean draw from the heartbeats and the J/TH — over every
      visit, settle minutes skipped, windows before a device change or a
      start with another chip discarded. Below the table the point each mode
      should run: Max the most hashes, Eco the fewest J/TH, Standard the most
      hashes within 5 % of Eco's efficiency; a point needs --min-shares
      (200) to be picked, and Max says when the runner-up is within the
      error. The regulator's ten-minute judge is a safety net, not a way to
      tell 700 MHz at 1210 mV from 700 MHz at 1160 mV; the first run on the
      Octaxe did (26 665 shares: 11.62 TH/s at 1210, 102 % of expected).
      --json for scripts.

    dvb-WarpPool v1.34.0 — Downloads

    Docker

    git.warppool.org/dvb-projekt/dvb-warppool:v1.34.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