# Lido on Ethereum Node Operator (Numic) Security Incident Disclosure - May 21, 2024 **URL:** \ **Category:** Node Operators\ **Created:** [May 21, 2024, 10:54am UTC](https://research.lido.fi/t/lido-on-ethereum-node-operator-numic-security-incident-disclosure-may-21-2024/7536 "2024-05-21T10:54:00Z")\ **Posts on this page:** 1\ **Showing post:** 7
**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:** [May 27, 2024, 8:10am UTC](https://research.lido.fi/t/lido-on-ethereum-node-operator-numic-security-incident-disclosure-may-21-2024/7536/7 "2024-05-27T08:10:17Z")
It should be noted that DVT by itself doesn’t really solve the problem here, only if [DKG](https://en.wikipedia.org/wiki/Distributed_key_generation) was involved for key creation and a full key was never reconstituted somewhere, which is why for [Simple DVT](https://research.lido.fi/t/staking-router-module-proposal-simple-dvt/5625) a requirement for all integrations was that validator keys were created using DKG ceremonies where all cluster participants were participating was a requirement. A similar approach in terms of “sharding” the key can be employed using [Attestant’s Dirk](https://www.attestant.io/posts/introducing-dirk/), which Numic also identifies above as a a possible solution, and doesn’t require DVT. --- _[View the full topic](https://research.lido.fi/t/lido-on-ethereum-node-operator-numic-security-incident-disclosure-may-21-2024/7536)._