Skip to content

v1.3.1-DIMEBAG

Choose a tag to compare

View all tags
@github-actions github-actions released this 09 Nov 02:12
v1.3.1-DIMEBAG
c182986

Release v1.3.1-DIMEBAG of midwimble.

Two additions for producers and pools. No consensus change: this is
v1.3-DIMEBAG's chain, with Midstate Walk from block 37,300 and midstate's
from 371,500. Nodes that only follow the chain need not upgrade. A pool
that wants to take co-bonds, or a miner with an NVIDIA GPU, does.

Co-bonds while the node runs

A pool's midwimble blocks count in full only while enough bonds stand behind
its hashrate, so its capacity grows with the co-bonds locked on its mining
key. Until now a co-bond reached a node only as a file loaded at startup, and
its registration proof aged out within a day or two.

A node started with --mining-bond now takes co-bonds while it runs, from no
more than the coin:

  • GET /co-bonds returns the node's mining key, its own bond's id, and its
    co-bonds with their progress.
  • POST /co-bonds takes {script, value, salt} and hands one in.

The node takes only a bond on its own key whose coin is on midstate. The bond
must hold what a new one must, be locked long enough to count, and be within
the one-year horizon. The node then registers it itself, through its
--midstate-rpc, as midwimble bond register would:

  • it takes a proof of the coin;
  • it waits for a day of work above the proof;
  • its next blocks carry the registration;
  • it takes a fresh proof whenever the relay is about to pass the old one.

It signs with each co-bond once it is ready, and keeps them in co-bonds.json
in its data directory. --co-bond files work as before.

The RPC stays loopback-only. midstate pool (v6.4.0) publishes the key and
takes hand-ins at /pool/api/co-bonds, and can pay co-bonders. Midstate's
desktop wallet co-bonds with a pool by its address. See docs/BONDED_POW.md
and docs/POOL_MERGED_MINING.md.

Midstate Walk on NVIDIA GPUs

In a gpu build (the release binaries), the node's miner, pool-mine and
merge-mine mine Midstate Walk on CUDA GPUs, beside the CPU or instead of it:

  • --backend auto|gpu|cpu;
  • MINER_CUDA_DEVICES picks GPUs, and MINER_CUDA_WALKS sizes their batches;
  • gpu-info lists the GPUs and checks each against the known answers.

The NVIDIA driver is loaded when mining starts, so a machine without one mines
on its CPU as before. Every hash a GPU reports is checked on the CPU before it
becomes a share or a block.

Upgrading

  • Pools that merge-mine and want co-bonds: run this release on the
    midwimble node, with --mining-bond and --midstate-rpc, behind
    midstate pool v6.4.0. Keep the node's RPC on loopback.
  • Everyone else: optional. v1.3-DIMEBAG follows the same chain.

Built --release --features webrtc,gpu from commit c182986d57663a6f9cfdfe27dfde03f6dea065a9. Each archive holds one midwimble binary — node, wallet, pool, merged miner and anchoring — with LICENSE and README.

Download Platform
midwimble-v1.3.1-DIMEBAG-x86_64-unknown-linux-gnu.tar.gz Linux x86-64
midwimble-v1.3.1-DIMEBAG-aarch64-unknown-linux-gnu.tar.gz Linux ARM64 — Raspberry Pi 3 / 4 / 5 on a 64-bit OS
midwimble-v1.3.1-DIMEBAG-x86_64-apple-darwin.tar.gz macOS (Intel)
midwimble-v1.3.1-DIMEBAG-aarch64-apple-darwin.tar.gz macOS (Apple Silicon)
midwimble-v1.3.1-DIMEBAG-x86_64-pc-windows-msvc.zip Windows x64
midwimble-v1.3.1-DIMEBAG-aarch64-pc-windows-msvc.zip Windows on ARM

Verify with sha256sum -c SHA256SUMS.txt (checksums attached).

Assets 9
Loading