Ethereum draft lets compounding validators set sweep threshold

Draft proposal EIP-8148 would let compounding validators that use 0x02 withdrawal credentials choose a custom automatic-sweep threshold between 32 ETH and 2,048 ETH. The draft adds a 32-ETH minimum and allows an initial threshold to be encoded when a validator deposit is created. Invalid or absent custom values would default to the 2,048-ETH setting until a valid change is processed.

An Aug. 20 edit to the draft lowered the minimum custom threshold from 33 ETH to 32 ETH and added the deposit-time selection mechanism. The proposal requires any post-creation threshold change to be set at or above the validator’s current balance. If a deposit encodes a threshold below the deposited amount, the protocol would ignore that value and use the default. Validators seeking a lower on-chain threshold must first use the standard partial-withdrawal process.

Under current rules, validators using legacy 0x01 credentials have an effective-balance cap of 32 ETH: any balance above that level is periodically swept to a withdrawal address and stops compounding on the validator. Compounding validators with 0x02 credentials increase effective balance in 1-ETH increments up to the 2,048-ETH default and are automatically swept only after exceeding that higher cap. Compounding validators may request partial withdrawals to move rewards off the validator before reaching 2,048 ETH.

A snapshot from Pectrified dated July 28 recorded 16,926 active 0x02 validators, equal to 1.91% of active validators. Those validators held about 13.36 million ETH, representing 32.43% of active stake. The figures show that compounding credentials cover a larger share of ETH than their share of validator count.

Operational timing differs between exit processing and the automatic sweep cycle. A Validator Queue snapshot on Aug. 25 showed about 160 ETH in the exit queue with an estimated four-minute wait. The same dashboard estimated the network-wide automatic sweep cycle at roughly 7.8 days. Exit queues govern validators leaving the active set, while sweep cycles process eligible validator balances. Public data on partial-withdrawal backlogs is not available.

Documentation from staking services indicates different product-layer handling of reward flows. Provider documentation states that staking and execution-layer rewards feed pooled accounting and that staked-token balances are updated through oracle-driven rebases. Another service documents that rewards on Pectra-enabled 0x02 validators compound and can be claimed through an existing partial-withdrawal process, subject to the provider’s conditions. Those materials do not specify how validator-level sweep thresholds would be set or applied.

EIP-8148 remained in Draft status as of Aug. 25. A related consensus-spec change was merged on Aug. 24, and tooling trackers list the proposal as proposed for the Hegotá fork. Fork placement, activation timing and final implementation remain pending. Until developers finalize the proposal, the network continues to apply automatic sweeps above 32 ETH for 0x01 credentials, compounding up to 2,048 ETH for 0x02 credentials, and manual partial withdrawals for compounding validators that want rewards moved sooner.

Background: Effective balance is the protocol-level measure used to calculate consensus rewards and penalties. Principal withdrawals from validators continue to use existing partial-withdrawal or full-exit paths followed by ordered withdrawal processing. EIP-8148 would change when rewards become eligible for automatic withdrawal sweeps but would not alter those principal-withdrawal mechanisms.