Matthew Di Ferrante 80c6dfc19f crypto/bn256: fix generator on G1 (#15591) ... Generator in the current lib uses -2 as the y point when doing ScalarBaseMult, this makes it so that points/signatures generated from libs like py_ecc don't match/validate as pretty much all other libs (including libsnark) have (1, 2) as the standard generator. This does not affect consensus as the generator is never used in the VM, points are always explicitly defined and there is not ScalarBaseMult op - it only makes it so that doing "import github.com/ethereum/go-ethereum/crypto/bn256" doesn't generate bad points in userland tools.		2017-12-01 13:03:39 +01:00
..
bn256_test.go	consensus, core/*, params: metropolis preparation refactor	2017-05-18 09:05:58 +02:00
bn256.go	core/vm, crypto/bn256: fix bn256 use and pairing corner case	2017-08-17 16:46:46 +03:00
constants.go	consensus, core/*, params: metropolis preparation refactor	2017-05-18 09:05:58 +02:00
curve.go	crypto/bn256: fix generator on G1 (#15591)	2017-12-01 13:03:39 +01:00
example_test.go	consensus, core/*, params: metropolis preparation refactor	2017-05-18 09:05:58 +02:00
gfp2.go	consensus, core/*, params: metropolis preparation refactor	2017-05-18 09:05:58 +02:00
gfp6.go	crypto/bn256: fix go vet false positive	2017-05-24 15:40:26 +02:00
gfp12.go	consensus, core/*, params: metropolis preparation refactor	2017-05-18 09:05:58 +02:00
main_test.go	consensus, core/*, params: metropolis preparation refactor	2017-05-18 09:05:58 +02:00
optate.go	core/vm, crypto/bn256: fix bn256 use and pairing corner case	2017-08-17 16:46:46 +03:00
twist.go	crypto/bn256: fix go vet false positive	2017-05-24 15:40:26 +02:00