Description

In the fake GLV method we return the sign, but it is not used in the point. Due to the hint calling abstraction for non-native computation we still range check the variables. It is unoptimal, but in Linea prover we explicitly check if the variables are used in sequential constraints. As we don't, then this leads to compile error.

However, we still use the fifth output in BLS12-377, so no change there.

@yelhousni - can you double check that we haven't previously added unsoundness due to unused variable?

Type of change

• Bug fix (non-breaking change which fixes an issue)

How has this been tested?

All existing tests succeed.

How has this been benchmarked?

Updated stats - saves a bit more than 100 constraints for scalar multiplication

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I did not modify files generated from templates
• golangci-lint does not output errors locally
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules