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

implement TIP 0001: Contiguity Argument for Memory Consistency #80

Merged
merged 23 commits into from
Oct 19, 2022

Conversation

jan-ferdinand
Copy link
Member

@jan-ferdinand jan-ferdinand commented Oct 7, 2022

Fix #77

Co-authored-by: Alexander Lemmens <alexanderlemmens@hotmail.com>
- Introduce register `ramp`, which is updated on executing instructions
    `read_mem` & `write_mem`.
- Explicitly treat clock jump differences of magnitude 1.
- Also, make running evaluation `reu` absorb first (not last) cell of
    every contiguous region.
- Adapt figure accordingly.
- Improve wording regarding forward / backward directed jumps.
jan-ferdinand and others added 17 commits October 17, 2022 17:58
Co-authored-by: Ferdinand Sauer <ferdinand@neptune.cash>
Also:
 - clean up depracated comments
Also:
 - add eighth instruction bit column
 - rename KeepRamp -> KeepRam
 - fix off-by-one error in OpStack
 - add constraints for generic instruction buckets
 - add constraints for KeepRam
 - update ramv in VM correctly
 - catch error in test hash_table::table_satisfies_constraints_test
 - add initial boundary constraint on ramp

Co-authored-by: Ferdinand Sauer <ferdinand@neptune.cash>
triton-vm/src/table/challenges.rs Outdated Show resolved Hide resolved
implement TIP 0003: Subset Argument for Memory Consistency
@aszepieniec aszepieniec merged commit 4d7d22f into master Oct 19, 2022
@jan-ferdinand jan-ferdinand deleted the tips branch October 31, 2022 09:31
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.

Implement TIP 0001: Contiguity Argument for Memory Consistency
2 participants