Supply validator deposits on chain

The five-minute read

One action, walked through

1. Open EIP 6110 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Appends validator deposits to the Execution Layer block structure.
3. Name the object that changes: JSON, RPC, API.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing EIP 6110 at the status the text itself states: Final.
• The object that has to change is JSON, RPC, API. A neighbouring document with a similar name is not this one.
• Parameter choices in one release are not the proof.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What does Supply validator deposits on chain treat as decided, and what can still be reorged?
• What share of stake or hash power does the argument need?
• Which objects are defined: JSON, RPC, API?

Terms

EIP 6110

The public text titled Supply validator deposits on chain.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

A consensus change that is only described in a client does not tell an outside verifier what must be true.

What the design proposes

• Appends validator deposits to the Execution Layer block structure.
• This shifts responsibility of deposit inclusion and validation to the Execution Layer and removes the need for deposit (or eth1data) voting from the Consensus Layer.
• Validator deposits list supplied in a block is obtained by parsing deposit contract log events emitted by each deposit transaction included in a given block.

How the mechanism is specified

• Taken from the specification, the next constraint is: This shifts responsibility of deposit inclusion and validation to the Execution Layer and removes the need for deposit (or eth1data) voting from the Consensus Layer.
• Locate JSON, RPC, API in EIP 6110 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• Final in the EIP process is not finality of a checkpoint.
• Parameter choices in one release are not the proof.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use EIP 6110 when a pitch says 'Supply validator deposits on chain' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.