{ "review_date": "2026-09-21", "method": "Existing-domain claims plus NIST/FIPS and pinned SPHINCS+ sources. Tables are editorial comparisons, not new SYNX measurements.", "articles": [ { "url": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#bitcoin", "related_entities": [ "https://synxcrypto.com/entity-graph.json#ecdsa-over-secp256k1", "https://synxcrypto.com/entity-graph.json#bitcoin-schnorr-signatures", "https://synxcrypto.com/entity-graph.json#secp256k1", "https://synxcrypto.com/entity-graph.json#shor-s-algorithm", "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "label": "Existing SYNX Bitcoin research and underlying source register" } ], "answers": [ { "id": "signatures", "question": "Can quantum computers break Bitcoin's ECDSA and Schnorr signatures?", "answer": "A sufficiently capable fault-tolerant quantum computer could recover a Bitcoin private key from its exposed public key by solving an elliptic-curve discrete logarithm. Bitcoin's ECDSA and Schnorr signatures both use secp256k1, so changing between those schemes does not remove this threat. Resource estimates describe conditional attacks, not a demonstrated theft from Bitcoin today." }, { "id": "timeline", "question": "How many qubits would a quantum attack on Bitcoin require?", "answer": "A 2026 resource study reports two circuit options for a 256-bit elliptic-curve discrete logarithm: fewer than 1,200 logical qubits with fewer than 90 million Toffoli gates, or fewer than 1,450 logical qubits with fewer than 70 million gates. These are modeled logical resources. Physical-qubit requirements and runtime depend on the error-correction architecture, physical error rate and operation speed." }, { "id": "exposure", "question": "Which Bitcoin outputs expose a public key to a quantum attacker?", "answer": "Bitcoin public-key exposure depends on the output type and what has already been revealed. A Taproot output includes an elliptic-curve public key; some other output types initially commit to a key or script hash. Spending, reuse or disclosure can reveal additional information. An exposure assessment therefore needs the output's history as well as its address format, without collecting private keys or seed phrases." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-over-secp256k1" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-schnorr-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#secp256k1" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#shor-s-algorithm" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "answer_id": "answer-signatures", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "answer_id": "answer-timeline", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php" ], "evidence_label": "source-derived" }, { "file": "articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "answer_id": "answer-exposure", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-upgrades.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-migration", "related_entities": [ "https://synxcrypto.com/entity-graph.json#bitcoin", "https://synxcrypto.com/entity-graph.json#bip-360", "https://synxcrypto.com/entity-graph.json#pay-to-merkle-root-p2mr", "https://synxcrypto.com/entity-graph.json#bip-361", "https://synxcrypto.com/entity-graph.json#post-quantum-signatures" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "label": "Existing SYNX Bitcoin research and underlying source register" } ], "answers": [ { "id": "bip360", "question": "What does BIP 360 change about Bitcoin quantum resistance?", "answer": "BIP 360 proposes Pay-to-Merkle-Root, a Bitcoin output that commits to a script-tree root without Taproot's key-path spending route. Its intended benefit is to reduce long-duration exposure to elliptic-curve key-recovery attacks. BIP 360 does not itself introduce post-quantum signatures. The source was Draft when checked on September 21, 2026." }, { "id": "bip361", "question": "Does BIP 361 set a deadline to move Bitcoin?", "answer": "BIP 361 is a draft migration proposal, not an active deadline for Bitcoin holders. It describes future restrictions on funding quantum-vulnerable outputs and later spending under legacy ECDSA or Schnorr rules. The proposal depends on a future post-quantum-signature BIP. Any timetable must be read together with its activation conditions, unresolved dependencies and the rules actually enforced by the network." }, { "id": "migration", "question": "Why does Bitcoin migration require more than a new signature?", "answer": "Bitcoin migration joins three separate tasks: defining secure spending rules, deploying compatible validation and signing software, and giving existing holders a workable transition. Signature size, verification cost, recovery support and service compatibility affect that transition. Choosing a cryptographic algorithm alone does not resolve how inactive holdings, old devices or outputs using legacy authorization rules will be handled." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-migration" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-upgrades.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-migration" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bip-360" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-upgrades.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-migration" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#pay-to-merkle-root-p2mr" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-upgrades.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-migration" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bip-361" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-upgrades.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-migration" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-upgrades.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/bitcoin-quantum-resistance-upgrades.php", "answer_id": "answer-bip360", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/bitcoin-quantum-resistance-upgrades.php", "answer_id": "answer-bip361", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/bitcoin-quantum-resistance-upgrades.php", "answer_id": "answer-migration", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work-mining", "related_entities": [ "https://synxcrypto.com/entity-graph.json#grover-s-algorithm", "https://synxcrypto.com/entity-graph.json#shor-s-algorithm", "https://synxcrypto.com/entity-graph.json#sha-256", "https://synxcrypto.com/entity-graph.json#bitcoin-mining-asic", "https://synxcrypto.com/entity-graph.json#bitcoin-elliptic-curve-signatures" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "label": "Existing SYNX Bitcoin research and underlying source register" } ], "answers": [ { "id": "mining", "question": "How could Grover's algorithm change Bitcoin mining?", "answer": "Bitcoin mining searches for a candidate block header whose hash satisfies the current proof-of-work target. Grover's algorithm offers a quadratic query advantage for an idealized unstructured search. Turning that advantage into a useful Bitcoin miner requires a reversible hashing circuit, reliable operations and competitive execution time while the network keeps finding blocks. The algorithm alone is not a practical hashrate measurement." }, { "id": "shor", "question": "Why is Shor's algorithm different from quantum Bitcoin mining?", "answer": "Shor's algorithm attacks the discrete-logarithm assumption behind Bitcoin's elliptic-curve signatures, seeking a private key from a known public key. Mining instead seeks a block hash below a target. These tasks have different circuits, inputs and success conditions. A resource estimate for key recovery therefore cannot be read as the specification, hashrate or operating cost of a quantum Bitcoin miner." }, { "id": "asic", "question": "What would prove an advantage over Bitcoin ASIC mining?", "answer": "An advantage over Bitcoin ASIC mining requires evidence about the complete mining workload, not only a qubit count or a small search demonstration. The comparison must state circuit depth, operation time, error-correction overhead, parallel resources, energy and equipment costs, plus the competing network and target assumptions. A profitable result under one model does not establish profitability for available hardware or future difficulty levels." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work-mining" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#grover-s-algorithm" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work-mining" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#shor-s-algorithm" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work-mining" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sha-256" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work-mining" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-mining-asic" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work-mining" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-elliptic-curve-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-computing-bitcoin-mining.php", "answer_id": "answer-mining", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-computing-bitcoin-mining.php", "answer_id": "answer-shor", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-computing-bitcoin-mining.php", "answer_id": "answer-asic", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-resistant-crypto-coins.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#quantum-resistant-cryptocurrency", "related_entities": [ "https://synxcrypto.com/entity-graph.json#synx", "https://synxcrypto.com/entity-graph.json#xmss", "https://synxcrypto.com/entity-graph.json#native-cryptocurrency", "https://synxcrypto.com/entity-graph.json#hosted-token", "https://synxcrypto.com/entity-graph.json#wrapped-asset" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://synxcrypto.com/summaries/28-quantum-resistant-cryptocurrencies-list.php", "label": "Existing domain cryptocurrency classification" }, { "url": "https://csrc.nist.gov/pubs/sp/800/208/final", "label": "NIST SP 800-208 — stateful signatures" } ], "answers": [ { "id": "comparison", "question": "Which quantum-resistant coins have useful technical evidence?", "answer": "SYNX and QRL illustrate two hash-based signing approaches already described on this domain: SYNX specifies SPHINCS+-SHAKE-128s, while the existing coin summary identifies QRL with XMSS. These are documentary classifications, not equivalent implementation certificates. A useful cryptocurrency comparison records the exact asset, signing scheme, active network and recovery requirements, then distinguishes each project statement from independently demonstrated behavior." }, { "id": "categories", "question": "Does a quantum-themed token inherit quantum resistance?", "answer": "A quantum-themed token does not inherit post-quantum protection from its name. Its transfers still depend on the host network, account authorization and contract controls; a wrapped asset adds bridge or custody dependencies. A native post-quantum coin and a representation issued elsewhere therefore require separate evidence records. Compare the transaction path actually used, not just the architecture advertised by an issuer." }, { "id": "state", "question": "How do stateful and stateless signatures change wallet recovery?", "answer": "Stateful hash-based signatures make signing history part of safe operation. NIST SP 800-208 covers stateful schemes including XMSS, while FIPS 205 defines stateless SLH-DSA based on SPHINCS+. Removing the consumed-signing-state requirement does not remove key-loss or malware risk. Wallet recovery must preserve the chosen scheme’s requirements and be tested against the actual implementation, rather than inferred from its quantum label." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistant-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-crypto-coins.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistant-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#xmss" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-crypto-coins.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistant-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#native-cryptocurrency" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-crypto-coins.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistant-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#hosted-token" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-crypto-coins.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistant-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#wrapped-asset" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-crypto-coins.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-resistant-crypto-coins.php", "answer_id": "answer-comparison", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://synxcrypto.com/summaries/28-quantum-resistant-cryptocurrencies-list.php" ], "evidence_label": "project-statement" }, { "file": "articles/quantum-resistant-crypto-coins.php", "answer_id": "answer-categories", "source_urls": [ "https://synxcrypto.com/summaries/28-quantum-resistant-cryptocurrencies-list.php", "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-resistant-crypto-coins.php", "answer_id": "answer-state", "source_urls": [ "https://csrc.nist.gov/pubs/sp/800/208/final", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "standards" } ] }, { "url": "https://synxcrypto.com/articles/quantum-cryptocurrency-explained.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency", "related_entities": [ "https://synxcrypto.com/entity-graph.json#synx", "https://synxcrypto.com/entity-graph.json#kyber-768", "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s", "https://synxcrypto.com/entity-graph.json#post-quantum-key-encapsulation-mechanism", "https://synxcrypto.com/entity-graph.json#stateless-hash-based-digital-signature" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "NIST FIPS 204 — ML-DSA" } ], "answers": [ { "id": "meaning", "question": "What does quantum cryptocurrency mean?", "answer": "Quantum cryptocurrency usually refers to a coin designed to resist quantum attacks, rather than a coin that requires a quantum computer. A post-quantum blockchain can use mathematical algorithms on ordinary hardware. The phrase can also describe quantum-network research or branding. Identify which meaning a project uses before treating its name as evidence about transaction security." }, { "id": "threat", "question": "Why can quantum computing threaten cryptocurrency signatures?", "answer": "Cryptocurrency spending depends on proving authorization, often through a public-key signature. A sufficiently capable quantum computer could undermine common elliptic-curve signature systems, allowing an attacker to forge authorization from exposed public-key information. That is a different problem from decrypting every transaction or accelerating mining. The relevant question is which cryptographic operation protects the funds and what an attacker can observe." }, { "id": "check", "question": "How can you check whether a cryptocurrency is quantum resistant?", "answer": "Check the native network or host chain, the signature used for an ordinary transfer, and the validation rules nodes enforce. Then distinguish a proposed design from a testnet, optional feature or active mainnet rule. Include recovery keys, bridge operators and administrative controls in the review. A protected communication channel alone does not establish post-quantum spending authorization." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-key-encapsulation-mechanism" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#stateless-hash-based-digital-signature" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-explained.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-cryptocurrency-explained.php", "answer_id": "answer-meaning", "source_urls": [ "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/205/final", "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-cryptocurrency-explained.php", "answer_id": "answer-threat", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-cryptocurrency-explained.php", "answer_id": "answer-check", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/72-post-quantum-cryptography-explained.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography", "related_entities": [ "https://synxcrypto.com/entity-graph.json#ml-kem", "https://synxcrypto.com/entity-graph.json#ml-dsa", "https://synxcrypto.com/entity-graph.json#slh-dsa", "https://synxcrypto.com/entity-graph.json#sphincs", "https://synxcrypto.com/entity-graph.json#crystals-kyber" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "NIST FIPS 204 — ML-DSA" }, { "url": "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/README.md", "label": "Pinned SPHINCS+ parameter table" } ], "answers": [ { "id": "standards", "question": "Which post-quantum standards define key encapsulation and signatures?", "answer": "NIST published FIPS 203, FIPS 204 and FIPS 205 on August 13, 2024. They specify ML-KEM for key encapsulation, ML-DSA for digital signatures and SLH-DSA for stateless hash-based signatures. These algorithms address different jobs. Selecting one standard does not validate an entire cryptocurrency, and earlier Kyber or SPHINCS+ names should not be treated as automatic proof of finalized-standard compatibility." }, { "id": "roles", "question": "Why can a post-quantum KEM not replace a transaction signature?", "answer": "A key-encapsulation mechanism establishes a shared secret; a digital signature lets a verifier check a message against a public key. Those are different cryptographic jobs. Protecting a wallet’s communication channel does not change the signature a blockchain requires for spending. A post-quantum design must separately identify its communication protection, transaction authorization and any recovery or administrative signing keys." }, { "id": "migration", "question": "What must change when a blockchain adopts post-quantum signatures?", "answer": "A blockchain migration must connect the chosen signature scheme to transaction encoding, node verification, wallet behavior and activation rules. Developers also need a path for existing keys and funds, plus recovery and rollback handling where relevant. Larger signatures or different verification costs can affect capacity. Adding one algorithm to an application is not evidence that every network authorization path has migrated." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ml-kem" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/72-post-quantum-cryptography-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ml-dsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/72-post-quantum-cryptography-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#slh-dsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/72-post-quantum-cryptography-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/72-post-quantum-cryptography-explained.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#crystals-kyber" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/72-post-quantum-cryptography-explained.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/72-post-quantum-cryptography-explained.php", "answer_id": "answer-standards", "source_urls": [ "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/204/final", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "standards" }, { "file": "articles/72-post-quantum-cryptography-explained.php", "answer_id": "answer-roles", "source_urls": [ "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "standards" }, { "file": "articles/72-post-quantum-cryptography-explained.php", "answer_id": "answer-migration", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/81-qkd-vs-pqc-comparison.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#quantum-key-distribution", "related_entities": [ "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography", "https://synxcrypto.com/entity-graph.json#authentication", "https://synxcrypto.com/entity-graph.json#ml-kem", "https://synxcrypto.com/entity-graph.json#digital-signature" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper — project claims, reviewed September 21, 2026" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203 — ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205 — SLH-DSA" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "NIST FIPS 204 — ML-DSA" }, { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-quantum-cryptography", "label": "NIST — quantum cryptography" }, { "url": "https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=906629", "label": "NIST — authenticated messages in QKD integration" } ], "answers": [ { "id": "comparison", "question": "What is the difference between quantum cryptography and PQC?", "answer": "Quantum cryptography uses quantum physical effects; post-quantum cryptography uses mathematical algorithms intended to resist quantum attacks. Quantum key distribution, or QKD, establishes key material through a suitable physical link. PQC includes software key-encapsulation and signature schemes that run on conventional computers. The right comparison is the protected operation, equipment and trust model, rather than which label sounds more advanced." }, { "id": "authentication", "question": "Why does quantum key distribution still need authentication?", "answer": "Quantum key distribution still needs authenticated communication: exchanging key material does not, by itself, prove the identity of the other endpoint. NIST’s quantum-network integration work describes authentication of QKD messages on the classical channel. Security therefore depends on the complete protocol and its endpoint assumptions, rather than on the presence of a quantum link alone." }, { "id": "blockchain", "question": "Why does QKD not replace a blockchain’s transaction signatures?", "answer": "A public blockchain needs independent nodes to verify transaction authorization without sharing each wallet’s private secret. Digital signatures provide that public-verification function. QKD distributes key material between communication parties and is not, by itself, the same authorization mechanism. Adding a quantum link between selected servers therefore does not automatically replace the spending keys or verification rules used by every wallet." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-key-distribution" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/81-qkd-vs-pqc-comparison.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-key-distribution" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#authentication" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/81-qkd-vs-pqc-comparison.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-key-distribution" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ml-kem" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/81-qkd-vs-pqc-comparison.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-key-distribution" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signature" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/81-qkd-vs-pqc-comparison.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/81-qkd-vs-pqc-comparison.php", "answer_id": "answer-comparison", "source_urls": [ "https://www.nist.gov/cybersecurity-and-privacy/what-quantum-cryptography", "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "source-derived" }, { "file": "articles/81-qkd-vs-pqc-comparison.php", "answer_id": "answer-authentication", "source_urls": [ "https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=906629" ], "evidence_label": "source-derived" }, { "file": "articles/81-qkd-vs-pqc-comparison.php", "answer_id": "answer-blockchain", "source_urls": [ "https://csrc.nist.gov/pubs/fips/204/final", "https://www.nist.gov/cybersecurity-and-privacy/what-quantum-cryptography" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/which-cryptocurrencies-quantum-resistant-from-genesis", "primary_entity": "https://synxcrypto.com/entity-graph.json#quantum-resistance-from-genesis", "related_entities": [ "https://synxcrypto.com/entity-graph.json#synx", "https://synxcrypto.com/entity-graph.json#qrl", "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s", "https://synxcrypto.com/entity-graph.json#xmss", "https://synxcrypto.com/entity-graph.json#consensus-activation-history" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper: project-stated genesis design and signature/KEM roles" }, { "url": "https://synxcrypto.com/articles/103-synx-price-analysis-2026-2030.php", "label": "Existing domain comparison: QRL/XMSS from-genesis classification only" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205: stateless hash-based digital signature standard" } ], "answers": [ { "id": "documented-examples", "question": "Which projects have a documented from-genesis claim here?", "answer": "SYNX’s whitepaper claims quantum resistance from genesis using SPHINCS+-SHAKE-128s signatures and Kyber-768 key encapsulation. This site’s existing comparison also describes QRL’s XMSS signatures as present from genesis. These sources document claims for native networks, not independent checks of their launch history. A hosted token or bridged representation needs a separate assessment of the rules that authorize its transfers." }, { "id": "verify-genesis", "question": "What would independently verify quantum resistance from genesis?", "answer": "Verify a from-genesis claim against the original consensus verifier, subsequent activation rules and historical transaction authorization. Establish whether any accepted spending or recovery path used classical signatures, then match that evidence to the native chain and released software. NIST FIPS 205 defines a stateless signature standard; it does not certify SYNX’s or QRL’s historical deployment. A current specification alone cannot prove every earlier authorization path." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/which-cryptocurrencies-quantum-resistant-from-genesis#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#qrl" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/which-cryptocurrencies-quantum-resistant-from-genesis#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/which-cryptocurrencies-quantum-resistant-from-genesis#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#xmss" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/which-cryptocurrencies-quantum-resistant-from-genesis#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#consensus-activation-history" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/which-cryptocurrencies-quantum-resistant-from-genesis#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-resistant-cryptocurrencies-from-genesis.php", "answer_id": "answer-documented-examples", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://synxcrypto.com/articles/103-synx-price-analysis-2026-2030.php" ], "evidence_label": "project-statement" }, { "file": "articles/quantum-resistant-cryptocurrencies-from-genesis.php", "answer_id": "answer-verify-genesis", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/sphincs-plus-vs-dilithium-layer-1", "primary_entity": "https://synxcrypto.com/entity-graph.json#sphincs-versus-dilithium-for-layer-1-blockchains", "related_entities": [ "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s", "https://synxcrypto.com/entity-graph.json#ml-dsa", "https://synxcrypto.com/entity-graph.json#slh-dsa", "https://synxcrypto.com/entity-graph.json#transaction-signature", "https://synxcrypto.com/entity-graph.json#synx" ], "review_date": "2026-09-21", "sources": [ { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "NIST FIPS 204: ML-DSA standard and current errata notice" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205: SLH-DSA and its SPHINCS+ basis" }, { "url": "https://www.nist.gov/news-events/news/2024/08/nist-releases-first-3-finalized-post-quantum-encryption-standards", "label": "NIST standards announcement: CRYSTALS-Dilithium to ML-DSA" }, { "url": "https://raw.githubusercontent.com/sphincs/sphincsplus/7ec789ace6874d875f4bb84cb61b81155398167e/README.md", "label": "SPHINCS+ revision 7ec789a: 128s raw parameter sizes" }, { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper: stated SPHINCS+-SHAKE-128s/Kyber-768 roles" } ], "answers": [ { "id": "design-differences", "question": "What changes when a blockchain chooses SPHINCS+ instead of Dilithium?", "answer": "SPHINCS+ is stateless and hash-based; Dilithium is module-lattice-based and underlies ML-DSA. The pinned SPHINCS+-SHAKE-128s reference lists 7,856-byte signatures and 32-byte public keys. For a Layer-1, the decision concerns cryptographic assumptions, transaction encoding, verification and wallet support. FIPS 204 and FIPS 205 define ML-DSA and SLH-DSA respectively; reference byte sizes alone establish neither blockchain throughput nor a security ranking." }, { "id": "synx-choice", "question": "What does SYNX publicly specify, and what still needs measurement?", "answer": "SYNX’s whitepaper specifies SPHINCS+-SHAKE-128s signatures and Kyber-768 key encapsulation. The pinned SPHINCS+ reference supplies raw parameter sizes, not SYNX release measurements. Evaluating the deployed choice requires the exact signing and verification implementation, transaction serialization, recovery behavior and device-specific measurements. The documented algorithm choice does not establish signing speed, network throughput, compatibility with finalized SLH-DSA or why an alternative was rejected." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-versus-dilithium-for-layer-1-blockchains" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/sphincs-plus-vs-dilithium-layer-1#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-versus-dilithium-for-layer-1-blockchains" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ml-dsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/sphincs-plus-vs-dilithium-layer-1#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-versus-dilithium-for-layer-1-blockchains" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#slh-dsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/sphincs-plus-vs-dilithium-layer-1#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-versus-dilithium-for-layer-1-blockchains" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#transaction-signature" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/sphincs-plus-vs-dilithium-layer-1#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-versus-dilithium-for-layer-1-blockchains" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/sphincs-plus-vs-dilithium-layer-1#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/sphincs-plus-vs-dilithium-layer-1.php", "answer_id": "answer-design-differences", "source_urls": [ "https://csrc.nist.gov/pubs/fips/204/final", "https://csrc.nist.gov/pubs/fips/205/final", "https://raw.githubusercontent.com/sphincs/sphincsplus/7ec789ace6874d875f4bb84cb61b81155398167e/README.md" ], "evidence_label": "source-derived" }, { "file": "articles/sphincs-plus-vs-dilithium-layer-1.php", "answer_id": "answer-synx-choice", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://raw.githubusercontent.com/sphincs/sphincsplus/7ec789ace6874d875f4bb84cb61b81155398167e/README.md" ], "evidence_label": "project-statement" } ] }, { "url": "https://synxcrypto.com/harvest-now-decrypt-later-bitcoin-ethereum", "primary_entity": "https://synxcrypto.com/entity-graph.json#harvest-now-decrypt-later", "related_entities": [ "https://synxcrypto.com/entity-graph.json#bitcoin", "https://synxcrypto.com/entity-graph.json#ethereum", "https://synxcrypto.com/entity-graph.json#ciphertext-confidentiality", "https://synxcrypto.com/entity-graph.json#digital-signature-forgery", "https://synxcrypto.com/entity-graph.json#post-quantum-key-encapsulation" ], "review_date": "2026-09-21", "sources": [ { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "label": "NIST: HNDL concerns captured encrypted data" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203: key encapsulation and shared secrets" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "NIST FIPS 204: the digital-signature function" }, { "url": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "label": "Existing Bitcoin article: public-key exposure and signature risk" }, { "url": "https://synxcrypto.com/is-ethereum-quantum-safe-2026.php", "label": "Existing Ethereum page: public ledger and signature inventory only" }, { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper: project-specified signature and key-encapsulation roles" } ], "answers": [ { "id": "meaning", "question": "Does harvest-now-decrypt-later mean decrypting Bitcoin or Ethereum?", "answer": "Harvest-now-decrypt-later means recording encrypted information now to recover its plaintext if future capabilities break the protection. Ordinary Bitcoin and Ethereum ledger records are already public, so reading them is not decryption. Their exposed signing public keys create a different potential quantum threat: private-key recovery followed by forged authorization. Captured wallet communications and blockchain spending rights therefore require separate threat assessments." }, { "id": "separate-risks", "question": "How should a wallet distinguish decryption risk from signature risk?", "answer": "For Bitcoin or Ethereum wallet traffic, identify what is encrypted, the key-establishment scheme and the required secrecy lifetime. For spending authority, identify the signature scheme, public-key exposure and network migration rules. FIPS 203 addresses shared-secret establishment; FIPS 204 addresses digital signatures. Protecting communications with a post-quantum KEM does not replace a vulnerable spending signature, and a signature does not conceal public ledger data." } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#harvest-now-decrypt-later" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/harvest-now-decrypt-later-bitcoin-ethereum#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#harvest-now-decrypt-later" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ethereum" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/harvest-now-decrypt-later-bitcoin-ethereum#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#harvest-now-decrypt-later" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ciphertext-confidentiality" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/harvest-now-decrypt-later-bitcoin-ethereum#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#harvest-now-decrypt-later" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signature-forgery" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/harvest-now-decrypt-later-bitcoin-ethereum#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#harvest-now-decrypt-later" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-key-encapsulation" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/harvest-now-decrypt-later-bitcoin-ethereum#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/harvest-now-decrypt-later-bitcoin-ethereum.php", "answer_id": "answer-meaning", "source_urls": [ "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "https://synxcrypto.com/is-ethereum-quantum-safe-2026.php" ], "evidence_label": "source-derived" }, { "file": "articles/harvest-now-decrypt-later-bitcoin-ethereum.php", "answer_id": "answer-separate-risks", "source_urls": [ "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-computing-bitcoin-evidence-matrix.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-risk-evidence", "related_entities": [ "https://synxcrypto.com/entity-graph.json#ecdsa", "https://synxcrypto.com/entity-graph.json#secp256k1", "https://synxcrypto.com/entity-graph.json#shor-s-algorithm", "https://synxcrypto.com/entity-graph.json#logical-qubits", "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "label": "SYNX: Bitcoin ECDSA quantum-risk discussion" }, { "url": "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "label": "SYNX: logical and physical qubit discussion" }, { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "label": "NIST: post-quantum cryptography and hardware uncertainty" } ], "answers": [ { "id": "classify", "question": "What evidence belongs behind a Bitcoin quantum-risk claim?", "answer": "A Bitcoin quantum-risk claim should identify the task being attacked, the public information available and the kind of evidence supplied. A mathematical algorithm, resource estimate, hardware demonstration and observed network event establish different things. Record which one the source provides before using it to support a claim about private-key recovery, spending authorization or the timing of a future attack.", "detail_html": "

The SYNX qubit discussion distinguishes logical and physical resources. NIST explains the uncertainty surrounding cryptographically relevant hardware. This matrix is an editorial classification of evidence, not an attack experiment.

" }, { "id": "quote", "question": "How should a Bitcoin quantum-risk citation preserve its limits?", "answer": "A useful citation carries the source's assumptions into the sentence that cites it. Keep the task, resource model and required capability together; distinguish a projection from an observation. If the source evaluates an exposed public key, do not silently extend the conclusion to every output, all transaction history or an entire network's consensus security.", "detail_html": "

Write down the source title, revision and checked date beside the classified claim. If a field is missing, label it unspecified rather than filling the gap with an inference presented as a measurement.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-risk-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-evidence-matrix.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-risk-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#secp256k1" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-evidence-matrix.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-risk-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#shor-s-algorithm" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-evidence-matrix.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-risk-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#logical-qubits" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-evidence-matrix.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-risk-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-evidence-matrix.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-computing-bitcoin-evidence-matrix.php", "answer_id": "answer-classify", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-computing-bitcoin-evidence-matrix.php", "answer_id": "answer-quote", "source_urls": [ "https://synxcrypto.com/articles/123-how-many-qubits-to-break-bitcoin-secp256k1.php", "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-resistant-cryptocurrency-genesis-evidence.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#evidence-for-quantum-resistance-from-genesis", "related_entities": [ "https://synxcrypto.com/entity-graph.json#blockchain-genesis", "https://synxcrypto.com/entity-graph.json#transaction-authorization", "https://synxcrypto.com/entity-graph.json#digital-signatures", "https://synxcrypto.com/entity-graph.json#software-release-provenance" ], "review_date": "2026-09-21", "sources": [ { "url": "https://csrc.nist.gov/pubs/ir/8202/final", "label": "NIST IR 8202: Blockchain Technology Overview" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "FIPS 204: purpose of digital signatures" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "FIPS 205: SLH-DSA standard and SPHINCS+ relationship" } ], "answers": [ { "id": "launch-evidence", "question": "What evidence supports quantum resistance from genesis?", "answer": "A defensible genesis claim connects an identified network to its launch-era transaction-verification rules. Record the launch source revision, exact signature algorithm and parameters, and the authorization paths that revision accepted. Then trace subsequent rule changes. A genesis identifier locates the chain being discussed; a current wallet description alone cannot establish what the network enforced at launch.", "detail_html": "

This is our evidence-checking method, not a certification checklist issued by NIST. NIST’s blockchain overview supplies the ledger context; FIPS 204 explains the distinct role of a digital signature.

" }, { "id": "bounded-claim", "question": "How should a genesis claim state its limits?", "answer": "State the network, period, authorization paths and source revisions covered by the evidence. Separate the claim about launch rules from any claim about today’s downloadable release. If a legacy, recovery or administrative path exists, record its rules separately. A standards reference identifies an algorithm; it does not establish a cryptocurrency’s deployment history or the contents of its binaries.", "detail_html": "

Record format: Network [identifier]; launch rules [revision]; signature [algorithm and parameters]; covered paths [list]; later changes [references]; release checked [identifier]; evidence gaps [list]. Leave an unverified field explicit instead of filling it from a marketing label.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#evidence-for-quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#blockchain-genesis" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-cryptocurrency-genesis-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#evidence-for-quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#transaction-authorization" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-cryptocurrency-genesis-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#evidence-for-quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-cryptocurrency-genesis-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#evidence-for-quantum-resistance-from-genesis" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#software-release-provenance" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-resistant-cryptocurrency-genesis-evidence.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-resistant-cryptocurrency-genesis-evidence.php", "answer_id": "answer-launch-evidence", "source_urls": [ "https://csrc.nist.gov/pubs/ir/8202/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-resistant-cryptocurrency-genesis-evidence.php", "answer_id": "answer-bounded-claim", "source_urls": [ "https://csrc.nist.gov/pubs/ir/8202/final", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-cryptocurrency-terminology-reference.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency-terminology", "related_entities": [ "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography", "https://synxcrypto.com/entity-graph.json#key-encapsulation", "https://synxcrypto.com/entity-graph.json#digital-signatures", "https://synxcrypto.com/entity-graph.json#slh-dsa", "https://synxcrypto.com/entity-graph.json#sphincs" ], "review_date": "2026-09-21", "sources": [ { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "label": "NIST: What Is Post-Quantum Cryptography?" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "FIPS 203: ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "FIPS 204: ML-DSA" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "FIPS 205: SLH-DSA" }, { "url": "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/ref/params/params-sphincs-shake-128s.h", "label": "Pinned upstream SHAKE-128s parameters" }, { "url": "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/README.md", "label": "Pinned upstream SPHINCS+ README" }, { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-quantum-cryptography", "label": "NIST: What Is Quantum Cryptography?" } ], "answers": [ { "id": "precise-names", "question": "Which names make a quantum cryptocurrency claim precise?", "answer": "A useful claim names the cryptographic operation before naming its algorithm. Distinguish a signature that supports public verification from a key-encapsulation mechanism that establishes shared secret material. Add the parameter set and source version. “Quantum cryptocurrency” alone supplies none of those identifiers; use the linked definitions to turn the phrase into a claim that can be checked.", "detail_html": "

The lookup table points to controlling publications or upstream source files. It is a terminology aid, not a list of approved cryptocurrencies.

" }, { "id": "name-relationship", "question": "Can SPHINCS+ and SLH-DSA be used as interchangeable names?", "answer": "Record the name the implementation actually claims. FIPS 205 specifies SLH-DSA and states that it is based on SPHINCS+. That relationship does not let a reader infer finalized-standard compatibility from the earlier family name alone. A precise reference pairs the claimed algorithm with its parameter set, source revision and any separately established conformance evidence.", "detail_html": "

For a source record, retain both the implementation’s literal name and the relevant standard’s name. The pinned SPHINCS+ README is a source for upstream parameter labels, not a certificate for a product.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency-terminology" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-terminology-reference.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency-terminology" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#key-encapsulation" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-terminology-reference.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency-terminology" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-terminology-reference.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency-terminology" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#slh-dsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-terminology-reference.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-cryptocurrency-terminology" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptocurrency-terminology-reference.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-cryptocurrency-terminology-reference.php", "answer_id": "answer-precise-names", "source_urls": [ "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/204/final", "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/ref/params/params-sphincs-shake-128s.h" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-cryptocurrency-terminology-reference.php", "answer_id": "answer-name-relationship", "source_urls": [ "https://csrc.nist.gov/pubs/fips/205/final", "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/README.md" ], "evidence_label": "source-derived" } ] }, { "url": "https://synxcrypto.com/articles/quantum-crypto-coins-asset-evidence.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#asset-identity-in-quantum-crypto-coin-comparisons", "related_entities": [ "https://synxcrypto.com/entity-graph.json#native-cryptocurrency", "https://synxcrypto.com/entity-graph.json#hosted-token", "https://synxcrypto.com/entity-graph.json#blockchain-bridge", "https://synxcrypto.com/entity-graph.json#transaction-authorization" ], "review_date": "2026-09-21", "sources": [ { "url": "https://csrc.nist.gov/pubs/ir/8202/final", "label": "NIST IR 8202: Blockchain Technology Overview" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "FIPS 204: digital-signature function" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "FIPS 203: key-encapsulation function" } ], "answers": [ { "id": "asset-identity", "question": "What should a quantum crypto coin evidence record identify?", "answer": "Record the exact asset and transfer route: a native coin’s network, a hosted token’s network and contract identifier, or a wrapped asset’s origin, destination and bridge. Then identify the rules that authorize movement on that route. A ticker or project name can conceal these differences, so it cannot serve as the complete identity of the asset being assessed.", "detail_html": "

This is our comparison worksheet. NIST’s blockchain overview provides the ledger context; the digital-signature standard provides the authorization primitive’s role. Neither publication rates particular coins.

" }, { "id": "scoped-conclusion", "question": "How should the conclusion handle a token or bridge dependency?", "answer": "Write the conclusion at the same scope as the evidence. Native-chain signature evidence describes that chain’s authorization rules; it does not automatically describe a representation on another chain. For a token, inspect the applicable host-chain and contract controls. For a wrapped asset, add the bridge’s release or minting rules and any custody arrangements that actually apply.", "detail_html": "

A missing bridge or contract record is an unanswered dependency. Preserve it as a separate field so a reader can tell which part of the transfer route has evidence and which part still needs examination.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#asset-identity-in-quantum-crypto-coin-comparisons" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#native-cryptocurrency" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-crypto-coins-asset-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#asset-identity-in-quantum-crypto-coin-comparisons" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#hosted-token" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-crypto-coins-asset-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#asset-identity-in-quantum-crypto-coin-comparisons" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#blockchain-bridge" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-crypto-coins-asset-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#asset-identity-in-quantum-crypto-coin-comparisons" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#transaction-authorization" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-crypto-coins-asset-evidence.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-crypto-coins-asset-evidence.php", "answer_id": "answer-asset-identity", "source_urls": [ "https://csrc.nist.gov/pubs/ir/8202/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-crypto-coins-asset-evidence.php", "answer_id": "answer-scoped-conclusion", "source_urls": [ "https://csrc.nist.gov/pubs/ir/8202/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s-parameter-provenance", "related_entities": [ "https://synxcrypto.com/entity-graph.json#sphincs", "https://synxcrypto.com/entity-graph.json#shake-128s", "https://synxcrypto.com/entity-graph.json#digital-signatures", "https://synxcrypto.com/entity-graph.json#slh-dsa" ], "review_date": "2026-09-21", "sources": [ { "url": "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/README.md", "label": "Pinned upstream SPHINCS+ parameter table" }, { "url": "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/ref/params/params-sphincs-shake-128s.h", "label": "Pinned upstream SHAKE-128s parameter header" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "FIPS 205: SLH-DSA and its SPHINCS+ basis" } ], "answers": [ { "id": "published-parameters", "question": "What does the pinned SHAKE-128s source record establish?", "answer": "At the pinned upstream revision, the SPHINCS+-128s README row lists a 32-byte public key, a 64-byte secret key and a 7,856-byte signature. The SHAKE-128s header supplies the matching parameter configuration. These are published raw object sizes for that source configuration; they are not measurements of a SYNX wallet, compressed storage or a serialized blockchain transaction.", "detail_html": "

Revision: 7ec789ace6874d875f4bb84cb61b81155398167e. Checked September 21, 2026. The README table and SHAKE-specific header are both pinned to this revision.

" }, { "id": "reproduce-record", "question": "How can another reader check the parameter record?", "answer": "Retrieve the pinned README and SHAKE-128s header, compare their parameter values, and retain the revision with the result. The companion reproduction record also stores source digests and checks the size entries. This is a source-derived verification of published values. It does not execute the signing implementation, validate a wallet binary or explain why a project selected this parameter set.", "detail_html": "

Companion records: source digests and calculation results and reproduction script. For the standardized descendant’s specification, consult FIPS 205 / SLH-DSA; an upstream name alone does not establish conformance.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s-parameter-provenance" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s-parameter-provenance" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#shake-128s" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s-parameter-provenance" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s-parameter-provenance" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#slh-dsa" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/sphincs-shake-128s-parameter-source.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/sphincs-shake-128s-parameter-source.php", "answer_id": "answer-published-parameters", "source_urls": [ "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/README.md", "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/ref/params/params-sphincs-shake-128s.h" ], "evidence_label": "source-derived" }, { "file": "articles/sphincs-shake-128s-parameter-source.php", "answer_id": "answer-reproduce-record", "source_urls": [ "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/README.md", "https://github.com/sphincs/sphincsplus/blob/7ec789ace6874d875f4bb84cb61b81155398167e/ref/params/params-sphincs-shake-128s.h" ], "evidence_label": "source-derived" } ] }, { "url": "https://synxcrypto.com/articles/quantum-blockchain-authorization-map.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#post-quantum-blockchain-authorization", "related_entities": [ "https://synxcrypto.com/entity-graph.json#key-encapsulation-mechanisms", "https://synxcrypto.com/entity-graph.json#digital-signatures", "https://synxcrypto.com/entity-graph.json#consensus-rules", "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s", "https://synxcrypto.com/entity-graph.json#kyber-768" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper: specified algorithm roles" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "NIST FIPS 203: key encapsulation" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205: digital signatures" } ], "answers": [ { "id": "dependencies", "question": "Which dependencies belong in a quantum-blockchain authorization map?", "answer": "A post-quantum blockchain authorization map should identify transaction signatures, key establishment, validation rules and recovery dependencies separately. A key-encapsulation mechanism establishes a shared secret; a signature authenticates signed data. Neither algorithm label alone specifies the blockchain's consensus rules or proves that every path to spending authority has the claimed protection. Map each role to the evidence that supports it.", "detail_html": "

FIPS 203 defines the KEM role; FIPS 205 defines a stateless hash-based signature standard. These standards establish cryptographic roles, not a complete blockchain architecture.

" }, { "id": "project", "question": "How should SYNX be represented in that dependency map?", "answer": "Represent SYNX using the roles its published whitepaper assigns: SPHINCS+-SHAKE-128s for signatures and Kyber-768 for key encapsulation. Label these as project specifications. Keep network validation and recovery as separate entries, and distinguish documentation from evidence about a particular release. The presence of an algorithm name in the map is not an independent conformance or implementation assessment.", "detail_html": "

The SYNX whitepaper is the source of those project design statements. A standards reference and a project specification answer different questions, so the table keeps their evidence boundaries visible.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-blockchain-authorization" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#key-encapsulation-mechanisms" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-blockchain-authorization-map.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-blockchain-authorization" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-blockchain-authorization-map.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-blockchain-authorization" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#consensus-rules" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-blockchain-authorization-map.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-blockchain-authorization" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-blockchain-authorization-map.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-blockchain-authorization" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-blockchain-authorization-map.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-blockchain-authorization-map.php", "answer_id": "answer-dependencies", "source_urls": [ "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/205/final", "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-blockchain-authorization-map.php", "answer_id": "answer-project", "source_urls": [ "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "project-statement" } ] }, { "url": "https://synxcrypto.com/articles/can-quantum-computers-break-bitcoin-key-exposure.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#bitcoin-public-key-exposure", "related_entities": [ "https://synxcrypto.com/entity-graph.json#bitcoin-outputs", "https://synxcrypto.com/entity-graph.json#public-keys", "https://synxcrypto.com/entity-graph.json#private-keys", "https://synxcrypto.com/entity-graph.json#transaction-signatures", "https://synxcrypto.com/entity-graph.json#shor-s-algorithm" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "label": "SYNX: public-key exposure and Bitcoin signing" }, { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "label": "NIST: conditions and uncertainty of the quantum threat" } ], "answers": [ { "id": "inventory", "question": "Which information belongs in a Bitcoin key-exposure inventory?", "answer": "A Bitcoin key-exposure inventory records the output being assessed, its spending history and any known disclosure of the relevant public key or script. It should distinguish observed evidence from assumptions about an address format. Public information can support an exposure assessment; a private key or seed phrase is not needed to explain that assessment and should not be collected for it.", "detail_html": "

The live SYNX Bitcoin discussion connects exposure with public keys and prior spending. Use the inventory below as a record of evidence, not as an automated verdict that a balance is safe or vulnerable.

" }, { "id": "prerequisites", "question": "Does public-key exposure prove a usable quantum attack?", "answer": "Public-key exposure supplies potential input to a key-recovery attack; it does not demonstrate that the attack can be completed. A claim of usable quantum theft would also need evidence of sufficient computation, recovery of the relevant spending authority and a transaction accepted under the applicable network rules. Keep those prerequisites separate when reporting an exposure finding.", "detail_html": "

NIST distinguishes the quantum threat from the uncertain arrival of capable hardware. The attack prerequisites here are a way to qualify a claim, not a prediction of when an attack will occur.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-public-key-exposure" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-outputs" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/can-quantum-computers-break-bitcoin-key-exposure.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-public-key-exposure" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#public-keys" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/can-quantum-computers-break-bitcoin-key-exposure.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-public-key-exposure" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#private-keys" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/can-quantum-computers-break-bitcoin-key-exposure.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-public-key-exposure" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#transaction-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/can-quantum-computers-break-bitcoin-key-exposure.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-public-key-exposure" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#shor-s-algorithm" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/can-quantum-computers-break-bitcoin-key-exposure.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/can-quantum-computers-break-bitcoin-key-exposure.php", "answer_id": "answer-inventory", "source_urls": [ "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/can-quantum-computers-break-bitcoin-key-exposure.php", "answer_id": "answer-prerequisites", "source_urls": [ "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-status-checklist.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-claim-status", "related_entities": [ "https://synxcrypto.com/entity-graph.json#post-quantum-signatures", "https://synxcrypto.com/entity-graph.json#bitcoin-consensus-rules", "https://synxcrypto.com/entity-graph.json#wallet-software", "https://synxcrypto.com/entity-graph.json#network-activation", "https://synxcrypto.com/entity-graph.json#holder-migration" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "label": "SYNX: Bitcoin signature replacement and migration discussion" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "NIST FIPS 205: signature algorithm scope" }, { "url": "https://www.nist.gov/news-events/news/2024/08/nist-releases-first-3-finalized-post-quantum-encryption-standards", "label": "NIST: finalized post-quantum standards" } ], "answers": [ { "id": "claim-record", "question": "What must a Bitcoin quantum-resistance claim identify?", "answer": "A Bitcoin quantum-resistance claim should identify the affected spending rules, the network and the software release being discussed. It should then show whether the claim concerns a proposal, an implementation, active network rules or a completed holder migration. Naming a post-quantum algorithm establishes none of those deployment stages by itself; each stage needs evidence with a defined scope.", "detail_html": "

NIST FIPS 205 specifies a signature algorithm. Its publication is not a notice that Bitcoin has changed its transaction rules. The distinction between a cryptographic specification and a network deployment is the organizing principle of this checklist.

" }, { "id": "status-labels", "question": "How should Draft and deployment claims be reported?", "answer": "Report a Draft as a proposal under development, with the source date and any stated dependencies. Report implementation or deployment only for the exact software and network supported by the evidence. A test, release announcement or migration plan should retain that narrower label until the source establishes the broader claim being made about holders' spending protection.", "detail_html": "

This reference assigns no current status to an individual Bitcoin proposal. It supplies fields for recording a status check; the linked upgrade explainer discusses the proposal-specific evidence.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-claim-status" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-status-checklist.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-claim-status" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-consensus-rules" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-status-checklist.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-claim-status" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#wallet-software" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-status-checklist.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-claim-status" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#network-activation" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-status-checklist.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-quantum-resistance-claim-status" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#holder-migration" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/bitcoin-quantum-resistance-status-checklist.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/bitcoin-quantum-resistance-status-checklist.php", "answer_id": "answer-claim-record", "source_urls": [ "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php", "https://csrc.nist.gov/pubs/fips/205/final" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/bitcoin-quantum-resistance-status-checklist.php", "answer_id": "answer-status-labels", "source_urls": [ "https://synxcrypto.com/articles/02-when-will-quantum-computers-break-bitcoin-ecdsa.php" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining-evidence.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#quantum-bitcoin-mining-benchmark-evidence", "related_entities": [ "https://synxcrypto.com/entity-graph.json#grover-s-algorithm", "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work", "https://synxcrypto.com/entity-graph.json#asic-mining", "https://synxcrypto.com/entity-graph.json#error-correction", "https://synxcrypto.com/entity-graph.json#mining-economics" ], "review_date": "2026-09-21", "sources": [ { "url": "https://synxcrypto.com/whitepaper.php", "label": "SYNX whitepaper: cryptographic roles and consensus design" }, { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography", "label": "NIST: quantum computation and cryptographic capability" } ], "answers": [ { "id": "benchmark", "question": "What must a quantum Bitcoin mining benchmark disclose?", "answer": "A quantum Bitcoin mining benchmark should disclose the mining task actually executed, its success condition and the execution environment. It should distinguish measured hardware results from simulation or a resource model, then identify the target and competing-work assumptions. A reported search advantage becomes a mining comparison only when the complete workload and relevant operating conditions are stated.", "detail_html": "

The SYNX whitepaper treats signing and consensus as separate protocol roles. This checklist applies that separation to evidence: an algorithm result or signature measurement cannot silently become a Bitcoin mining-performance result.

" }, { "id": "compare", "question": "When can two mining results be compared fairly?", "answer": "Two mining results are comparable only to the extent that their workloads, success conditions and accounting boundaries match. Record what was measured, what was modeled and which costs were omitted. A speed claim does not establish an economic advantage unless it also states the relevant equipment, operating and network assumptions; unknown inputs should remain unknown rather than become a profitability estimate.", "detail_html": "

Use the table as a reporting form. It contains no measured SYNX or quantum-miner results and assigns no performance score to a project or device.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-bitcoin-mining-benchmark-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#grover-s-algorithm" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-bitcoin-mining-benchmark-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#bitcoin-proof-of-work" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-bitcoin-mining-benchmark-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#asic-mining" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-bitcoin-mining-benchmark-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#error-correction" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining-evidence.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-bitcoin-mining-benchmark-evidence" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#mining-economics" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-computing-bitcoin-mining-evidence.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-computing-bitcoin-mining-evidence.php", "answer_id": "answer-benchmark", "source_urls": [ "https://synxcrypto.com/whitepaper.php", "https://www.nist.gov/cybersecurity-and-privacy/what-post-quantum-cryptography" ], "evidence_label": "editorial-synthesis" }, { "file": "articles/quantum-computing-bitcoin-mining-evidence.php", "answer_id": "answer-compare", "source_urls": [ "https://synxcrypto.com/whitepaper.php" ], "evidence_label": "editorial-synthesis" } ] }, { "url": "https://synxcrypto.com/articles/quantum-cryptography-pqc-claim-classifier.php", "primary_entity": "https://synxcrypto.com/entity-graph.json#classification-of-qkd-and-post-quantum-cryptography-claims", "related_entities": [ "https://synxcrypto.com/entity-graph.json#quantum-key-distribution", "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography", "https://synxcrypto.com/entity-graph.json#key-encapsulation", "https://synxcrypto.com/entity-graph.json#digital-signatures" ], "review_date": "2026-09-21", "sources": [ { "url": "https://www.nist.gov/cybersecurity-and-privacy/what-quantum-cryptography", "label": "NIST: What Is Quantum Cryptography?" }, { "url": "https://csrc.nist.gov/pubs/fips/203/final", "label": "FIPS 203: ML-KEM" }, { "url": "https://csrc.nist.gov/pubs/fips/204/final", "label": "FIPS 204: ML-DSA" }, { "url": "https://csrc.nist.gov/pubs/fips/205/final", "label": "FIPS 205: SLH-DSA" } ], "answers": [ { "id": "classify-operation", "question": "Which details distinguish a QKD claim from a PQC claim?", "answer": "Ask what the system uses and what it produces. A QKD claim describes quantum signals and equipment used to establish shared key material. A post-quantum KEM describes an algorithmic shared-secret operation. A post-quantum signature describes signing and verification with public and private keys. These operational details are more informative than a product’s use of the word “quantum.”", "detail_html": "

NIST’s quantum cryptography overview identifies QKD as one example within a broader field. The table classifies these common claims; it does not treat QKD as the whole of quantum cryptography.

" }, { "id": "authorization-test", "question": "When does a claim provide evidence about blockchain authorization?", "answer": "A claim concerns blockchain authorization when it identifies the signed transaction data and the verification rules that the network enforces. Evidence about a protected communication link or established shared secret addresses another operation. To connect either claim to spending security, request the actual authorization scheme, its parameters and its deployed verifier rather than inferring them from the channel technology.", "detail_html": "

The distinction follows the separate operations specified by FIPS 203 and FIPS 204. Our classification applies that distinction to the scope of a cryptocurrency claim; it does not evaluate any particular QKD product.

" } ], "entity_relationships": [ { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#classification-of-qkd-and-post-quantum-cryptography-claims" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#quantum-key-distribution" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptography-pqc-claim-classifier.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#classification-of-qkd-and-post-quantum-cryptography-claims" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#post-quantum-cryptography" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptography-pqc-claim-classifier.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#classification-of-qkd-and-post-quantum-cryptography-claims" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#key-encapsulation" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptography-pqc-claim-classifier.php#article" } }, { "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#classification-of-qkd-and-post-quantum-cryptography-claims" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#examined-with" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#digital-signatures" }, "synxrel:evidence": { "@id": "https://synxcrypto.com/articles/quantum-cryptography-pqc-claim-classifier.php#article" } } ], "project_claims": [ { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-1", "text": "SYNX — uses → Kyber-768 for key encapsulation, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#kyber-768" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-2", "text": "SYNX — uses → SPHINCS+-SHAKE-128s for signatures, according to its published whitepaper.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#uses" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#sphincs-shake-128s" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." }, { "@type": "Claim", "@id": "https://synxcrypto.com/entity-graph.json#synx-relationship-3", "text": "The SYNX whitepaper contrasts its project-stated post-quantum signature design with ECDSA-based Layer-1 authorization.", "about": [ { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" } ], "citation": { "@type": "CreativeWork", "url": "https://synxcrypto.com/whitepaper.php" }, "dateModified": "2026-09-21", "synxrel:subject": { "@id": "https://synxcrypto.com/entity-graph.json#synx" }, "synxrel:predicate": { "@id": "https://synxcrypto.com/research/relationships.html#contrasts" }, "synxrel:object": { "@id": "https://synxcrypto.com/entity-graph.json#ecdsa-l1" }, "synxrel:qualification": "Project-stated roles, reviewed September 21, 2026; no independent release certification, timing result or universal security ranking is asserted." } ], "method": "Editorial comparison of existing domain claims, NIST/FIPS and pinned SPHINCS+ source files; no SYNX laboratory or historical engineering record is asserted.", "answer_provenance": [ { "file": "articles/quantum-cryptography-pqc-claim-classifier.php", "answer_id": "answer-classify-operation", "source_urls": [ "https://www.nist.gov/cybersecurity-and-privacy/what-quantum-cryptography", "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "source-derived" }, { "file": "articles/quantum-cryptography-pqc-claim-classifier.php", "answer_id": "answer-authorization-test", "source_urls": [ "https://csrc.nist.gov/pubs/fips/203/final", "https://csrc.nist.gov/pubs/fips/204/final" ], "evidence_label": "editorial-synthesis" } ] } ] }