annotated-spec

I know about that but thanks for your comment - I’ll clarify what I mean. It’s just the specifics of how this works - slashing is part of the protocol in the sense that I described: when you are chosen to create a new block and you have proof that someone violated the rules then you include this proof in your proposed block and update balance. Any validator can do it including the smallest of home stakers. More details here. https://github.com/ethereum/annotated-spec/blob/master/phase... Here we have slashing fields in the block body where you insert your proofs of slashable offense. There are functions with a “slash” in the name that describes precise state transition. The hard part of slashing is finding these proofs because you have to do more work than necessary to detect slashing and produce proofs - that’s what this software does.

Great question. You can check here how the 32 ETH came to be: https://github.com/ethereum/annotated-spec/blob/master/phase...