v1.1.2-WONKABURN

Release v1.1.2-WONKABURN of midwimble.

⚠️ Mandatory upgrade before 2026-10-31 00:00 UTC. This release changes consensus at the mainnet switch. Every node — bond holders, pools, explorers, gateways — must run it by then, or it will reject tapered blocks and fork off on the old rules. v1.1-WONKABURN and v1.1.1-WONKABURN are superseded: do not run them.

🔁 Re-cut 2026-10-28. The archives first published under this tag, built from 73f395a, also widened the fork-choice cap windows — CAP_WINDOW to a week and CAP_K to 720. Those windows are not gated on the block timestamp, so changing them re-weighs every block already on the chain: a node running that build rejected the live chain at its own tip and banned its peers. The change has been reverted and the windows now match v1.1.1 exactly. If you downloaded this release before 2026-10-28, replace your binary and check it against the checksums below.

What changes

Over-cap reward taper (from 2026-10-31 00:00 UTC)

• A bond that has signed n of the last 1,440 blocks against a cap of cap mints only reward × cap / n of a block's subsidy, rounded down. Fees are always paid in full.
• What the taper withholds is never minted by anyone. It is a burn, not a redistribution, so the scheduled supply is now a ceiling the real supply sits under.
• Earning the full reward means spreading hashrate over enough bonds. A producer with a share s of the hashrate needs about 360 × s of them — and a margin above that is worth buying, because over a 1,440-block window a producer bonded exactly at its floor gives up part of its pay to ordinary luck. Roughly 15–20% more bonds covers it.
• Blocks past the cap stay valid but add only 1/1024 of their work to fork choice. While fewer than 360 bonds are eligible, they share the window equally.
• Nodes record what each block actually minted. The explorer shows minted and withheld amounts per block, a mints column on the bonds page, and supply as minted vs withheld.

Bond-size retarget (from 2026-11-30 00:00 UTC)

• What a new bond must lock follows midwimble's own difficulty. It doubles for every 16-fold rise in midwimble's work since genesis, from 128 gMDS up to a ceiling of 512 gMDS. There is no oracle; it reads the chain's own target.
• It applies to registrations only. A bond already registered keeps the price it registered at until its lock ends, so nothing is stranded.
• midwimble bond register checks the chain's current figure before you lock. /bonds and the explorer show the current minimum, the floor and the ceiling.

Smaller fixes

• Bond amounts in the explorer are shown in gMDS.
• CLI and docs wording updated for the new rules.

The cap windows are unchanged from v1.1.1, so fork choice weighs the existing chain exactly as it did before. No new snapshot format and no change to the bond set's leaf.

Upgrade

1. Stop your node: systemctl stop midwimble (or however you run it).
2. Back up the old binary, then swap in the new one from the archive below.
3. Start it and check the logs. After the switch, your bond's mints column on the explorer should read below 100% only if you're over your cap.

Downloads

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

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

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