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

Terminology: Disambiguate "Table" #329

Open
aszepieniec opened this issue Sep 28, 2024 · 0 comments
Open

Terminology: Disambiguate "Table" #329

aszepieniec opened this issue Sep 28, 2024 · 0 comments

Comments

@aszepieniec
Copy link
Collaborator

In the code base, the word "table" refers to two things. In both cases it's a 2-d array of base or extension field elements, so the word "table" does seem justified; but I think the two senses may benefit from some disambiguation none the less.

  1. The isolated trace of a chiplet such as processor or hash or u32 etc.
  2. The concatenation of all chiplet-traces along with table-linking columns, degree-lowering columns, and randomizer columns.

Most of the time when sense (2) is used it is distinguished from (1) through the qualifier "master", i.e., master_main_table, master_aux_table, etc. I think the word "master" is a poor choice because it sounds like just another chiplet, one that comes with a "slave" counterpart.

I suggest using the word "aet" for sense (2). So any "table" is always in reference to a chiplet in isolation of the rest of the architecture; and "aet" is always what the prover accesses.

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

No branches or pull requests

1 participant