Blockle 0.2.10 — mining compatibility fixes (Bitaxe + Namecoin merge pools)

Blockle 0.2.10 — mining compatibility fixes (Bitaxe + Namecoin merge pools)

Two fixes from a Bitaxe (BM1370) operator's bug report. Node/pool operators should update; the consensus change (2) means all nodes should run ≥0.1.4.

1. Direct stratum no longer crashes ASIC firmware

The v0.2.6 "job on subscribe" change sent mining.set_difficulty + mining.notify before the mining.subscribe reply, so a miner received a job with no extranonce1 and rebooted (same inversion on authorize). The node now sends the subscribe/authorize reply first, then the work — standard stratum order — while keeping the subscribe-and-wait behavior MiningRigRentals needs. Bitaxes and other ASICs connect cleanly on the direct pools (:3340–:3347 solo, :3360–:3367 PPLNS).

2. Accepts Namecoin-style (byte-reversed) aux commitments

check_aux_pow previously compared the folded header hash only against the aux root exactly as written after fabe6d6d. Standard multi-coin merge pools (Myriad, Doichain, Syscoin, Unobtanium…) write that root byte-reversed (uint256 display order). BLOCK now accepts either orientation, so an existing multi-coin pool can add BLOCK at chain id 16972 with its normal coinbase. (Consensus relaxation; our own pools are unchanged.)

Crates: blockle 0.2.10 / chain workspace 0.1.4 on crates.io.

Downloads

platform	wallet	CLI tools
Linux x86_64	BlockleWallet-linux-x86_64.zip	blockle-binaries-linux-x86_64.zip
Windows x64	BlockleWallet-windows-x86_64.zip	blockle-binaries-windows-x86_64.zip
macOS (Apple Silicon)	BlockleWallet-macos-arm64.zip	blockle-binaries-macos-arm64.zip

Blockle 0.2.9 — chain-stall fix finalized

Blockle 0.2.9 — chain-stall fix finalized (fast difficulty recovery)

Required update. It changes consensus from block height 360: older nodes/wallets will reject blocks past 360 and stop following the chain.

Why another release

0.2.7/0.2.8 added a quiet-lane difficulty decay and a miner that rebuilds its template so the decay actually applies to a solo miner. But the fast-recovery schedule was gated at height 400, and the chain stalled at 359 before reaching it — so it fell back to the slow schedule (~3.3 h grace) and took hours to recover.

The fix

• Fast decay now activates at height 360 (the first block after the stall), not 400.
• The fast schedule is aggressive: grace of one block interval (~10 min), difficulty halving every ~2 min, so a lane that outruns its hashrate recovers within an hour from any overshoot — in practice a quiet lane never freezes for more than a few minutes.
• Blocks below 360 keep validating under the schedule they were mined with.

Crates: blockle 0.2.9 / chain workspace 0.1.3 on crates.io.

Downloads

platform	wallet	CLI tools
Linux x86_64	BlockleWallet-linux-x86_64.zip	blockle-binaries-linux-x86_64.zip
Windows x64	BlockleWallet-windows-x86_64.zip	blockle-binaries-windows-x86_64.zip
macOS (Apple Silicon)	BlockleWallet-macos-arm64.zip	blockle-binaries-macos-arm64.zip

macOS builds are Apple Silicon only and signed ad-hoc; if macOS says "damaged," clear quarantine: xattr -dr com.apple.quarantine /Applications/BlockleWallet.app.

Blockle 0.2.8 — chain-stall fix (miner refresh + faster recovery)

Blockle 0.2.8 — chain-stall fix (miner template refresh + faster difficulty recovery)

Required update. It carries a consensus change that activates at block height 400. Nodes/wallets older than 0.2.8 will reject blocks from 400 onward and stop following the chain.

What happened

0.2.7 added a quiet-lane difficulty decay, but it was inert for a lone miner: the node's miner only rebuilt its block template when the chain tip changed. With no other miners, the tip never moved, so it ground a single stale template forever — never picking up the decayed (lower) difficulty. The chain stalled for hours even though the target had already decayed to near-minimum.

The fix

• Miner rebuilds its template every 15s (not only on a tip change), so the time-based decay actually takes effect for a solo miner.
• Faster "v2" decay schedule — grace of two block intervals, difficulty halving every half-interval (~20 min / 5 min on mainnet, vs the earlier 3.3 h / 10 min). A quiet lane now recovers in minutes. Gated at height 400 so blocks already mined under the earlier schedule keep validating.

Crates bumped to blockle 0.2.8 / chain workspace 0.1.2 on crates.io.

Downloads

platform	wallet	CLI tools
Linux x86_64	BlockleWallet-linux-x86_64.zip	blockle-binaries-linux-x86_64.zip
Windows x64	BlockleWallet-windows-x86_64.zip	blockle-binaries-windows-x86_64.zip
macOS (Apple Silicon)	BlockleWallet-macos-arm64.zip	blockle-binaries-macos-arm64.zip

macOS builds are Apple Silicon only and signed ad-hoc; if macOS says "damaged," clear quarantine: xattr -dr com.apple.quarantine /Applications/BlockleWallet.app.

Blockle 0.2.7 — the chain can't stall (quiet-lane difficulty decay)

Blockle 0.2.7 — the chain can't stall (quiet-lane difficulty decay)

This is a required update. It introduces a consensus rule that activates at block height 298. Older nodes/wallets will reject blocks from 298 onward and stop syncing — update to keep following the chain.

Why

When a mining lane's hashrate spikes and then leaves, LWMA can't retarget the difficulty back down — it only adjusts when a block is found. With no hashrate left at that difficulty, the lane (and with it the whole chain) freezes. This happened on mainnet: every lane went quiet and no block was produced for ~10 hours.

The fix

A time-based difficulty decay for quiet lanes. Once a lane has been silent past a grace window (2× its target spacing), the difficulty it demands of the next block halves once per target block-interval of overdue time, down to the minimum if needed. That caps the practical time between blocks: a lane that loses its hashrate always becomes mineable again instead of stalling the chain.

• Keys off the block's own timestamp, which consensus already bounds by median-time-past and the 2-hour future-drift cap, so it can't be gamed to force difficulty down faster than real elapsed time.
• Enforced from decay_activation_height (mainnet 298); all prior history validates unchanged.
• New unit + integration tests cover the decay, the grace window, and the pow-limit cap.

Also in this release: per-lane algorithm reporting so the pool site groups pools by their true algorithm, and the Rust crates are bumped (blockle 0.2.7, chain workspace 0.1.1 on crates.io).

Downloads

platform	wallet	CLI tools
Linux x86_64	BlockleWallet-linux-x86_64.zip	blockle-binaries-linux-x86_64.zip
Windows x64	BlockleWallet-windows-x86_64.zip	blockle-binaries-windows-x86_64.zip
macOS (Apple Silicon)	BlockleWallet-macos-arm64.zip	blockle-binaries-macos-arm64.zip

macOS builds are Apple Silicon only and are signed ad-hoc (not notarised) — if macOS says the app is "damaged," clear the quarantine flag: xattr -dr com.apple.quarantine /Applications/BlockleWallet.app.

Blockle 0.2.6 — sync fix (critical) + MiningRigRentals support

CRITICAL: fixes wallets/nodes that stopped syncing once the chain contained merged-mined blocks. Headers-first sync was running a native Equihash check on every header, but merged (AuxPoW) blocks carry their proof in the body — so the first sha256d block stalled all syncing. If your wallet froze, update to this build and it will resume to tip. Also adds MiningRigRentals/pool-validator compatibility (jobs on subscribe, tolerant authorize). Recommended for everyone.

Blockle 0.2.5 — ASIC-firmware-compatible mining

Validated against live SHA-256 ASIC hardware (Bitaxe BM1370 / ESP-Miner). Fixes real-firmware mining: per-algorithm share-difficulty floors, BIP-310 version-rolling negotiation, and correct submit-time version application — sha256d share acceptance went from ~0% to 100% at multi-TH/s on real hardware. Plus the P2P hygiene from 0.2.4. Recommended for anyone running a pool node.

Blockle 0.2.4 — P2P hygiene

Clean peer discovery for the now-live network: dial logs fire once per real dial instead of flooding every tick, loopback/wildcard addresses are never gossiped or dialed (nodes could previously connect to themselves via gossiped 127.0.0.1), and a route-probe guard stops a node dialing its own public address. Fully wire-compatible with 0.2.3 peers. Recommended update for everyone running a wallet or node.

Blockle 0.2.3 — 18 pools, deep explorer, maturity-aware wallet

Solo AND PPLNS pools for every ASIC algorithm (18 endpoints, 1% fee), the in-depth BLOCK explorer (block/tx/address pages + search, served live by the node), maturity-aware wallet balances (Spendable vs Immature tiles; clear coinbase-maturity errors), P2P dial dedupe (no more duplicate seed connections), basic-auth RPC + multi-algo share validation for parent pools, and per-pool mining pages with live miner lookup at blockle.org/mine.

Blockle 0.2.2 — full wallet management

Everything you expect from a Bitcoin Core wallet, on post-quantum keys: passphrase encryption (scrypt + ChaCha20-Poly1305; locked wallets still receive and render), unlock-for-session, change-passphrase, wallet backup, portable key export/import, and message signing/verification — in the CLI (blockle-chain wallet …) and in the Qt wallet's new Wallet tab. Also hardens concurrent wallet access (atomic writes) and headless passphrase handling.

Blockle 0.2.1 — wallet bundle fixes

Fixes the Windows wallet bundle (BinaryNotFound on launch: the bundled blockle-chain.exe wasn't found by the resolver) and gives the packaged apps the Blockle logo as their executable icon on Windows and macOS. All ten BLOCK pools (Equihash solo/PPLNS + eight per-algorithm direct pools) and the aux-work merged-mining interface from 0.2.0 are included.