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.
This PR adds and exposes the minimal structure that should allow for creation of distinct circuits for each coroutine. This will be required in order to support actual NIVC proving.
Future work should include:
rc
per coroutine circuit. Currently, the circuit will just contain exactly as many prove-and-remove steps as required for the actual computation witnessed. In reality, we need a fixed number per circuit — such that multiple circuits can be used if needed, and dummies (which don't affect the MemoSet or transcript) can be provided to pad. i.e. if rc=100 and a computation uses 240, then we would create 3 circuits, the last of which has 60 dummy padding instances.