midnight-node:node-governance

Federated governance for Midnight nodes distributes authority across two bodies, the Council and Technical Committee. It enforces a verifiable motion lifecycle from proposal to execution, requiring a 2/3 voting threshold in both bodies to approve actions like runtime upgrades.

To execute runtime upgrades, you propose a governance motion and simulate the voting process through a Propose, Vote, Approve, and Close lifecycle. Joint approval from both bodies triggers time-delayed execution to ensure the upgrade is applied securely.

The voting threshold for Midnight council and technical committee approvals is 2/3 in both bodies. The system enforces a 5-day voting window for motions, ensuring sufficient time for deliberation before a proposal can be closed and executed.

Yes, you can adjust D-parameters by proposing a governance motion through the federated workflow. D-parameter changes require joint approval from the Council and Technical Committee along with time-delayed execution, ensuring critical parameter changes are secure and auditable.

You need joint approval from both a council and a technical committee for critical on-chain operations like runtime upgrades and D-parameter adjustments. This federated approach reduces single-point risk by distributing authority across both bodies.