-
Notifications
You must be signed in to change notification settings - Fork 50
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
specs: circuit architecture, memory, continuations #1457
specs: circuit architecture, memory, continuations #1457
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
In the following, we will refer to a circuit as a collection of AIR matrices (also referred to as chips) of possibly | ||
different heights, which may communicate with one another over buses using a log-up permutation argument. We refer to | ||
messages sent to such a bus as [interactions](https://github.com/openvm-org/stark-backend/tree/main/crates/stark-backend/src/interaction). | ||
In the following, we will refer to a circuit as a collection of chips that communicate with one another over buses using a LogUp permutation argument. We refer to messages sent to such a bus as [interactions](https://github.com/openvm-org/stark-backend/blob/main/docs/interactions.md). Every _chip_ is an entity responsible for a certain operation (or set of operations), and it has an AIR to check the correctness of its execution. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically, in the backend we used "interaction" to refer to the "for every row, send ..." constraint/rule. But we do also colloquially use interaction to kind of refer to the message. I couldn't find a good way to really distinguish this, and here when you say refer to mesages -> interaction, it is technically still correct in a sense. so no change required
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Commit: 4be954c |
Write the specs for the circuit and memory