Affiliation disclosure: I am submitting this on behalf of the proposed BlackCoin v30.1.0 “Quantum Quasar” implementation. Project contact: Nick Rogers, @qq_blackcoin.
BlackCoin v30.1.0 directly uses liboqs 0.15.0 and OQS_SIG_alg_ml_dsa_44 for ML-DSA-44 key generation, signing, verification, and startup known-answer/self-tests. The implementation uses ML-DSA witness paths for post-quantum migration outputs and later transaction authorization.
Primary references:
Could OQS please review whether this project is appropriate for the External users of OQS page? A possible neutral entry would be:
BlackCoin v30.1.0: a Bitcoin-derived proof-of-stake implementation using liboqs ML-DSA-44 for staged post-quantum wallet and consensus authorization paths.
Important status and scope disclosures:
- This implementation is a proposed and disputed BlackCoin consensus fork/relaunch; established CoinBlack maintainers dispute its authorization.
- The project’s “quantum” claim work does not form a second header chain or add fork-choice chainwork.
- We are requesting directory inclusion and technical feedback, not endorsement, certification, or a conclusion that the system is quantum-safe.
- We understand and will preserve OQS/liboqs’s production-use and security disclaimers.
- Some project documentation currently has schedule inconsistencies that are being identified for correction; the source code is the implementation reference.
If the preferred contribution path is a pull request instead of an issue, please say so and we will prepare the minimal documentation change.
Affiliation disclosure: I am submitting this on behalf of the proposed BlackCoin v30.1.0 “Quantum Quasar” implementation. Project contact: Nick Rogers, @qq_blackcoin.
BlackCoin v30.1.0 directly uses liboqs 0.15.0 and
OQS_SIG_alg_ml_dsa_44for ML-DSA-44 key generation, signing, verification, and startup known-answer/self-tests. The implementation uses ML-DSA witness paths for post-quantum migration outputs and later transaction authorization.Primary references:
Could OQS please review whether this project is appropriate for the External users of OQS page? A possible neutral entry would be:
Important status and scope disclosures:
If the preferred contribution path is a pull request instead of an issue, please say so and we will prepare the minimal documentation change.