Skip to content

pq-account

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

pq-account

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
deployments
deployments
 
 
js
js
 
 
lib
lib
 
 
script
script
 
 
src
src
 
 
test
test
 
 
README.md
README.md
 
 
foundry.toml
foundry.toml
 
 
makefile
makefile
 
 
remappings.txt
remappings.txt
 
 

README.md

Post-Quantum Account

Implementation of an ERC4337 account enabling post-quantum security. The account lets us verify two signatures rather than only one. The goal is to enable post-quantum signatures while keeping the current ECDSA verification.

How to run

In order to run the tests, it is required to install the requirements for both Solidity and python (the python signer is used inside the Solidity tests):

make install

Then, run the tests as follows:

make test_opt

Note that Falcon key generation in python is a bit slow, and the test file computes it several times. In order to run tests separately:

forge test test/ZKNOX_ERC4337_account_K1_ETHFALCON.t.sol -vv
forge test test/ZKNOX_ERC4337_account_K1_FALCON.t.sol -vv
forge test test/ZKNOX_ERC4337_account_K1_MLDSA.t.sol -vv
forge test test/ZKNOX_ERC4337_account_K1_MLDSAETH.t.sol -vv
forge test test/ZKNOX_ERC4337_account_R1_ETHFALCON.t.sol -vv
forge test test/ZKNOX_ERC4337_account_R1_FALCON.t.sol -vv
forge test test/ZKNOX_ERC4337_account_R1_MLDSA.t.sol -vv
forge test test/ZKNOX_ERC4337_account_R1_MLDSAETH.t.sol -vv

Fixed contracts

Pre-quantum logic contracts

  • ZKNOX_ECDSA.sol: verifies an ECDSA signature on Ethereum using the precompile ecrecover,
  • ERC7913P256Verifier.sol (from OpenZeppelin): verifies an ECDSA signature on P256 using the precompile p256verifiy.

Post-quantum logic contracts

  • ZKNOX_dilithium.sol: verifies a MLDSA signature,
  • ZKNOX_ethdilithium.sol: verifies a MLDSAETH signature.
  • ZKNOX_falcon.sol: verifies a FALCON signature.
  • ZKNOX_ethfalcon.sol: verifies a ETHFALCON signature.

User contracts

Each user owns a 4337 account contract which contains:

  • a pre_quantum_pubkey in bytes; it can be an ethereum address (20 bytes) or a P256 point (64 bytes)
  • a post_quantum_pubkey in bytes; the address of a PKContract for MLDSA(ETH), the public key bytes for FALCON
  • a pre_quantum_logic_contract_address referring to one of the two pre-quantum fixed contracts above,
  • a post_quantum_logic_contract_address referring to one of the two post-quantum fixed contracts above,

Note: for MLDSA, this requires an extra contract PKContract storing the MLDSA public key.

Onchain Sepolia Testnets

Because of the high gas amount, we decided to deploy the contracts on both L1 Sepolia and Arbitrum Sepolia.

Fixed contracts

The signature verifier contract addresses are fixed and deployed once for all. The address of the contracts are provided in the deployments/deployments.json file.

Example of user MLDSA PK contracts

MLDSA public keys are large and we decided to write them inside contracts. Thus, each user needs to submit his (20kB) expanded MLDSA public key as an initialization step.

We provide an example of public key contract for both MLDSA and MLDSAETH, on the two testnets:

Expanded PubKey Example for Address on L1 Sepolia Address on Arbitrum Sepolia
MLDSA 0xCc28B19d743F3E139D6D8078B6600bad95CD7B2c 0x8e130f25f30c9375971c9469f2adc30b6e91846f
MLDSAETH 0x898Fec6390D8297BC0C92F834E4210a821ccD8B8 0xa854bf182dd854c7b85e35566aa5a46678e2be37

Note that these contracts do not correspond to the latest update of the contracts, but illustrate the structure of the contracts containing the public key.

Gas cost

Using the current contracts, the gas cost is the following:

Contracts MLDSA MLDSA-ETH FALCON ETHFALCON
ECDSA-k1 8.39M 5.12M 4.06M 1.69M
ECDSA-r1 8.40M 5.13M 4.07M 1.70M