Keep the history. Remove the bottleneck.

What changes in 30.1.5.1

These are bounded capacity improvements—not unlimited wallet scale. Independent scan limits can still refuse oversized or ambiguous work. No partial scan authorizes spending, and no hashrate, reward, or earnings outcome is guaranteed.

Read the reviewed 30.1.5.1 candidate notes · Follow release qualification in PR #57

The 30.1.5 improvements it builds on

• Same-anchor claim continuation. The miner can wait for a live claim, relay eligible retained bytes, or refresh an authenticated family on its existing anchor. Expiry does not release a reserved anchor just because the local mempool no longer contains its claim.
• Explicit signing authority. A locked or staking-only wallet cannot sign Gold Rush PoW claims. Manual lock, timed relock, and scope changes stop signing authority; normal unlock is required to resume that work.
• Clearer recovery controls. Manual fee-paying conflict recovery uses an exact reviewed plan and explicit acknowledgement. Automatic fee-paying recovery remains off by default and needs bounded operator authorization.
• Typed mining status. Inspect getpowmininginfo for the actual mining gate. A safe wait or relay can report zero instantaneous hashrate; raw historical quarantine counts are not a health verdict.
• Durable, inspectable history. Recovery pagination, authorization receipts, relay revocation, and wallet-load synchronization improve operator visibility without dropping retained claims.

Published 30.1.5 release notes and full authority boundaries →

A safe upgrade, in order

1. Wait for your platform's published artifact. Use the release catalog, not an unpublished build, local canary, or guessed download URL. Check the tag and exact SOURCE_COMMIT.txt.
2. Back up first. Preserve wallet backups and take a cold datadir copy after a clean shutdown. Quantum ML-DSA keys are non-HD: a seed alone does not recover newly generated quantum keys.
3. Verify the package. Match SHA256SUMS.txt, source commit/tag signatures, provenance, SBOM, and the release's platform-signing notice. A signed Git source object is not an OS-signed application.
4. Replace executables with the node stopped. Preserve the existing wallet, datadir, configuration, and permissions. Never run two versions against one datadir. The version change alone does not require a rewind, wallet recreation, or reindex.
5. Check the actual running build and state. Inspect getnetworkinfo, getblockchaininfo, getstakinginfo, and, if used, getpowmininginfo. Require the intended network, synchronized tip, appropriate unlock scope, and the expected typed mining state.
6. Keep rollback state. Follow the release's reviewed rollback procedure and preserve post-upgrade wallet/chain history. An older binary can be data-compatible yet lack the new claim-continuation behavior.

Version identity and what does not change

The display and package version is 30.1.5.1, while numeric CLIENT_VERSION remains 300105. Do not use that integer alone to distinguish 30.1.5 from 30.1.5.1; verify the full displayed version and exact source identity. On macOS the numeric short version is 30.1.5, the bundle version is 30.1.501, and the full version is 30.1.5.1.

This maintenance release changes no consensus rule, network protocol, reward amount, activation height, wallet format, or chainstate format. The height-governed lifecycle and live halving countdown remain separate from software release milestones.

Windows packages are not Authenticode-signed. macOS apps use ad-hoc signatures, not Apple Developer ID signatures or notarization. Verify the exact published notices before launch; these artifacts do not carry an independent security certification.