bug fix: UltraPlonk RAM witnesses affect verification key #520
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.
Fixed bug where UltraPlonk RAM constraints made verification key depend on witness
Fixed following issues:
memory_read_records
,memory_write_records
are a function of the input witness, and should be assigned to the proving key incompute_witness
(notcompute_proving_key
)apply_aux_selectors(AUX_SELECTORS::RAM_TIMESTAMP_CHECK)
was being called on the original ram records witnesses and NOT the set of sorted ram record witnessesDescription
Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
/markdown/specs
have been updated.@brief
describing the intended functionality.