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

enforce RAM initializating to all zero #155

Closed
jan-ferdinand opened this issue Dec 12, 2022 · 0 comments · Fixed by #144
Closed

enforce RAM initializating to all zero #155

jan-ferdinand opened this issue Dec 12, 2022 · 0 comments · Fixed by #144
Labels
🖐 blocked Requires something else first. 🤖 code Changes the implementation 💫 good first issue Good for newcomers 🟡 prio: medium Not super urgent 📜 specification Relates to the specification

Comments

@jan-ferdinand
Copy link
Member

In our current design, we can't enforce that the RAM is initialized to all zeros. As discussed with @aszepieniec, the following changes are the least invasive way of achieving this stated goal.

  1. Upon encountering (as opposed to executing) either instruction read_mem or write_mem, the processor's registers RAMP and RAMV get updated.
  2. In the RAM Table, whenever a new contiguous RAMP region starts, the RAMV is 0. This includes an initial constraint on RAMV being 0.

I'm happy to provide assistance and more details to anyone considering tackling this issue. It's probably best to wait until #139 is done, i.e., #144 is merged.

@jan-ferdinand jan-ferdinand added 📜 specification Relates to the specification 💫 good first issue Good for newcomers 🟡 prio: medium Not super urgent 🤖 code Changes the implementation 🖐 blocked Requires something else first. labels Dec 12, 2022
@jan-ferdinand jan-ferdinand mentioned this issue Dec 12, 2022
25 tasks
jan-ferdinand added a commit that referenced this issue Dec 22, 2022
- add master tables (#144)
- distinguish AIR constraints of base and extension tables (#119)
- enforce RAM initialization to all zero (#155)
- reduce memory footprint (#11)
- split Triton VM's instructions into separate sub-crate
- use twenty-first v0.10
jan-ferdinand added a commit that referenced this issue Dec 22, 2022
- add master tables (#144)
- distinguish AIR constraints of base and extension tables (#119)
- enforce RAM initialization to all zero (#155)
- reduce memory footprint (#11)
- split Triton VM's instructions into separate sub-crate
- use twenty-first v0.10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖐 blocked Requires something else first. 🤖 code Changes the implementation 💫 good first issue Good for newcomers 🟡 prio: medium Not super urgent 📜 specification Relates to the specification
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant