# Slashing Incident involving Launchnodes Validators - Oct 11, 2023 **URL:** \ **Category:** Node Operators\ **Created:** [October 11, 2023, 8:58pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631 "2023-10-11T20:58:58Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [October 11, 2023, 8:58pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/1 "2023-10-11T20:58:58Z")
On October 11, 2023 20 validator slashings related to validators operators by Launchnodes as a part of the Lido protocol were observed. The node operator has shut down the impacted node(s) and is investigating the root cause. The Node Operator is currently assessing the full impact and working on a plan to bring back the remaining validators together with the assistance of Lido DAO NOM contributors. More information and a detailed incident report will follow. **[https://twitter.com/LidoFinance/status/1712142945783013393](https://twitter.com/LidoFinance/status/1712142945783013393)** ---
**Author:** ![kethfinex](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kethfinex/32/930_2.png) [@kethfinex](https://research.lido.fi/u/kethfinex)\ **Post date:** [October 12, 2023, 11:07am UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/2 "2023-10-12T11:07:16Z")
**Update:** At this time, the situation is stable as the Launchnodes team worked through the night to slowly bring the rest of the validator infrastructure back up. The root cause of the slashing incident is understood, with small details still being investigated. Slashed validator penalties currently amount to 20.04 ETH and are estimated to increase to 23.06 ETH by time of withdrawal. Infra downtime penalties and overall missed rewards (excl. EL rewards) amount to 5.663 ETH (including slashed validators). Launchnodes immediately expressed their desire to compensate stakers at the soonest possible time, and so disbursed 25.663 ETH prior to today’s rebase, which means that stakers will see no reduced rewards for the day resulting from the outage and slashing. Once future penalties and missed rewards for the slashed validators are finalised (i.e. the validators are withdrawn), a final calculation will be made and Launchnodes have indicated that they will also cover this amount resulting in no lost rewards for stETH holders. The compensation transaction for the day’s reduced rewards can be found [here](https://etherscan.io/tx/0x7b0a1a53f9435c1d29d0c973ff5883ac0764dc90f6ad40fa5360b205bf9754c2). A full post-mortem will be posted here in the coming days. ---
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [October 13, 2023, 6:13pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/3 "2023-10-13T18:13:35Z")
The blog with the post mortem which includes the full incident report by Launchnodes has been published. > **[Post Mortem: Lido on Ethereum Launchnodes Slashing Incident](https://blog.lido.fi/post-mortem-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. Note: In the previous slashing incident, there was a DAO vote to lower the operator’s key limit as a precautionary measure to prevent additional stake being allocated. In this case, while exploring options and considering functionality introduced in LoP V2, Launchnodes elected to remove an unused key (below their limit at the time, which was 4000 keys) which reset their vetted keys (i.e. validator limit) to their current number of used keys (2582) (details and relevant transaction are in the post mortem). As a result, there is no current need to set a validator limit for the NO by explicit DAO vote. EDIT: Also including the relevant tweets here for posterity [https://twitter.com/LidoFinance/status/1712898983998214645](https://twitter.com/LidoFinance/status/1712898983998214645) ---
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [November 27, 2023, 4:56pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/4 "2023-11-27T16:56:41Z")
An update on the slashing incident: as at Nov 16, 2023 the 20 validators in question are now withdrawable (and have thus stopped accumulating penalties). The breakdown of the total penalties and missed rewards can be found in the below-attached image. Actual total penalties have been calculated as the change in balance of the relevant validators as of the slashing epoch for each validator up until the epoch that each became withdrawable. Missed rewards have been calculated in the same manner that they were in the [post mortem](https://blog.lido.fi/post-mortem-launchnodes-slashing-incident/). The actual amount of penalties was less than the initially projected amount per the post mortem. The total amount of | Total Penalties & Missed Rewards (initial estimate) | Total Penalties & Missed Rewards (actual) | Initially Compensated on day of incident | Remainder | | --- | --- | --- | --- | | 28.677 ETH | 28.463 ETH | 25.663 ETH | 28.463 - 25.663 = 2.8 ETH | For those who wish to check or re-perform the calculations it can be done here: - [Using the Lido DAO maintained public Ethereum beacon chain dataset on BigQuery](https://colab.research.google.com/drive/1hQAWxTSgffwpqL250VN9ke2FQ_NikfXt) (user must pay for queries) _Note that penalties for specific duties (attestations, proposals, etc.) are based on calculation and cannot be queried directly from chain data._ As indicated by Launchnodes, they will be compensating stakers for the remainder of this amount (i.e. less the compensation already sent). The compensation will occur by sending the ETH amount to the [Lido Execution Layer Rewards Vault](https://docs.lido.fi/deployed-contracts/). ---
**Author:** ![Rajesh](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/rajesh/32/2451_2.png) [@Rajesh](https://research.lido.fi/u/Rajesh)\ **Post date:** [November 28, 2023, 2:41pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/5 "2023-11-28T14:41:46Z")
Many thanks to the whole Lido DAO community and the broader ecosystem of Operators and Stakers. We really appreciate your support with this event, and with your diligence in helping to ensure that all Lido stakers have been made whole. The Launchnodes team sent the outstanding balance to the Lido Execution Layer Rewards Vault today: > **[Ethereum Transaction Hash (Txhash) Details | Etherscan](https://etherscan.io/tx/0x21106629e611405f6e74ac1754dc8e10bd085af35936424aca907f335a714ab3)** > > Ethereum (ETH) detailed transaction info for txhash 0x21106629e611405f6e74ac1754dc8e10bd085af35936424aca907f335a714ab3. The transaction status, block confirmation, gas fee, Ether (ETH), and token transfer are shown. We’re looking forward to supporting and participating in the projects already underway to help ensure the robustness and security of Lido. 🙏 ---
**Author:** ![Rajesh](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/rajesh/32/2451_2.png) [@Rajesh](https://research.lido.fi/u/Rajesh)\ **Post date:** [January 10, 2024, 2:49pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/6 "2024-01-10T14:49:18Z")
Hi All We wanted to provide an update on progress and plans. We have been running our nodes in a backup environment while restoring and hardening our bare metal infrastructure in Africa. The new infrastructure removes key dependencies and risks, and is being assessed for vulnerabilities by a leading web3 security body this week. After taking on board any of their findings and recommendations, we aim to switch back to our original data center as soon as possible, ideally from next week onwards. We have been running test nodes on the new infrastructure, and are looking forward to being back with production nodes soon too. In terms of a migration plan, we have very well rehearsed processes for safely moving between environments and avoiding double attestations or other issues. Key steps are included below, with feedback or questions very welcome. We’ll keep you posted, thank you as always for your support. 🙏 ![Launchnodes - Lido Migration from Failover Site - Steps 1-16](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/4/4cd5bf5e3268cfc86d323f072cb3522608cbc096.jpeg) ---
**Author:** ![Rajesh](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/rajesh/32/2451_2.png) [@Rajesh](https://research.lido.fi/u/Rajesh)\ **Post date:** [March 17, 2024, 6:54pm UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/7 "2024-03-17T18:54:37Z")
I wanted to update you on plans for Launchnodes to migrate back to its bare metal infrastructure in Africa, following the outage and issues experienced last year. We have carefully rebuilt our infrastructure with an improved architecture designed to further reduce points of failure, and provide additional robustness and security. Over the past 2 months, in addition to the feedback and support we have had from Lido operators and the broader community, we have had support from 3rd parties to examine our setup prior to go-live, and highlight areas for improvement. To date, the following have been flagged: - 10 ‘High Severity’ risk issues - 11 ‘Medium Severity’ risk issues - 11 ‘Low Severity’ risk issues - 2 ‘Informational’ issues As examples: One ‘High Severity’ issue flagged was traffic from our internal Grafana servers not being SSL encrypted. A ‘Medium Severity’ issue was not using SSO across all of our infrastructure. A ‘Low Severity’ issue was not logging all traffic and connections, which would be useful for diagnostics and forensics. (These and the majority of other recommendations have been implemented). Resolutions have been implemented for all ‘High’ severity issues. Resolutions for 8 of the ‘Medium’ severity issues have been implemented, with the remaining 3 acknowledged by Launchnodes for further investigation and future planned updates. Resolutions have been applied for 10 of the 11 ‘Low’ Severity issues, with 1 issue acknowledged. Issues have typically been ‘acknowledged’ for non-critical issues, where the recommendation is understood, however further investigation or planning/testing is required for the recommendation to be fully implemented. For example, we are cautious in implementing some automation of processes/server re-starts, and to set hard limits for some parameters until we have monitored production systems for some weeks at least. Where a resolution might have an impact on node performance or uptime, we have been particularly careful. We are conscious that our environments and software will continue to change and evolve, and we regard this as a journey of continous improvement. We are planning further reviews and optimizations with our 3rd party specialists in the coming days and weeks. We have also been successfully running multiple nodes on Holesky in our updated environments. The team is confident in moving back to our bare metal data centres, and aiming to start this process from 20th March 2024. We plan to move across a small number of nodes, monitor these for 7 days, before migrating our remaining nodes to the new environment. The old environment and web3signer will be destroyed before nodes are migrated and re-started. This timing has been chosen to provide a good period of stability after Dencun and a decent period of monitoring unaffected by major events or public holidays. Our monitoring and alerting will continue to operate 24x7, with our global team on standby throughout. Please reach out if you have any feedback or would like more information, happy to discuss in more detail. Many thanks as always for your patience and support - We’ll update you with progress as this migration takes place and ongoing. 🙏 ---
**Author:** ![Izzy](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/izzy/32/320_2.png) [@Izzy](https://research.lido.fi/u/Izzy)\ **Post date:** [March 20, 2024, 7:04am UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/8 "2024-03-20T07:04:01Z")
Hey Rajesh. Thanks for sharing detailed updates on the infrastructure review you’ve performed and the plans for moving ack to bare metal infra. Look forward to the updates on progress of the migration efforts. ---
**Author:** ![Rajesh](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/rajesh/32/2451_2.png) [@Rajesh](https://research.lido.fi/u/Rajesh)\ **Post date:** [May 8, 2024, 7:19am UTC](https://research.lido.fi/t/slashing-incident-involving-launchnodes-validators-oct-11-2023/5631/9 "2024-05-08T07:19:53Z")
Hi all Sharing an update on our Africa Infrastructure for Lido nodes here: > [@Launchnodes: Africa Infrastructure Update](https://research.lido.fi/t/launchnodes-africa-infrastructure-update/7441): > > We wanted to provide an update on Launchnodes’ Africa infrastructure and Lido nodes. Following the major incident last year, Launchnodes has rebuilt our infrastructure to be more resilient. Changes have included: Architecture updated to remove key points of failure / dependencies Node configuration changes, in conjunction with the client teams Additional slashing protection added Testing and adding multiple MEV relays These changes have been bedded down and optimized over several months, w… Please reach out with any questions or feedback. Many thanks.