midnight-node:node-architecture

Describe Midnight Substrate node architecture, block production, and finality.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, actionable explanation of how a Midnight Substrate-based node is organized and operates so developers and operators can debug, audit, and integrate nodes with Cardano and adjacent services without reading scattered design notes.

Core Features & Use Cases

  • Runtime layout and pallets: Describes the node, runtime, pallets (system, consensus, midnight-specific, partner-chain bridge) and where on-chain logic lives.
  • Consensus & finality: Explains AURA block production, GRANDPA finality, BEEFY bridge proofs, and MMR usage for light clients.
  • Ledger, storage & transaction flow: Details ParityDB-backed ledger storage, ZK-proof verification, transaction pool filtering, throttle pallet, and the lifecycle from RPC submission to state update.
  • Cardano integration: Covers db-sync/PostgreSQL follower architecture, cNIGHT bridging constraints, validator rotation, and governance sync scenarios.
  • Use case: Use this Skill to onboard new node operators, troubleshoot block production/finality issues, or prepare a security/design review of cross-chain bridge behavior.

Quick Start

Ask the skill to explain how the Midnight node produces blocks, list the runtime pallets involved, and describe the transaction flow and Cardano bridging points.

Frequently Asked Questions about midnight-node:node-architecture

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

FAQPage Schema
How does the Midnight node produce blocks and reach finality?

The Midnight node produces blocks using AURA and reaches finality through GRANDPA. BEEFY generates bridge proofs and MMR supports light clients, enabling secure cross-chain communication and verifiable state transitions.

What runtime pallets are involved in Midnight Substrate node architecture?

The Midnight runtime includes system, consensus, midnight-specific, and partner-chain bridge pallets. These modules govern on-chain logic, transaction filtering, throttle mechanisms, and ZK proof verification within the node's operational framework.

How do I troubleshoot block production or finality issues on a Midnight node?

Troubleshooting Midnight node block production and finality involves auditing AURA configuration, GRANDPA voter state, and BEEFY proof generation. Analyzing ParityDB ledger storage and transaction pool filtering helps identify consensus stalls or runtime pallet errors.

How does ZK proof verification work in the Midnight ledger and transaction flow?

ZK proof verification in Midnight occurs during the transaction lifecycle from RPC submission to state update. The node validates zero-knowledge proofs against ParityDB-backed ledger storage, applying transaction pool filtering and throttle pallet rules before committing state changes.

Can I integrate a Midnight Substrate node with Cardano using db-sync?

Yes, Midnight integrates with Cardano through a db-sync PostgreSQL follower architecture. This setup handles cNIGHT bridging constraints, validator rotation, and governance synchronization, allowing Substrate-based nodes to track and verify Cardano chain state.

What is the role of ParityDB in Midnight node storage and ledger management?

ParityDB serves as the backend for Midnight node ledger storage, managing state and transaction data efficiently. It supports ZK proof verification and transaction pool filtering by providing persistent, queryable storage for the Substrate runtime and consensus mechanisms.