BLACKCOIN PROTOCOL V4
v30.1.1 Hardening Update | Alpha 1 Controlled Test Staking & Mining | Beta Integration Draft
STATUS — 15 JULY 2026 UTC
Blackcoin-Dev tagged v30.1.0 on 5 July 2026. That tag defines Gold Rush reward accounting from height 5,950,000. Subsequent field use and the public roadmap recorded material consensus, wallet, lifecycle, recovery, accounting, and operability defects in v30.1.0.
v30.1.1 is the hardening release built around those findings. Alpha 1 is available as an unsigned, unnotarized, pre-boundary controlled-testing canary. It is not a production release or a fleet-upgrade recommendation. Beta has not been released. A final v30.1.1 is planned only after its exact-source candidate completes the required P0/P1, platform, reproducibility, signing, canary, and rollback gates.
RELEASE SEQUENCEFIRST GOLD RUSH REWARD HALVING — LIVE COUNTDOWN SNAPSHOTThe Alpha 1 source fixes the first shadow-reward halving at height
5,993,200: the 5,950,000 start plus the 43,200-block interval. At the public base-chain explorer height of
5,953,282 checked at 05:03 UTC on 15 July,
39,918 blocks remained. At the source-defined 64-second target spacing, that is approximately
29.6 days—roughly 13–14 August if target pace holds. Actual time varies with chain pace; refresh the explorer height immediately before relying on the estimate.
Live base-chain height:
https://chainz.cryptoid.info/blk/Tag-specific schedule source:
https://github.com/Blackcoin-Dev/Blackcoin/blob/v30.1.1-alpha1/src/shadow.hCURRENT RECOMMENDATIONThis post does not recommend a new v30.1.0 production deployment or unrestricted Alpha use.
- Ordinary users: wait for the signed final v30.1.1. Qualified testers may use only a published canary under its exact tagged release instructions.
- Existing v30.1.0 operators: preserve every wallet and a cold copy of the complete datadir; do not use migratetoquantum to move ordinary value; do not treat Alpha as a fleet fix; monitor the tagged releases and roadmap for exact-version instructions.
- Alpha testers: qualified experimenters may test stake and test mine now using one isolated node with a nonessential/test-value wallet, no fleet rollout, and the complete tagged release notes linked below.
WHAT GOLD RUSH ACCOUNTING MEANSProtocol V4 records additional shadow-ledger state from base-chain transactions. Gold Rush shadow credits are synthetic, non-Merkle, phase-locked, and not ordinary spendable base-layer outputs during Gold Rush. Unmodified legacy software does not calculate that additional state. The repository does not document a completed exchange integration; do not assume exchange support.
The project targets continuity with existing Blackcoin base-chain history, but compatibility is an exact-client, exact-source, exact-fixture claim. Issue #20 records four confirmed v30.1.0 base-block split paths involving marker-shaped outputs, OP_NOP4/OP_ISCOINSTAKE semantics, STRICTENC treatment, and historical fee allowance. That gate remains open. Alpha fixtures cover the tested cases only; no blanket v30.1.0 or Alpha compatibility guarantee is made.
https://github.com/Blackcoin-Dev/Blackcoin/issues/20ALPHA 1 IMPROVEMENTS AND SCOPEAlpha 1 contains targeted work on staking-index behavior and GUI responsiveness, recovery and journaled reconstruction, transaction-time provenance, claim preservation, identified lock-order inversions, current candidate explorer RPC/index interfaces, and historical-client fixtures.
The exact Alpha audit records only two roadmap issues as fully closed on the Alpha source: #5 for theme readability and #7 for the v30.1.0 ordinary-PoS restriction. In that Alpha source, whitelist checks govern shadow-PoS reward eligibility; they do not govern otherwise-valid ordinary legacy PoS.
Exact Alpha audit:
https://github.com/Blackcoin-Dev/Blackcoin/issues/8#issuecomment-4973767559CONTROLLED TEST STAKING AND MINING ARE OPEN NOWQualified experimenters do not need to wait for final v30.1.1 to help. Alpha 1 is the published controlled-testing lane for test staking and test mining while the remaining release gates are completed. Participation must stay inside the exact Alpha release instructions and the boundary below; it is not a production or fleet rollout.
MANDATORY ALPHA BOUNDARY- Alpha 1 is pre-boundary only. Do not run it at or beyond height 5,993,200. Replace it before that height.
- Do not reopen in v30.1.0 a datadir that processed post-boundary v30.1.1 shadow state. Preserve the cold pre-upgrade datadir copy for rollback.
- Current safety guidance is not to attempt ordinary-value migration during Gold Rush. v30.1.0 can advertise that path, and #14 remains open until candidate creation, relay, mining, and spend-phase gates are proven.
MINIMUM ALPHA CANARY PROCEDUREThe complete tagged release notes control; the following list is only a minimum:
- Stop the existing process cleanly. Back up every wallet and make a cold copy of the complete datadir.
- Use one isolated node with prune=0. Do not perform a fleet rollout.
- Use protected -reindex-chainstate only when complete block history is available; otherwise use a full -reindex.
- Keep staking and mining disabled during reconstruction, then complete the required clean second verification start.
- Use stable power. Do not force-stop or power-cycle Windows during reconstruction and verification.
- Do not use Alpha as a historical explorer with -shadowindex=1.
- Quantum keys are non-HD. Make and verify a new wallet backup after every newly generated quantum key or address.
- Alpha PoW is test-only. After reconstruction and the clean second start, use one thread and 1% CPU, one separate PoW wallet, one confirmed small legacy fee UTXO, and a pre-created payout address included in a fresh verified backup.
- Do not use a high-value or whitelisted PoS wallet for Alpha PoW. Issue #26 remains open: a custom block can confirm a valid later claim that pays a base fee but receives no shadow credit.
Complete procedure and platform limits:
https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.1-alpha1KNOWN OPEN RELEASE GATESAs of 14 July 2026, the repository records these principal open risks and gates:
- Claim accounting — #6 and #26: late or stale QQSPROOF handling can reserve inputs or confirm a fee-paid transaction without granting shadow credit.
- Resource-failure isolation — #12: internal Argon2/resource failures are not yet fully isolated from base-block validity.
- Premature quantum-family funding — #14: current safety guidance is not to attempt ordinary-value migration during Gold Rush. v30.1.0 can advertise that path, and the P0 gate remains open.
- Lifecycle clocks — #16: v30.1.0 height and median-time-past clocks can disagree. Demurrage is not meaningfully active in v30.1.0; it is intended to begin only at the first Final Lockout block, with the grace baseline beginning there.
- Wallet/explorer/index interfaces — #18: stable schema, indexing, and ingestion criteria remain open. Review or prototype against the current candidate interfaces without treating them as stable.
- Base-block compatibility — #20: confirmed v30.1.0 split paths require exact-client regression evidence.
- Quantum-key durability — #23: Alpha has strong partial work, but the exact Alpha audit did not close the end-to-end crash/restore gate; a fresh verified backup remains mandatory.
- Liveness and lock ordering — #25: full cleanup, liveness, and lock-order proof remains open.
Roadmap and all gates:
https://github.com/Blackcoin-Dev/Blackcoin/issues/8POST-QUANTUM SCOPEProtocol V4 implements a migration path using ML-DSA-44, one parameter set standardized in NIST FIPS 204. This is not a claim of FIPS implementation validation or certification. Release safety also depends on dependency provenance, random-number generation, key storage, backup behavior, consensus integration, resource limits, review, testing, and deployment.
VERSIONED PARAMETERS AND EVIDENCEA tag fixes the behavior of that release. Historical base-chain and already-recorded shadow results are not subject to retroactive marketing changes. Any proposed correction at a future boundary must be explicit, prospective, deterministic, and tested; existing reward arithmetic and historical results must remain preserved.
No artifact built from an older source commit is promotable as the final release. Affected evidence must be reevaluated after source changes, and the complete release matrix must pass on the final exact SHA.
WAYS TO PARTICIPATEThere are useful paths for different skill levels, and no purchase is required to contribute:
- Reproduce the exact-source fixtures and report discrepancies.
- Review consensus, wallet, recovery, resource-limit, and lifecycle code.
- Download Alpha 1 and run one qualified, isolated test-staking or test-mining canary under the complete tagged procedure.
- Validate build reproducibility and platform packages.
- Improve operator documentation and rehearse rollback procedures.
- Review or prototype against the current candidate wallet, explorer, and index interfaces without treating them as stable; issue #18 remains open.
- Report ordinary bugs and request a private path for sensitive findings.
Protocol participation routes are distinct. On Alpha 1’s exact source, issue #7 restores otherwise-valid ordinary legacy proof-of-stake. Shadow-PoS reward eligibility remains governed by the fixed historical snapshot; that snapshot is not reopened by this announcement. Proof-of-work is a separate non-whitelist lane. Alpha 1 remains canary-only. These are protocol paths, not an APY, profit, price, or return promise.
REVIEW THE CODE. REPRODUCE THE TESTS. HELP CLOSE THE GATES.The most useful participation now is technical: reproduce exact-source fixtures, review consensus and recovery paths, test isolated canaries, validate platform packages, improve operator documentation, and prototype against the current candidate explorer interfaces without treating them as stable.
Repository:
https://github.com/Blackcoin-Dev/BlackcoinRoadmap:
https://github.com/Blackcoin-Dev/Blackcoin/issues/8Releases:
https://github.com/Blackcoin-Dev/Blackcoin/releasesFor ordinary bugs, use GitHub Issues. For a sensitive report, use the repository’s private advisory flow when available; otherwise open a minimal public issue requesting a private reporting path without disclosing the finding.
