Increase max attestation inclusion slot

The five-minute read

One action, walked through

1. Open EIP 7045 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Increases max attestation inclusion slot from attestation.slot + SLOTS_PER_EPOCH to the last slot of epoch N+1 where N is the epoch containing the attestation slot.
3. Name the object that changes: SLOTS_PER_EPOCH, LMD, GHOST.
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 7045 at the status the text itself states: Final.
• The object that has to change is SLOTS_PER_EPOCH, LMD, GHOST. 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 Increase max attestation inclusion slot treat as decided, and what can still be reorged?
• What share of stake or hash power does the argument need?
• Which objects are defined: SLOTS_PER_EPOCH, LMD, GHOST?

Terms

EIP 7045

The public text titled Increase max attestation inclusion slot.

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

• Increases max attestation inclusion slot from attestation.slot + SLOTS_PER_EPOCH to the last slot of epoch N+1 where N is the epoch containing the attestation slot.
• This increase is critical to the current LMD-GHOST security analysis as well as the confirmation rule.
• Attestations can currently be included after some minimum delay (1 slot on mainnet) up until SLOTS_PER_EPOCH slots after the slot the attestation was created in.

How the mechanism is specified

• Taken from the specification, the next constraint is: This increase is critical to the current LMD-GHOST security analysis as well as the confirmation rule.
• Locate SLOTS_PER_EPOCH, LMD, GHOST in EIP 7045 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 7045 when a pitch says 'Increase max attestation inclusion slot' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.