Post Mortem
Post Mortem
Post Mortem: Lido on Ethereum Launchnodes Slashing Incident A slashing incident took place on October 11 2023 affecting 20 validators operated by Launchnodes as part of the Lido protocol. This is an overview of events, timeline and resolution.
Lido
Post Mortem
Post Mortem: Delayed Oracle Report (April 8, 2023) On 8th of April 2023 the Oracle report finalisation had been made 6 hours later than usual ~12pm UTC. The delay had been caused by the occurence of an edge-case with a report slot being missed on the Consensus Layer, preventing the software from collecting the data.
Lido
Post Mortem
Post Mortem: Lido on Ethereum RockLogic GmbH Slashing Incident At April 13 a slashing incident occurred affecting 11 validators in the Lido on Ethereum protocol. This post mortem details what occurred and the identified root cause.
Izzy
Post Mortem
Post Mortem 26/01/2022: bETH Anchor Integration Upgrade Incident After the AnchorVault upgrade switching the bETH Anchor integration from using Shuttle to Wormhole bridge, two users have been able to execute transactions aimed for Shuttle-using code, effectively blocking their funds on unaccessible Terra addresses.   The integration have been upgraded to prevent such events from happening. Users have been refunded,
Lido
Post Mortem
Post Mortem: Disrupted rewards distribution due to missed oracle reports On November 9 and 11, 2022, Lido Oracle failed to report validator balance updates causing the rewards distribution to occur every other day instead of daily.
Lido
Post Mortem
Lido UI Potential Malicious Code Injection - Bug Bounty Report On 21.02.2022 Lido has received Immunefi report from the United Global Whitehat Security Team on a vulnerability affecting the number Lido UIs
Lido
Post Mortem
Vulnerability Response Update On Oct 5, 2021, a vulnerability was reported via the Lido bug bounty program on Immunefi by an anonymous whitehat (who later turned out to be Dmitri Tsumak, the founder of Stakewise).
Lido
Post Mortem
20.08.2021 Orphaned Blocks in Ethereum Incident Postmortem Friday night last week (Aug 20), a misconfiguration within Chorus One’s Lido Ethereum beacon chain setup led to a network-wide drop of participation of about 1% (measured by the so-called attestation rates) on the beacon chain. The issue was fixed within hours of the discovery by the involved teams.
Vasiliy Shapovalov
Telegram | Discord | Twitter | Lido.fi

© Lido . All rights reserved