Lido Proposes Execution Delegation Framework: When Staking Delegates More Than Just Consensus
Lido proposes separating consensus attestation from block proposal through execution delegation, improving efficiency but creating MEV concentration, staker disenfranchisement, and censorship infrastructure risks.

The proposal appeared on the Lido research forum in September 2026 with the governance language of a DAO that had spent years managing validator sets and was ready to formalize a practice that had been happening informally since the protocol launched. The Execution Delegation Framework—a proposal to allow Lido stakers to delegate their execution layer responsibilities to specialized node operators—was designed to improve block proposal efficiency, reduce MEV extraction losses, and optimize validator profitability. The pitch was specialization: consensus and execution are different skills, different hardware requirements, and different economic incentives, so separating them would improve outcomes for everyone. The fine print raised a question about whether a liquid staking protocol that was supposed to decentralize validator operations was now creating a two-tiered system where consensus operators controlled the stake and execution operators controlled the rewards.
That was the proposal. Then came the question of whether the staker who deposited ETH with Lido to participate in decentralized validation was now finding their stake split between a consensus operator they chose and an execution operator they did not, with the execution operator taking a cut of rewards for a role the staker never agreed to delegate.
What the Execution Delegation Framework Actually Proposes
The framework describes a validator role separation with specific mechanics:
The Core Components:
- Consensus delegation: Stakers delegate their ETH to consensus node operators who attest to blocks
- Execution delegation: Block proposal responsibilities are delegated to execution specialists
- Reward splitting: Execution operators receive a share of MEV and priority fee revenue
- Performance requirements: Execution operators must meet latency, connectivity, and profitability benchmarks
- Rotation mechanism: Execution operators can be rotated based on performance metrics
The Current System:
- Unified validators: Each Lido operator handles both consensus and execution
- Fixed reward split: Operators receive a predictable percentage of staking rewards
- Direct responsibility: The operator that holds the stake also proposes blocks
- Decentralized selection: Node operators are vetted by the DAO and selected by stakers
The Proposed Changes:
- Role separation: Consensus operators attest; execution operators propose blocks
- Additional intermediaries: Execution operators sit between stakers and block rewards
- Variable rewards: MEV and priority fees flow through execution operators first
- Performance hierarchy: Better execution operators get more delegated block proposals
- Centralization pressure: Efficient execution operators accumulate more delegation
The framework frames these as efficiency improvements. They are also a mechanism that concentrates block proposal power in specialized execution operators.

Key Metrics at a Glance
| Dimension | Current (Unified Validators) | Proposed (Delegated Execution) | Impact |
|---|---|---|---|
| Validator Count | Distributed among operators | Same stake, fewer execution operators | Concentration |
| MEV Extraction | Operator-dependent | Optimized by specialists | Uneven |
| Reward Split Complexity | Simple (operator fee) | Complex (consensus + execution) | Opaque |
| Operator Responsibility | Clear (one operator) | Split (two operators) | Blurred |
| Block Proposal Centralization | Moderate | Higher | Risk |
| Staker Control | Moderate (choose operator) | Low (choose consensus, accept execution) | Reduced |
| Censorship Resistance | Distributed | Dependent on execution operator set | Weakened |
| Protocol Complexity | Manageable | Significantly higher | Risk |
The Proprietary Validator Role Integrity Score (VRIS)
I've developed a framework to evaluate whether execution delegation preserves or undermines validator decentralization:
Formula: VRIS = (Decentralization Preservation × 0.3) + (Staker Control × 0.25) + (Reward Transparency × 0.2) + (Censorship Resistance × 0.15) + (Operator Accountability × 0.1)
Lido Execution Delegation Assessment:
| Factor | Score | Analysis |
|---|---|---|
| Decentralization Preservation | 3/10 | Execution delegation concentrates block proposal in fewer, more specialized operators; the decentralization that was supposed to be Lido's strength is undermined by efficiency incentives that reward concentration; the operator that can extract more MEV gets more delegation, creating a winner-take-all dynamic |
| Staker Control | 3/10 | Stakers choose their consensus operator but do not choose their execution operator; the control that was supposed to be exercised through DAO governance is now fragmented across two layers; the staker who delegated to a trusted consensus operator finds their block proposals controlled by a different entity they never selected |
| Reward Transparency | 3/10 | MEV and priority fees are opaque by nature; adding an execution operator layer makes them more opaque; the transparency that was supposed to be on-chain is now obscured by execution operator algorithms; the staker who wants to verify their rewards faces an additional black box |
| Censorship Resistance | 3/10 | Execution operators control what transactions are included in blocks; a concentrated execution operator set can censor transactions more effectively than a distributed validator set; the censorship resistance that was supposed to be preserved by decentralization is weakened by specialization |
| Operator Accountability | 4/10 | Execution operators are accountable to performance metrics but not directly to stakers; the accountability that was supposed to flow from staker choice is now mediated by the protocol's delegation algorithm; the operator that underperforms is rotated, not removed by staker vote |
| Total VRIS | 3.2/10 | The execution delegation framework represents a significant degradation of validator role integrity: genuine efficiency improvements but severe costs to decentralization, staker control, and censorship resistance |
A score of 3.2 indicates that execution delegation is a high-risk optimization: real efficiency gains but fundamental erosion of what decentralized staking is supposed to mean.

The Three Delegation Traps
Trap 1: The MEV Concentration
The fundamental problem with execution delegation is that it incentivizes MEV extraction specialization. The execution operator that builds the most profitable blocks gets more delegated proposals. The operator that runs the most sophisticated MEV strategies outcompetes those that do not. The arms race that was supposed to be between validators is now between execution specialists. The validator that was supposed to be a distributed network becomes a hierarchy of execution operators competing for delegated block rights. The decentralization that was supposed to prevent MEV extraction from becoming extractive becomes a mechanism for concentrating it.
Trap 2: The Staker Disenfranchisement
Stakers delegate their ETH to participate in consensus. The execution delegation framework means they also delegate block proposal—whether they want to or not. The staker who chose Operator A for their consensus track record finds Operator B proposing their blocks. The staker who wanted to support a specific operator's values finds those values irrelevant to execution. The governance that was supposed to flow from staker choice is fragmented by a technical separation that stakers did not approve. The deposit that was supposed to represent a vote for a validator becomes a deposit that funds a system the staker did not design.
Trap 3: The Censorship Infrastructure
Block proposers control transaction inclusion. Execution operators are block proposers. If execution operators are concentrated, censorship is easier. A government that wants to block transactions from a specific address needs to pressure fewer entities. An execution operator that wants to exclude transactions for competitive reasons has the power to do so. The censorship resistance that was supposed to be a property of decentralized validation becomes dependent on the goodwill of a specialized execution operator set. The protocol that was supposed to resist censorship builds infrastructure that enables it.
Competitive Landscape: Staking Role Separation Models
| Protocol/Model | Validator Structure | Execution Control | Staker Choice | Censorship Resistance | VRIS |
|---|---|---|---|---|---|
| Lido (current) | Unified operators | Operator-controlled | Operator-selected | Moderate | 5.5/10 |
| Lido (delegated) | Split roles | Execution specialist | Limited | Lower | 3.2/10 |
| Rocket Pool | Decentralized minipools | Node operator | Operator-selected | Higher | 6.5/10 |
| EigenLayer | Restaked validators | Restaked operators | Protocol-dependent | Variable | 4.5/10 |
| Solo Staking | Individual | Self-controlled | Full | Highest | 8.5/10 |
| Coinbase | Centralized | Coinbase-controlled | None | Lowest | 2.0/10 |
| Kiln | Professional operator | Operator-controlled | Limited | Moderate | 4.0/10 |
The landscape shows that role separation exists but tends to reduce staker control and increase centralization. Solo staking remains the gold standard for censorship resistance.

Scenario Analysis: Three Futures for Execution Delegation
Scenario A: Execution Oligopoly (45% probability)
- A small number of execution operators dominate block proposal
- MEV extraction becomes concentrated and extractive
- Stakers accept reduced control in exchange for marginally higher rewards
- VRIS degrades to 2.0/10
Scenario B: Managed Competition (35% probability)
- The DAO implements strict limits on execution operator concentration
- Stakers retain veto power over execution operator selection
- Role separation improves efficiency without catastrophic centralization
- VRIS stabilizes at 4.5/10
Scenario C: Community Rejection (20% probability)
- Stakers and the DAO reject execution delegation as contrary to Lido's values
- The framework is abandoned or significantly modified
- Lido preserves its unified validator model
- VRIS improves to 5.5/10
The Bottom Line
The Execution Delegation Framework is sophisticated protocol engineering from a team that understands validator economics and wants to improve staking efficiency. The Validator Role Integrity Score is 3.2/10. Decentralization preservation is poor. Staker control is weak. Reward transparency is compromised. Censorship resistance is endangered. Operator accountability is fragmented.
The three traps—MEV concentration, staker disenfranchisement, and censorship infrastructure—are structural risks that accompany every attempt to specialize validator roles in a liquid staking protocol. They reflect the fundamental tension between efficiency and decentralization in protocol design. The community that wants better execution must also accept that the specialization may destroy the decentralization that made staking worthwhile.
The deeper question is whether Lido can afford to become an execution operator marketplace. The entire value proposition of Lido is that it decentralizes Ethereum validation. The protocol that concentrates block proposal in specialized operators is a protocol that has abandoned that value proposition for a different one: staking yield optimization. The staker who believed in decentralized validation now funds a system where their blocks are proposed by entities they did not choose.
The framework deserves recognition for economic sophistication. The Lido research team understands validator incentives, MEV dynamics, and role specialization. But economic sophistication is not the same as protocol integrity. The staking protocol that optimizes for yield over decentralization has optimized for the wrong thing. The validator set that becomes an execution operator hierarchy is a validator set that has failed.
TL;DR
- What: Lido proposes an Execution Delegation Framework allowing stakers to separate consensus attestation from block proposal, with execution operators specializing in MEV extraction and block optimization
- The Score: Validator Role Integrity Score of 3.2/10—decentralization preservation (3/10) collapses as execution concentrates in fewer operators; staker control (3/10) fragments as block proposal is delegated to entities stakers did not choose; reward transparency (3/10) degrades with additional opaque MEV layers; censorship resistance (3/10) weakens as concentrated execution operators control transaction inclusion; operator accountability (4/10) is mediated by algorithm rather than staker choice
- The Reality: A genuine efficiency improvement that fundamentally alters what staker delegation means, creating a two-tiered operator system
- Three Traps: MEV concentration (execution operators compete in winner-take-all MEV arms race); staker disenfranchisement (consensus choice does not control block proposal); censorship infrastructure (concentrated execution operators enable transaction filtering)
- Outlook: Execution oligopoly (45%) where few operators dominate block proposal; managed competition (35%) where DAO limits concentration and preserves staker veto; community rejection (20%) where Lido abandons role separation
Sources
- Lido Research Forum - Execution Delegation Framework - September 2026 proposal for validator role separation
- Lido Protocol Documentation - Current validator operator model and reward distribution
- Ethereum Validator Economics - Consensus and execution layer responsibilities and incentives
- MEV-Boost Documentation - Existing block proposal delegation and MEV extraction mechanisms
- Rocket Pool Minipool Model - Alternative decentralized staking with unified operator responsibility
- EigenLayer Restaking - Restaked validation and execution operator dynamics
- The Block - Liquid Staking Centralization - Analysis of validator concentration risks in liquid staking protocols
- Ethereum Research - Proposer-Builder Separation - Academic discussion of block proposal role separation and censorship risks
Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter. He writes about Ethereum, ETH, smart contracts, DeFi, Layer 2 networks, staking, validators, and the real-world consequences of technical and financial failure.



