BLACKCOIN / PROTOCOL V4
Public hardening

v30.1.1 ALPHA 1 / CONTROLLED TESTING

Blackcoin Protocol V4 is being hardened in public.

Blackcoin-Dev is an independent team implementing an ML-DSA-44 migration path. v30.1.0 established the structure; v30.1.1 is the evidence-gated hardening response to defects and community feedback.

Ordinary holders should wait for the signed final. Do not migrate ordinary value during Gold Rush.

PROTOCOLV4ML-DSA-44 PATH
LANE
Alpha 1 / canary
BETA
not released
BOUNDARY
5,993,200
LIVE CHAIN SNAPSHOT / 15 JULY 2026 UTC

First Gold Rush reward halving

Alpha 1 fixes the first shadow-reward halving at height 5,993,200: the 5,950,000 start plus a 43,200-block interval.

Open the live explorer
Explorer height
5,953,282
Blocks remaining
39,918
Target-spacing estimate
29.6 days

Snapshot checked at 05:03 UTC. The 64-second target spacing points to roughly 13-14 August if target pace holds; actual time varies with chain pace. This is a protocol estimate, not a financial-return forecast.

RELEASE LADDER

Four distinct states. No blurred labels.

30.1.0 → Alpha 1 → pending Beta → gated signed Final

01
Known defects

v30.1.0

Tagged 5 July

The structurally working Protocol V4 launch release. Public testing exposed material consensus, wallet, recovery, accounting and operability defects. No new production deployment is recommended.

Inspect the exact record
02
Controlled canary

v30.1.1 Alpha 1

Tagged 14 July

Targeted hardening for qualified, isolated and pre-boundary test staking or mining. It is unsigned, unnotarized and not a production or fleet-upgrade release.

Inspect the exact record
03
Not released

v30.1.1 Beta

Pending

The integration lane remains a draft pull request. No binary should be represented as a published Blackcoin-Dev beta until an exact candidate is tagged and released.

Inspect the exact record
04
Not released

v30.1.1 Final

Evidence-gated

Final requires exact-source P0/P1 evidence, release identity, signed artifacts, reproducible outputs, consistent documentation and rehearsed canary and rollback procedures.

Inspect the exact record

GOLD RUSH / WHAT THE SOFTWARE ACTUALLY DOES

Participation paths are distinct.

01 / ORDINARY POS

Legacy staking remains a separate path.

On Alpha 1's exact source, issue #7 restores otherwise-valid ordinary legacy proof-of-stake without shadow-whitelist gating.

02 / SHADOW POS

The historical snapshot is fixed.

Shadow-PoS reward eligibility remains governed by the fixed historical snapshot. This project is not reopening it.

03 / PROOF OF WORK

PoW is the non-whitelist test lane.

Qualified CPU-mining canaries use a separate wallet and strict resource limits. PoW is mined; it is not staked.

Shadow credits are not ordinary UTXOs.

Gold Rush credits are synthetic, non-Merkle and phase-locked. They are not spendable base-layer outputs during Gold Rush. Unmodified legacy software does not calculate that state, and the repository does not document completed exchange integration. Do not assume exchange support, APY, price or returns.

ALPHA 1 / CONTROLLED CANARY ONLY

Test the implementation, not your holdings.

Stop before height 5,993,200. Replace Alpha 1 before that boundary.

DO NOT

Use migratetoquantum for ordinary value during Gold Rush. Quantum keys are non-HD; make and verify a fresh wallet backup after every newly generated quantum key or address.

SHARED CANARY BASELINE

Before staking or mining

  1. Stop the existing process cleanly.
  2. Back up every wallet and make a cold copy of the complete datadir.
  3. Use one isolated node with test-value funds and prune=0.
  4. Keep staking and mining disabled during reconstruction.
  5. Complete reconstruction, then perform a clean second start.
  6. Retain the cold pre-upgrade datadir for rollback. No fleet rollout.

CONTROLLED POS

Test staking lane

  • Use a test-value wallet on one isolated node.
  • Distinguish ordinary legacy PoS from snapshot-governed shadow-PoS.
  • Verify accounting and restart behavior against the exact Alpha source.
  • No APY or reward outcome is promised.
Read every Alpha limit

CONTROLLED POW

Test mining lane

  • One thread and 1% CPU.
  • Separate PoW wallet; never use a high-value or whitelisted PoS wallet.
  • One confirmed small legacy fee UTXO.
  • Payout address already present in a fresh verified backup.
  • Issue #26 remains open: a custom block can pay a base fee yet receive no shadow credit.
Inspect issue #26

POST-QUANTUM SCOPE

A migration path, not an absolute-security slogan.

Protocol V4 implements an ML-DSA-44 migration path. ML-DSA-44 is one parameter set standardized in NIST FIPS 204. That is not a claim that this implementation is FIPS-validated or certified.

Security also depends on dependency provenance, random-number generation, key storage, backup behavior, signature integration, consensus handling, resource limits and exact implementation evidence.

Read NIST FIPS 204

path / ML-DSA-44

status / migration inactive

keys / non-HD

validation / not claimed

final / evidence-gated

OPEN RELEASE GATES

Known risk belongs above the fold.

Open means open. Each exact candidate must earn its own evidence.

PARTICIPATE WITHOUT HYPE

Review it. Reproduce it. Try to break the evidence.

Consensus testers, recovery testers, independent builders, wallet engineers, explorer developers and documentation reviewers can contribute now. No purchase is required.