Deploying the full stack Polygon CDK zkRollup EVM-compatible network requires installing and deploying a number of different components.
Each component runs in its own Docker container.
|Fetches txs from the pool DB, checks if valid, then puts valid ones into a batch.
|Validates sequenced batches by generating verifiable zero-knowledge proofs.
|Updates the state by fetching data from Ethereum through the Etherman.
|An interface for interacting with the network. e.g., Metamask, Etherscan or Bridge.
|A database for permanently storing state data (apart from the Merkle tree).
|Used by the aggregator to create zk-proofs. The full prover is extremely resource-heavy and runs on an external cloud server. Use the mock prover for evaluation/test purposes.
|Stores txs from the RPC nodes, waiting to be put in a batch by the sequencer.
|Executes all processes. Collects results’ metadata (state root, receipts, logs)
|Implements methods for all interactions with the L1 network and smart contracts.
|User-interface for bridging ERC-20 tokens between L2 and L1 or another L2.
|A database for storing bridge-related transactions data.
|A backend service enabling clients like the web UI to interact with bridge smart contracts.
|L2 network’s block explorer. i.e., The zkRollup Etherscan explorer.
|zkEVM explorer DB
|Database for the L2 network’s Block explorer. i.e., Where all the zkRollup Etherscan explorer queries are made.
|Responsible for suggesting the gas price for the L2 network fees.
|L1 node’s execution layer.
|L1 node’s consensus layer.
Last update: January 17, 2024