github.com/0xPolygon/supernets2-node@v0.0.0-20230711153321-2fe574524eaa/docs/components/aggregator.md (about) 1 # Component: Aggregator 2 3 ## ZKEVM Aggregator: 4 5 The ZKEVM Aggregator is an optional module responsible for receiving connections from Prover(s) in order to generate the proofs for the batches not proven yet. 6 7 ## Hard dependencies: 8 9 - [Synchronizer](./synchronizer.md) 10 - [StateDB Database](./databases.md) 11 - [Prover, Merkle Tree and Executor](./prover.md) 12 13 ## Running: 14 15 The preferred way to run the ZKEVM Aggregator component is via Docker and Docker Compose. 16 17 ```bash 18 docker pull hermeznetwork/supernets2-node 19 ``` 20 21 To orchestrate multiple deployments of the different ZKEVM Node components, a `docker-compose.yaml` file for Docker Compose can be used: 22 23 ```yaml 24 supernets2-aggregator: 25 container_name: supernets2-aggregator 26 image: supernets2-node 27 command: 28 - "/bin/sh" 29 - "-c" 30 - "/app/supernets2-node run --genesis /app/genesis.json --cfg /app/config.toml --components aggregator" 31 ``` 32 33 The container alone needs some parameters configured, access to certain configuration files and the appropriate ports exposed. 34 35 - volumes: 36 - `your Account Keystore file`: /pk/keystore (note, this `/pk/keystore` value is the default path that's written in the Public Configuration files on this repo, meant to expedite deployments, it can be superseded via an env flag `ZKEVM_NODE_ETHERMAN_PRIVATEKEYPATH`.) 37 - `your config.toml file`: /app/config.toml 38 - `your genesis.json file`: /app/genesis.json 39 40 - environment: Env variables that supersede the config file 41 - `ZKEVM_NODE_STATEDB_HOST`: Name of StateDB Database Host 42 43 ### The Account Keystore file: 44 45 Since the Aggregator will send transactions to L1 you'll need to generate an account keystore: 46 47 [Generate an Account Keystore file](./account_keystore.md)