Post-quantum cryptography usually means learning a new language or a new execution model. Lithosphere is building EVM precompiles for post-quantum verification so Solidity developers can write quantum-resistant smart accounts, multisigs, and treasuries using the tools they already know.
The EVM ecosystem is the largest base of smart contract developers in the industry, and that base has built its expertise around Solidity, standard tooling, and the EVM’s specific execution model. Any post-quantum migration strategy that requires these developers to abandon that tooling and learn an entirely new environment is asking for a much larger commitment than most teams will be willing to make on a timeline that still feels distant to many of them. This is a real obstacle to post-quantum adoption across the industry, independent of whether the underlying cryptography is sound: a security upgrade that requires developers to relearn their stack from scratch faces adoption friction that has nothing to do with the strength of the cryptography itself.
Lithosphere’s approach to this problem is to make post-quantum verification available as EVM precompiles — native operations that Solidity contracts can call directly, the same way contracts already call existing precompiles for operations like elliptic curve verification or hashing. A Solidity developer building a multisig, a treasury contract, a DAO governance mechanism, or a bridge does not need to leave the EVM execution model or learn a new language to incorporate post-quantum signature verification. The precompile handles the underlying ML-DSA, SLH-DSA, or hybrid verification logic, and the contract calls it the way it would call any other precompiled operation.
This matters most for exactly the categories of contract where post-quantum security is most consequential. A smart account that controls significant value benefits from quantum-resistant authorization the same way a validator identity key does — the asset being protected has a long time horizon, and a quantum-capable attacker years from now could target it just as effectively as one today, if the underlying account was never upgraded. Multisigs that govern treasury access, DAOs that control protocol parameters, and bridges that move value across chains are all long-lived, high-value targets where the cost of retrofitting post-quantum security after the fact is considerably higher than building it in through tooling developers already know how to use.
The precompile approach also means post-quantum adoption on Lithosphere’s EVM-compatible environment does not require a flag day where every contract switches simultaneously. Developers can build new contracts with post-quantum verification from the start, using the same Solidity patterns and the same deployment processes they already follow, while existing contracts continue operating under classical cryptography until their teams choose to migrate. The precompile exists as an available tool rather than a mandatory replacement, which is consistent with the hybrid, staged approach that characterizes Lithosphere’s broader post-quantum crypto agility architecture.
There is a structural benefit here beyond convenience. Native precompiles are typically more gas-efficient and more consistently verified across validators than the same cryptographic operation implemented as ordinary contract bytecode, because precompiles run as part of the execution client’s native code rather than being interpreted line by line as EVM opcodes. Making post-quantum verification a precompile rather than a library that developers would otherwise have to implement in Solidity themselves means the operation is faster, cheaper, and less prone to subtle implementation bugs than if every team building a quantum-resistant contract had to write and audit their own verification logic.
The broader point is that post-quantum security adoption depends as much on how accessible the tooling is as on how sound the underlying cryptography is. A quantum-resistant primitive that only specialists can implement correctly will see limited real-world use. Lithosphere’s EVM precompiles are built on the premise that the Solidity developers who will eventually need to build quantum-resistant contracts should be able to do so with the skills and tools they already have, not with an entirely new set they have to acquire first.
