-
v1.16.0
StableAll checks were successfulCI / Rust clippy (push) Successful in 1m28sCI / Rust fmt (push) Successful in 1m2sCI / Rust test (push) Successful in 4m35sCI / UI (SvelteKit) (push) Successful in 56sCI / Security Audit (push) Successful in 1m7sRelease / Docker Multi-Arch (push) Successful in 19m59sRelease / Binary aarch64-unknown-linux-gnu (push) Successful in 10m59sRelease / Binary x86_64-unknown-linux-gnu (push) Successful in 9m50sRelease / Linux .deb + .rpm (amd64) (push) Successful in 10m32sRelease / Linux .deb + .rpm (arm64) (push) Successful in 11m27sRelease / Linux AppImage (aarch64) (push) Successful in 10m43sRelease / Linux AppImage (x86_64) (push) Successful in 9m44sdocs / build (push) Successful in 23sRelease / Cosign sign artifacts (push) Successful in 15sRelease / Forgejo Release (push) Successful in 25sbenches / Criterion benches (push) Benchmarks pass; the upload-artifact step (Forgejo infra) was fixed in benches.ymlreleased this
2026-07-09 20:26:06 +00:00 | 93 commits to main since this releaseAdds an opt-in low-latency block-template source over Bitcoin Core's IPC
interface and hardens concurrent admin config saves. No breaking changes —
GBT remains the default template source, so existing setups are unaffected.Added
- Bitcoin Core IPC template backend (opt-in, Core >= 31). A new
warppool-bitcoin-ipccrate speaks Bitcoin Core's Cap'n Proto mining
interface to pull block templates directly, bypassing the GBT+ZMQ round
trip. A sharedTemplateSourcetrait keeps the GBT and IPC paths
interchangeable. Select it via[node] template_source = "ipc"(default
"gbt") with[node] ipc_socket_pathpointing at Core's-ipcbindUNIX
socket, or from Admin → Bitcoin Core with a live GBT/IPC switch that
probes the socket before committing and fails safe back to GBT if the
socket is unreachable. On Umbrel the Bitcoin app has exposed the IPC socket
since its v1.3.0 (requires Bitcoin Core v31.0). Measured template latency
~5–12 ms (IPC) versus ~90–100 ms (GBT+ZMQ, under Core's ZMQ queue lag).
Fixed
- Concurrent admin config saves no longer lose updates. Overlapping writes
toconfig.tomlfrom the admin API now share a write lock, so two saves
racing at the same time can no longer clobber each other (lost-update race).
Internal
- Deterministic
lowdiff_diagcapture tests (Stratum V1 + V2). The opt-in
low-difficulty diagnostic tests captured tracing output via a thread-local
subscriber, which could be gated out under parallel test load when a
neighbouring test's first-hit callsite registration recomputed the global
tracingmax-level against the (off) global default. The tests now pin the
max-level floor, so they pass deterministically; no production behaviour
changed.
dvb-WarpPool v1.16.0 — Downloads
Docker
git.warppool.org/dvb-projekt/dvb-warppool:v1.16.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.pubin the repo root):cosign verify-blob \ --key cosign.pub \ --bundle SHA256SUMS.bundle \ SHA256SUMS sha256sum --check SHA256SUMSFirst-time setup: run
dvb-warppool-setupfor the first-run wizard.Downloads
-
Source code (ZIP)
2 downloads
-
Source code (TAR.GZ)
1 download
- Bitcoin Core IPC template backend (opt-in, Core >= 31). A new