<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Glamsterdam on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/glamsterdam/</link>
    <description>Recent content in Glamsterdam on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Jul 2026 07:58:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/glamsterdam/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Glamsterdam Explained: Every EIP in Ethereum&#39;s Next Upgrade</title>
      <link>https://blazed.sh/blog/posts/glamsterdam-ethereum-upgrade/</link>
      <pubDate>Tue, 21 Jul 2026 07:58:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/glamsterdam-ethereum-upgrade/</guid>
      <description>&lt;p&gt;Glamsterdam is the next Ethereum hard fork after Fusaka, and it is shaping up as the most structural release the network has shipped in years. It moves the block-building auction into the protocol itself, puts a consensus-verified state diff inside every block, and reprices the corners of the EVM that stood in the way of much higher gas limits. Multi-client devnets have been running the full slate since June 2026, and mainnet activation is targeted for the second half of the year.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What Is ePBS? Ethereum&#39;s Enshrined Proposer-Builder Separation (EIP-7732), Explained</title>
      <link>https://blazed.sh/blog/posts/epbs-eip-7732-searchers-builders/</link>
      <pubDate>Mon, 20 Jul 2026 08:12:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/epbs-eip-7732-searchers-builders/</guid>
      <description>&lt;p&gt;ePBS stands for enshrined proposer-builder separation. It is the change, specified in &lt;a href=&#34;https://eips.ethereum.org/EIPS/eip-7732&#34;&gt;EIP-7732&lt;/a&gt;, that moves Ethereum&amp;rsquo;s block-building marketplace out of trusted off-chain middleware and into the protocol itself. Today, a validator who wants a professionally built block hands the deal to a relay, an unpaid third party that both sides simply have to trust. Under ePBS the builder&amp;rsquo;s signed bid goes into the beacon block directly, payment is enforced by consensus, and the relay&amp;rsquo;s trust role disappears. It ships as the headline consensus change of Glamsterdam, the hard fork after Fusaka, currently targeted at mainnet in the second half of 2026.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lean Ethereum: Vitalik&#39;s Third Rebuild of the Protocol, Explained</title>
      <link>https://blazed.sh/blog/posts/lean-ethereum-roadmap-explained/</link>
      <pubDate>Mon, 06 Jul 2026 10:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/lean-ethereum-roadmap-explained/</guid>
      <description>&lt;p&gt;Two weeks ago, Ethereum researchers met in Berlin to keep charting the protocol&amp;rsquo;s long-term trajectory, picking up threads from the client-team discussions held in Svalbard back in April. The output is an updated &lt;a href=&#34;https://strawmap.org/&#34;&gt;strawmap&lt;/a&gt;, the community&amp;rsquo;s deliberately provisional sketch of where the protocol is headed, and a set of high-level takeaways that Vitalik Buterin published on July 4. The framing that ties them together is a name: Lean Ethereum.&lt;/p&gt;&#xA;&lt;p&gt;It helps to be precise about what that name means, because it is easy to file under &amp;ldquo;another roadmap.&amp;rdquo; Lean Ethereum is not a single one-shot upgrade. It is a collection of improvements that will come online over the course of three or four years. But make no mistake: this is the third major iteration of Ethereum, in the same way that &lt;a href=&#34;https://ethereum.org/roadmap/merge/&#34;&gt;the Merge&lt;/a&gt; was the second. Almost every major piece of the protocol is on the table to be replaced, and the through-line is simplification, cleanup, and future-proofing, done in a way that minimizes disruption to the applications already running. Ethereum has done exactly this before with the transition from proof-of-work, so the precedent for a deep rebuild that users barely feel already exists.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Block-Level Access Lists Explained (EIP-7928)</title>
      <link>https://blazed.sh/blog/posts/block-level-access-lists-eip-7928/</link>
      <pubDate>Fri, 03 Jul 2026 10:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/block-level-access-lists-eip-7928/</guid>
      <description>&lt;p&gt;Glamsterdam, the next Ethereum upgrade after Fusaka, has two headline changes. The consensus-layer half is &lt;a href=&#34;https://blazed.sh/blog/posts/epbs-eip-7732-searchers-builders&#34;&gt;ePBS, EIP-7732&lt;/a&gt;, which restructures how blocks get built and has absorbed most of the attention. The execution-layer half is &lt;a href=&#34;https://eips.ethereum.org/EIPS/eip-7928&#34;&gt;EIP-7928, Block-Level Access Lists&lt;/a&gt;, and it is arguably the more practical change for anyone whose job is consuming Ethereum data rather than producing blocks. It is also further along than most people realize: &lt;a href=&#34;https://github.com/ethereum/go-ethereum/releases/tag/v1.17.4&#34;&gt;Geth 1.17.4&lt;/a&gt; already constructs and verifies BALs during block execution and serves them over the new &lt;code&gt;eth/71&lt;/code&gt; wire protocol, ahead of the fork activating anywhere public.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
