DAO representatives: @FREDY @mcitizen42
Clarification
Retain the existing 6-of-9 signature threshold for the Council Multisig.
Apply the proposed 5-of-9 threshold to all other DAO Multisigs (Treasury, Integrations, Marketing, and any future operational Multisigs).
Rationale
1. Protocol-critical security.
As per TIP-001 the Council Multisig safeguards ownership of core protocol contracts and serves as the final recovery key. Maintaining a 6-of-9 super-majority (≥ 66 %) preserves Byzantine-fault-tolerance while still allowing timely action. The community already endorsed this balance in GP-007, which lowered the Council from 7-of-9 to 6-of-9 after extensive debate on usability versus risk.
2. Operational efficiency elsewhere.
Treasury, Integrations, and Marketing Multisigs execute frequent, lower-risk transactions. The 5-of-9 threshold proposed in TIP-103 strikes an appropriate blend of speed and security for these day-to-day functions, minimising signer-coordination delays without exposing mission-critical assets.
3. Layered security model.
Distinct thresholds formalise a clear governance hierarchy:
-
Council Multisig (6-of-9) – highest-security, protocol-level actions, veto / recovery powers.
-
Operational Multisigs (5-of-9) – delegated spending and maintenance responsibilities.
This separation hardens the network’s defence-in-depth while empowering the Threshold Committee to move quickly within their mandates.
As the newly formed Threshold Committee champions openness and community-driven governance, explicitly documenting this threshold distinction avoids confusion for contributors, auditors, and new stakeholders.TIP-103 does not explicitly address this distinction, so we seek to clarify it.
Please share your concerns, recommendations or alternative views.