Skip to content

Blackcoin Core v30.1.1 Beta 1 — WITHDRAWN (Historical Replay Regression)

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Blackcoin-Dev Blackcoin-Dev released this 16 Jul 13:39
Immutable release. Only release title and notes can be modified.
v30.1.1-beta1
b328d22

WITHDRAWN — DO NOT INSTALL OR DEPLOY

Beta 1 (b328d2263038cdddef46b9f427827aac9e83b513) is affected by a release-blocking historical replay regression. During an authenticated schema-12 rebuild it rejects accepted mainnet block 4,272,172 (41c4dbbe2a1238a4d1d901ec451b99dcbdd018746f6229b533a4f102b5840968) by applying the post-v3.1 500-block generated-output maturity rule to a pre-v3.1 coinstake spend at depth 182.

Do not reuse these binaries. The assets remain attached only for provenance and regression audit. A corrected build will be published under a new Beta 2 tag with a new exact source SHA, filenames, checksums, and replay evidence.

Blackcoin Core v30.1.1 Beta 1

This is a publisher-unsigned, unnotarized canary prerelease for controlled testing. It is not the signed v30.1.1 production release. The macOS application bundles carry deterministic ad-hoc launch-integrity signatures only; those signatures identify no developer or publisher.

The packages are labeled Beta 1. The enclosed binaries self-identify as v30.1.1rc1-b328d2263038 so a running process can be tied to this exact source candidate.

Included Beta 1 work

  • Improves GUI and daemon responsiveness with bounded staking-candidate work and wallet/core lock-order corrections.
  • Includes the required light/dark theme readability repair.
  • Keeps ordinary legacy PoS unrestricted; Gold Rush whitelist status controls only eligibility for the associated shadow reward.
  • Adds a consent-based first-launch schema-12 rebuild assistant. The GUI offers an automatic protected rebuild or an exit/manual path and does not silently rewrite persistent settings.
  • Adds deterministic QQP3 competing-claim selection at height 5,993,200, capped fee reimbursement, logical-proof deduplication, and restart/reorg accounting safeguards.
  • Hardens the shadow index, explorer RPC schemas, lifecycle replay, and authenticated auxiliary-state reconstruction.
  • Requires explicit operator consent for optional staking, Gold Rush PoW, QQSIGNAL, fee-paying automation, and non-HD quantum-key creation.
  • Keeps phase changes height-authoritative: Gold Rush credits remain locked until Migration height 6,193,000; Final Lockout and permanent-burn demurrage begin automatically at height 6,922,000.

Gold Rush is already live. Height 5,993,200 is an upgrade boundary for wallets, mining/staking nodes, explorers, and indexers that consume the shadow ledger. v30.1.0 and v30.1.1 can continue accepting the same base chain, but they intentionally derive different post-boundary shadow allocations. Upgrade before that height if authoritative post-boundary shadow state is required.

Do not reopen a wallet or datadir that has processed post-boundary state with v30.1.1 in v30.1.0. Roll back only by restoring the cold pre-upgrade copy.

No software release can guarantee that every future fork is impossible. This beta is limited to the concrete compatibility, deterministic-build, and failure-isolation evidence identified here and in the linked technical notes.

Beta 1 is not a production recommendation and does not reclassify roadmap items recorded as Partial or Candidate as Verified.

Mandatory canary procedure

  1. Cleanly stop the existing client. Back up every wallet and preserve a cold copy of the complete datadir. ML-DSA quantum keys are non-HD, so the backup must be newer than every quantum address it is expected to recover.

  2. Test one isolated node before any fleet rollout. Use archival mode with prune=0.

  3. An existing v30.1.0 datadir requires one authenticated schema-12 rebuild. Use the GUI assistant, or run:

    blackcoind -datadir=/path/to/data -networkactive=0 -staking=0 \
  -reindex-chainstate -daemonwait

    If historical block files are incomplete, use prune=0 -reindex instead. After the rebuild process exits, start normally without either reindex flag so a separate process verifies the replacement. Never persist a reindex option in configuration.

  4. After synchronization, record getblockchaininfo, gettxoutsetinfo muhash, and getgoldrushstate. Stop cleanly, restart normally without either reindex flag, and compare height, best-block hash, UTXO MuHash, Gold Rush totals, and the schema-12 replay_state commitment. At or after the whitelist height, confirm present, marker_valid, and valid_for_tip are all true. Repeat one offline chainstate-rebuild comparison before enabling networking, staking, or mining; then verify wallets, peers, GUI/RPC responsiveness, and the cold-copy rollback path before expanding the canary.

  5. Verify the included SHA256SUMS-UNSIGNED.txt before launching any binary and compare it with the unsigned JSON manifest. Checksums detect corruption; they are not a publisher signature.

Known Beta 1 limitations

  • Linux and Windows packages have no publisher signature. macOS packages have no Developer ID and are not notarized.
  • A fee-paying Gold Rush PoW claim that leaves the local mempool remains quarantined because a peer can retain and later confirm it. Its input stays reserved, and that wallet's built-in PoW miner pauses while the claim remains unresolved. Automatic abandonment would create an unsafe double-spend race. A retained pre-QQP3 claim can confirm late, pay a base fee, and receive no shadow credit. Use isolated canary wallets. See issues #6 and #26.
  • Pruning is not supported for Quantum Quasar archival/replay use in this beta. Use prune=0.
  • Sudden-power-loss durability of directory renames is not claimed on Windows. Keep the cold datadir copy and stable power during reconstruction.

Safety-evidence disclosure

Run 29461608948 completed target resolution plus 14 safety jobs successfully, but the workflow's overall conclusion was failure and the complete extended functional suite was skipped. Its address/undefined-sanitizer job reported no sanitizer diagnostic; it stopped because a recovery fixture expected cleanup after exactly two failed resubmissions while the safe nonblocking implementation completed cleanup after three. The source repair changes that test expectation only.

Run 29475302999 verifies the immutable prior source, job/log evidence, artifact identity and digest, and the one-file repair, then reruns the corrected native recovery regression against the exact prior binaries before building these packages. It is not represented as a new sanitizer pass.

The unsigned manifest records the bundle's state when workflow run 29475302999 completed (published=false, tag=null). This GitHub prerelease is a later manual promotion of those unchanged artifacts; the asset bytes and enclosed manifest were not rewritten.

Every uploaded canary asset name includes the full source commit. The bundle also includes five per-platform source markers, byte-for-byte evidence from independent primary and verifier builds, an unsigned JSON manifest, unsigned SHA-256 sums, and an UNSIGNED-CANARY warning. GitHub's automatically generated source archives are outside that manifest; use the uploaded exact-SHA assets for testing.

Assets 20
Loading