# Validated, staking on eth2: #6 - Perfect is the enemy of the good

DevFeed: [Validated, staking on eth2: #6 - Perfect is the enemy of the good](<https://devfeed.tech/articles/validated-staking-on-eth2-6-perfect-is-the-enemy-of-the-good-16940.md>)

Original publisher: [Read original article](<https://blog.ethereum.org/en/2020/12/10/validated-perfect-is-the-enemy-of-the-good>)

Author: Carl Beekhuizen

Published: 2020-12-10T00:00:00Z

Content type: opinion

Language: en

Sources: [Ethereum Foundation Blog](<https://devfeed.tech/sources/ethereum-foundation-blog.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Internet](<https://devfeed.tech/topics/internet.md>)

Tags: [firewalls](<https://devfeed.tech/tags/firewalls.md>), [internet](<https://devfeed.tech/tags/internet.md>), [network](<https://devfeed.tech/tags/network.md>), [offline](<https://devfeed.tech/tags/offline.md>), [research-development](<https://devfeed.tech/tags/research-development.md>), [ssd](<https://devfeed.tech/tags/ssd.md>), [uptime](<https://devfeed.tech/tags/uptime.md>)

## AI overview

This article examines validator failure modes on the beacon chain, including missed duties, inactivity leaks, and slashings. It argues that validators should prioritize failures that could affect many validators simultaneously, because correlated failures can lead to more severe penalties.

## Source excerpt

T'was the day before genesis, when all was prepared, geth was in sync, my beacon node paired. Firewalls configured, VLANs galore, hours of preparation meant nothing ignored. Then all at once everything went awry, the SSD in my system decided to die. My configs were gone, chain data was...