Thank you to @SEEDGov and the Operations Committee team on this policy. I really like implementing a policy such as this, something that we need to operate successfully.
I particularly appreciate the 3/5 signature threshold, as it strikes a solid balance between operational security and committee accountability. Furthermore, the Program Multisigs (Section 5) are an excellent inclusion; utilizing separate 2/3 wallets effectively isolates risk and ensures payment efficiency without bottlenecking individual projects. Finally, the addition of an Operational Ledger (Section 6) as a live dashboard is a fantastic step toward institutional-grade transparency, I’m looking forward to seeing this published!
However, to ensure our operational security matches our growth, I recommend the following refinements to the policy:
Accelerated Hardware Mandate:
While the move toward hardware wallets is the correct direction, the July 2026 enforcement date and the “recommended and encouraged use” leaves a significant vulnerability gap. Since during this time we will be voting for the next cohort of the Operations Committee and therefore, we should establish a secure foundation now instead of closer to July. This ensures that that any programmatic issues are resolved before the new cohort of Operations committee starts.
I propose moving to a mandatory hardware wallet requirement to March 1, 2026. Transitioning mid-term introduces unnecessary security debt; starting the new term with hardened security ensures the integrity of the Treasury from the outset.
Mandatory Security Training:
To professionalize our operations, security training must evolve from an ‘encouragement’ to a mandatory prerequisite for being added to any multisig. I suggest implementing a Signer Readiness requirement by March, ensuring all signers, are fully briefed on secure custody, air-gapped signing, and physical backup protocols. We cannot treat security as optional when managing the DAO assets and budget.