Skip to content
This repository has been archived by the owner on Dec 18, 2023. It is now read-only.

Consider implementing BLS27-319 #16

Closed
jon-chuang opened this issue Mar 31, 2020 · 0 comments
Closed

Consider implementing BLS27-319 #16

jon-chuang opened this issue Mar 31, 2020 · 0 comments

Comments

@jon-chuang
Copy link

If we are considering a model in which a group of users are willing to trust a server to preserve their functional privacy, one could consider proof batching. Value privacy is still preserved if the user generates their own proof. If not, the user can also delegate this.

In this setting, it seems that the miller loop arithmetic complexity is the most important number, at least for batching for Groth16, in which case BLS27, which has both the lowest arithmetic complexity and G1 size among all curves considered at the 128-bit security level in the 2019 review on pairings, should be considered.

Taking into account Cheon's attack, I propose to find a curve with a 319-bit modulus, which would have a subgroup of size about 275-bits, giving a security of 125-bits with powers of tau up to 2^23.

@jon-chuang jon-chuang changed the title Batching Groth16, consideration of BLS27-319 for batching Batching Groth16, consideration of BLS27-319 Mar 31, 2020
@Pratyush Pratyush transferred this issue from arkworks-rs/snark Nov 20, 2020
@Pratyush Pratyush changed the title Batching Groth16, consideration of BLS27-319 Consider implementing BLS27-319 Nov 20, 2020
@Pratyush Pratyush closed this as not planned Won't fix, can't repro, duplicate, stale Dec 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants