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
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,27 @@ The following table lists the components and where you can find them for CDK rol
29
29
!!! important
30
30
For specific release tags, please reference the [version matrix document](version-matrix.md).
31
31
32
+
### Component descriptions
33
+
34
+
Next are the brief descriptions of each CDK component.
35
+
36
+
- 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
+
- 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.
44
+
- 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.
50
+
- 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.
52
+
32
53
## CDK stack with pessimistic proofs
33
54
34
55
The CDK with pessimistic proofs release follows on shortly after the CDK FEP release.
0 commit comments