REMINDER: BlackcoinDev (Me) is NOT the same developer as Blackcoin-Dev. #StaySafe #DontTrustButVerify
Blackcoin Github is
https://github.com/CoinBlackMy GitHub profile is
https://github.com/BlackcoinDevGPG fingerprint: 7F9EFB458122B8A39C46947DA87935AB61FABA71
Blackcoin is currently running stable on v26.2.0 and close to release v28.4.0. Identity and security are separate questionsCorrect:
BlackcoinDev and Blackcoin-Dev are different maintainers. Blackcoin-Dev v30.1.3 is an independently maintained Blackcoin implementation. It is not presented as a CoinBlack release, and no endorsement from CoinBlack or the historical maintenance team is claimed.
“Don’t trust; verify” is the right standard for every wallet. Verification, however, requires technical evidence. Post #586 identifies no affected v30.1.3 commit, package hash, malicious code, vulnerability, consensus failure, or reproducible test. A maintainer-name distinction is not a security finding. If there is a concrete issue, please identify the exact source commit or artifact SHA-256, affected platform, reproduction steps, expected behavior, observed result, and sanitized evidence—or use the private security-reporting process. Reproducible findings will be investigated. Separate authorship should not be mistaken for evidence that software is malicious or fraudulent.
What v30.1.3 actually implementsDuring Gold Rush, v30.1.3 retains Blackcoin’s existing chain history and Proof-of-Stake base consensus. V4 wallets publish fee-paying, legacy-valid OP_RETURN transactions. Legacy nodes can relay and include those underlying transactions, while v30.1.3 nodes deterministically interpret
QQSIGNAL and
QQSPROOF into separate authenticated synthetic shadow-accounting state. This is a replay-derived accounting overlay anchored in canonical base blocks, not a second blockchain.
Stock legacy clients can continue following compatible base-chain activity during this phase, but they do not interpret Protocol V4 shadow accounting or provide its V4 signaling, shadow RPC/indexing, Argon2id claim, and supported height-gated ML-DSA-44 migration workflows. Operators who want to evaluate or participate in V4 therefore need a current V4-capable client. Blackcoin block production remains PoS; the optional Argon2id PoW feature is a claim transaction carried inside PoS blocks, not PoW blocks and not “PoW staking.”
Gold Rush credits are synthetic, non-Merkle, and phase-locked. They are not currently spendable base-layer outputs, exchange deposits, circulating supply, or guaranteed rewards. ML-DSA funding and spending begin at Migration height 6,193,000; this is not a claim that the entire present chain is already quantum-proof or that the implementation is FIPS-certified.
Apply verification to v30.1.3 as wellThe current v30.1.3 source record is commit
86c6855ab135afe784635a564f21c74d67aa366b. The exact commit and annotated tag are SSH-signed and verified by GitHub. The release publishes SHA-256 checksums, an SPDX SBOM, provenance, and attestation/evidence records.
Those controls establish source identity and traceability; they are not an independent security audit or certification. Windows packages are not Authenticode-signed. macOS packages are ad-hoc signed rather than Developer-ID signed and are not notarized. The project also discloses the open P1 Gold Rush PoW wallet-recovery issue #37. That issue changes no consensus rule, but it can leave the built-in miner paused until the affected claim family is resolved. These limits are public rather than hidden.
Exact v30.1.3 release recordVerification guideSecurity reporting and known issuesLive base-chain and V4 accounting viewBack up wallets, verify the exact release, test in a controlled environment, and retain a rollback path. Technical disagreement is welcome. It should be addressed against exact code, hashes, and reproducible behavior—not by implication.
