How upcoming EIPs affect preconfirmations
By Aikaterini-Panagiota Stouka and Conor McMenamin, all Nethermind. This article was completed thanks to funding from the PBS Foundation. Thanks to Lin Oshitani, also Nethermind, for the thorough review and many comments. Thanks to Davide from PBS Foundation for reviewing.
Preconfirmations are a specific type of commitment from block proposers and builders that give users assurances about their transaction inclusion/execution before the proposer or builder publishes a completed block for finalization. However, most preconfirmation protocols have been designed and analysed with the Ethereum’s current design in mind. Thanks to Ethereum Improvement Proposals (EIPs*), Ethereum is always changing and upgrading. Some of these EIPs directly affect the compatibility of preconfirmation protocols, either by design or as a side-effect.
This article looks at some of the most impactful EIPs from preconfirmations’ perspective, and examines how these EIPs will affect preconfirmations, and what amendments, if any, can be adopted by preconfirmation protocols to stay compatible if/when these EIPs get included on Ethereum. These EIPs seek to modify how L1 block proposers are selected, hide the proposer lookahead, distribute block proposal responsibilities across multiple entities, or introduce new entities who contribute to block content and censorship resistance. This report analyzes how these EIPs are likely to affect preconfirmations, based on the most plausible EIP designs at the time of writing.
In the Preliminaries section, we present;
In the Framework for Analysing Each EIP section, we introduce the framework used to assess whether and how existing preconfirmation designs are affected by the proposals and EIPs.
Subsequently, each of the following sections examines a specific EIP. The EIPs we analyse are: