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

WHY? "As BLS public keys reside in G2" #16

Open
TinyVege opened this issue Oct 24, 2023 · 0 comments
Open

WHY? "As BLS public keys reside in G2" #16

TinyVege opened this issue Oct 24, 2023 · 0 comments

Comments

@TinyVege
Copy link

TinyVege commented Oct 24, 2023

It is mentioned in the paper that As BLS public keys reside in G, the signature is in G

I want to know why? Or conversely, put the bls public key in G1 and the signature in G2.

I learned that on the bls12381 curve, both are possible. Ethereum 2 chose the latter "the bls public key is placed in G1 and the signature is placed in G2

We can choose to use either group for public keys, as long as we use the other group for signatures: the pairing function doesn't care; everything still works if we swap the groups over. The original paper describing BLS aggregate signatures has public keys in G2G2​ and signatures in G1G1​, while for Ethereum 2 we made the opposite choice.
ref: https://eth2book.info/capella/part2/building_blocks/signatures/#sync-aggregates

There is another idea that I don’t know if it is correct: the pairing operation in e(P1, Q1) = e(P2, Q2) will not change whether the public key is in G1 or G2.

@PhilippSchindler

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant