A thread to finish off our #WhyZK series: the tl;dr
https://twitter.com/MantaNetwork/status/1607735076275601410
https://twitter.com/MantaNetwork/status/1605165349431029761
https://twitter.com/MantaNetwork/status/1610984265994362881
There’re two participants in #zkps: provers and verifiers. Provers provide ‘proofs’ of a statement, and verifiers verify it without giving additional information.
#ZKP is encryption on computation. After the encryption, a cryptography proof of the correctness or validity of the computation will be generated. It is this cryptography proof that allows a border Zero-knowledge application.
🔒 3 Properties 🔒
Completeness: The prover needs the right answer for the statement to be true.
Soundness: If the prover doesn’t, then they can't prove to the verifier that the statement is true.
Zero-Knowledge: The verifier won't get any information besides the proof itself.
Completeness: The prover needs the right answer for the statement to be true.
Soundness: If the prover doesn’t, then they can't prove to the verifier that the statement is true.
Zero-Knowledge: The verifier won't get any information besides the proof itself.
ZK Rollups include StarkWare, zkSync, Scroll, Polygon and etc. ZK Rollups mainly apply two features of ZKP, completeness and soundness, to compile transactions, achieve expansion, and make transactions transparent onchain.
Manta Network and other ZK Privacy projects are leveraging the Zero-Knowledge feature of ZKP. On top of compiling transactions, the privacy of transaction information could be protected.
🔒 The Fundamentals of zk scaling 🔒
One node can do the computation, generate the Zero-Knowledge Proof, and have others verify computation results instead of repeating computation on every transaction.
One node can do the computation, generate the Zero-Knowledge Proof, and have others verify computation results instead of repeating computation on every transaction.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
