midnight-node:node-configuration

Configure Midnight node deployments and resolve runtime configuration issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, authoritative reference for resolving Midnight node configuration complexity so operators can reliably select networks, load presets, map environment variables, and debug runtime behavior without guesswork.

Core Features & Use Cases

  • Layered configuration model: Explains defaults, TOML presets, environment variables, and CLI argument precedence to avoid unexpected overrides.
  • Validator key and network setup: Details required seed files and env vars for AURA, GRANDPA, BEEFY and cross-chain keys and how to run nodes on qanet, preview, preprod, perfnet, devnet, and local networks.
  • Operational flags and tuning: Covers Substrate pruning, RPC and Prometheus exposure, DB cache and trie cache sizing, and development shortcuts like --dev and --tmp.
  • Debugging and reproducibility: Advises using SHOW_CONFIG to print resolved configuration and using chain spec files or TOML presets for reproducible deployments.
  • Use case: Prepare a validator for preview network with proper seed management, external RPC exposure, and pruning policy for production readiness.

Quick Start

Start a preview node and print the fully resolved configuration by setting SHOW_CONFIG=1 and launching midnight-node with the desired --chain value.

Frequently Asked Questions about midnight-node:node-configuration

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

FAQPage Schema
How do I configure a Midnight node for the preview network?

Configure a Midnight node for the preview network by selecting the desired --chain value, loading the appropriate TOML presets, and setting required environment variables. This layered configuration model ensures reliable runtime behavior.

How does configuration precedence work for Midnight nodes?

Midnight node configuration precedence applies defaults first, then TOML presets, environment variables, and Substrate CLI arguments. Understanding this hierarchy prevents unexpected overrides and ensures the intended settings take effect during deployment.

What is the best way to debug resolved Midnight node configuration?

The best way to debug resolved Midnight node configuration is setting SHOW_CONFIG=1 before launching the node with your desired --chain value. This prints the fully resolved configuration, exposing any unexpected overrides from environment variables or presets.

Do I need specific seed files to set up validator keys on a Midnight node?

Yes, setting up validator keys on a Midnight node requires specific seed files and environment variables for AURA, GRANDPA, BEEFY, and cross-chain keys. Proper seed management is necessary to run nodes on qanet, preview, preprod, perfnet, and devnet.

Can I use Substrate CLI flags to manage pruning and RPC exposure on Midnight nodes?

Yes, you can use Substrate CLI flags to manage pruning policies, expose RPC and Prometheus endpoints, and size DB and trie caches on Midnight nodes. These operational flags tune the node for production readiness and development workflows.

Why does my Midnight node configuration show unexpected overrides at runtime?

Unexpected Midnight node configuration overrides occur because environment variables and CLI arguments take precedence over TOML presets and defaults. Use SHOW_CONFIG=1 to print the fully resolved configuration and identify which layer is causing the conflict.