So you wanna Post-Quantum Ethereum transaction signature

Super cool work on the NTT precompile @rdubois-crypto. Just purely evaluating PQ signatures by EVM verification gas cost, I think one would choose WOTS+ (cca. 200k gas). One-time signatures (OTS) have already allowed us to survive in a post-quantum world since one can always sign the public key of the next transaction. Though, OTSs do not allow, for instance, “replace by fee” mechanism, since one would need to sign with the same secret key multiple times. Therefore, transactions could get stuck in the mempool, as this was previously observed in the Bitcoin community. I believe XMSS is on par with Falcon in terms of verification gas cost. I also think that MAYO (and possibly other 2nd round NIST contenders as well) might be good candidates given the upcoming EVM upgrades, e.g., SIMD operations for the EVM or EOF.

(lol. just realised that @CPerezz already brought this up above)
I want to bring in a new perspective to evaluate/benchmark PQ signature schemes that previously (at least not in this thread) were not considered in detail. It might be worthwhile to anticipate that people also want to use these signature schemes in (zero-knowledge) proof systems to prove various statements. So, it would also be interesting to evaluate the ZK/MPC circuit-friendliness of the above-discussed verification algorithms and, put differently, how amenable they are to proof systems. I’d assume that hash-based signatures will compose well with hash-based proof systems, while FALCON and DILITHIUM may perform better when proven with lattice-based proof systems. (???) It’d be cool to have a concrete analysis on this.

1 Like

gas perspective is not fair, because hash functions used in the OTS are underpriced. When moving to a node implementation, the comparizon reflect the computational effort in client, which correspond to the effort for the network.

NTT can be implemented very efficiently in ZK. There also efficient MPC version like Musig-L for lattice candidates benefiting from the structure and not a “generic MPC compiler” working at gates level.

Looking at what the IACR community is pushing, lattice gonna be the future of ECC for web2. While NIST made another call to avoid to rely on a single technology, it seems like the way to go.

Also since last threads, we reduced the FALCON verification close to 2.5M, with SIMD, we will be able to be lesser than the 200k by vectorizing the operations (16 chunks of 16 bytes in a word).

1 Like