Repository navigation
Release v1.4.1-DIMEBAG of midwimble.
A hard fork that replaces v1.4.0-DIMEBAG's rule at the same height. From
block 50,000 an over-cap block is still invalid, but the cap now keeps the
chain moving at full pace: a bond's signature leaves its window a day after
its block, and the cap is shared among the bonds actually signing rather
than every registered one. Without these, idle bonds could stop the chain,
and on mainnet as it stands they would have, within an hour of the height.
Every node must upgrade before block 50,000, not only miners and pools.
It is expected around 18 November 2026 UTC, depending on block times.
v1.4.0-DIMEBAG and every older release reject blocks this rule accepts, so a
node on any of them leaves the network the first time one is mined.
What changes
- The window ages by time from 50,000. A signed block is invalid when its
bond has signed more than its cap of its window: the last 1,440 blocks, this
one included, less any stamped 86,400 seconds (a day) or more before it
(CAP_WINDOW_SECS). While blocks come at least once a minute this is
exactly the 1,440-block count; it differs only when they come slower. - The cap is shared among the bonds in use from 50,000. The cap is
ceil(1440 / bonds in use), at least 4, where a bond is in use when it is
eligible and signed at least one of the 1,439 blocks before the one being
judged. Bonds that are registered but not signing no longer lower anyone's
cap. It is the same whoever signs the block, and never lower than v1.4.0's
cap. - Why. v1.4.0 divides the window by every eligible bond, mining or not.
When the bonds actually mining cannot cover 1,440 blocks between them, they
all reach their caps, no valid block can be built, and a window counted in
blocks never moves again. At height 42,881, 36 bonds were eligible (a cap of
40) and 4 of them, eligible until about 31 December, had stopped signing
around block 38,900: 32 x 40 = 1,280. v1.4.0 would have stopped the chain
shortly after 50,000 for about six weeks. With the aging alone the chain
would run at 1,280 blocks a day; with the cap shared among the 32 bonds in
use (45 each), it runs at 1,440. - Both are needed. A bond that stops mining stays in use until its last
block leaves the window, which only new blocks can make happen; the aging
is what lets the others sign those blocks. - Weight and pay follow the same count. A valid block counts in full and
mints the whole reward. - The window comes from the headers, which carry every block's signer and
timestamp: storage, snapshots and headers-first sync need nothing new. - Nothing below 50,000 changes, and neither do
CAP_WINDOW(1,440) or
CAP_K(360).
Mining
- A bond at its cap can sign again once its oldest blocks in the window
are a day older than the block it would sign, once other blocks have
pushed them out of the last 1,440, or once other bonds' last blocks have
left the window and the cap has risen. Templates work this out at their own
timestamp, and the error says so when no bond can sign yet. - Idle bonds cost nobody anything. A bond you stop mining with keeps a
share of the window until its last block leaves it, a day at most on
schedule. - A bond that signs now and then still costs the network quota: one block
in every 1,440 keeps it in use, holding a full share of the window that it
barely uses.
Also in this release
GET /bondsreportsover_cap_window_secs, the next block'ssigner_cap
andbonds_in_use. The explorer'swindow_signedis what each bond has
used of the next block's window, aged as the cap counts it, and its window
shows the cap the next block faces within_useandeligible.
midwimble paramsprints the day limit and the share among bonds in use.midwimble --versionprints1.4.1-DIMEBAG.
Upgrading
- Every node: upgrade before block 50,000. v1.4.0-DIMEBAG is not enough.
- Miners: register bonds for your hashrate, about
360 xyour share.
Details: docs/OVER_CAP_INVALID.md, "Why the window also ages by time" and
"Why the cap is shared among the bonds in use".
Built --release --features webrtc,gpu from commit bef880e0dd0148c666f9b5dadaed7e1465d41a45. Each archive holds one midwimble binary — node, wallet, pool, merged miner and anchoring — with LICENSE and README.
| Download | Platform |
|---|---|
midwimble-v1.4.1-DIMEBAG-x86_64-unknown-linux-gnu.tar.gz |
Linux x86-64 |
midwimble-v1.4.1-DIMEBAG-aarch64-unknown-linux-gnu.tar.gz |
Linux ARM64 — Raspberry Pi 3 / 4 / 5 on a 64-bit OS |
midwimble-v1.4.1-DIMEBAG-x86_64-apple-darwin.tar.gz |
macOS (Intel) |
midwimble-v1.4.1-DIMEBAG-aarch64-apple-darwin.tar.gz |
macOS (Apple Silicon) |
midwimble-v1.4.1-DIMEBAG-x86_64-pc-windows-msvc.zip |
Windows x64 |
midwimble-v1.4.1-DIMEBAG-aarch64-pc-windows-msvc.zip |
Windows on ARM |
Verify with sha256sum -c SHA256SUMS.txt (checksums attached).