-
Notifications
You must be signed in to change notification settings - Fork 145
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
Stark: Update docs #611
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ 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
force-pushed
the
update-stark-docs
branch
from
October 19, 2023 16:49
ccabca3
to
a20b4ad
Compare
schouhy
force-pushed
the
update-stark-docs
branch
from
October 19, 2023 16:52
b7ad074
to
9925aa9
Compare
) & | ||
\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. |
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.
he
diegokingston
approved these changes
Oct 19, 2023
entropidelic
approved these changes
Oct 20, 2023
MauroToscano
approved these changes
Oct 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update docs
Description
This PR updates the STARK protocol documentation with the Stone prover compatibility changes recently added.