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 recordv30.1.1 ALPHA 1 / CONTROLLED TESTING
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.
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 explorerSnapshot 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
30.1.0 → Alpha 1 → pending Beta → gated signed Final
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 recordTagged 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 recordPending
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 recordEvidence-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 recordGOLD RUSH / WHAT THE SOFTWARE ACTUALLY DOES
On Alpha 1's exact source, issue #7 restores otherwise-valid ordinary legacy proof-of-stake without shadow-whitelist gating.
Shadow-PoS reward eligibility remains governed by the fixed historical snapshot. This project is not reopening it.
Qualified CPU-mining canaries use a separate wallet and strict resource limits. PoW is mined; it is not staked.
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
Stop before height 5,993,200. Replace Alpha 1 before that boundary.
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
prune=0.CONTROLLED POS
CONTROLLED POW
POST-QUANTUM SCOPE
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 204path / ML-DSA-44
status / migration inactive
keys / non-HD
validation / not claimed
final / evidence-gated
OPEN RELEASE GATES
Open means open. Each exact candidate must earn its own evidence.
Late or stale claims can reserve inputs or confirm a fee-paid transaction without shadow credit.
#12Failure isolationInternal Argon2 or resource failures are not yet fully isolated from base-block validity.
#14Quantum fundingOrdinary-value migration remains unsafe during Gold Rush; the complete funding and spend path is not active.
#16Lifecycle clocksHeight and median-time-past behavior require exact boundary and grace-period evidence.
#18Wallet and explorer APIsSchemas, indexing and ingestion criteria remain candidate interfaces, not stable integrations.
#20Base-block compatibilityFour confirmed v30.1.0 split paths require exact-client and exact-SHA regression evidence.
#23Quantum-key durabilityThe end-to-end crash and restore gate remains open; fresh verified backups are mandatory.
#25Liveness and locksCleanup, lock-order and liveness proof remain open before a final release.
PARTICIPATE WITHOUT HYPE
Consensus testers, recovery testers, independent builders, wallet engineers, explorer developers and documentation reviewers can contribute now. No purchase is required.