- Lido confirmed a signer rotation on its Emergency Brakes multisigs, replacing signer ujenjt with tamtamchik across all five supported chains
- The rotation covers 3-of-5 multisig Safes deployed on Ethereum, Optimism, Arbitrum, Base and BSC
- Emergency Brakes signers can pause affected contracts in a crisis but hold no ability to move or withdraw user funds under the system’s design
Lido published a confirmation to its governance research forum on November 11, 2026 at 18:12 UTC detailing a routine but security-relevant change to the signer set controlling its Emergency Brakes system, a cross-chain set of multisignature wallets designed to let the protocol quickly pause specific contracts in the event of a detected exploit or critical bug. The update confirms that signer ujenjt has been replaced by tamtamchik across every chain where the Emergency Brakes system is deployed.
The rotation spans five separate blockchain networks: Ethereum, Optimism, Arbitrum, Base and BSC. On each of these chains, Lido maintains a dedicated Emergency Brakes Safe, a multisignature wallet requiring three of five designated signers to agree before any pause action can be executed, a structure intended to prevent any single compromised or malicious signer from unilaterally triggering a pause, while still allowing a quick response if a genuine threshold of signers agrees a pause is warranted.
Importantly, the Emergency Brakes system is deliberately scoped to a narrow capability: signers can pause relevant contracts, halting further deposits, withdrawals, or other sensitive operations temporarily, but the system’s design explicitly does not grant signers any ability to move, withdraw, or otherwise access user funds held within those contracts. That separation between “pause” authority and “custody” authority is a deliberate security design choice meant to limit the blast radius of any compromise among the signer set itself.
Signer rotations of this kind are a routine part of maintaining any multisig-based security system over time, whether prompted by a signer’s own request to step back, a scheduled rotation policy, or other operational considerations, and this particular change does not appear tied to any detected incident or exploit attempt. Lido’s decision to publish a public confirmation of the swap nonetheless reflects the protocol’s practice of maintaining transparency around who holds keys to systems capable of pausing its infrastructure, even for routine personnel-level changes.
For a protocol managing billions of dollars in staked assets across multiple blockchains, maintaining a well-documented, regularly refreshed signer set for emergency-response systems like this one is a foundational piece of operational security, even when, as in this case, the specific change itself is unremarkable on its face. The full confirmation is published on Lido’s governance research forum.
Disclaimer: Cryip's content is strictly for educational and informational purposes and does not constitute financial, legal, or investment advice. Cryptocurrency involves significant risk, and readers assume full responsibility for their own financial decisions. Asset references are never endorsements.
To make complex crypto topics accessible to readers at all experience levels, our team uses AI tools strictly to refine language, correct grammar, and simplify terminology. AI is never used to draft facts, source information, or form conclusions. Every article is fact-checked and approved by a human editor before publication. Read our full AI Use & Content Policy.
