Onchain Logic and State

The Midnight node follows the standard Polkadot SDK model: core logic (except native pre-compiles) compiles to WebAssembly (WASM) and forms the runtime — the state transition function executed identically on every node.

Runtime architecture

flowchart TB
  subgraph Runtime["WASM Runtime"]
    direction TB
    PA["pallet-aura"]
    PG["pallet-grandpa"]
    PS["pallet-partnerchains-session"]
    PVM["pallet_session_validator_management"]
    PM["pallet-midnight ★"]
    Other["Other FRAME pallets"]
  end

  Block["Incoming block + extrinsics"] --> Runtime
  Runtime --> Trie["Patricia-Merkle trie commit"]
  Trie --> DB["ParityDB persistence"]
  PM --> Ledger["Midnight Ledger state commitment"]

FRAME pallets

Each FRAME pallet encapsulates a domain of on-chain logic and may define:

• Storage (maps, multi-maps, lists, values)
• Events
• Dispatchable functions (transactions)
• Offchain workers
• Hooks
• Host-exposed functions
• RPC methods

This modular design is similar in spirit to a smart contract framework, but logic is compiled ahead of time and governed at the chain level.

Key pallets on Midnight

pallet-midnight: the ledger state machine

pallet-midnight is internally maintained and encapsulates the Midnight Ledger state machine.

sequenceDiagram
  participant Tx as Ledger transaction
  participant Pool as Transaction pool
  participant PM as pallet-midnight
  participant Lib as Native proof libraries
  participant State as On-chain storage

  Tx->>Pool: Submit (unsigned, proof-embedded)
  Pool->>Pool: Well-formedness check
  Pool->>PM: Included in block
  PM->>Lib: Verify cryptographic proof
  Lib-->>PM: Valid / invalid
  PM->>State: Execute state transition
  State->>State: Commit trie + ledger commitment

What it processes

• ZSwap asset transfers
• Contract operations (deploy, invoke)
• Specialized transactions from the Midnight Ledger format

Validation model

• Not traditional signature-based dispatch for ledger txs.
• Each transaction embeds a cryptographic proof attesting validity.
• Native libraries verify proofs and execute corresponding state transitions.

State commitment

After execution:

1. New state is committed on-chain.
2. Canonical ledger state lives in a Patricia-Merkle trie backed by a key-value database.
3. A commitment to the full Midnight Ledger state is persisted per block — tamper-proof and verifiable.

Public vs ledger state

For application-level privacy patterns, see why-midnight/ and compact/.

Related skills

• midnight-consensus/ — AURA + GRANDPA pallets
• midnight-transactions/ — transaction pool → runtime → commit lifecycle
• midnight-storage/ — ParityDB + trie details
• midnight-rpc/ — querying contract and ledger state via RPC