[Canary] Blackcoin v30.1.1-alpha1 PoW/PoS testing before height 5,993,200

[QuantumQuasar]

Purpose

This thread is for operators conducting controlled Blackcoin Core v30.1.1-alpha1 PoW and PoS tests. It is not a production recommendation, a general download announcement, or an invitation to move ordinary-value wallets.

Alpha 1 is a publisher-unsigned, unnotarized canary prerelease. It has not passed the beta or production release gates.

Release identity

Tag: v30.1.1-alpha1
Source commit: a6dba4b5a8e6716dd7e6e859a840de2a584d8d87

Every uploaded canary asset includes the complete source commit in its filename. Verify the supplied SHA-256 manifest before launching a binary. A checksum detects corruption; it is not a publisher signature.

Hard stop

Do not run Alpha 1 at or beyond height 5,993,200. Replace it with a later fixed candidate before that boundary. Alpha 1 does not prove the maximum-size custom-block claim/accounting resource bounds required for post-boundary operation.

What this canary is intended to test

1. Archival chainstate reconstruction followed by a clean second start.
2. Ordinary legacy PoS behavior after reconstruction and restart checks complete.
3. The built-in PoW claim path under strict resource and wallet separation controls.
4. Restart, tip, wallet, peer, RPC, staking-state and rollback observations tied to the exact release commit.

Ordinary legacy PoS, snapshot-governed shadow-PoS eligibility and PoW are distinct paths. Protocol V4 shadow credits are synthetic, non-Merkle and phase-locked accounting records, not ordinary spendable UTXOs or circulating supply.

Mandatory canary controls

1. Cleanly stop v30.1.0. Back up every wallet and make a cold copy of the complete datadir.
2. Test one isolated node first. Do not deploy Alpha 1 across a fleet.
3. Use archival mode with prune=0.
4. Keep staking and mining disabled during reconstruction.
5. If complete block history is present, use the documented protected -reindex-chainstate path. If history is incomplete or pruned, use prune=0 and perform a full -reindex.
6. After reconstruction succeeds, stop cleanly and start again without a reindex option. Verify the tip, wallets, GUI or RPC, peers, staking state and rollback path.
7. Use test-value funds. Quantum keys are non-HD; make and verify a new wallet backup after every newly generated quantum key or address.
8. Preserve the cold pre-upgrade datadir for rollback. Do not reopen a datadir that processed post-boundary v30.1.1 state using v30.1.0.

Controlled PoW lane

After the reconstruction and clean second start pass:

- Limit built-in PoW to one thread and 1% CPU.
- Use a separate PoW wallet with its own confirmed, small legacy fee UTXO.
- Pre-create the payout with getnewquantumaddress "PoW - Quantum Claim Address".
- Complete and verify a fresh wallet backup before enabling PoW.
- setpowmining is wallet-scoped. On a multiwallet node, enable exactly one designated PoW wallet and explicitly leave PoW disabled on every other loaded wallet.
- Do not enable built-in PoW in a high-value or whitelisted PoS wallet.
- Phase-locked Gold Rush accounting cannot fund the legacy claim fee.

Controlled PoS lane

Enable PoS only after reconstruction, the clean second start and rollback checks complete. Use a test-value wallet on the isolated node. Keep ordinary legacy PoS observations separate from snapshot-governed shadow-PoS accounting.

An ordinary staking UTXO selected for a pending claim stops contributing stake weight while pending. Confirmed change must mature before it can stake again.

Public telemetry boundary

The Project Blackcoin explorer preview publishes a timestamped base-chain anchor and a separately labeled Protocol V4 accounting view. At the time this thread was prepared, its public feed reported agreement among all three sampled nodes. That is a project telemetry sample, not a network-wide node count, adoption metric or independent consensus claim.

Use the timestamp on the live page when judging freshness. The explorer fails closed rather than substituting chain facts when its validation gates are unavailable. Full indexed history and search remain release-gated. Alpha 1 must not be used as a historical mainnet explorer indexer with -shadowindex=1.

Reporting useful test observations

Please include:

- operating system and exact embedded build identifier;
- starting and ending height and best-block hash;
- reconstruction path used;
- wallet count and wallet roles, without addresses or keys;
- PoW/PoS settings and observed state;
- clean-second-start result;
- rollback result; and
- relevant log excerpts with IP addresses, filesystem paths, credentials and other identifying data removed.

Downloads and release limits:
https://projectblackcoin.org/#downloads
https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.1-alpha1