We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We always had a division by zero in blueprint_algebra_curves_plonk_variable_base_scalar_mul_test, near
assignment.witness(component.W(7), i + 1) = (P[0].Y - Q.Y) * (P[0].X - Q.X).inversed();
in include/nil/blueprint/components/algebra/curves/pasta/plonk/variable_base_scalar_mul.hpp.
P[0].X - Q.X is zero because both P[0].X and Q.X are zero.
We never noticed it because of in multiprecision A / 0 = 0, here:
So all this time when asking for the inverse element of zero, we were getting zero back... With changes to multiprecision we get a segfault...
The text was updated successfully, but these errors were encountered:
Not sure that I understand:
DO you mean P[0].X and Q.X are always zero or do you consider particular case when they're zeros?
Sorry, something went wrong.
@SK0M0R0H No, they are not always zero, they are sometimes zero for a particular input.
Iluvmagick
No branches or pull requests
We always had a division by zero in blueprint_algebra_curves_plonk_variable_base_scalar_mul_test, near
assignment.witness(component.W(7), i + 1) = (P[0].Y - Q.Y) * (P[0].X - Q.X).inversed();
in include/nil/blueprint/components/algebra/curves/pasta/plonk/variable_base_scalar_mul.hpp.
P[0].X - Q.X is zero because both P[0].X and Q.X are zero.
We never noticed it because of in multiprecision A / 0 = 0, here:
So all this time when asking for the inverse element of zero, we were getting zero back... With changes to multiprecision we get a segfault...
The text was updated successfully, but these errors were encountered: