The slashing model is revamped with Pectra to accomodate for
validators with a higher effective balance, and also to be
more permissive torwards operator errors which do not threaten
the security of the network.
The slashing penalty for a given stake depends on the number
on the number of stakes on the network (Network Staked Amount)
and the number of slashes that happened 36 days around the
slashing of the stake (Slashing Event Scale).
Diversity Risk
Diversity Risk Simulator
On Ethereum, operators have to chose a consensus client
type. Each client offers different trade-offs in terms of
security, performance, and features. However there is an
inherent risk that arises for clients that are used by more
than 1/3 of the network for a specific category of bugs. If
this category of bugs arises as it happend on testnets, the
incurred penalty for stakes running under those clients is
unavoidable. It is thus important to rely on operators that
use minority consensus clients.
This simulator uses
the Rated Network
estimations of consensus client type usage. More on this
topic can be found in our series of R&D articles on the
topic:
Part 1,
Part 2,
Part 3.
Similar to consensus clients, operators have to chose an
execution client type.
There is an inherent risk to the network if more than 2/3 of
the network is using the same execution lient, as a bug in
this client would finalize the chain, making it impossible to
revert without huge losses. As of today, no execution client
has more than 2/3 of shares so it is fine to use any execution
client available. Note that this is different than consensus
client execution, where >1/3 is a systemic risk.
This simulator uses
the Super Majority
estimations of execution client type usage. More on this
topic can be found in our series of R&D articles on the
topic:
Part 1,
Part 2,
Part 3.
Credits
Generated using 48 WEI, powered by nakamotards @ Kiln.