EIP-4895: getting staked ETH back without a transaction

The problem: a balance no transaction can reach

A validator’s money lives on the consensus layer as a plain balance entry — 32 ETH of stake plus whatever it has earned. The natural way to move ETH on Ethereum is a transaction: an account signs “send X to Y”. But a validator is not an execution-layer account. It has no EOA, no private key the EVM recognizes, and no balance in the execution-layer state to draw from. So there is literally no transaction anyone can write to pull that money across — the sender doesn’t exist where transactions live.

The two layers don’t share an account model, and a transaction is a pull initiated by an account that owns the funds. Here the owner of the funds is the protocol’s validator registry, not an EOA.

→ Step 2: stop pulling and start pushing.

Invert the flow: the CL pushes withdrawals into the block

A transaction is a pull the funds’ owner signs. So flip the direction: let the consensus layer push. Define a new object — a withdrawal A system-level object the consensus layer inserts into an execution block: { index, validatorIndex, address, amount }. It is not a transaction — it has no signature, no sender account, and costs no gas. A user can never create one. — that the CL inserts directly into each execution block. Every execution block gains a withdrawals list, and the block header gains a withdrawalsRoot (a Merkle root committing to that list, exactly like transactionsRoot commits to the transactions). The execution layer doesn’t ask for these; the consensus layer hands them over as part of building the block.

This is the key reframing: a withdrawal is a system-level operation, not a transaction. No one signs it, it has no from, and it consumes no gas. The protocol itself moves the money, and the withdrawalsRoot makes the set verifiable and part of consensus.

→ Step 3: the simplest possible processing.

Processing a withdrawal: increase a balance, full stop

Here’s how little it takes. For each withdrawal { index, validatorIndex, address, amount }, the execution layer simply adds amount (converted from Gwei to Wei) to address’s balance. That’s the entire operation. It is not a value-bearing call: no EVM execution is triggered, no contract code runs, no receive() or fallback fires, and it costs no gas. It can’t revert, because there’s nothing to execute — it’s an unconditional credit, the protocol minting back ETH that was already staked.

Because it bypasses the EVM entirely, even a contract account receiving a withdrawal just sees its balance go up, with no execution. The index is a global, ever-increasing counter so every withdrawal is unique and ordered.

→ Step 4: two flavors, both automatic.

Two flavors — and you never press a button

The consensus layer continuously walks the validator set (a rolling sweep) and emits withdrawals automatically, in two forms. A partial withdrawal Automatic 'skimming' of rewards: any validator balance above the 32 ETH cap is periodically withdrawn to the validator's withdrawal address, while the 32 ETH stays staked and keeps validating. skims everything above the 32 ETH effective-balance cap — your rewards come home while your stake keeps working. A full withdrawal returns a validator’s entire remaining balance once it has fully exited the active set. Both require the validator to have set an 0x01 withdrawal credential pointing at an execution-layer address — and once it has, the ETH simply arrives; there’s no withdrawal transaction to send.