- Post-quantum cryptography solves the security problem and creates a performance one — larger signatures, heavier verification, more state. LithoVM addresses this with native, parallelized verification rather than accepting degraded throughput as the cost of quantum resistance.
Post-quantum cryptography is frequently discussed purely as a security upgrade, and the security case is genuinely strong — ML-DSA, SLH-DSA, and similar algorithms are designed to resist attacks from quantum computers that would break the elliptic-curve cryptography underlying most blockchain networks today. What gets discussed less often is that this security comes at a real performance cost, and that cost is not trivial for a network processing meaningful transaction volume.
Post-quantum signatures and keys are substantially larger than their elliptic-curve equivalents. Where a classical signature might be on the order of 64 to 96 bytes, post-quantum signatures can run into the kilobytes depending on the algorithm and security level. That size difference compounds across every layer of a blockchain network’s operation: block size grows because each transaction carries a larger signature, validator bandwidth requirements increase because larger blocks need to propagate across the network, mempool capacity is affected because pending transactions occupy more memory, and state growth accelerates because more data is being stored per transaction over time.
Verification cost is the other half of the problem. Post-quantum signature verification is generally more computationally expensive than elliptic-curve verification, which means the CPU and memory cost of confirming that a signature is valid increases per transaction. On a network processing thousands of transactions per block, that per-signature cost multiplies into a meaningful aggregate load on every validator that has to verify every transaction in every block it processes.
The naive response to this trade-off is to accept degraded throughput as the price of post-quantum security — process fewer transactions per block, accept slower finality, and treat the performance cost as an unavoidable consequence of stronger cryptography. Lithosphere’s approach through LithoVM is different: rather than accepting the performance hit as a fixed cost, the verification work itself is restructured to absorb it.
LithoVM implements post-quantum verification as native operations — MLDSA_VERIFY, SLHDSA_VERIFY, and HYBRID_VERIFY — rather than treating post-quantum cryptography as an external library call bolted onto the execution environment. Native implementation allows these operations to be optimized specifically for the execution context they run in, with consensus-versioned behavior and predictable gas costs that account for the actual computational load rather than approximating it. On top of the native implementation, LithoVM distributes signature verification across parallel worker pools, allowing multiple post-quantum signatures within a block to be verified concurrently rather than sequentially, while still preserving deterministic results before execution proceeds.
The determinism requirement here is not incidental — it is the hard part of the engineering problem. Parallelizing verification is straightforward if the order in which results arrive is allowed to affect the outcome. It is considerably harder when every validator must arrive at exactly the same result regardless of how the verification work happened to be scheduled across worker threads on their particular hardware. LithoVM’s parallel verification architecture is built to preserve that determinism, meaning the performance gain from parallelization does not come at the cost of the consensus guarantee that every validator processing the same block reaches the same conclusion.
This matters because post-quantum security is only useful if the network remains functional while providing it. A quantum-resistant blockchain that cannot process meaningful transaction volume is not a solution — it is a different problem wearing the first one’s clothing. Lithosphere’s position is that the performance cost of post-quantum cryptography should be engineered down through native, parallel, deterministic verification, not accepted as an inherent trade-off that users have to live with in exchange for security that will eventually be necessary regardless of the performance implications.
