A withdrawal credential is a 32-byte field associated with an Ethereum validator that determines how the validator’s staked ETH and rewards can be withdrawn. It effectively links the validator’s consensus-layer balance to the account or key that is authorized to receive or control withdrawals.
Withdrawal credentials are separate from the validator signing key. The signing key is used for active validator duties such as attestations and block proposals, while the withdrawal credential is tied to ownership and withdrawal control. This separation allows the validator key to remain online for daily consensus duties while withdrawal authority can be kept under stricter security.
Ethereum currently uses several withdrawal credential types. The first byte of the 32-byte field identifies the type, most commonly 0x00, 0x01, or 0x02. These types determine whether withdrawals are enabled, whether rewards are automatically swept, and whether the validator can compound stake above 32 ETH.
Why Withdrawal Credentials Exist
Ethereum validators need two different forms of authority. One is operational authority, which allows the validator to participate in consensus. The other is financial authority, which controls what happens to the ETH associated with the validator.
Combining both functions into a single hot key would create unnecessary security risk. Validator signing keys need to be available to online software because they regularly sign attestations and, when selected, block proposals. Withdrawal authority does not need to remain online in the same way.
Withdrawal credentials provide this separation. A validator operator can run the validator software while the owner of the staked ETH retains control over the withdrawal destination.
This distinction is particularly important in delegated staking. One entity may operate the validator infrastructure while another entity owns the funds. The withdrawal credential helps ensure that control over the validator’s ETH is not automatically transferred to the node operator.
How Withdrawal Credentials Are Structured
Every Ethereum validator has a 32-byte withdrawal credential field. The first byte defines the credential type, while the remaining bytes contain information used by that credential format.
The three main types are:
- 0x00 credentials, the original BLS-based format used before execution-layer withdrawal addresses became standard. These credentials do not directly identify an Ethereum withdrawal address, so the validator must be converted before ordinary withdrawals can occur.
- 0x01 credentials, which point to an execution-layer Ethereum address and support standard withdrawals. 0x02 credentials also point to an execution address but enable the newer compounding validator model with a higher maximum effective balance.
The prefix is therefore not merely an identifier. It changes how Ethereum handles the validator’s balance and withdrawal behavior.
0x00 BLS Withdrawal Credentials
The 0x00 format is the original withdrawal credential type from the early Beacon Chain period. It is based on a BLS withdrawal key rather than a normal Ethereum execution address.
Validators using 0x00 credentials cannot receive normal staking withdrawals directly because no execution-layer destination has been assigned. Their ETH remains associated with the validator until the credentials are changed to a withdrawal-enabled format.
To enable withdrawals, the validator owner signs a one-time BLSToExecutionChange message using the withdrawal key. This assigns an Ethereum address and converts the validator to 0x01 credentials.
The change is significant because it moves withdrawal control from the original BLS credential model to an execution-layer address. Once this conversion has been processed, it cannot be reversed back to 0x00.
For validators created during the early Beacon Chain period, preserving the original mnemonic or withdrawal key is critical. Without the required key material, the owner may be unable to perform the conversion needed to access the validator balance.
0x01 Execution Withdrawal Credentials
The 0x01 format assigns a regular Ethereum execution address as the validator’s withdrawal destination. It became the standard withdrawal-enabled model around the Shapella upgrade, which activated staking withdrawals in April 2023.
For a 0x01 validator, the effective balance used for consensus participation is capped at 32 ETH. If rewards push the actual validator balance above 32 ETH, the excess can be automatically swept to the configured withdrawal address during Ethereum’s withdrawal processing.
This means rewards do not remain inside the validator to increase its effective stake beyond 32 ETH. The validator continues participating with an effective balance of up to 32 ETH, while eligible excess ETH is periodically transferred out.
A full validator exit ultimately sends the remaining withdrawable balance to the same configured execution address.
0x02 Compounding Withdrawal Credentials
The 0x02 credential type was introduced with Ethereum’s Pectra changes and is designed for compounding validators. It allows the effective balance of a validator to grow beyond the traditional 32 ETH limit.
A validator using 0x02 credentials can have an effective balance of up to 2,048 ETH. Rewards can therefore remain within the validator and contribute to future staking rewards rather than being automatically swept whenever the balance exceeds 32 ETH.
The higher limit also enables validator consolidation. Instead of operating many individual validators each capped at 32 ETH, an operator can consolidate stake into fewer validators with larger effective balances.
The basic differences between the major credential types are:
| Credential type | Withdrawal destination | Max effective balance | Excess balance behavior | Main purpose |
|---|---|---|---|---|
| 0x00 | BLS withdrawal key | 32 ETH | No normal withdrawal until converted | Original Beacon Chain format |
| 0x01 | Ethereum execution address | 32 ETH | Excess above 32 ETH can be automatically swept | Standard withdrawals |
| 0x02 | Ethereum execution address | 2,048 ETH | Balance can compound up to the maximum | Compounding and consolidation |
A conversion from 0x01 to 0x02 is one-way. A validator that switches to the compounding model cannot simply revert to 0x01 later.
Withdrawal Credential vs Validator Signing Key
The validator signing key and withdrawal credential serve different purposes and should not be treated as interchangeable.
The validator signing key is actively used by the consensus client. It signs attestations, block proposals, and other consensus messages. Because the validator must perform these duties regularly, the signing key is usually available to online infrastructure.
The withdrawal credential controls the financial side of the validator. It determines where ETH can be withdrawn and, with modern Ethereum functionality, can also participate in operations related to exiting or managing the validator.
If a validator signing key is compromised, an attacker may be able to cause slashing or interfere with validator duties. However, possession of the signing key does not automatically give the attacker the right to redirect withdrawals to an arbitrary address.
Conversely, the owner of the withdrawal address controls the destination of the staked funds without needing to perform daily validator duties.
Withdrawal Credential vs Fee Recipient
A withdrawal credential should also not be confused with a validator’s fee recipient.
The withdrawal address receives ETH related to staking withdrawals. This includes eligible validator rewards and the validator balance after a completed exit.
The fee recipient is an execution-layer address configured to receive certain execution-related rewards associated with blocks proposed by the validator. It is set separately from the withdrawal credential.
The two addresses can be the same, but Ethereum does not require them to be identical. Changing a fee recipient does not change the validator’s withdrawal credentials.
This distinction is important operationally because setting the correct fee recipient does not mean that staking withdrawals have been configured correctly.
Partial Withdrawals
A partial withdrawal removes some ETH from a validator while leaving the validator active.
For legacy 0x01 validators, balances above the 32 ETH effective balance can be swept automatically to the withdrawal address. The validator remains active with its required staking balance.
For 0x02 validators, the model is different because balances above 32 ETH can contribute to the validator’s effective stake. Compounding can continue in increments until the maximum effective balance of 2,048 ETH is reached.
Partial withdrawals for these validators can be requested rather than relying on the same automatic excess-balance behavior used by 0x01 validators.
This difference is one of the main reasons withdrawal credential type now affects more than the destination address. It also influences the validator’s capital management strategy.
Full Withdrawals and Validator Exits
A full withdrawal occurs after a validator exits active participation and becomes eligible to withdraw its remaining balance.
Exiting and withdrawing are not exactly the same event. A validator first leaves the active validator set through the protocol’s exit process. It then passes through the required waiting and processing stages before the balance becomes fully withdrawable.
Once eligible, the remaining ETH is transferred according to the withdrawal credential.
Modern Ethereum also allows execution-layer withdrawal authority to play a larger role in initiating validator exits. This reduces dependence on the active validator signing key and can be especially useful when the node operator and fund owner are different parties.
The withdrawal address therefore represents an important layer of control over the economic lifecycle of the validator.
Can a Withdrawal Address Be Changed?
For a validator using an execution-layer withdrawal address, choosing the address is a critical decision because the assigned destination is not freely editable like an ordinary account setting.
When a legacy 0x00 validator performs the one-time BLS-to-execution change, the selected execution address becomes the validator’s withdrawal destination. The operation cannot simply be repeated to replace it with another arbitrary address.
This makes address verification essential. Sending the change with an incorrect or inaccessible address can create a permanent problem because the validator’s future withdrawals will follow the credential recorded by the protocol.
The security of the withdrawal address is therefore as important as the security of the ETH itself.
How Withdrawal Credentials Affect Staking Rewards
Withdrawal credential type directly affects how rewards are treated.
With 0x01 credentials, a validator’s effective balance remains capped at 32 ETH. Rewards that increase the actual balance beyond that level do not raise the validator’s effective stake. Eligible excess funds are instead moved to the withdrawal address through the withdrawal sweep.
With 0x02 credentials, rewards can remain in the validator and increase its effective balance. This allows compounding beyond 32 ETH and up to the 2,048 ETH maximum effective balance.
The distinction changes staking economics. A 0x01 validator provides automatic reward distribution, while a 0x02 validator can retain more capital inside the validator for compounding.
This does not mean that 0x02 automatically produces higher returns under every condition. Actual validator rewards depend on Ethereum’s reward rules, effective balance, network participation, and other protocol factors.
Withdrawal Credentials and Validator Consolidation
The introduction of 0x02 credentials also changed how large staking operations can organize validators.
Historically, increasing active stake generally required creating additional validators in 32 ETH units. An operator with 320 ETH, for example, could operate ten separate validators.
With compounding credentials and higher effective balances, multiple validator balances can be consolidated into fewer validators, subject to Ethereum’s protocol rules.
This can reduce the number of validator records and consensus messages required for the same amount of stake. For large operators, fewer validators may also reduce infrastructure overhead.
However, consolidation changes operational structure and should not be interpreted as transferring control away from the withdrawal credential. The execution withdrawal address remains central to the management of the staked funds.
Security of Withdrawal Credentials
Withdrawal credentials deserve stronger protection than ordinary operational configuration because they are associated with control over the validator’s funds.
Important security practices include:
- verify the withdrawal address carefully before submitting deposit or conversion data, keep legacy withdrawal mnemonics offline, and avoid entering sensitive seed material into untrusted websites or software;
- separate validator signing infrastructure from withdrawal custody where practical, maintain secure backups, and confirm credential type before assuming that rewards or full withdrawals are enabled.
For a 0x00 validator, loss of the withdrawal key before setting an execution address can prevent the owner from completing the necessary credential conversion.
For execution-address credentials, security depends heavily on control of the corresponding Ethereum account. If the private key controlling that address is compromised, the economic ownership of withdrawals can also be compromised.
Why Withdrawal Credentials Matter
Withdrawal credentials define the relationship between an Ethereum validator and the account that controls its staked ETH. They are not simply an address field. They influence whether withdrawals are enabled, where validator funds go, whether rewards are automatically distributed, and whether stake can compound above 32 ETH.
The role of withdrawal credentials has expanded as Ethereum staking has evolved. The original 0x00 format reflected the early Beacon Chain architecture, 0x01 enabled execution-layer withdrawals, and 0x02 introduced compounding and validator consolidation.
Understanding the credential type is therefore essential for anyone operating or controlling an Ethereum validator. It determines not only the destination of withdrawn ETH but also important aspects of the validator’s staking and capital-management behavior.