[ZK Stack] - Example of production ready setup for a rollup #889
-
Team or ProjectNo response Module Affected
Rust Version1.82.0 Operating System
Issue DescriptionI find your documentation extremely helpful and very detailed! Thank you for putting all the work into this. I hope I'm not missing some obvious here but I'm trying to find the steps for creating a more production ready rollup spin up, not just local setup.
Expected BehaviorCurrent BehaviorRepository Link (if applicable)No response Additional DetailsNo response Prior Research
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hello! Right now, the documentation and infrastructure for running ZKsync networks in production is under development. Docker images can currently be found on dockerhub, we're working on migrating to ghcr fully, but it's WIP. The information on releases can be found on the releases page. Now, onto the configuration. Currently, we're using file-based configuration system, so configuring it is very similar to running the system locally via To see how to pass arguments to the server binary, you can run it directly after compiling, e.g. |
Beta Was this translation helpful? Give feedback.
Hello! Right now, the documentation and infrastructure for running ZKsync networks in production is under development.
In general, the architecture is built for k8s using helm charts. The charts, however, are not open-source yet.
Docker images can currently be found on dockerhub, we're working on migrating to ghcr fully, but it's WIP.
There is a tag for each release that was pushed to testnet, you can query it as
2.0-v<version>
, e.g. here's an image for release v25.4.0.Prover images can be found there as well, they follow the different release schedule.
The information on releases can be found on the releases page.
Now, onto the configuration. Currently, we're using file-based configurat…