🏛️ Multi-Sig-Governance | Quorum Threshold Checker for WASM Code Upgrades

[ayandipe]

Description

Implements N-of-M multi-sig authorization for WASM code upgrade proposals to prevent single-key compromise exploits.

Changes

• Track threshold weight and registered administrative signers — MultiSigConfig (required_weight, max_signer_weight) and per-signer weights stored in instance storage
• Abort upgrade if below quorum — propose_upgrade now accepts signers: Vec<Address> and returns ThresholdNotReached when collected weight < configured threshold
• Emit GovernanceUpgradeProposed event — published via emit_simple2 with EV_UPGRADE_PROPOSED topic, includes new_wasm_hash, proposer, signers, staged_at, required_weight, and collected_weight
• Default required_weight set to 1 for backward compatibility; production deployments configure via set_multisig_config

Files Changed

File	Change
src/governance.rs	Default required_weight 3→1; cleaned dead code in verify_upgrade_quorum
src/lib.rs	New imports; propose_upgrade accepts signers, verifies quorum, stores proposal, emits event
src/test.rs	Updated propose_upgrade call with signers param
tests/unit.rs	Updated propose_upgrade calls with signers param

Closes #595

[ayandipe]

remaining errors are pre-existing cascade failures in other modules ( consensus.rs , staging.rs , settlement/ , router/ , etc.) from ongoing development work — none related to #595.