Skip to content

Import Ethereum's KZG common reference string for compatibility #12

Description

@seresistvanandras

We use the following unsafe, completely insecure, common reference string for our proof of concept implementation.

fde/src/commit/kzg.rs

Lines 18 to 28 in 8759afa

pub fn unsafe_setup(tau: C::ScalarField, range: usize) -> Self {
let mut g1 = Vec::new();
let mut g2 = Vec::new();
let mut exponent = C::ScalarField::one();
for _ in 1..=range {
g1.push((<C::G1Affine as AffineRepr>::generator() * exponent).into_affine());
g2.push((<C::G2Affine as AffineRepr>::generator() * exponent).into_affine());
exponent *= tau;
}
Self { g1, g2 }
}

For applications that want to be compatible with Ethereum, it will be necessary to use the common reference string of the KZG commitment created in 2023 during a large-scale KZG ceremony by the Ethereum Foundation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions