[ZK Stack] - build zksync Server and zksync Prover on different servers

[Niet-Pham]

Team or Project

No response

Module Affected

• System contracts (era-system-contracts)
• Smart contracts (era-contracts)
• zkEVM (era-zk_evm)
• Server (zksync-era)
• Prover (era-boojum)
• Fee withdrawer (era-fee-withdrawer)
• Block Explorer (clock-explorer)
• Portal - Wallet + Bridge (dapp-portal)
• Other (please specify below)

Rust Version

1.88.0

Operating System

• Ubuntu
• MacOS
• Windows
• Other (Please specify below)

Issue Description

I want to asked how to build zksync Server and zksync Prover on different servers for my chain

Expected Behavior

i want zksync server run on server which without gpu and run zksync prover on server that have gpu

Current Behavior

Somebody pls guild for me how to build

Repository Link (if applicable)

No response

Additional Details

No response

Prior Research

• Yes, I searched for similar issues and did not find any matching ones.

[antonbaliasnikov]

Hi @Niet-Pham ,
Thank you for raising this issue.

Yes, it should be possible. To achieve server setup on one machine, and prover on another, you would need:

1. Initialize prover and prover database on one machine, start the prover.
2. Make sure the prover API URL is accessible from the server machine
3. Initialize server and server database on another machine
4. Change prover API URL in the generated configuration (by default, it's in chains/era/configs/general.yaml) to point to your prover API from another machine.

So, instead of the default value:

...
  prover_gateway:
    api_url: http://127.0.0.1:3320/
...

Provide the prover URL:

...
  prover_gateway:
    api_url: http://<host>:<port>/
...

Please, let us know if this works for you.

[Niet-Pham]

Hi @antonbaliasnikov,
I would like to confirm the steps I ran:

• I’ll refer to Server A as the one running zkstack server, and Server B as the one running zkstack prover.

Step 1:
On Server A, I ran:
zkstack ecosystem create
zkstack ecosystem init

Step 2:

• I copied the ecosystem and chain configurations from Server A.
• Then I updated the Prover API URL in the configuration generated on Server A to point to Server B.
• After that, I ran:
  zkstack prover init

Step 3:
Back on Server A, I started the server:
zkstack server

Step 4:
On Server B,

• I update prover_gateway on general.yaml
• I ran the prover:

zkstack prover run --component=gateway
zkstack prover run --component=witness-generator --round=all-rounds 

zkstack prover run --component=circuit-prover -l 15 -h 1 

zkstack prover run --component=prover-job-monitor

zkstack prover run --component=compressor 

Did I follow the correct steps?

[Niet-Pham]

On server A, I got log

And on server B I got log at componet gateway

[antonbaliasnikov]

Hey @Niet-Pham ,

In general, it appears correct, but you must ensure that the prover components can communicate with each other without any issues on the same host, while the server should be able to access the prover URL you use.

Can you try running everything on the same machine at first, using the documentation:
https://matter-labs.github.io/zksync-era/prover/latest/03_launch.html
And confirm if it's working for you?

[Niet-Pham]

Yayy! Let me try it. Thank you very much Vào Th 2, 21 thg 7, 2025 vào lúc 18:59 Anton Baliasnikov < ***@***.***> đã viết:

…

Hi @Niet-Pham <https://github.com/Niet-Pham> , Thank you for raising this issue. Yes, it should be possible. To achieve server setup on one machine, and prover on another, you would need: 1. Initialize prover and prover database on one machine, start the prover. 2. Make sure the prover API URL is accessible from the server machine 3. Initialize server and server database on another machine 4. Change prover API URL in the generated configuration (by default, it's in chains/era/configs/general.yaml) to point to your prover API from another machine. So, instead of the default value: ... prover_gateway: api_url: http://127.0.0.1:3320/ ... Provide the prover URL: ... prover_gateway: api_url: http://<host>:<port>/ ... Please, let us know if this works for you. — Reply to this email directly, view it on GitHub <#1068 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANHZNAYNYYQOSPQBEFQMO5L3JTIYTAVCNFSM6AAAAACB4CGRROVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOBTGMZDMOA> . You are receiving this because you were mentioned.Message ID: <zkSync-Community-Hub/zksync-developers/repo-discussions/1068/comments/13833268 @github.com>