midnight-tooling:proof-server

Manage Midnight proof server Docker deployments and health checks.

37|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-tooling-proof-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: midnight-tooling:proof-server
Source: https://github.com/devrelaicom/midnight-expert/tree/main/plugins/midnight-tooling/skills/proof-server
Command: npx skills add https://github.com/devrelaicom/midnight-expert --skill midnight-tooling-proof-server

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides clear, actionable guidance to run, inspect, and troubleshoot the Midnight proof server so developers can generate and verify zero-knowledge proofs reliably for local, testnet, or mainnet environments.

Core Features & Use Cases

  • Start, stop, and restart: Instructions to run the proof server as a Docker container, manage container lifecycle, and replace existing instances.
  • Health and readiness checks: How to verify /health, /ready, and /version endpoints and interpret HTTP 200 vs 503 readiness states.
  • Version selection and tagging: Guidance to list Docker Hub tags, choose the latest stable semver, and fall back to latest when necessary.
  • Troubleshooting: Common failure modes, Docker daemon checks, port conflicts, log inspection, and resource recommendations for reliable operation.
  • Use Case: A developer running a local devnet or connecting a DApp to testnet can follow these steps to ensure the proof server is running on port 6300 and serving proof generation requests.

Quick Start

Ask the assistant to start the Midnight proof server in Docker and verify it responds on port 6300.

Frequently Asked Questions about midnight-tooling:proof-server

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Midnight proof server in Docker?

To run a Midnight proof server, use Docker to pull the midnightntwrk/proof-server image, start the container with port 6300 exposed, and verify the instance is serving proof generation requests.

How do I check the health and readiness of a Midnight proof server?

Check Midnight proof server health by querying the /health, /ready, and /version endpoints, interpreting HTTP 200 as ready and HTTP 503 as not ready for proof generation.

Why is my Midnight proof server returning a 503 readiness status?

A 503 readiness status from the Midnight proof server indicates the instance is not ready, requiring log inspection, Docker daemon checks, and port conflict resolution for reliable operation.

How do I select the correct Docker image tag for a Midnight proof server?

Select a Midnight proof server Docker image tag by listing tags on Docker Hub, choosing the latest stable semver, and falling back to the latest tag when a specific stable version is unavailable.

Do I need Docker to manage a Midnight proof server deployment?

Docker runtime is required to manage Midnight proof server deployments for local containers and devnet-managed instances, though remote testnet and mainnet endpoints can be accessed without local Docker.

What are common troubleshooting steps when a Midnight proof server fails to start?

Troubleshoot a Midnight proof server startup failure by checking the Docker daemon, resolving port 6300 conflicts, inspecting container logs, and verifying resource allocations for reliable operation.