Increase exit and consolidation churn

The five-minute read

One action, walked through

1. Open EIP 8061 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This EIP roughly doubles the consolidation churn, as well as quadrupling the exit churn and restoring its proportionality to total stake (though maintaining the existing cap on activations).
3. Name the object that changes: ETH, CHURN_LIMIT_QUOTIENT.
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 8061 at the status the text itself states: Review.
• The object that has to change is ETH, CHURN_LIMIT_QUOTIENT. 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 review. 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 does Increase exit and consolidation churn treat as decided, and what can still be reorged?
• What share of stake or hash power does the argument need?
• Which objects are defined: ETH, CHURN_LIMIT_QUOTIENT?

Terms

EIP 8061

The public text titled Increase exit and consolidation churn.

Review

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

• This EIP roughly doubles the consolidation churn, as well as quadrupling the exit churn and restoring its proportionality to total stake (though maintaining the existing cap on activations).
• The choice of parameters balances maintaining a sufficiently long weak subjectivity period (~7 days, roughly halving the current period) with achieving two goals: allowing for faster consolidation of the validator set, in turn accelerating the timeline to faster finality, and relieving exit queue congestion, improving staking liquidity.
• EIP-7514 introduced an activation cap of 8 validators per epoch (now 256 ETH per epoch) to prevent overly rapid validator set growth.

How the mechanism is specified

• Taken from the specification, the next constraint is: The choice of parameters balances maintaining a sufficiently long weak subjectivity period (~7 days, roughly halving the current period) with achieving two goals: allowing for faster consolidation of the validator set, in turn accelerating the timeline to faster finality, and relieving exit queue congestion, improving staking liquidity.
• Locate ETH, CHURN_LIMIT_QUOTIENT in EIP 8061 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 review. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use EIP 8061 when a pitch says 'Increase exit and consolidation churn' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.