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.

Sign up for GitHub

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

zk-SNARK definition added. #30

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

zk-SNARK definition added. #30

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions pages/other-terms.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,3 +347,7 @@ A zero-knowledge proof is the resulting output of a [zero-knowledge](#Zero-knowl
## ZK-Rollup

A [rollup](/foundational-terms#rollup) that uses [ZKPs](#Zero-knowledge-proof-(ZKP)) (also often called [validity proofs](#Validity-proof) to [validate](#Validator) the correctness of the state transition function and update the rollup state. This is one of two main types of rollup constructions, along with [optimistic rollups](#Optimistic-rollup). In general, ZK-Rollups do not provide privacy preserving properties; privacy preserving ZK-Rollups are sometimes called ZK-ZK-Rollups.

## zk-SNARK

zk-SNARK (zero-knowledge Succinct Non-interactive ARgument of Knowledge) is a type of zero-knowledge proof (ZKP). This proof construction allows one party to prove to another that a certain statement is true, without revealing any information about the statement itself.