# Validator fee recipients: where tips go versus staking withdrawals A validator’s fee recipient is the execution-layer address nominated to receive transaction tips when it proposes a block. It is separate from the validator’s consensus withdrawal credentials. Configure and verify the address through your client’s documented method; changing it does not change the destination for consensus withdrawals. Evidence: [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html); [Ethereum gas and fees](https://ethereum.org/en/developers/docs/gas/); [Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-validator-fee-recipient/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Income:** The fee recipient concerns execution-layer block income. ([Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html)) - **Separate destination:** Consensus withdrawal credentials are a different validator property. ([Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx)) - **Configuration:** Lighthouse supports validator-specific and fallback fee-recipient settings. ([Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html)) ## Two reward paths can use two addresses A validator’s consensus balance and its execution block income follow different accounting paths. The BLS validator key is not an ordinary account address that can directly receive transaction tips. The configured fee recipient can coincide with the withdrawal address, but they remain separate settings. Never infer one merely from seeing the other on a dashboard. Evidence: [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html); [Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx) ## Changing tips does not redirect the validator principal Suppose a validator uses a treasury address for execution tips and a separate address for staking withdrawals. Updating the fee recipient to a new treasury changes the requested execution-payment destination. It does not edit the withdrawal credentials for the validator’s principal. Check each setting and its actual resulting payments independently. A successful configuration change for one stream says nothing about the other. Evidence: [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html); [Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx) ## Verify the setting that actually takes priority In the Lighthouse documentation retrieved on 2 October 2026, a validator-specific fee recipient takes priority over validator-client and beacon-node fallback settings. This ordering is a client-specific example, not a universal command-line recipe. The documentation calls the value a suggestion passed through the node stack and identifies trust in the nodes that honor it. When using third-party infrastructure, verify the resulting block-payment behavior as well as your local configuration. Evidence: [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html) ## Questions ### Can I use the validator public key as the fee recipient? No. The nominated recipient is an execution-layer Ethereum address. A validator’s BLS public key identifies a different object. Evidence: [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html) ### Will changing the fee recipient recover tips already paid elsewhere? No. It affects subsequent configured block production. It does not reverse earlier execution payments. Evidence: [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html) ## Claims and scope ### ethereum-validator-fee-recipient-quick-answer A validator’s fee recipient is the execution-layer address nominated to receive transaction tips when it proposes a block. It is separate from the validator’s consensus withdrawal credentials. Configure and verify the address through your client’s documented method; changing it does not change the destination for consensus withdrawals. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-validator-fee-recipient-fact-income Income: The fee recipient concerns execution-layer block income. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-validator-fee-recipient-fact-separate-destination Separate destination: Consensus withdrawal credentials are a different validator property. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-validator-fee-recipient-fact-configuration Configuration: Lighthouse supports validator-specific and fallback fee-recipient settings. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Suggested fee recipient](https://lighthouse-book.sigmaprime.io/validator_fee_recipient.html) — Lighthouse contributors. Execution rewards use configured addresses distinct from consensus withdrawal credentials. Locator: Configuring fee recipients. Retrieved: 2026-10-02T18:58:04.982Z. - [Ethereum gas and fees](https://ethereum.org/en/developers/docs/gas/) — ethereum.org contributors. Gas budgeting, actual use, burnt base fee and proposer priority fees. Locator: Gas limit; fee calculation; base fee; priority fee. Retrieved: 2026-10-02T18:55:24.873Z. - [Ethereum staking launchpad FAQ source](https://raw.githubusercontent.com/ethereum/staking-launchpad/dev/src/pages/FAQ/index.jsx) — Ethereum Foundation. Staking lifecycle, qualifying balances, network duties and deposit-data handling. Locator: Validators; deposits; activation; rewards; key management. Retrieved: 2026-10-02T18:58:48.434Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Validator fee recipients: where tips go versus staking withdrawals.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-validator-fee-recipient/