EIP-8148 rewrite stores a validator's sweep threshold in its credentials
Victoria Shinder1 min readValidators that switched to compounding withdrawal credentials, type 0x02, only see their rewards swept automatically once the balance passes 2,048 ETH. EIP-8148, a draft first created in February, proposes letting each such validator choose a lower threshold. A revision merged into the EIPs repository on 30 October changes where that choice lives.
The earlier draft sketched a new validator_sweep_thresholds mapping in the beacon state. The new text embeds the threshold directly in the validator's 0x02 withdrawal credentials: two bytes starting at byte offset 1, replacing an earlier offset of 10. It also caps the number of set-threshold requests at 16 per execution payload, and renames the EIP-7685 request type constant to SWEEP_THRESHOLD_REQUEST_TYPE, keeping the type value 0x05. The list of consensus-layer changes that described the mapping approach was removed from the reference section.
The mechanism itself is unchanged in outline. A validator's withdrawal address calls a predeployed contract on the execution layer, the request travels to the consensus layer through the EIP-7685 general request framework, and the validator's rewards above the chosen level are then swept without a manual partial withdrawal. The authors argue that the 2,048 ETH default has kept adoption of 0x02 credentials low, and that partial withdrawals are a poor substitute because they need a transaction and wait in the shared exit queue.
What it means
Storing the value in the credentials avoids growing the beacon state with another per-validator field, which client teams tend to resist. The proposal remains a draft with no fork assigned. For staking operators the question it answers is practical: whether moving to 0x02 can be made as convenient as the old automatic reward sweep, which is what has kept many on 0x01 credentials.