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

Stark: Update docs #611

Merged
merged 8 commits into from
Oct 23, 2023
Merged

Stark: Update docs #611

merged 8 commits into from
Oct 23, 2023

Conversation

schouhy
Copy link
Contributor

@schouhy schouhy commented Oct 19, 2023

Update docs

Description

This PR updates the STARK protocol documentation with the Stone prover compatibility changes recently added.

@codecov-commenter
Copy link

codecov-commenter commented Oct 19, 2023

Codecov Report

Merging #611 (7d9905f) into main (6d686d3) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #611   +/-   ##
=======================================
  Coverage   97.11%   97.11%           
=======================================
  Files         114      114           
  Lines       26540    26540           
=======================================
  Hits        25775    25775           
  Misses        765      765           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@schouhy schouhy marked this pull request as ready for review October 19, 2023 16:50
@schouhy schouhy requested review from ajgara and a team as code owners October 19, 2023 16:50
) &
\end{align}
$$

### Verifier
From the point of view of the verifier, the proof they receive is a bunch of values that may or may not be what they claim to be. To make this explicit, we avoid denoting values like $t_j(z)$ as such, because that implicitly assumes that the value was obtained after evaluating a polynomial $t_j$ at $z$. And that's something the verifier can't assume. We use the following convention.
Copy link
Contributor

Choose a reason for hiding this comment

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

he

@MauroToscano MauroToscano added this pull request to the merge queue Oct 23, 2023
Merged via the queue into main with commit 6f16669 Oct 23, 2023
7 checks passed
@MauroToscano MauroToscano deleted the update-stark-docs branch October 23, 2023 16:50
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.

5 participants