Slashing Protection Interchange Format

The five-minute read

One action, walked through

1. Open EIP 3076 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: A standard format for transferring a key's signing history allows validators to easily switch between clients without the risk of signing conflicting messages.
3. Name the object that changes: Slashing Protection Interchange Format.
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 3076 at the status the text itself states: Last Call.
• The object that has to change is Slashing Protection Interchange Format. A neighbouring document with a similar name is not this one.
• Wallet support is not the same as consensus validity.

What happened after the paper

The source marks this last call. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What is covered by the signed bytes in Slashing Protection Interchange Format?
• Can the same signature be replayed on another chain, account, or message?
• Which primitive does the text require: Slashing Protection Interchange Format?

Terms

EIP 3076

The public text titled Slashing Protection Interchange Format.

Last Call

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

The problem the paper names

A signature that does not commit to what the user saw can be replayed into a different spend, a different chain, or a different message.

What the design proposes

• A standard format for transferring a key's signing history allows validators to easily switch between clients without the risk of signing conflicting messages.
• While a common keystore format provides part of the solution, it does not contain any information about a key's signing history.
• For a validator moving their keys from client A to client B, this could lead to scenarios in which client B inadvertently signs a message that conflicts with an earlier message signed with client A.

How the mechanism is specified

• Taken from the specification, the next constraint is: While a common keystore format provides part of the solution, it does not contain any information about a key's signing history.
• Locate Slashing Protection Interchange Format in EIP 3076 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

• A signature scheme is not a privacy system. It hides the signer only if the protocol says so.
• Wallet support is not the same as consensus validity.
• The source marks this last call. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use EIP 3076 when a pitch says 'Slashing Protection Interchange Format' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.