Staking pools aggregate native assets (like ETH) from multiple users to meet the capital requirements necessary to run validator nodes and secure a Proof-of-Stake network. Unlike Liquid Staking, these native pools do not issue a secondary tradeable receipt token (LST); user capital remains locked in the protocol’s native smart contracts, earning direct consensus and execution rewards. Because validators mint the literal blockspace of the network and earn continuous issuance rewards, they are structurally positioned to fund the ecosystem they secure.
Protocol-Level Validator Reward Redirect
Definition. A majority-triggered protocol rule where validators vote to mandate a capped percentage (e.g., up to 10%) of base staking rewards to be redirected to a dynamic splitter contract. Once a majority is reached, the extraction becomes mandatory for all validators, eliminating free-riders while funding shared infrastructure via a “King of the Hill” Condorcet winner selection model.
Value-stack tap. Protocol Surface (protocol-level consensus reward distribution).
Cost-bearer class. Validator borne (a mandatory revenue sacrifice taken directly from global staking yield to fund shared network security).
Example protocols. Validator Redirected Revenue EIP.
MEV-Boost Block Execution Surplus Skim
Definition. Native staking pools receiving MEV execution rewards (priority fees and builder tips) can configure their validator client’s fee-recipient address to intercept the payout. A micro-percentage of these highly variable MEV block rewards is routed to a CaaS rail before the remainder is distributed to the pool’s depositors.
Value-stack tap. Execution Surface (MEV-boost fee recipient configuration).
Cost-bearer class. MEV bots-pass-through (extracted purely from the highly variable block execution surplus).
Example protocols. Native staking pools running Flashbots MEV-Boost.
Distributed Validator (DVT) Operator Toll
Definition. Native stakers frequently use DVT networks to split their validator key across a cluster of independent nodes to prevent downtime and slashing. The staker pays an ongoing network fee to these operators. A programmatic fraction of this DVT network fee is intercepted at the smart contract registry layer and routed to the CaaS rail before the operators claim their payment.
Value-stack tap. Smart Contract Surface (DVT operator payment registry).
Cost-bearer class. Operator-borne / Project paid (subsidized from the DVT node operator’s infrastructure fee margin).
Example protocols. SSV Network, Obol Network.