Thanks to dapplion, Maxim Merkulov, Mikhail Kalinin, and P2P.org’s Ethereum team for reviewing and providing valuable feedback.

Written by Pavel Iashin, a researcher at P2P.org.

If you have any questions or comments, feel free to reach out to me on X.


Table of Contents

  1. TL;DR
  2. Intro
    1. About the writing
    2. EIP-7251 in a nutshell
    3. Autocompounding and Consolidation
  3. About Slashing
    1. Essentials
    2. Pectra Slashing Penalty Changes
    3. Why does slashing usually happen?
  4. Slashing Risks Under Consolidation
    1. Cluster Case
    2. Delegator Case
  5. Closing notes

TL;DR

Putting it even more shortly: it’s all about the number of validator keys.

*A cluster is a set of nodes/keys united by the same operational environment/setup and hence exposed to the same risk. In the context of this writing, this, more often than not, will mean the set of keys sharing the same key management solution.

**Here, a large cluster is loosely thought to be larger than 2048 keys of 32 ETH validators, or 32 keys of 2048 ETH validators, or just larger than 65k ETH in total. This is the point where full consolidation won’t introduce significant changes in the risk profile. Significance is quite subjective, though; make your own judgment before action.

Intro