Skip to content
New issue

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

Separate FRI parameters from FRI snippet #78

Merged
merged 5 commits into from
Feb 7, 2024

Conversation

Sword-Smith
Copy link
Contributor

@Sword-Smith Sword-Smith commented Feb 7, 2024

To call the FRI snippet outside of an internal testing context, we need to have a snippet object that doesn't require us to set FRI's run-time parameters at compile-time. With this change, setting those parameters at compile-time is optional and only required when invoking tests.

All tests pass.

There might be a cleaner way to achieve this. This was just the 1st thing that I came to mind and that I could get to compile.

To call from, we need to have a snippet object that doesn't require
us to set run-time parameters at compile-time which the previous
FRI snippet struct did. With this change, setting those parameters
at compile-time is optional and only required when invoking tests.
@Sword-Smith
Copy link
Contributor Author

Also: Now that we're looking at the interface of the FRI snippet, I think it should not return the VmProofIter pointer, but just consume that argument and mutate the underlying structure. That way, the FRI snippet would only return one value, the index/codeword tuples.

@jan-ferdinand jan-ferdinand merged commit 5ad75dd into master Feb 7, 2024
3 checks passed
@Sword-Smith Sword-Smith deleted the thv/improve-fri-verifier-interface branch July 19, 2024 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants