A note from the Kvanta5 development team — the authors of the codebase this project is built on. VoidCoin has disclosed that it was forked from Kvanta5-Core, which is accurate and consistent with the MIT license. We have no legal objection to this. What we do want to provide is an accurate technical record for anyone evaluating this project, because several claims in the ANN require context.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. THE ORIGIN OF THIS CODEBASE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
KVANTA5 launched mainnet on
June 1, 2026 — 28 days before VoidCoin.
The following is what a standard
diff -rq between
Kvanta5-Core-1.0.0 and
VoidCoin-Core produces when you strip name/branding changes and count only meaningful technical modifications:
Total files changed: 1,148
Meaningful non-rename lines changed: 314
Those 314 lines are:
- Port numbers (55555 → 7777, 55556 → 7778)
- Network magic bytes (0x4b563521 → 0xD3ADC0DE)
- Genesis block timestamp and nonce (two numbers)
- Bech32 prefix (kvqr → vqr, kv5 → void)
- Dev fund enforcement deleted from validation.cpp (~20 lines, replaced with a comment)
- Testnet/regtest genesis asserts commented out (4 lines)
- V2_FRAGMENT constants refactored (computed instead of hardcoded)
Everything else — the ML-DSA-87 consensus integration, the P2QR script engine, the CheckSignatureAndProgram() pubkey-to-program binding, the DGW difficulty algorithm, the V2_FRAGMENT large-block propagation protocol, the wallet key generation with GetStrongRandBytes() and self-test, all 110+ RPC commands — came from the Kvanta5 development team unchanged.
Anyone can verify this independently:
git clone https://github.com/Kvanta-Organization/Kvanta5-Core kv5
git clone https://github.com/VoidHash-Crypto/VoidCoin-Core void
diff -rq kv5/src void/src | wc -l
diff -ru kv5/src void/src | grep "^[+-]" | grep -iv "kvanta5\|voidcoin\|copyright" | wc -l
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
2. THE DEVFUND.H FINDING
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
VoidCoin's ANN states "no dev fund, no team allocation." This is accurate for their chain — block 1 validation was correctly removed from
src/validation.cpp.
However, the file
src/consensus/devfund.h still exists in VoidCoin-Core's repository, unchanged, containing all 21 of the Kvanta5 developer P2QR program hashes verbatim:
{"57bbf8552c15302a447300590136ee2af11d6d7de264e90e6a2fe66120ce421a", ...},
{"82c91b4ef34ae90f2a9e6195e09959c3eecc57d736c220b5a8b4b1216aa03c55", ...},
{"fea9594f3bf310ab9f533f0a81d106c1d57fcc4d6d1760934332793699ec54c7", ...},
... (18 more)
These are the private key derivations of our wallets. They have no effect on VoidCoin's chain since enforcement was removed — but their presence as dead code in the published repository is a verifiable record of the codebase's origin that no amount of rebranding changes.
Check it yourself:
https://github.com/VoidHash-Crypto/VoidCoin-Core/blob/main/src/consensus/devfund.h ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
3. ON THE "NO DEV FUND" NARRATIVE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The framing that "no dev fund" is inherently better deserves examination.
KV5's 21,000,000 KV5 dev fund allocates
25% (5,250,000 KV5) specifically for third-party security audits of the codebase.
VoidCoin has no funding mechanism for security review of any kind. The ML-DSA-87 implementation they shipped — which every VOID holder depends on for quantum resistance — has never been audited by a third party on their behalf. The pqcrystals reference implementation it's based on has been audited externally, but the integration layer, the P2QR consensus rules, and the wallet key derivation have not.
When you hold VOID, you are holding a chain with no budget to verify its own cryptography. When you hold KV5, 25% of the dev fund exists specifically to do that work.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
4. ON REPLAY SAFETY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
To be fair to VoidCoin on one technical point: the sighash domain separation was handled correctly. VoidCoin uses
TaggedHash("VoidCoinP2QRSighash") versus KV5's
TaggedHash("Kvanta5P2QRSighash"). A P2QR signature from one chain cannot be replayed on the other. Cross-chain replay attacks are not a concern.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
5. ON-CHAIN PROOF OF THE ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
KV5 has on-chain milestones that cannot be retroactively replicated on any fork:
Block #283 — 6/2/2026First non-coinbase P2QR spend on any live PoW mainnet.
TXID: `62572d2127da3d42afb0b20757edb844b0820851f4d8340cbc7e26954ae6272c`
Block #21797 — 6/18/20261 → 4,001 P2QR output fanout. 179,323 bytes.
TXID `804b8e7bcea43dbaebe62078f5f28e2df26ceb77a828102c231d598f5634e255`
Block #21798 — 6/18/20264,000 P2QR inputs → 1 output. ~29 MB block.
TXID `9d24c8669da9bcccf05b3eee6cf80a210873ed4a8b5d408da29c64a13c02dbca`
First large-block production proof of the V2_FRAGMENT protocol.
Block #24521 — 6/20/26715,001 P2QR outputs in a single transaction. ~29.34 MB block.
World's largest known post-quantum signed UTXO transaction on any live PoW chain.
TXID `abb67b2c05c965080cc19b6d4dcf23d501888e1d87bf4cf4122a50bcee2e6cf8`
Verifiable:
https://kvanta5.live VoidCoin launched June 29. These milestones are dated on a chain that started June 1. This timeline is permanently recorded on both blockchains.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
KVANTA5 — THE ORIGINAL
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Website: https://www.kvanta5.org/Explorer: https://kvanta5.live/GitHub: https://github.com/Kvanta-Organization/Kvanta5-Core Mainnet since June 1, 2026.
ML-DSA-87 · NIST FIPS 204 · SHA-256d PoW · 32 MB blocks · V2_FRAGMENT
— The Kvanta5 Development Team
