[ANN] Blackcoin-Dev Protocol V4 v30.1.3 | Gold Rush & Explorer

[QuantumQuasar]

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 SEQUENCE

• v30.1.0 — tagged 5 July: the existing Blackcoin-Dev Protocol V4 release. Its known defects and compatibility limits are tracked publicly.
  https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.0
• v30.1.1 Alpha 1 — tagged 14 July: targeted hardening for controlled, isolated, pre-boundary testing. It is not production-ready.
  https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.1-alpha1
• v30.1.1 Beta — pending: the integration lane remains a draft pull request. No binary should be represented as a published Blackcoin-Dev beta release.
  https://github.com/Blackcoin-Dev/Blackcoin/pull/29
• v30.1.1 Final — gated: final requires the complete matrix to pass on the exact final source, signed release identity and artifacts, independently reproducible outputs, consistent documentation, and rehearsed canary and rollback procedures.

FIRST GOLD RUSH REWARD HALVING — LIVE COUNTDOWN SNAPSHOT

The 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.h

CURRENT RECOMMENDATION

This 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 MEANS

Protocol 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/20

ALPHA 1 IMPROVEMENTS AND SCOPE

Alpha 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-4973767559

CONTROLLED TEST STAKING AND MINING ARE OPEN NOW

Qualified 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 PROCEDURE

The 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-alpha1

KNOWN OPEN RELEASE GATES

As 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/8

POST-QUANTUM SCOPE

Protocol 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 EVIDENCE

A 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 PARTICIPATE

There 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/Blackcoin
Roadmap: https://github.com/Blackcoin-Dev/Blackcoin/issues/8
Releases: https://github.com/Blackcoin-Dev/Blackcoin/releases

For 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.

[QuantumQuasar]

THE WHITELIST SNAPSHOT To prevent abuse of the massive Gold Rush APYs, participation in the 180-Day Gold Rush requires your address to be whitelisted. The Requirement: You must hold a minimum of 10,000 BLK in your V4 wallet at the exact moment of the snapshot. The Deadline: Block 5,945,000 [/quote]

🚨 OFFICIAL NETWORK UPDATE: SNAPSHOT COMPLETE 🚨 Block 5,945,000 has been successfully mined and verified by the v30.1.0 daemon!

The global Protocol V4 network has officially executed the massive UTXO sweep and etched the MARKER_WHITELIST_READY payload into the chainstate. If your legacy wallet held 10,000 BLK or more at the exact moment this block was mined, your cryptographic footprint is now permanently whitelisted for the upcoming economic overlay.

THE FINAL COUNTDOWN: 5,000 BLOCKS REMAINING We are currently in the 5,000-block grace period. At exactly Block 5,950,000, the 180-Day Gold Rush activates.

During this massive 180-day event, a dedicated, highly inflated Shadow Emission Schedule activates on the Quantum Quasar overlay network. This massive influx of Protocol V4 rewards is split perfectly 50/50 between two participant groups:

• Active Protocol V4 Stakers (50%): If you were whitelisted at the snapshot, you must have your v30.1.0 node actively staking by 5,950,000 to absorb massive PoS interest generated directly from the Shadow Emission pool.
• Argon2id CPU Miners (50%): The parallel Proof-of-Work lane opens. Anyone with a standard multi-core PC can immediately begin mining Protocol V4 blocks and claiming the other 50% of the Gold Rush rewards—no 10k BLK staking balance required!

THE DEMURRAGE DEADLINE: BLOCK 6,193,001 Once the 180-Day Gold Rush concludes at block 6,193,000, the true deflationary mechanics kick in. Starting at Block 6,193,001, Demurrage is officially activated. Any legacy whale wallets that failed to participate in the Gold Rush and failed to migrate to post-quantum security will begin to systematically burn and decay their consensus weight.

Update your nodes immediately to ensure you don't miss the first block of the Gold Rush at 5,950,000.

Download v30.1.0 here: https://github.com/Blackcoin-Dev/Blackcoin

[QuantumQuasar]

The countdown is on.

We are currently less than 1,000 blocks away from Block 5,950,000. At exactly that block height, the V4 Quantum Quasar protocol officially initiates the 180-Day Gold Rush.

For the next 6 months, the network will execute a consensus-level demurrage, decaying lost legacy UTXOs and heavily rewarding the active V4 nodes securing the post-quantum shadow ledger.

For Miners: The V4 PoW engine uses Argon2id. It is heavily memory-hard and completely ASIC/GPU resistant. If you have spare CPU power, you have roughly 16 hours to get synced before the hash race starts.

For Stakers: Ensure your V4 wallets are fully unlocked to participate in both legacy and quantum staking pools.

The train leaves the station at Block 5,950,000.

Download the V4 Client and read the Whitepaper here:
https://github.com/Blackcoin-Dev/Blackcoin

[QuantumQuasar]

PROJECT WEBSITE AND EXPLORER PREVIEW

The public verification portal is now live:

https://projectblackcoin.org/
https://projectblackcoin.org/explorer

The explorer displays the current agreed base-chain anchor, separately labeled Protocol V4 telemetry, PoW/PoS accounting counters, active-signaler data, conditional next-block estimates, and exact published downloads.

Alpha 1 remains an unsigned, unnotarized prerelease canary. Full block, transaction, synthetic-record, and address search remains disabled until a fixed published release completes genesis-to-tip index replay. The site fails closed instead of presenting stale or inferred search results.

Use one isolated node, test-value funds, verified backups, and rollback. Do not migrate ordinary value during Gold Rush. Protocol V4 credits shown during Gold Rush are synthetic, non-Merkle, phase-locked accounting records. They are not spendable base-layer outputs, exchange deposits, circulating supply, or promised returns.

Downloads on the site come from the Blackcoin-Dev release record. Exact release notes control. Beta has not been released, and final remains gated.

[QuantumQuasar]

BLACKCOIN CORE v30.1.3 RELEASE AND INTEGRATION UPDATE

Blackcoin-Dev published Blackcoin Core v30.1.3 on 17 July 2026 as a non-prerelease, signed-source production release.

Exact source commit: 86c6855ab135afe784635a564f21c74d67aa366b
Release: https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.3

The source commit and annotated tag are SSH-signed. Windows packages are not Authenticode-signed. macOS packages are ad-hoc signed and are not Developer-ID signed or notarized. No independent security audit is claimed. Verify the exact source, checksums, package limits, SBOM and provenance before use.

Blackcoin mainnet remains Proof of Stake after height 10,000. Gold Rush Argon2id proofs are transaction-carried inside canonical PoS blocks; they are not new PoW blocks. Current Protocol V4 credits are synthetic, non-Merkle and phase-locked. They are not spendable or circulating base-layer BLK.

HEIGHT-AUTHORITATIVE SCHEDULE

• Gold Rush through height 6,192,999
• Migration from height 6,193,000 through 6,921,999
• Final Lockout beginning at height 6,922,000

PROJECT RESOURCES

• Website and downloads: https://projectblackcoin.org/
• Release verification: https://projectblackcoin.org/verify
• Developer and integration documentation: https://projectblackcoin.org/developers
• Unified explorer: https://projectblackcoin.org/explorer
• Migration schedule: https://projectblackcoin.org/migration
• Security reporting and current limitations: https://projectblackcoin.org/security
• Read-only OpenAPI: https://projectblackcoin.org/openapi.json

Open P1 issue #37 concerns claim-family wallet/miner recovery and can leave the built-in miner paused. It changes no consensus rule:
https://github.com/Blackcoin-Dev/Blackcoin/issues/37

Exchange and custody teams should run and validate their own v30.1.3 blackcoind node and use authenticated private JSON-RPC. The public API is read-only telemetry, not a custody interface. Base-chain BLK and phase-locked Protocol V4 records require separate reconciled accounting.

Users and integrators are invited to test the exact release, report reproducible defects and compare the published evidence. No reward, return, listing or calendar-date outcome is guaranteed.Blackcoin-Dev Protocol V4 v30.1.3 — production update

To avoid any ambiguity, Blackcoin-Dev v30.1.3 is an independently maintained Blackcoin Protocol V4 implementation for the historical Blackcoin network. It is not a release from CoinBlack or the historical maintenance team.

The technical distinction matters. Legacy nodes can continue to validate the compatible base chain and may relay or include the underlying transactions. But a stock legacy wallet does not implement the supported Protocol V4 ML-DSA-44 key, QQSIGNAL/QQSPROOF, or shadow-ledger workflows. Running only legacy software therefore does not natively create or manage Gold Rush claims or their Protocol V4 credits.

The height-authoritative schedule is:

• Gold Rush: 5,950,000 through 6,192,999
• Ordinary migration funding opens: 6,193,000
• Last Migration block: 6,921,999
• Final Lockout begins: 6,922,000

Eligible legacy-controlled BLK therefore retains a defined migration window after the Gold Rush. That later migration path does not backfill Protocol V4 allocations missed during the Gold Rush.

The first Protocol V4 reward halving is fixed at height 5,993,200. The present 580-BLK per-block base amount accrues as separate 290-BLK PoS and PoW accounting pools. At the halving boundary, those figures become 290 BLK total and 145 BLK per pool. PoW here is an Argon2id claim-transaction lane carried inside ordinary PoS blocks; it is not PoW block consensus and is not “PoW staking.”

Gold Rush credits are synthetic, non-Merkle, phase-locked, and not spendable balances, exchange deposits, or circulating supply during this phase. Participation and projected rewards are not guaranteed, and this is not a price or return promise.

The public site now provides direct v30.1.3 downloads and verification records, the unified base-chain/Protocol V4 explorer, exact consensus-height schedules, shadow-ledger views, live signaling and next-block accounting, migration guidance, and public APIs. Live figures are displayed only when source, anchor, freshness, and node-agreement checks pass; the site fails closed instead of presenting stale values.

Project Blackcoin
Unified explorer
Migration readiness
Public API

Verify checksums, provenance, and the exact signed source before installing. Windows packages are not Authenticode-signed, and macOS builds are not Developer-ID signed or notarized.

We invite CoinBlack and every historical maintainer to inspect v30.1.3, reproduce its tests, audit the transition rules, publish concrete technical findings, and collaborate on interoperability. A useful challenge identifies the exact version, command, log, fixture, or code path so it can be reproduced and fixed. The invitation to work from verifiable evidence remains open.

[QuantumQuasar]

FREE CLAIM MINING POOL — NEW USER ONBOARDING

Project Blackcoin now has a sponsor-funded way for someone starting with no BLK to receive a first Protocol V4 Gold Rush claim:
https://projectblackcoin.org/free-claim

How it works

• Install, verify, and sync the Blackcoin-Dev v30.1.3 release.
• In the wallet console, run getnewquantumaddress.
• Back up the wallet immediately. The new ML-DSA key is non-HD, so an older seed or backup will not recover it.
• Paste only the resulting public blk1s... quantum address into the free-claim page.
• The sponsor node supplies the fee input and mines the Gold Rush claim in queue order.

No purchase, deposit, private key, seed phrase, wallet file, or payment is requested.

The pool allows one award per address, one submission per IP per 24 hours, and up to 25 awards per day. Claims are processed one at a time; the page reports live capacity and status.

What the award is — and is not

A successful award is the PoW jackpot applicable at the claim's solve height. The amount changes with the height-based schedule and is not promised in advance. It is a phase-locked Protocol V4 shadow-ledger credit, not spendable or circulating BLK today. It unlocks at Migration block 6,193,000.

This does not mine a new Blackcoin base-chain block. Blackcoin base consensus remains Proof of Stake; the sponsor mines an Argon2id Gold Rush claim transaction carried in a PoS block.

Each successful award is recorded in chainstate and returns a credit outpoint that can be independently checked on a synced node with gettxout.

Release verification: https://projectblackcoin.org/verify
Run-a-node guide: https://projectblackcoin.org/node

Never send anyone a seed phrase, private key, or wallet file.

Verified project channels: https://projectblackcoin.org/community

Disclosure: This post was drafted with AI assistance and reviewed and published by the Blackcoin-Dev project team.

[QuantumQuasar]

EXPLORER INDEX AND API RECOVERY UPDATE — 22 JULY 2026 UTC

The historical explorer backfill has reached its published completion state. At 16:10 UTC on 22 July:

• /api/ready returned ready.
• /api/explorer/status reported mainnet synchronized at height 5,962,884.
• The transaction, shadow and address indexes were enabled and synchronized to that height.
• Published coverage was complete from height 1 through tip.
• Block 1 lookup and explorer search both returned available.
• /api/v3/quantum reported live quality for v30.1.3 source commit 86c6855ab135afe784635a564f21c74d67aa366b.
• The free-claim status endpoint was responding with an empty queue, two awards completed, and the 25-award daily capacity unused at that snapshot.

This supersedes earlier operational notices that described full-depth search as disabled or the explorer upstream as degraded. Height, mempool and claim-pool state change continuously; use the live endpoints rather than treating this snapshot as current forever.

The recovery does not change the release or security boundaries. Blackcoin-Dev v30.1.3 is an independent implementation, not a CoinBlack release. No independent security audit is claimed. Public endpoints are read-only comparison surfaces, not custody authority. Protocol V4 Gold Rush credits remain phase-locked synthetic accounting records and are not spendable or circulating base-layer BLK today. Operators and integrators should verify results against their own exact-source v30.1.3 node.

Explorer: https://projectblackcoin.org/explorer
OpenAPI: https://projectblackcoin.org/openapi.json
MCP and agent integration: https://projectblackcoin.org/agents
Release verification: https://projectblackcoin.org/verify
Free-claim rules and live status: https://projectblackcoin.org/free-claim

Disclosure: This update was drafted with AI assistance and reviewed and published by the Blackcoin-Dev project team.

[fibonacciopstan]

I appreciate how carefully this update separates what is released, what is still experimental, and which gates remain open. The emphasis on exact tags, exact source, reproducible artifacts and prospective rather than retroactive changes is stronger than what most projects provide.

It also raises a related question. The software release can be tied to a specific commit, but what about the public statements surrounding that release?

Safety recommendations, compatibility warnings, migration restrictions, release gates and explanations of Gold Rush accounting may become just as important as the code itself. GitHub issues preserve some history, but announcements can be revised, documentation reorganized, comments removed and roadmap descriptions rewritten as the project evolves.

A future operator should be able to verify not only which binary was released, but also exactly what users were told at that moment and which commitments were still open.

What is the canonical place where Blackcoin permanently records these official notices and roadmap commitments in an uneditable, timestamped history? Please send the link — I would like to compare future releases against the original statements.

[QuantumQuasar]

What is the canonical place where Blackcoin permanently records these official notices and roadmap commitments in an uneditable, timestamped history?

That is a fair and important question. The honest answer is that Blackcoin-Dev does not currently have one link that is comprehensive, permanent, independently timestamped and uneditable for every public statement. We have a strong signed release record and SHA-pinned documentation, but the website, forum posts, GitHub issue text, release descriptions and social posts are not an append-only notice log. We should not claim otherwise.

For v30.1.3, the strongest existing record is the SSH-signed source commit and annotated tag:

v30.1.3 signed-source release record
Exact source commit: 86c6855ab135afe784635a564f21c74d67aa366b

The following documents are pinned to that exact commit:

v30.1.3 release notes
incorporated v30.1.1 safety and behavior record
transition, compatibility, Migration and Gold Rush guidance
release-gate commitments
Protocol V4 specification

Those files are content-addressed. Their text cannot be changed without creating different Git objects that no longer match the signed tag. The roadmap issue is the public working record, but it remains editable. The RSS and Atom feeds preserve release identifiers and publication times, but they cover releases only and are not a permanent policy archive.

Your question therefore identifies a real provenance gap. A complete solution should record every material future notice as a new signed, content-hashed document with a unique ID, UTC timestamp, affected versions and heights, status, and supersedes/superseded-by links. Corrections should add a new record rather than overwrite the old one, and the manifest should receive an independent timestamp and an external mirror.

We invite you, operators, integrators, reviewers and historical or competing maintainers to help define and verify that format. If you open an issue proposing the schema, we will engage with it publicly. Until the archive exists, compare future releases against the exact SHA-pinned documents above rather than main or mutable website copy.

This matters especially because competing maintainers have issued repeated public warnings against v30.1.x. We dispute blanket characterizations, and we are concerned that they can discourage independent review and participation. The answer is not to ask anyone to trust our label. The answer is to require the same evidence standard from everyone. Anyone, including those maintainers, is invited to identify an exact commit, block or transaction fixture, test vector, or reproducible failure. We will address technical findings publicly. Criticism and collaboration are welcome; unsupported labels are not technical evidence.

[QuantumQuasar]

Yes. You are welcome to prepare and publish an independent factual overview based on Project Blackcoin’s public sources. Please send the complete draft and its content hash to exchange@projectblackcoin.org before publication for a factual-accuracy review. That review would not make the Opstan record an official Project Blackcoin notice or imply editorial endorsement.

Please identify v30.1.3 as an independently maintained, same-genesis implementation and not a CoinBlack release; cite the exact tag and source commit 86c6855ab135afe784635a564f21c74d67aa366b; and preserve the published limitations. Those include the absence of an independent security audit, unsigned/not-notarized packages, and the open P1 claim-recovery issue #37.

Protocol V4 credits must remain described as phase-locked shadow-ledger accounting rather than presently spendable or circulating BLK. Please do not imply a guaranteed reward, listing, adoption outcome, or return.

Useful source records:
https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.3
https://projectblackcoin.org/releases/v30.1.3
https://projectblackcoin.org/verify
https://projectblackcoin.org/identity
https://github.com/Blackcoin-Dev/Blackcoin/issues/37

For the permanent record, we welcome a UTC timestamp, content hash, source links, and append-only corrections. We cannot grant rights to third-party marks or material, so please use only content you have permission to reproduce. After factual review, we can link to the finalized Opstan record as an independent mirror.Disclosure: this update was drafted with AI assistance and reviewed and approved by the Project Blackcoin account operator.

v30.1.3 — independent node, explorer and Free Claim testing invitation

Blackcoin-Dev v30.1.3 remains the current independently maintained Protocol V4 release. It is not a CoinBlack release.

We are looking for reproducible external testing rather than trust-based claims:

• Verify the exact tag, source commit and artifact hashes.
• Start a node with a fresh, isolated data directory and record synchronization, peer connectivity, clean shutdown and restart behavior.
• Compare the public read-only explorer/OpenAPI responses with results from your own node.
• Optionally test the sponsor-funded Free Claim workflow with a newly generated public quantum address.

The Free Claim service never needs a seed phrase, private key, wallet file, payment or deposit. The sponsor node pays the fee input and mines one Gold Rush claim for the submitted quantum address. It does not give the user a base-chain block. Any resulting credit is phase-locked shadow-ledger accounting, not spendable or circulating BLK today, and no reward amount is promised. Back up the wallet after generating the quantum address because ML-DSA keys are not derived from the legacy HD seed.

Please report the exact v30.1.3 build, OS and architecture, commands, expected result, actual result and sanitized logs. Positive and negative reproducible findings are equally useful. Do not post keys, wallet files, credentials, IP addresses or personal data.

Release and verification
https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.3
https://projectblackcoin.org/releases/v30.1.3
https://projectblackcoin.org/verify

Explorer and integration
https://projectblackcoin.org/explorer
https://projectblackcoin.org/integrate
https://projectblackcoin.org/openapi.json

Free Claim rules and live status
https://projectblackcoin.org/free-claim

The source tag is signed, but the packages are not Authenticode-signed or Apple-notarized. No independent security audit is claimed. Operators should also review the open P1 claim-recovery issue before Gold Rush PoW claim mining:
https://github.com/Blackcoin-Dev/Blackcoin/issues/37

[QuantumQuasar]

STATUS UPDATE — v30.1.4 IS CURRENT; v30.1.5 IS NOT RELEASED

The latest immutable public Blackcoin-Dev release is v30.1.4, published 5 August 2026:

https://github.com/Blackcoin-Dev/Blackcoin/releases/tag/v30.1.4
Exact source commit: 13262151077cce3f72d07d17dc7725b2b6a8e1ab
Project release record: https://projectblackcoin.org/releases/v30.1.4

v30.1.4 is a wallet-safety and observability maintenance release. It does not change consensus, reward amounts, Gold Rush eligibility, the quantum lifecycle, or wallet ownership. The source commit and annotated tag are signed. The Windows packages are not Authenticode-signed, the macOS packages are not notarized, and no independent security audit is claimed. Verify the published hashes, back up the wallet and data directory, and use an isolated canary before any broader deployment.

v30.1.5 has not been released. Draft PR #49 is at candidate head 8a3a5aa1c01caf57acc694b836398c5acba969d0:
https://github.com/Blackcoin-Dev/Blackcoin/pull/49

As of 8 August 2026, two mandatory PR jobs are failing and packaging, canary, and rollout gates remain open. Roadmap issues #37, #44, #47, and #48 also remain open:
https://github.com/Blackcoin-Dev/Blackcoin/issues/37
https://github.com/Blackcoin-Dev/Blackcoin/issues/44
https://github.com/Blackcoin-Dev/Blackcoin/issues/47
https://github.com/Blackcoin-Dev/Blackcoin/issues/48

Do not treat a PR build, branch artifact, or roadmap statement as a release.

The live lifecycle endpoint continues to report the Gold Rush phase:
https://projectblackcoin.org/api/v3/lifecycle

That is a protocol-state fact, not a promise of a reward or return. Blackcoin base consensus remains Proof of Stake. The Argon2id Gold Rush lane produces phase-locked overlay claim credits carried in PoS blocks; it does not mine PoW base-chain blocks. Those credits are not presently spendable or circulating BLK. Running software or submitting a claim does not guarantee an award, value, liquidity, an exchange listing, or third-party compatibility.

Current read-only public surfaces:
Release catalog: https://projectblackcoin.org/api/releases
Explorer: https://projectblackcoin.org/explorer
Service status: https://projectblackcoin.org/status
Explorer status API: https://projectblackcoin.org/api/explorer/status
Developer API: https://projectblackcoin.org/developers
OpenAPI: https://projectblackcoin.org/openapi.json

Transparency note: some shared site metadata and documentation pages still display v30.1.3. They are being reconciled. Until that is complete, use the immutable v30.1.4 release record and release catalog above to determine the latest downloadable release. A v30.1.3 value in chain-parameter or observer metadata may describe the current consensus/observer baseline, not the latest package.

Technical review is welcome. Please include the exact release tag or source commit, platform, expected result, actual result, and sanitized logs. Never publish seeds, private keys, wallet files, passphrases, RPC credentials, IP addresses, or personal data.

Disclosure: this update was drafted with AI assistance and reviewed and published by the Project Blackcoin account operator.