# Publication of the use of the Multi-Sig emergency powers on the 6th of March 2025
**URL:** https://forum.ssv.network/t/publication-of-the-use-of-the-multi-sig-emergency-powers-on-the-6th-of-march-2025/1856
**Category:** DAO
**Created:** [March 9, 2025, 8:11am UTC](https://forum.ssv.network/t/publication-of-the-use-of-the-multi-sig-emergency-powers-on-the-6th-of-march-2025/1856 "2025-03-09T08:11:37Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@BenAffleck](https://forum.ssv.network/u/BenAffleck)
#### Post date: [March 9, 2025, 8:11am UTC](https://forum.ssv.network/t/publication-of-the-use-of-the-multi-sig-emergency-powers-on-the-6th-of-march-2025/1856/1 "2025-03-09T08:11:37Z")
On the 6th of March 2025, the ssv.network DAO Multi-Sig Committee exercised its emergency powers under the Defined Emergency Procedure as outlined in [[DIP-2] Multi-Sig Committee](https://snapshot.org/#/mainnet.ssvnetwork.eth/proposal/0x393b81f83e63e6ecbd95a61d88ecc53d8668e6a2b32a5f323291860c280dd050).
Following the execution of [[DIP-29] Increase of validator limit per operator](https://snapshot.box/#/s:mainnet.ssvnetwork.eth/proposal/0x0c3795a0f0dd1ac99c62f9ee4e2acc89421756605d7611de97759add211173ff) on the 6th of March 2025, it has been noticed that anyone can set the number of validators per operator. The practical implication of this state was that validator registration would become blocked, consequently.
In reaction to the above, the ssv.network Multi-Sig [has voted with 5/9] on its dedicated emergency channel to consider this situation as a Defined Emergency Situation as described in [[DIP-2] Multi-Sig Committee](https://snapshot.org/#/mainnet.ssvnetwork.eth/proposal/0x393b81f83e63e6ecbd95a61d88ecc53d8668e6a2b32a5f323291860c280dd050). Within the first 24 hours, the ssv.network DAO Multi-Sig Committee has found a solution to the issue, and as such, it required a 5/9 “Yes” vote to consider this situation as a Defined Emergency Situation. No member of the ssv.network DAO Multi-Sig Committee has voted “No”.
The fix was deployed with [TX 522](https://app.safe.global/transactions/tx?safe=eth:0xb35096b074fdb9bBac63E3AdaE0Bbde512B2E6b6&id=multisig_0xb35096b074fdb9bBac63E3AdaE0Bbde512B2E6b6_0x6e7b21575a1917fc2b74de01bc0cc4436939dfa465362ad4d7c83eae7d531ec6), making sure no one can call the relevant `initializeV2()` function but the owner.
In line with [[DIP-2] Multi-Sig Committee](https://snapshot.org/#/mainnet.ssvnetwork.eth/proposal/0x393b81f83e63e6ecbd95a61d88ecc53d8668e6a2b32a5f323291860c280dd050), the ssv.network DAO Multi-Sig Committee is publishing the use of its emergency powers to the community.
---
### Author:  [@Yuting](https://forum.ssv.network/u/Yuting)
#### Post date: [March 9, 2025, 1:32pm UTC](https://forum.ssv.network/t/publication-of-the-use-of-the-multi-sig-emergency-powers-on-the-6th-of-march-2025/1856/2 "2025-03-09T13:32:48Z")
Very good emergency handling practices. Additionally, I think we can analyze the weaknesses in the testing phase that lead to logical bugs in the contract.
---
### Author:  [@AXBLOX](https://forum.ssv.network/u/AXBLOX)
#### Post date: [March 9, 2025, 8:02pm UTC](https://forum.ssv.network/t/publication-of-the-use-of-the-multi-sig-emergency-powers-on-the-6th-of-march-2025/1856/3 "2025-03-09T20:02:25Z")
Great job to the Multi-Sig Committee for acting quickly to resolve this! Transparency and fast decision-making like this keep the network secure and resilient.
---
### Author:  [@llifezou](https://forum.ssv.network/u/llifezou)
#### Post date: [March 10, 2025, 9:52am UTC](https://forum.ssv.network/t/publication-of-the-use-of-the-multi-sig-emergency-powers-on-the-6th-of-march-2025/1856/4 "2025-03-10T09:52:30Z")
The quick and effective action of the multi-sig committee avoids malicious settings and protects the network! Good job!