# Emergency Brakes multi-sig upgrade
**URL:** https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608
**Category:** Proposals
**Created:** [July 21, 2022, 1:58pm UTC](https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608 "2022-07-21T13:58:41Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@GrStepanov](https://research.lido.fi/u/GrStepanov)
#### Post date: [July 21, 2022, 1:58pm UTC](https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608/1 "2022-07-21T13:58:41Z")
Security and transparency are among the most valued properties of any new Lido integration, governance tool, or general protocol upgrade. Lido contributors tend to provide full control over the protocol to the DAO, and avoid permissioned and trusted designs wherever it is possible. All the critical roles are normally assigned to the DAO Agent, an Aragon app that can perform arbitrary calls to contracts on behalf of the DAO.
However, the existing DAO governance mechanisms are sometimes too slow to react to emergencies. In such cases, we suggest consistently using a dedicated Emergency Brakes Multi-sig that normally would be able to pull only one lever – that is, pause whatever project, protocol, or integration it is used for. At the same time, it isn’t meant to have the ability to unpause things, the DAO Agent should be the entity to resume operations.
For the first time, we have used an emergency brakes multi-sig for [the Easy Track](https://research.lido.fi/t/lip-3-easy-track-release/1406#pause-multi-sig-7). The current composition of [this 2/4 multi-sig](https://gnosis-safe.io/app/eth:0x73b047fe6337183A454c5217241D780a932777bD/settings/owners) includes core Lido contributors:
@vsh
`0x2a96805188e583dd760785A0dE93128504DDd5c7`
@kadmil
`0x6f5c9B92DC47C89155930E708fBc305b55A5519A`
@psirex
`0x2a61d3ba5030Ef471C74f612962c7367ECa3a62d`
@ujenjt
`0xdd19274b614b5ecAcf493Bc43C380ef6B8dfB56c`
### We propose:
1. Extending and reinforcing the existing Easy Track Security multi-sig to 3/5 by including another Lido protocol developer @folkyatina with address `0xCFfE0F3B089e46D8212408Ba061c425776E64322` ([tweet to confirm the address](https://twitter.com/folkyatina/status/1550112058003169284?s=20&t=9RHqr47D6r_5Vin6SrU5Qw)).
2. Use the same multi-sig as Emergency Brakes multi-sig for other Lido projects and integrations on Ethereum. Set up multi-sigs of the same composition to manage pause levers on other networks as Lido expands there, starting with Optimism and Arbitrum in the nearest future.
The decision will be made via a 5-days snapshot voting starting shortly.
---
### Author:  [@GrStepanov](https://research.lido.fi/u/GrStepanov)
#### Post date: [July 21, 2022, 2:08pm UTC](https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608/2 "2022-07-21T14:08:18Z")
The snapshot to extend the Emergency Brakes multi-sig is live!
[https://snapshot.org/#/lido-snapshot.eth/proposal/0x2b368b535b2024394daff218d222e260dbc4543b6d4e49aa4700cc0a9233e86a](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2b368b535b2024394daff218d222e260dbc4543b6d4e49aa4700cc0a9233e86a)
---
### Author:  [@kadmil](https://research.lido.fi/u/kadmil)
#### Post date: [July 26, 2022, 4:05pm UTC](https://research.lido.fi/t/emergency-brakes-multi-sig-upgrade/2608/3 "2022-07-26T16:05:59Z")
The snapshot concluded “for” changes — thank you for the votes! We’ll proceed with multisig tweaks shortly