Bridge ETH to the validator’s withdrawal address, then submit the request from that address. On Ethereum, EIP-7002 lets an execution-layer withdrawal credential request a validator exit or partial withdrawal; the transaction needs ETH for both network gas and the request fee.
What exactly needs funding?
You need spendable ETH on Ethereum at the address that controls the validator’s withdrawal credentials. A validator’s active signing key and withdrawal credentials serve different roles: the credentials control the staked ETH, and EIP-7002 checks that the address making the request matches those credentials. The Ethereum Improvement Proposal for EIP-7002 describes this request mechanism and its separate fee.
If your ETH or other tokens are on another chain, a relay bridge can carry value across to Ethereum, provided its route supports the chains and asset conversion you need. Compare the route’s quoted relay bridge fees with its delivery time and output: the bridge cost is separate from Ethereum gas and the withdrawal request fee.
What should you check before bridging?
First confirm that the validator uses execution-layer withdrawal credentials, commonly called 0x01 credentials. A 0x00 credential is a BLS key and cannot simply receive ETH at an ordinary wallet address; if you are unsure, check the validator’s credentials in a trusted staking interface or ask the withdrawal-credential owner.
Next verify the exact destination address and who controls it. With an externally owned account (EOA), the owner signs the request transaction. With a contract address, that contract must provide a way to call the request mechanism; bridging ETH to a contract alone does not make it submit a request.
How do you bridge enough ETH and submit the request?
Follow these steps in order. The example assumes you control an EOA with 0x01 credentials and are moving funds from another chain into that same Ethereum address.
- Read the validator’s withdrawal address and public key. Match the address to the credential recorded for the validator, and copy the validator public key from a trusted source. A wrong address may receive your bridge transfer without giving you the authority to request an exit.
- Check the request method and current fee. Use a compatible wallet or reputable interface that submits EIP-7002 requests. The protocol fee can change before your transaction is included, so read the current fee immediately before sending; ordinary transaction gas is an additional cost.
- Estimate the ETH needed on Ethereum. Add the request fee, the wallet’s gas estimate, and a small buffer for fee changes or a retry. For example, if the displayed request fee is 0.002 ETH and estimated gas is 0.001 ETH, bridge somewhat more than 0.003 ETH rather than sending exactly that amount. These figures are illustrative, not a live quote.
- Choose a route that delivers usable ETH. Select Ethereum as the destination network and the verified withdrawal address as recipient. If your source balance is a token such as USDC, check that the route converts it into native ETH; an ERC-20 token balance cannot pay Ethereum gas. Review the output after all bridge and conversion charges.
- Wait for the bridge transfer to complete, then verify the balance. A relay bridge uses relayers to carry or verify cross-chain information, and the source transaction may need to reach finality before delivery. The wait depends on the source chain, route, and network conditions; use the bridge’s status and the Ethereum wallet balance rather than assuming a submitted transfer is spendable.
- Submit and verify the request on Ethereum. Recheck the validator public key, request type, amount if applicable, and fee in the transaction preview. Sign only from the credential-matching address, then confirm the transaction on an Ethereum block explorer and check that the request was accepted.
What can delay or prevent the withdrawal?
A successful request does not mean ETH arrives immediately. Ethereum processes requests through its consensus layer, and exit timing depends on protocol queues and validator conditions; bridging only funds and submits the request. If the transaction fails, inspect its error and receipt before trying again, since a failed transaction can still consume gas.
One easily missed detail is fee overpayment: EIP-7002’s request fee is dynamic, and excess ETH sent for that fee is not necessarily returned to an EOA. I would use a wallet that fetches the current fee or simulates the transaction, keep a modest gas buffer, and avoid padding the protocol fee by a large amount.