The cryptographic primitives behind Quantova
Security and integrity across Quantova rest on a defined set of cryptographic primitives selected to hold under both classical and quantum analysis. These primitives secure transactions, authenticate nodes and protect state integrity at every layer of the protocol.
Hashing, signatures and authenticated data structures are applied as protocol execution rules, evaluated identically on every node. The reference below states each primitive, its role and how it is enforced within the layered architecture of the network.
| Primitive | Role |
|---|---|
| Hashing | SHA3 256 |
| Account signatures | Falcon, Dilithium, SPHINCS+ |
| State commitment | Merkle trees over SHA3 256 |
| Address binding | Public key pinning |
| Order flow privacy | ML KEM encrypted mempool |
| Standard | NIST approved |
SHA3 256 across identity and integrity
Hash functions establish data integrity, generate unique identifiers for blocks and transactions, and anchor authenticated data structures such as Merkle trees.
Quantova applies SHA3 256 as the single hashing primitive across the protocol. It produces the cryptographic digests used for transaction identity, block linkage, randomness seeds and state commitments. Output size is selected to retain resistance where brute force search can be accelerated under quantum models.
Hashing behaviour is fixed at the protocol level. No smart contract or application can substitute an alternative function or alter how digests are computed, so every participant interprets state identically.
- ✓Cryptographic digests for transactions, blocks and randomness seeds
- ✓Collision and pre image resistance retained under classical and quantum adversaries
- ✓Output size chosen for resistance under accelerated search
- ✓Applied uniformly and fixed at the protocol level
| Property | Detail |
|---|---|
| Function | SHA3 256 |
| Transaction identity | Payload digest |
| Block linkage | Header hash commitments |
| Randomness seeds | SHA3 256 derived |
| Resistance | Collision and pre image |
| Enforcement | Fixed at the protocol |
Post quantum signatures for authorisation
Accounts, validator keys and finality are authorised by NIST approved post quantum signatures, verified inside the QVM before any state transition.
Lattice signatures
Falcon and Dilithium provide compact lattice based signatures for account and validator authorisation, with verification performed before any state change.
Hash based signatures
SPHINCS+ provides a stateless, hash based scheme that rests on no number theoretic assumptions, available across accounts, validator keys and finality.
Public key pinning
An account is bound to the exact key it first signs with. The execution layer rejects any attempt to authorise that account with substituted cryptographic material.
Merkle commitments and state security
Beyond the primary primitives, Quantova applies authenticated data structures that commit to full execution state and make any alteration of historical data immediately evident.
Merkle trees store transaction data so that the full chain state can be verified quickly. Each leaf is the SHA3 256 hash of a transaction, and any change to underlying data changes the root, exposing the alteration.
State roots commit to the complete execution state after each block, anchoring independent verification. Merkle proofs and succinct verification let resource constrained devices check blockchain data without holding the full state.
| Structure | Detail |
|---|---|
| Merkle leaves | SHA3 256 of each transaction |
| Verification | Quick check of full chain state |
| State roots | Commit to execution state per block |
| Tamper evidence | Any change alters the root |
| Light client proofs | Merkle proofs and succinct verification |
ML KEM encrypted mempool
Quantum resistant key exchange protects communications between nodes and pending order flow. An optional encrypted mempool uses ML KEM threshold encryption so transactions are not exposed before inclusion in a block.
The same construction safeguards data in transit between nodes, keeping it confidential and tamper evident during transmission. Post quantum precompiles expose verified cryptographic operations to smart contracts, so applications inherit protocol grade primitives without reimplementing them.
- ✓ML KEM threshold encryption protects pending order flow
- ✓Quantum resistant key exchange for node to node communication
- ✓Pending transactions remain private until inclusion
- ✓Post quantum precompiles available to smart contracts in the QVM
Primitives across the layered architecture
Each primitive is enforced where it matters, from consensus and transactions through networking, storage and light client support.
Signed and verified
Digital signatures and SHA3 256 hashing keep each block and transaction verified and immutable, with verification performed before state execution.
Confidential transport
Quantum resistant key exchange protects communication between nodes, keeping data confidential and tamper evident in transit.
Tamper evident state
Merkle trees and authenticated commitments fortify integrity, so historical data cannot be altered without detection.
Verifiable on small devices
Merkle proofs and succinct verification let resource constrained devices check blockchain data without holding full state.
Enforced in the QVM
The QVM defines which primitives are valid and when verification occurs. Contracts call them but cannot weaken authorisation rules.
NIST approved
Signature schemes and hashing follow NIST approved selections, with classical only constructions excluded from the protocol.
Primitives enforced by the protocol
SHA3 256 hashing, post quantum signatures, Merkle commitments and an encrypted mempool are applied uniformly across all network activity and validated deterministically by the QVM. State transitions become authoritative only after verification and consensus finality, establishing clear accountability boundaries and supporting independent audit.
Owned by Quantova Inc. Released under the Business Source License 1.1.
