<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ePBS on archive @rootwarp</title><link>https://archive.rootwarp.xyz/tags/epbs/</link><description>Recent content in ePBS on archive @rootwarp</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 18 Oct 2026 21:56:00 +0900</lastBuildDate><atom:link href="https://archive.rootwarp.xyz/tags/epbs/index.xml" rel="self" type="application/rss+xml"/><item><title>EIP-7732: What ePBS Changes in Ethereum’s Consensus Layer</title><link>https://archive.rootwarp.xyz/posts/2026-0001-what_epbs_changes_in_ethereum_consensus_layer/</link><pubDate>Sun, 18 Oct 2026 21:56:00 +0900</pubDate><guid>https://archive.rootwarp.xyz/posts/2026-0001-what_epbs_changes_in_ethereum_consensus_layer/</guid><description>&lt;p&gt;A validator can propose an Ethereum block without choosing every transaction inside it. Specialist builders do that work, and MEV-Boost connects the two sides through relays. EIP-7732 would bring the exchange they rely on into Ethereum’s consensus rules. That sounds like a small change in plumbing, but it changes who participants have to trust and how validators spend each slot.&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;This post is a shorter version of a longer survey. The &lt;a href="https://archive.rootwarp.xyz/pdf/2026-0001-epbs_survey.pdf" &gt;full survey (PDF, 11 pages)&lt;/a&gt; goes deeper into the payment paths, fork choice, and security properties.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>