fix: issue where precompute p function bakes runtime input #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A function that is supposed to assume runtime input in stack had hardcoded those values on script. This PR fixes the issue.
The function hinted_from_eval_point is used to calculate p'x and p'y given px and py.
The values of px and py are part of groth16 proof.
Unit tests have been added for the function changed.
The function was used in test units, all of which have been appropriately modified i.e. now receive 'p' on stack.