midnight-tooling:devnet

You set up a local Midnight devnet by generating a ready-to-run devnet.yml that resolves the latest stable images for the node, indexer, and proof-server. This creates a reproducible local environment for testing smart contracts and connecting DApps.

Version resolution for Midnight devnet components works by automatically identifying and pulling the latest stable Docker images for the node, indexer, and proof-server. This ensures your local devnet environment remains reproducible and up-to-date across lifecycle operations.

Yes, you need Docker to run the containerized services and jq to process JSON data during devnet management. These dependencies are required to execute the scripts that resolve image versions and orchestrate the node, indexer, and proof-server lifecycle.

Yes, you can manage the start, stop, and status checks for a Midnight devnet using lifecycle orchestration commands. The devnet management tool applies health checks to monitor the 3-service devnet, ensuring the node, indexer, and proof-server are running correctly.

To connect your DApp to a local Midnight devnet, you read the exposed endpoints and configuration from the running devnet. This allows your DApps and wallets to interface directly with the local Midnight network for testing and development.

A local Midnight devnet is designed specifically as a reproducible test environment for smart contracts and tooling, meaning it is not optimized for production scale. Lifecycle management is limited to generating configurations and orchestrating the start and stop of the 3-service local network.