You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/cdk/releases/stack-components.md
+30-26Lines changed: 30 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,20 +11,19 @@ In the CDK with full execution proofs release, any zkEVM components can be consi
11
11
12
12
The following table lists the components and where you can find them for CDK rollup and validium stacks. You will notice only small differences in the component makeup of the two stacks; differences which are now mostly use case specific.
| Node = RPC and sequencer | <a href=https://github.com/0xPolygonHermez/cdk-erigon>cdk-erigon</a> | <a href=https://github.com/0xPolygonHermez/cdk-erigon>cdk-erigon</a> | Customizable but usually sequencer=1 node, multiple for RPC |
17
-
| Data availability | None | <a href=https://github.com/0xPolygon/cdk-data-availability>cdk-data-availability</a> ||
18
-
| Contracts | <a href=https://github.com/0xPolygonHermez/zkevm-contracts>zkevm-contracts</a> | <a href=https://github.com/0xPolygonHermez/zkevm-contracts>zkevm-contracts</a> | Same code for both: 8.0.0-rc.2-fork.12 |
19
-
| Data streamer | <a href=https://github.com/0xPolygon/zkevm-data-streamer>zkevm-data-streamer</a> | <a href=https://github.com/0xPolygon/zkevm-data-streamer>zkevm-data-streamer</a> | Same code for both |
20
-
| CLI | <a href=https://github.com/0xPolygon/cdk>CLI included</a> | <a href=https://github.com/0xPolygon/cdk>CLI included</a> | Same code for both |
21
-
| Sequence sender | <a href=https://github.com/0xPolygon/cdk>Sequence sender included</a> | <a href=https://github.com/0xPolygon/cdk>Sequence sender included</a> | Same code for both |
22
-
| Aggregator | <a href=https://github.com/0xPolygon/cdk>Aggregator included</a> | <a href=https://github.com/0xPolygon/cdk>Aggregator included</a> | Same code for both |
23
-
| Tx pool manager | <a href=https://github.com/0xPolygon/zkevm-pool-manager>zkevm-pool-manager| <a href=https://github.com/0xPolygon/zkevm-pool-manager>zkevm-pool-manager| Same code for both |
24
-
| Prover | <a href=https://github.com/0xPolygonHermez/zkevm-prover>zkevm-prover</a> | <a href=https://github.com/0xPolygonHermez/zkevm-prover>zkevm-prover</a> | Same code for both - wip |
| Bridge UI | <a href=https://portal.polygon.technology/>Polygon Portal</a> | <a href=https://portal.polygon.technology/>Polygon Portal</a> | Same UI for both |
27
-
| Blockscout | <a href=https://github.com/0xPolygonHermez/blockscout>blockscout</a> | <a href=https://github.com/0xPolygonHermez/blockscout>blockscout</a> | Same code for both |
| Recommended explorer service | <a href=https://github.com/0xPolygonHermez/blockscout>Blockscout</a> | IP free to implement another explorer service |
28
27
29
28
!!! important
30
29
For specific release tags, please reference the [version matrix document](version-matrix.md).
@@ -33,22 +32,27 @@ The following table lists the components and where you can find them for CDK rol
33
32
34
33
Next are the brief descriptions of each CDK component.
35
34
35
+
- CDK Erigon node, a fork of erigon, that manages the following:
36
+
- Multiple RPC nodes that provide common APIs for sending transactions.
37
+
- Sequencer for executing transactions, and creating blocks and batches.
38
+
- DAC: The Data Availability Committee, specifically for validium mode, is a set of *trusted actors* who keep custody of all transaction data, including monitoring and validating hash values the sequencer sender proposes to publish on L1.
39
+
- Contracts: Various smart contracts deployed on L1 for the full implementation and complete functionality of the Polygon zkEVM protocol:
40
+
-`PolygonRollupManager`
41
+
-`PolygonZkEVMBridgeV2`
42
+
-`PolygonZkEVMGlobalExitRootV2`
43
+
-`FflonkVerifier`
44
+
-`PolygonZkEVMDeployer`
45
+
-`PolygonZkEVMTimelock`
36
46
- CLI tool: A single command line interface tool for abstracting away the complexity of deploying or configuring CDK components.
37
-
- Sequencer: For executing transactions, and creating blocks and batches.
38
-
- RPC node: Each user can spin up an RPC node through which transactions are submitted.
39
-
- Tx-pool-manager: For storing transactions submitted by users.
40
47
- Sequence sender: For sequencing batches.
41
-
- In the case of a rollup, the SequenceSender sends batch data and the `sequenceBatches` transaction to L1.
42
-
- In the case of a validium, the SequenceSender sends batch data to the Data Availability Committee (DAC), requests for signatures from the DAC, and sends the `sequenceBatchesValidium` transaction to L1.
43
-
- Aggregator: For facilitating proving and verification, fetching and providing batch data and witness to the Prover.
48
+
- In the case of a rollup, the sequence sender sends batch data and the `sequenceBatches` transaction to L1.
49
+
- In the case of a validium, the sequence sender sends batch data to the Data Availability Committee (DAC), requests for signatures from the DAC, and sends the `sequenceBatchesValidium` transaction to L1.
50
+
- Aggregator: For facilitating proving and verification, fetching and providing batch data and witness to the prover.
51
+
- Transaction pool manager: For storing transactions submitted by users.
44
52
- Prover: A complex cryptographic tool capable of producing ZK-proofs of hundreds of batches, and aggregating these into a single ZK-proof which is published as the validity proof.
45
-
- Data streamer: A library developed to serve raw block data to nodes that need to maintain an up-to-date L2 state, irrespective of the required amount of data.
46
-
- DAC: The Data Availability Committee, specifically for the validium case, is a set of *trusted actors* who keep custody of all transaction data, including monitoring and validating hash values the sequencer sender proposes to publish on L1.
47
-
- Contracts: Various smart contracts deployed on L1 for the full implementation and complete functionality of the Polygon zkEVM protocol
48
-
- Here's the list: `PolygonRollupManager`, `PolygonZkEVMBridgeV2`, `PolygonZkEVMGlobalExitRootV2`, `FflonkVerifier`, `PolygonZkEVMDeployer`, and `PolygonZkEVMTimelock`.
49
-
- Bridge service: A backend service, written in Go, for enabling clients like the [web UI](https://github.com/0xPolygonHermez/zkevm-bridge-ui) to interact with the [bridge smart contract](https://github.com/0xPolygonHermez/zkevm-contracts) by providing Merkleproofs.
53
+
- Bridge service: A backend service for enabling clients like the [web UI](https://github.com/0xPolygonHermez/zkevm-bridge-ui) to interact with the [bridge smart contract](https://github.com/0xPolygonHermez/zkevm-contracts) by providing Merkle proofs.
50
54
- Bridge UI: The Polygon bridge portal which abstracts away the backend operations involved in bridge deposits and withdrawals.
51
-
- Blockscout: An application that allows to view, confirm, and inspect transactions on EVM chains, optimistic rollups and zkrollups. EVM chains include the POA Network, Gnosis Chain, Ethereum Classic and other Ethereum testnets, private networks and sidechains.
55
+
- Blockscout: An application that allows to view, confirm, and inspect transactions on EVM chains, optimistic rollups and zk rollups. EVM chains include the POA Network, Gnosis Chain, Ethereum Classic and other Ethereum testnets, private networks and side chains. Users may opt to use a different explorer service.
0 commit comments