Road to devnet #1187
Description
Description
This epic tracks the work required to bring the Mina Rust node to a state where it can reliably run on the Mina devnet and consistently produce blocks. The scope includes infrastructure, documentation, CLI features, stability, and alignment with the OCaml node.
Before o1Labs assumed stewardship of the Rust node codebase, some node operators were already experimenting with the earlier OpenMina implementation. This epic consolidates the work needed under o1Labs’ ownership to prepare for an official devnet launch.
Goals
- Define and implement the minimal feature set required for devnet readiness
- Operate and monitor a stable devnet environment managed by o1Labs
- Provide clear documentation and tooling for node operators and developers
- Ensure long-running stability and dependency alignment with the OCaml node
Scope
1. CLI & Node Features
- Submit zkApp transactions and simple transfers via CLI
- Generate block producer keys
2. Infrastructure
- Infrastructure code managed by o1Labs - see https://github.com/o1-labs/gitops-infrastructure/
- Deploy and maintain:
- Multiple seed nodes
- At least one archive node: Revamp the archive node #1475
- A set of block producers: Deploy two block producers on dev-net as part of o1Labs infrastructure #1463
- One node with memory profiler activated: Revamping memory profiler for the Rust node #1207
- One node with network debugger activated: Revamp mina-network-debugger to be used in the node dashboard #1365
- At least one community-facing frontend: Revamp the docker image for the front-end #1382
3. Documentation
- Deploy a documentation website with guides for running:
- Archive node
- Docker
- Docker Compose
- From source
- Block producer: Deploy two block producers on dev-net as part of o1Labs infrastructure #1463
- Docker: https://o1-labs.github.io/mina-rust/docs/node-operators/block-producer#using-docker-compose
- Docker Compose: https://o1-labs.github.io/mina-rust/docs/node-operators/block-producer#using-docker-compose
- From source: https://o1-labs.github.io/mina-rust/docs/node-operators/block-producer#using-make-command
- Seed node
- Docker
- Docker Compose
- From source
- Standard node
- Docker
- Docker Compose
- From source
- Front-end
- Docker
- Docker Compose
- From source
- Archive node
- The naming has been consistently changed from OpenMina to "the Mina Rust node" and "the Mina Web node".
- a release process has been defined and agreed with the team.
4. Community Feedback
- Resolve all community-reported issues raised before September 2025
5. Dependency Alignment
- Match OCaml node versions for:
6. Stability
- Stabilize nodes that are currently crashing after 56 days to at least 90 days
7. Web Node
- Test and deploy the web node
- Revamp the web-node on dev-net #1474
8. Release process
- Docker images for the infrastructure (mina-rust and mina-rust-frontend) are published automatically to a docker registry with a common tag pattern.
- Docker: push multi platform architecture #1337
- Docker images: publish and update docs accordingly #1334
- Docker images: publish and update docs accordingly #1335
- CI: split docker push jobs #1344
- Dockerfile: add ca-certificates to the node Docker image #1345
- CI: remove prefix 'release/' when tagging docker images #1393
- CI/docker: main branch push to latest #1394
- At least one minor release have been made to confirm the release process: Release/v0.17.0 #1398
9. CI
- The current set of tests are run in the CI environment
- This includes the unit tests ("per crate"), and the following e2e tests:
- scenario
- bootstrap
- p2p
- This does not include the revamp of the ignored or failing tests that have been defined prior August 2025. This would be postpone for the main-net readiness.
- The set of tests can be easily reproduced locally by any engineer, and is documented on the website.
Out of Scope
- Mainnet readiness
- Advanced performance optimizations
- This includes the field optimisation coined "32x9" in WebAssembly