Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Post-quantum solutions for Ethereum #636

Open
kayabaNerve opened this issue Dec 12, 2024 · 1 comment
Open

Post-quantum solutions for Ethereum #636

kayabaNerve opened this issue Dec 12, 2024 · 1 comment
Labels
cryptography An issue involving cryptography/a cryptographic library ethereum An issue with the Ethereum integration

Comments

@kayabaNerve
Copy link
Member

Same as #635, yet with a lot more flexibility for which signature we'll implement. We also already don't expect to have an EOA so we can simply maintain that assumption/infrastructure (being uncaring to which signature scheme Ethereum adopts for EOAs, if they don't simply move to contracts as EOAs).

@kayabaNerve kayabaNerve added ethereum An issue with the Ethereum integration cryptography An issue involving cryptography/a cryptographic library labels Dec 12, 2024
@kayabaNerve
Copy link
Member Author

We do have the privilege of not needing a threshold protocol which is indistinguishable from a single-signer protocol. In the worst case, we could use Lamport signatures where we verify each individual one on-chain.

Threshold MAYO with a 5-round DKG and 9-round signing protocol, with a chance of random failure increasing the round count by repeating the last part of the protocol. This doesn't appear to offer identifiable aborts.

Threshold Raccoon with a 2-round signing protocol. They don't explicitly posit a DKG but suggest use of others without confirming their validity. This doesn't offer identifiable aborts.

We can re-introduce identifiable aborts via the use of expensive, generic ZK proofs, but that wouldn't be great.

Pelican, with a 3-round key gen and 4-round signing protocol. This is notable for being robust. Unfortunately, the signing protocol is of quadratic complexity (at least).

We could also use a ZK-STARK aggregating Dilithium signatures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cryptography An issue involving cryptography/a cryptographic library ethereum An issue with the Ethereum integration
Projects
None yet
Development

No branches or pull requests

1 participant