Difference between revisions of "Prover"
Jump to navigation
Jump to search
↑ https://docs.zircuit.com/architecture-and-concepts/concepts
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
| − | The [[Zircuit provers]] are organized by a component called the proof orchestrator, which keeps track of which transitions need to be proved and which proofs need to be aggregated. The input to the proving pipeline is the L2 blocks, and the ultimate result is a [[validity proof]] for a batch of blocks.<ref>https://docs.zircuit.com/architecture-and-concepts/concepts</ref> | + | The [[Zircuit provers]] are organized by a component called the [[proof orchestrator]], which keeps track of which transitions need to be proved and which proofs need to be aggregated. The input to the proving pipeline is the L2 blocks, and the ultimate result is a [[validity proof]] for a batch of blocks.<ref>https://docs.zircuit.com/architecture-and-concepts/concepts</ref> |
== Related == | == Related == | ||
* [[ZK Stack]] | * [[ZK Stack]] | ||
| + | * [[EVM Prover]] | ||
== See also == | == See also == | ||
Latest revision as of 09:45, 1 August 2024
The Zircuit provers are organized by a component called the proof orchestrator, which keeps track of which transitions need to be proved and which proofs need to be aggregated. The input to the proving pipeline is the L2 blocks, and the ultimate result is a validity proof for a batch of blocks.[1]
Related[edit]
See also[edit]
Advertising:
