gnark-crypto provides a nice parallelized FFT algorithm on all field elements. I plan to move our codebase (eigenda) to use gnark's FFT instead of our current non-parallelized version (see this PR).
However, we also make use of ECNTT on BN254's G1 curve: https://github.com/Layr-Labs/eigenda/blob/master/encoding/fft/fft_g1.go
Wondering if gnark-crypto has plans to add support for ECNTT, or if there is some reason why it doesn't. The performance gains on ECNTT would be much more significant to us than the improvements we are seeing on Fr. Our slowest ECNTT is ~5seconds on CPU.
gnark-crypto provides a nice parallelized FFT algorithm on all field elements. I plan to move our codebase (eigenda) to use gnark's FFT instead of our current non-parallelized version (see this PR).
However, we also make use of ECNTT on BN254's G1 curve: https://github.com/Layr-Labs/eigenda/blob/master/encoding/fft/fft_g1.go
Wondering if gnark-crypto has plans to add support for ECNTT, or if there is some reason why it doesn't. The performance gains on ECNTT would be much more significant to us than the improvements we are seeing on Fr. Our slowest ECNTT is ~5seconds on CPU.