Overview

Uses the Custom database type to initialize a shared instance of ParityDb with custom config.

Ledger storage can either be stored separately to Substrate storage (default, for backwards compatibility) or can be stored in the same ParityDb instance. This is controlled via a new config option, storage_separation.

Using the unified option requires nodes to re-sync from genesis.

Resolves: https://github.com/midnightntwrk/midnight-security/issues/66
Resolves #1297

🗹 TODO before merging

• Ready
• Requires feat: allow shared parity_db backend through generic Deref midnight-ledger#430
• Waiting for feat: ledger 8.1 #1301
• Requires merge and release of feat: allow initialization of ParityDb backend using an existing database instance midnight-ledger#321

📌 Submission Checklist

• Changes are backward-compatible (or flagged if breaking)
• Pull request description explains why the change is needed
• Self-reviewed the diff
• I have included a change file, or skipped for this reason:
• If the changes introduce a new feature, I have bumped the node minor version
• Update documentation (if relevant)
• Updated AGENTS.md if build commands, architecture, or workflows changed
• No new todos introduced

🧪 Testing Evidence

Please describe any additional testing aside from CI:

• Added unit tests + integration tests for initializing storage in both separate and unified modes
• Nodes 4 and 5 (block producers) in local-env are set to use unified mode

🔱 Fork Strategy

• Node Runtime Update
• Node Client Update
• Other:
• N/A

Links