github.com/0xPolygon/supernets2-node@v0.0.0-20230711153321-2fe574524eaa/docs/components/prover.md (about)

     1  # Component: Prover
     2  
     3  NOTE: The Prover is not considered part of the ZKEVM Node and all issues and suggestions should be sent to the [Prover repo](https://github.com/0xPolygonHermez/supernets2-prover/).
     4  
     5  ## ZKEVM Prover:
     6  
     7  The ZKEVM Prover image hosts different components, *Merkle Tree*, *Executor* and finally the actual *Prover*.
     8  
     9  ## Hard dependencies:
    10  
    11  - [Aggregator](./aggregator.md)
    12  
    13  ## Running:
    14  
    15  The preferred way to run the ZKEVM Prover component is via Docker and Docker Compose.
    16  
    17  ```bash
    18  docker pull hermeznetwork/zkevm-prover
    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-prover:
    25      container_name: supernets2-prover
    26      image: supernets2-prover
    27      volumes:
    28        - ./prover-config.json:/usr/src/app/config.json
    29      command: >
    30        zkProver -c /usr/src/app/config.json
    31  ```
    32  
    33  The `prover-config.json` file contents will vary depending on your use case, the main document explains different values to be changed to achieve different behaviors.
    34  
    35  ### Ports:
    36  
    37  - `50051`: Prover
    38  - `50061`: Merkle Tree
    39  - `50071`: Executor