Skip to content

Conversation

@Nashtare
Copy link
Contributor

@Nashtare Nashtare commented Sep 24, 2025

Fairly high level for now and incomplete, but laying foundations for extensive description of the approach later on (also easier to maintain and access than the Google docs specs).

Feel free to iterate upon

@Nashtare Nashtare added this to the Design and specs milestone Sep 24, 2025
@Nashtare Nashtare added the doc/specs Improvements or additions to documentation label Sep 24, 2025
@Nashtare Nashtare moved this from Todo to Ready for review in Plonky3 Recursion Sep 24, 2025
@Nashtare Nashtare self-assigned this Sep 24, 2025
@tcoratger
Copy link
Collaborator

Amazing to have this, it will be easier to discuss topics and design considerations on our side with this!

Copy link
Contributor

@sai-deng sai-deng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome work!


Below is a representation of the interactions between the main Witness table and the different chips.

```mermaid
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somehow I got:

Syntax error in text
mermaid version 11.6.0

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've tweaked it lightly, it compiles locally so not sure what's wrong, could you retry with latest version please?

The Witness table is a central bus that stores values shared across operations. It gathers the pairs `(index, value)` that will be accessed by
the different chips via lookups to enforce consistency.

- The index column is *transparent*, or *preprocessed* [@@rap]: it is known to both prover and verifier in advance, requiring no online commitment.[^1]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we only need one @ not two @@. Also for other citations.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a single @ does not render the hyperlink when building on my side ([@@foo] is typical for the bib preprocessor AFAIK). An alternative solution (a tad prettier as it removes the brackets) is to forget about a common bibliography/references page and have everything inline as footnote references.

@github-project-automation github-project-automation bot moved this from Ready for review to Ready to be merged in Plonky3 Recursion Sep 24, 2025
@Nashtare Nashtare merged commit 0fe0719 into main Sep 25, 2025
8 checks passed
@github-project-automation github-project-automation bot moved this from Ready to be merged to Done in Plonky3 Recursion Sep 25, 2025
@Nashtare Nashtare deleted the mdbook branch October 11, 2025 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc/specs Improvements or additions to documentation

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants