-
The Barreto-Naehrig precompiles in geth are called `bn256*`. See here https://github.com/ethereum/go-ethereum/blob/3c46f557/core/vm/contracts.go#L75-L77
But the ones in Frontier are called `bn128*`…
-
I would like to try out a different Barreto-Naehrig pairing. How would I go about computing the curve parameters used in libsnark such as the Frobenius_coeffs, the ate_loop_count, the final_exponent,…
-
Hi,
I am currently heavily involved in Ethereum development and am currently implementing a Confidential Transactions token. The curve used for this is alt_bn_128 and not secp256k1 like in Bitcoin.…
-
Currently only ALT_BN128/BN128, MNT4-298/MNT6-298 and EDWARDS-80 elliptic curves are supported in libff. All of them have a lower security level than 128-bit. Is there any plans to support other curve…
-
Hello,
The current _ad hoc_ style ring signature gets too big as ring grows in size, due to the fact that it takes O(n) of memory.
I've been fiddling around with Kyber for a couple of weeks now,…
-
`cryptoProperties` (v1.1) -> `algorithmProperties` -> `curve` is proposed as an enum. This would require an update to the CBOM schema for every new curve. Why not just use OIDs?
I went over the pro…
-
Hi all, I would like to share with you guys some benchmarks I ran on zexe, gnark/goff and zkcrypto's BL12-381. I believe this is a good place to start to identify what the key avenues for optimisation…
-
This ticket will be a discussion of optimizations for implementing recursive SNARKs.
For Groth16 verification we need pairings, and for pairings we need extension field arithmetic. Assume that the …
daira updated
3 years ago
-
The following EIPs require support for new curves
- EIP 1895 - https://eips.ethereum.org/EIPS/eip-1895
- EIP 1962 - https://eips.ethereum.org/EIPS/eip-1962
- EIP 2539 - https://eips.ethereum.org/EI…
-
**Context:** [EcPairing.yul#L457](https://github.com/lambdaclass/zksync_era_precompiles/blob/bb9d3991d7af865a717f19559cd256a6ba6a90c8/precompiles/EcPairing.yul#L457)
**Description:**
`g2IsInSubG…