Ethereum Glamsterdam Upgrade: ePBS, Block-Level Access Lists and L1 Scaling in 2026 | Guardarian<\/title>\n <meta name=\"description\" content=\"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.\">\n <meta name=\"robots\" content=\"index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1\">\n <meta name=\"author\" content=\"Guardarian\">\n <link rel=\"canonical\" href=\"https:\/\/guardarian.com\/blog\/ethereum-glamsterdam-upgrade-2026\">\n <meta property=\"og:locale\" content=\"en_US\">\n <meta property=\"og:type\" content=\"article\">\n <meta property=\"og:site_name\" content=\"Guardarian\">\n <meta property=\"og:title\" content=\"Ethereum Glamsterdam Upgrade: ePBS, Block-Level Access Lists and L1 Scaling in 2026 | Guardarian\">\n <meta property=\"og:description\" content=\"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.\">\n <meta property=\"og:url\" content=\"https:\/\/guardarian.com\/blog\/ethereum-glamsterdam-upgrade-2026\">\n <meta property=\"og:image\" content=\"https:\/\/guardarian.com\/services\/meta-geo.jpg\">\n <meta property=\"og:image:alt\" content=\"Editorial article about Ethereum's Glamsterdam upgrade, ePBS, Block-Level Access Lists, and Layer 1 scaling in 2026.\">\n <meta name=\"twitter:card\" content=\"summary_large_image\">\n <meta name=\"twitter:title\" content=\"Ethereum Glamsterdam Upgrade: ePBS, Block-Level Access Lists and L1 Scaling in 2026 | Guardarian\">\n <meta name=\"twitter:description\" content=\"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.\">\n <meta name=\"twitter:image\" content=\"https:\/\/guardarian.com\/services\/meta-geo.jpg\">\n <meta name=\"theme-color\" content=\"#ffffff\">\n <link rel=\"preconnect\" href=\"https:\/\/fonts.googleapis.com\">\n <link rel=\"preconnect\" href=\"https:\/\/fonts.gstatic.com\" crossorigin>\n <link href=\"https:\/\/fonts.googleapis.com\/css2?family=Roboto:wght@400;500;700;900&display=swap\" rel=\"stylesheet\">\n <style>\n :root {\n --surface: rgba(255, 255, 255, 0.97);\n --line: #e4e4e4;\n --ink: #1d1d1d;\n --muted: #6f7783;\n --blue: #4c9de8;\n --blue-deep: #01268a;\n --orange: #f7931a;\n --shadow: 0 12px 28px rgba(1, 38, 138, 0.06);\n --radius-xl: 30px;\n --radius-lg: 22px;\n --content-width: min(1180px, calc(100vw - 40px));\n }\n\n * {\n box-sizing: border-box;\n }\n\n html {\n scroll-behavior: smooth;\n }\n\n body {\n margin: 0;\n font-family: \"Roboto\", sans-serif;\n color: var(--ink);\n background: linear-gradient(180deg, #ffffff 0%, #fbfbfb 52%, #f5f8fd 100%);\n }\n\n a {\n color: inherit;\n text-decoration: none;\n }\n\n img {\n display: block;\n max-width: 100%;\n }\n\n .page-shell {\n overflow-x: clip;\n }\n\n .container {\n width: var(--content-width);\n margin: 0 auto;\n }\n\n .eyebrow {\n display: inline-flex;\n align-items: center;\n gap: 10px;\n padding: 9px 14px;\n border-radius: 999px;\n border: 1px solid var(--line);\n background: #fff;\n color: var(--blue-deep);\n font-size: 0.8rem;\n font-weight: 700;\n letter-spacing: 0.03em;\n text-transform: uppercase;\n }\n\n .eyebrow-dot {\n width: 8px;\n height: 8px;\n border-radius: 999px;\n background: linear-gradient(135deg, var(--blue) 0%, #79bcff 100%);\n box-shadow: 0 0 0 6px rgba(76, 157, 232, 0.12);\n }\n\n .hero {\n margin-top: 18px;\n padding: 26px 26px 28px;\n border-radius: var(--radius-xl);\n border: 1px solid var(--line);\n background: var(--surface);\n box-shadow: var(--shadow);\n }\n\n .hero-grid {\n display: grid;\n grid-template-columns: minmax(0, 1.1fr) minmax(320px, 0.9fr);\n gap: 24px;\n align-items: stretch;\n }\n\n .hero-copy {\n display: flex;\n flex-direction: column;\n justify-content: flex-start;\n align-items: flex-start;\n min-height: 100%;\n padding-top: 4px;\n }\n\n .hero-copy-main {\n width: 100%;\n flex: 1;\n display: flex;\n flex-direction: column;\n align-items: center;\n justify-content: center;\n text-align: center;\n }\n\n .hero-copy h1 {\n margin: 22px 0 16px;\n font-size: clamp(2.7rem, 4.8vw, 4.8rem);\n line-height: 0.95;\n letter-spacing: -0.06em;\n text-wrap: balance;\n }\n\n .hero-copy p {\n margin: 0;\n max-width: 760px;\n font-size: 1rem;\n line-height: 1.66;\n color: var(--muted);\n }\n\n .hero-side {\n display: grid;\n gap: 14px;\n }\n\n .metric-card,\n .toc,\n .article-card,\n .quote-card,\n .table-card,\n .faq-card {\n background: var(--surface);\n border: 1px solid var(--line);\n box-shadow: var(--shadow);\n }\n\n .metrics-grid {\n display: grid;\n grid-template-columns: repeat(2, minmax(0, 1fr));\n gap: 14px;\n }\n\n .metric-card {\n min-height: 144px;\n padding: 18px;\n border-radius: var(--radius-lg);\n display: grid;\n align-content: start;\n }\n\n .metric-card span {\n font-size: 0.82rem;\n font-weight: 700;\n letter-spacing: 0.04em;\n text-transform: uppercase;\n color: var(--blue-deep);\n }\n\n .metric-card strong {\n margin-top: 10px;\n font-size: clamp(1.85rem, 2.8vw, 2.55rem);\n line-height: 0.96;\n letter-spacing: -0.05em;\n color: var(--ink);\n }\n\n .metric-card p {\n margin: 10px 0 0;\n color: var(--muted);\n line-height: 1.5;\n font-size: 0.92rem;\n }\n\n .layout {\n display: grid;\n grid-template-columns: minmax(0, 1fr) 260px;\n gap: 28px;\n align-items: start;\n padding-bottom: 80px;\n }\n\n .content {\n min-width: 0;\n }\n\n .rail {\n position: sticky;\n top: 28px;\n display: grid;\n gap: 14px;\n margin-top: 18px;\n align-self: start;\n }\n\n .toc {\n border-radius: 24px;\n padding: 18px;\n }\n\n .toc h2 {\n margin: 0 0 14px;\n font-size: 1rem;\n letter-spacing: -0.03em;\n }\n\n .toc-links {\n display: flex;\n flex-direction: column;\n gap: 8px;\n }\n\n .toc-link {\n display: block;\n padding: 10px 12px;\n border-radius: 14px;\n color: var(--muted);\n font-weight: 700;\n transition: background 0.18s ease, color 0.18s ease;\n }\n\n .toc-link:hover,\n .toc-link.is-active {\n background: rgba(227, 242, 255, 0.9);\n color: var(--blue-deep);\n }\n\n .mobile-toc-wrap {\n display: none;\n margin: 22px 0 10px;\n }\n\n .mobile-toc-button {\n width: 100%;\n justify-content: space-between;\n background: rgba(255, 255, 255, 0.96);\n color: var(--blue-deep);\n border: 1px solid var(--line);\n }\n\n .button {\n display: inline-flex;\n align-items: center;\n justify-content: center;\n gap: 10px;\n min-height: 50px;\n padding: 0 18px;\n border-radius: 999px;\n border: 1px solid transparent;\n font-family: \"Roboto\", sans-serif;\n font-weight: 700;\n font-size: 0.95rem;\n cursor: pointer;\n }\n\n .mobile-toc-panel {\n display: none;\n margin-top: 12px;\n padding: 14px;\n border-radius: 20px;\n background: rgba(255, 255, 255, 0.96);\n border: 1px solid var(--line);\n box-shadow: var(--shadow);\n }\n\n .mobile-toc-panel.is-open {\n display: block;\n }\n\n .mobile-toc-cta {\n margin-top: 14px;\n padding-top: 14px;\n border-top: 1px solid rgba(127, 152, 197, 0.16);\n }\n\n .section {\n display: grid;\n gap: 18px;\n padding: 34px 0;\n scroll-margin-top: 24px;\n }\n\n .section-head {\n margin-bottom: 0;\n }\n\n .section-head h2 {\n margin: 12px 0 10px;\n font-size: clamp(1.8rem, 3.2vw, 2.5rem);\n line-height: 1.02;\n letter-spacing: -0.05em;\n }\n\n .section-head p {\n margin: 0;\n max-width: 820px;\n color: var(--muted);\n line-height: 1.62;\n font-size: 0.98rem;\n }\n\n .article-card,\n .quote-card,\n .table-card {\n display: flex;\n flex-direction: column;\n gap: 14px;\n border-radius: 20px;\n padding: 22px;\n }\n\n .prose > * {\n margin: 0;\n }\n\n .prose p,\n .prose li {\n color: var(--muted);\n font-size: 0.98rem;\n line-height: 1.72;\n }\n\n .prose p strong,\n .prose li strong,\n .prose td strong,\n .prose blockquote strong {\n color: var(--ink);\n }\n\n .prose h3 {\n margin: 0;\n font-size: 1.34rem;\n line-height: 1.05;\n letter-spacing: -0.04em;\n color: var(--ink);\n }\n\n .prose ul,\n .prose ol {\n margin: 0;\n padding-left: 20px;\n }\n\n .prose li + li {\n margin-top: 8px;\n }\n\n .quote-card {\n background: linear-gradient(180deg, rgba(227, 242, 255, 0.56) 0%, rgba(255, 255, 255, 0.98) 100%);\n border-color: rgba(76, 157, 232, 0.18);\n }\n\n .quote-card blockquote {\n margin: 0;\n padding-left: 16px;\n border-left: 2px solid rgba(76, 157, 232, 0.3);\n }\n\n .quote-card p {\n margin: 0;\n color: var(--ink);\n font-size: 1rem;\n line-height: 1.72;\n }\n\n .source-inline {\n display: inline;\n white-space: normal;\n }\n\n .source-inline a,\n .source-table a {\n color: var(--blue-deep);\n text-decoration: underline;\n text-underline-offset: 0.12em;\n }\n\n .lead-metrics {\n display: grid;\n grid-template-columns: repeat(3, minmax(0, 1fr));\n gap: 12px;\n margin-top: 0;\n }\n\n .lead-metric {\n padding: 16px;\n border-radius: 16px;\n background: #fff;\n border: 1px solid var(--line);\n }\n\n .lead-metric strong {\n display: block;\n font-size: 1.18rem;\n line-height: 1;\n letter-spacing: -0.04em;\n color: var(--blue-deep);\n }\n\n .lead-metric span {\n display: block;\n margin-top: 8px;\n color: var(--muted);\n font-size: 0.88rem;\n line-height: 1.44;\n }\n\n .subgrid {\n display: grid;\n grid-template-columns: repeat(2, minmax(0, 1fr));\n gap: 14px;\n align-items: stretch;\n }\n\n .subgrid > .article-card,\n .subgrid > .quote-card {\n height: 100%;\n }\n\n .signal-grid,\n .compare-grid,\n .timeline-grid {\n display: grid;\n gap: 14px;\n }\n\n .signal-grid {\n grid-template-columns: repeat(4, minmax(0, 1fr));\n }\n\n .compare-grid,\n .timeline-grid {\n grid-template-columns: repeat(2, minmax(0, 1fr));\n }\n\n .signal-card,\n .compare-card,\n .timeline-card {\n padding: 18px;\n border-radius: 18px;\n border: 1px solid var(--line);\n background: rgba(255, 255, 255, 0.98);\n box-shadow: var(--shadow);\n }\n\n .signal-card span,\n .compare-card span,\n .timeline-card span {\n display: inline-flex;\n align-items: center;\n width: fit-content;\n min-height: 28px;\n padding: 0 10px;\n border-radius: 999px;\n background: rgba(227, 242, 255, 0.92);\n color: var(--blue-deep);\n font-size: 0.74rem;\n font-weight: 700;\n letter-spacing: 0.03em;\n text-transform: uppercase;\n }\n\n .signal-card strong,\n .compare-card h3,\n .timeline-card h3 {\n display: block;\n margin-top: 12px;\n font-size: 1.2rem;\n line-height: 1.06;\n letter-spacing: -0.04em;\n color: var(--ink);\n }\n\n .signal-card p,\n .compare-card p,\n .timeline-card p {\n margin: 10px 0 0;\n color: var(--muted);\n font-size: 0.93rem;\n line-height: 1.62;\n }\n\n .compare-card ul,\n .timeline-card ul {\n margin: 14px 0 0;\n padding-left: 18px;\n color: var(--muted);\n }\n\n .compare-card li + li,\n .timeline-card li + li {\n margin-top: 8px;\n }\n\n .status-pill-row {\n display: flex;\n flex-wrap: wrap;\n gap: 8px;\n margin-top: 12px;\n }\n\n .status-pill {\n display: inline-flex;\n align-items: center;\n min-height: 30px;\n padding: 0 12px;\n border-radius: 999px;\n border: 1px solid rgba(76, 157, 232, 0.16);\n background: #fff;\n color: var(--blue-deep);\n font-size: 0.78rem;\n font-weight: 700;\n }\n\n .scope-note {\n margin-top: 4px;\n color: var(--muted);\n font-size: 0.88rem;\n line-height: 1.58;\n }\n\n .bars {\n display: grid;\n gap: 12px;\n }\n\n .bar-row {\n display: grid;\n gap: 7px;\n }\n\n .bar-row label {\n font-size: 0.84rem;\n font-weight: 700;\n color: var(--ink);\n }\n\n .bar-track {\n position: relative;\n height: 10px;\n border-radius: 999px;\n background: rgba(227, 242, 255, 0.92);\n overflow: hidden;\n }\n\n .bar-fill {\n position: absolute;\n inset: 0 auto 0 0;\n border-radius: inherit;\n background: linear-gradient(135deg, var(--blue) 0%, #79bcff 100%);\n }\n\n .table-card {\n overflow: hidden;\n }\n\n .cta-band {\n display: grid;\n grid-template-columns: minmax(0, 1fr) auto;\n gap: 18px;\n align-items: center;\n padding: 24px 26px;\n border-radius: 24px;\n background: linear-gradient(135deg, rgba(227, 242, 255, 0.6) 0%, rgba(255, 255, 255, 0.98) 100%);\n border: 1px solid rgba(76, 157, 232, 0.18);\n box-shadow: var(--shadow);\n }\n\n .cta-band h3 {\n margin: 0 0 10px;\n font-size: clamp(1.45rem, 2.4vw, 2.05rem);\n line-height: 1;\n letter-spacing: -0.05em;\n }\n\n .cta-band p {\n margin: 0;\n max-width: 760px;\n color: var(--muted);\n line-height: 1.66;\n font-size: 0.96rem;\n }\n\n .cta-actions {\n display: flex;\n flex-wrap: wrap;\n gap: 10px;\n justify-content: flex-end;\n }\n\n .button-primary {\n background: linear-gradient(135deg, var(--orange) 0%, #ffad43 100%);\n color: #fff;\n box-shadow: 0 10px 22px rgba(247, 147, 26, 0.2);\n }\n\n .button-secondary {\n background: #ffffff;\n color: var(--blue-deep);\n border-color: rgba(76, 157, 232, 0.18);\n box-shadow: 0 10px 22px rgba(1, 38, 138, 0.06);\n }\n\n .sidebar-cta {\n padding: 16px;\n border-radius: 22px;\n border: 1px solid rgba(76, 157, 232, 0.16);\n background: linear-gradient(180deg, rgba(227, 242, 255, 0.52) 0%, rgba(255, 255, 255, 0.98) 100%);\n box-shadow: var(--shadow);\n }\n\n .sidebar-cta h3 {\n margin: 0 0 8px;\n font-size: 1.08rem;\n line-height: 1.04;\n letter-spacing: -0.04em;\n }\n\n .sidebar-cta p {\n margin: 0 0 12px;\n color: var(--muted);\n font-size: 0.86rem;\n line-height: 1.48;\n }\n\n .sidebar-cta .button {\n width: 100%;\n min-height: 44px;\n }\n\n .table-scroll {\n overflow-x: auto;\n margin-top: 0;\n padding-bottom: 6px;\n }\n\n table {\n width: 100%;\n min-width: 720px;\n border-collapse: collapse;\n }\n\n th,\n td {\n text-align: left;\n vertical-align: top;\n padding: 14px 12px;\n border-bottom: 1px solid rgba(127, 152, 197, 0.18);\n }\n\n th {\n font-size: 0.82rem;\n letter-spacing: 0.04em;\n text-transform: uppercase;\n color: var(--blue-deep);\n background: rgba(248, 248, 248, 1);\n }\n\n td {\n color: var(--muted);\n line-height: 1.62;\n font-size: 0.95rem;\n }\n\n .reviewer-card {\n display: grid;\n grid-template-columns: 88px minmax(0, 1fr);\n gap: 18px;\n align-items: start;\n border-radius: 22px;\n padding: 22px;\n background: rgba(255, 255, 255, 0.98);\n border: 1px solid var(--line);\n box-shadow: var(--shadow);\n }\n\n .reviewer-avatar {\n width: 88px;\n height: 88px;\n border-radius: 24px;\n background: linear-gradient(135deg, rgba(227, 242, 255, 0.92) 0%, rgba(248, 248, 248, 1) 100%);\n border: 1px solid var(--line);\n overflow: hidden;\n box-shadow: 0 10px 22px rgba(1, 38, 138, 0.08);\n }\n\n .reviewer-avatar img {\n width: 100%;\n height: 100%;\n object-fit: cover;\n }\n\n .reviewer-card h3 {\n margin: 0;\n font-size: 1.32rem;\n line-height: 1.04;\n letter-spacing: -0.04em;\n }\n\n .reviewer-role {\n display: inline-flex;\n align-items: center;\n width: fit-content;\n min-height: 30px;\n margin-top: 10px;\n padding: 0 11px;\n border-radius: 999px;\n background: rgba(227, 242, 255, 0.92);\n color: var(--blue-deep);\n font-size: 0.76rem;\n font-weight: 700;\n letter-spacing: 0.03em;\n text-transform: uppercase;\n }\n\n .reviewer-card p {\n margin: 12px 0 0;\n color: var(--muted);\n line-height: 1.68;\n font-size: 0.95rem;\n max-width: 760px;\n }\n\n .faq-list {\n display: grid;\n gap: 14px;\n }\n\n .faq-card {\n border-radius: 22px;\n overflow: hidden;\n background: rgba(255, 255, 255, 0.96);\n }\n\n .faq-card[open] {\n background: linear-gradient(180deg, rgba(227, 242, 255, 0.42) 0%, rgba(255, 255, 255, 0.98) 100%);\n border-color: rgba(76, 157, 232, 0.18);\n }\n\n .faq-card summary {\n list-style: none;\n cursor: pointer;\n display: flex;\n align-items: center;\n justify-content: space-between;\n gap: 18px;\n padding: 20px 24px;\n font-size: 1.04rem;\n font-weight: 700;\n line-height: 1.4;\n }\n\n .faq-card summary::after {\n content: \"\";\n width: 10px;\n height: 10px;\n border-right: 2px solid var(--blue-deep);\n border-bottom: 2px solid var(--blue-deep);\n transform: rotate(45deg);\n transition: transform 0.2s ease;\n flex-shrink: 0;\n margin-top: -4px;\n }\n\n .faq-card[open] summary::after {\n transform: rotate(225deg);\n margin-top: 2px;\n }\n\n .faq-card summary::-webkit-details-marker {\n display: none;\n }\n\n .faq-card p {\n margin: 0;\n padding: 0 24px 22px;\n color: var(--muted);\n line-height: 1.72;\n font-size: 0.96rem;\n }\n\n .source-table td:first-child {\n color: var(--ink);\n font-weight: 700;\n }\n\n @media (max-width: 1100px) {\n .hero-grid,\n .layout,\n .subgrid,\n .cta-band,\n .signal-grid,\n .compare-grid,\n .timeline-grid {\n grid-template-columns: 1fr;\n }\n\n .lead-metrics,\n .metrics-grid {\n grid-template-columns: repeat(2, minmax(0, 1fr));\n }\n\n .cta-actions {\n justify-content: flex-start;\n }\n\n .toc {\n display: none;\n }\n\n .rail {\n display: none;\n }\n\n .mobile-toc-wrap {\n display: block;\n }\n }\n\n @media (max-width: 860px) {\n .lead-metrics,\n .metrics-grid {\n grid-template-columns: 1fr;\n }\n\n .reviewer-card {\n grid-template-columns: 1fr;\n }\n\n .reviewer-avatar {\n width: 72px;\n height: 72px;\n border-radius: 20px;\n }\n }\n\n @media (max-width: 640px) {\n :root {\n --content-width: min(100vw - 24px, 100vw - 24px);\n }\n\n .hero {\n padding: 22px 18px 24px;\n }\n\n .article-card,\n .quote-card,\n .table-card,\n .faq-card summary {\n padding-left: 18px;\n padding-right: 18px;\n }\n\n .faq-card p {\n padding-left: 18px;\n padding-right: 18px;\n }\n\n th,\n td {\n padding: 12px 10px;\n }\n }\n <\/style>\n<\/head>\n<body>\n <div class=\"page-shell\">\n <main class=\"container\">\n <section class=\"hero\">\n <div class=\"mobile-toc-wrap\">\n <button class=\"button mobile-toc-button\" id=\"mobileTocButton\" type=\"button\" aria-expanded=\"false\" aria-controls=\"mobileTocPanel\">\n <span>On this page<\/span>\n <span>\u2630<\/span>\n <\/button>\n <div class=\"mobile-toc-panel\" id=\"mobileTocPanel\">\n <a class=\"toc-link\" href=\"#overview\">Why Glamsterdam matters<\/a>\n <a class=\"toc-link\" href=\"#epbs\">What ePBS changes<\/a>\n <a class=\"toc-link\" href=\"#bals\">What BALs change<\/a>\n <a class=\"toc-link\" href=\"#scope\">Current EIP scope<\/a>\n <a class=\"toc-link\" href=\"#fees\">Gas fees and capacity<\/a>\n <a class=\"toc-link\" href=\"#users\">What users should do<\/a>\n <a class=\"toc-link\" href=\"#timeline\">Timeline to watch<\/a>\n <a class=\"toc-link\" href=\"#risks\">Risks and open questions<\/a>\n <a class=\"toc-link\" href=\"#takeaway\">Key takeaway<\/a>\n <a class=\"toc-link\" href=\"#faq\">FAQ<\/a>\n <a class=\"toc-link\" href=\"#reviewed-by\">Reviewed by<\/a>\n <a class=\"toc-link\" href=\"#sources\">Sources<\/a>\n <div class=\"mobile-toc-cta\">\n <div class=\"sidebar-cta\">\n <h3>Buy ETH<\/h3>\n <p>Open the Guardarian flow directly.<\/p>\n <a class=\"button button-primary\" href=\"https:\/\/guardarian.com\/buy-eth\">Buy ETH<\/a>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n <div class=\"hero-grid\">\n <div class=\"hero-copy\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Research article<\/div>\n <div class=\"hero-copy-main\">\n <h1>Ethereum\u2019s Glamsterdam Upgrade<\/h1>\n <p>\n Ethereum\u2019s next major planned upgrade is focused on Layer 1 scaling, cleaner block production,\n parallelization foundations, and the infrastructure needed to raise capacity without giving up decentralization.\n <\/p>\n <\/div>\n <\/div>\n\n <div class=\"hero-side\">\n <div class=\"metrics-grid\">\n <article class=\"metric-card\">\n <span>Main focus<\/span>\n <strong>L1 scaling<\/strong>\n <p>Ethereum.org frames Glamsterdam around capacity expansion, parallelization and long-term network sustainability.<\/p>\n <\/article>\n <article class=\"metric-card\">\n <span>Headline features<\/span>\n <strong>ePBS + BALs<\/strong>\n <p>EIP-7732 changes block production while EIP-7928 adds block-level access lists for parallel work and faster validation paths.<\/p>\n <\/article>\n <article class=\"metric-card\">\n <span>Scope status<\/span>\n <strong>Draft meta EIP<\/strong>\n <p>EIP-7773 is still in draft, which means the current proposal set is real but the scope is not immutable yet.<\/p>\n <\/article>\n <article class=\"metric-card\">\n <span>Latest public signal<\/span>\n <strong>June 8, 2026<\/strong>\n <p>ACDT #82 focused on glamsterdam-devnet-5 and named glamsterdam-devnet-6 scope finalization as the next step.<\/p>\n <\/article>\n <\/div>\n <\/div>\n <\/div>\n <\/section>\n\n <div class=\"layout\">\n <div class=\"content\">\n <section class=\"section\" id=\"overview\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Overview<\/div>\n <h2>Ethereum\u2019s Next Big Upgrade Is About Scaling Layer 1<\/h2>\n <p>Glamsterdam is not a new chain or a user-facing app release. It is a protocol-level upgrade that goes deeper into Ethereum\u2019s base layer and the mechanics of block production.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>Ethereum\u2019s next major planned upgrade, <strong>Glamsterdam<\/strong>, is shaping up to be one of the most important protocol changes on the 2026 roadmap. While recent upgrades were easier to explain through blobs, rollups, or immediate user cost changes, Glamsterdam is more infrastructural. It changes how Ethereum prepares, builds, and validates blocks.<\/p>\n <p>The official <strong>ethereum.org<\/strong> roadmap page frames Glamsterdam around <strong>Layer 1 scaling<\/strong>, <strong>parallelization<\/strong>, <strong>capacity expansion<\/strong>, and <strong>sustainability<\/strong>. That is the cleanest summary of why it matters: Ethereum wants to handle more activity on the base layer without turning node operation into an arms race. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>]<\/span><\/p>\n <p>One quick decoding note before we go deeper: <strong>EIP<\/strong> means <strong>Ethereum Improvement Proposal<\/strong>. It is just Ethereum\u2019s name for a formal upgrade proposal. So when you see a number like <strong>EIP-7981<\/strong>, that does not mean users are expected to memorize it. It just means \u201cone specific change being considered inside the broader upgrade.\u201d<\/p>\n <p>At the same time, the current scope is still evolving. The meta EIP for the upgrade, <strong>EIP-7773<\/strong>, is in <strong>Draft<\/strong> status as of <strong>June 17, 2026<\/strong>. That means Glamsterdam is very real, but anyone speaking about it as if every feature and every activation detail is already final is getting ahead of the process. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <\/article>\n\n <div class=\"signal-grid\">\n <article class=\"signal-card\">\n <span>Roadmap focus<\/span>\n <strong>Capacity on L1<\/strong>\n <p>Ethereum.org positions Glamsterdam as a scaling and sustainability upgrade rather than a narrow UX patch.<\/p>\n <\/article>\n <article class=\"signal-card\">\n <span>Critical pair<\/span>\n <strong>ePBS + BALs<\/strong>\n <p>Those two proposals are doing much of the conceptual heavy lifting for block production and parallel work.<\/p>\n <\/article>\n <article class=\"signal-card\">\n <span>Current state<\/span>\n <strong>Still moving<\/strong>\n <p>The official scope is being tracked publicly, but both the meta EIP and several key proposals remain draft-stage items.<\/p>\n <\/article>\n <article class=\"signal-card\">\n <span>Mainnet date<\/span>\n <strong>Not announced<\/strong>\n <p>No public activation date is listed yet, so testing progress matters more than roadmap hype right now.<\/p>\n <\/article>\n <\/div>\n\n <div class=\"compare-grid\">\n <article class=\"compare-card\">\n <span>Quick glossary<\/span>\n <h3>Terms you actually need<\/h3>\n <ul>\n <li><strong>EIP:<\/strong> a formal Ethereum upgrade proposal.<\/li>\n <li><strong>ePBS:<\/strong> a new way to split who builds a block and who proposes it.<\/li>\n <li><strong>BALs:<\/strong> a map of what a block will touch in Ethereum\u2019s state.<\/li>\n <li><strong>Devnet:<\/strong> an early test network used by client teams before public testnets.<\/li>\n <\/ul>\n <\/article>\n <article class=\"compare-card\">\n <span>What not to worry about<\/span>\n <h3>You do not need every number<\/h3>\n <p>Most readers do not need to know what <strong>EIP-7981<\/strong> means line by line. The useful question is what category it belongs to. In this article, the important split is simple:<\/p>\n <ul>\n <li>a few proposals are foundational and user-relevant, like ePBS and BALs;<\/li>\n <li>many others are lower-level pricing, opcode, and execution cleanups that mostly matter to client teams and infrastructure.<\/li>\n <\/ul>\n <\/article>\n <\/div>\n <\/section>\n\n <section class=\"section\" id=\"epbs\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> ePBS<\/div>\n <h2>What ePBS Actually Changes<\/h2>\n <p>The most important Glamsterdam proposal is not a cosmetic tweak. It changes the shape of block validation itself.<\/p>\n <\/div>\n\n <div class=\"subgrid\">\n <article class=\"article-card prose\">\n <h3>From off-protocol habits to in-protocol rules<\/h3>\n <p><strong>EIP-7732<\/strong>, Enshrined Proposer-Builder Separation, separates the consensus side of the block from the execution side and introduces <strong>in-protocol builders<\/strong>. It also adds a <strong>Payload Timeliness Committee<\/strong>, a validator subset that attests whether the committed payload was revealed correctly and on time. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>]<\/span><\/p>\n <p>Today, Ethereum\u2019s proposer-builder separation largely exists through extra-protocol systems such as MEV-Boost. ePBS moves more of that flow into Ethereum itself. That makes block production less dependent on outside coordination and more explicitly defined by protocol rules.<\/p>\n <\/article>\n\n <article class=\"quote-card prose\">\n <h3>Why client teams treat it as the hard part<\/h3>\n <blockquote>\n <p>\n Checkpoint #9 says ePBS is proving trickier than anticipated because the protocol now has to handle two-party coordination and disagreement inside consensus rather than outside of it.\n <\/p>\n <\/blockquote>\n <p>That source-backed caution matters. Glamsterdam is not slow because teams forgot to ship it. It is slow because ePBS touches practically every layer of the block production path. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9, Apr 10 2026<\/a>]<\/span><\/p>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>The official roadmap page adds a useful operational angle: ePBS is intended to expand the tight propagation and validation window from roughly <strong>2 seconds<\/strong> to about <strong>9 seconds<\/strong>. That gives Ethereum more room to safely handle larger and more complex blocks if the rest of the stack can keep up. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>]<\/span><\/p>\n <p>The payoff, if it works, is straightforward: more efficient block production, better room for higher throughput, and less reliance on external builder infrastructure. The cost is complexity. And Ethereum is being unusually explicit that this complexity is real.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"bals\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> BALs<\/div>\n <h2>What Block-Level Access Lists Change<\/h2>\n <p>If ePBS is about cleaner block production, BALs are about making more of the execution path predictable and parallelizable.<\/p>\n <\/div>\n\n <div class=\"subgrid\">\n <article class=\"article-card prose\">\n <h3>What the spec says<\/h3>\n <p><strong>EIP-7928<\/strong> introduces <strong>Block-Level Access Lists<\/strong>, or BALs. The EIP says these lists record all accounts and storage locations accessed during block execution, along with their post-execution values. The stated goal is to enable <strong>parallel disk reads<\/strong>, <strong>parallel transaction validation<\/strong>, <strong>parallel state root computation<\/strong>, and even <strong>executionless state updates<\/strong>. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928<\/a>]<\/span><\/p>\n <p>In plain language, BALs give clients a much clearer map of what a block touches. That matters because Ethereum cannot safely parallelize more work if it has to discover every dependency too late in the process.<\/p>\n <\/article>\n\n <article class=\"quote-card prose\">\n <h3>Why this matters for scaling<\/h3>\n <blockquote>\n <p>\n BALs are not a cosmetic optimization. They are a preparation layer for a future where Ethereum can use modern hardware more intelligently instead of forcing every step through a strictly sequential bottleneck.\n <\/p>\n <\/blockquote>\n <p>The motivation section of the EIP makes this explicit: without knowing accessed addresses and storage slots ahead of time, clients cannot parallelize much of the work safely. BALs are the dependency map that makes more advanced execution strategies practical. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928<\/a>]<\/span><\/p>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <div class=\"bars\">\n <div class=\"bar-row\">\n <label>Parallel disk reads<\/label>\n <div class=\"bar-track\"><div class=\"bar-fill\" style=\"width: 82%;\"><\/div><\/div>\n <\/div>\n <div class=\"bar-row\">\n <label>Parallel transaction validation<\/label>\n <div class=\"bar-track\"><div class=\"bar-fill\" style=\"width: 88%;\"><\/div><\/div>\n <\/div>\n <div class=\"bar-row\">\n <label>Executionless state updates<\/label>\n <div class=\"bar-track\"><div class=\"bar-fill\" style=\"width: 74%;\"><\/div><\/div>\n <\/div>\n <\/div>\n <p class=\"scope-note\">These bars are illustrative, not measured performance numbers. They simply show the three workstreams BALs are meant to unlock based on the EIP\u2019s stated design goals.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"scope\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Scope snapshot<\/div>\n <h2>What Is Actually in the Current Glamsterdam Scope<\/h2>\n <p>The best source for \u201cwhat is in Glamsterdam right now\u201d is not social media or generic explainers. It is EIP-7773.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>As of <strong>June 17, 2026<\/strong>, EIP-7773 lists <strong>ten<\/strong> proposals as <strong>Scheduled for Inclusion<\/strong>: <strong>EIP-7708<\/strong>, <strong>EIP-7732<\/strong>, <strong>EIP-7778<\/strong>, <strong>EIP-7843<\/strong>, <strong>EIP-7928<\/strong>, <strong>EIP-7954<\/strong>, <strong>EIP-7976<\/strong>, <strong>EIP-7981<\/strong>, <strong>EIP-8024<\/strong>, and <strong>EIP-8037<\/strong>. That is already a useful fact-check, because some older summaries omit <strong>EIP-7708<\/strong> from the scheduled set. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <p>But that raw list is not the best way to understand the upgrade. In practice, you can group the current scheduled items into three buckets: <strong>big architecture changes<\/strong> like ePBS and BALs, <strong>developer or EVM quality-of-life changes<\/strong> like new opcodes and contract-size adjustments, and <strong>gas repricing items<\/strong> that change how certain actions are charged. That framing is much more useful than memorizing proposal numbers.<\/p>\n <\/article>\n\n <div class=\"compare-grid\">\n <article class=\"compare-card\">\n <span>Scheduled now<\/span>\n <h3>What the scheduled items really are<\/h3>\n <ul>\n <li><strong>Block-production overhaul:<\/strong> ePBS changes who builds the block and how the payload arrives.<\/li>\n <li><strong>Parallelization groundwork:<\/strong> BALs tell clients what state a block touches.<\/li>\n <li><strong>Gas repricing:<\/strong> proposals like EIP-7778, EIP-7976, EIP-7981, and EIP-8037 rebalance how certain operations are charged.<\/li>\n <li><strong>Developer-facing changes:<\/strong> EIP-7954 raises maximum contract size, EIP-7843 adds a <code>SLOTNUM<\/code> opcode, and EIP-8024 improves EVM instruction compatibility.<\/li>\n <li><strong>Small protocol cleanup:<\/strong> EIP-7708 makes ETH transfers emit a log, which is mainly a tooling and observability improvement.<\/li>\n <\/ul>\n <\/article>\n <article class=\"compare-card\">\n <span>Considered now<\/span>\n <h3>Why \u201cconsidered\u201d matters<\/h3>\n <ul>\n <li><strong>EIP-2780<\/strong> is the one often cited in \u201cfees may go down\u201d discussions, but it is still only considered, not scheduled.<\/li>\n <li>Other considered items are still real proposals, but they have not yet crossed the threshold where Ethereum is treating them as likely ship targets.<\/li>\n <li>That is why article summaries should separate \u201cvery likely\u201d from \u201cmaybe,\u201d even when both sound exciting.<\/li>\n <li>For readers, the practical meaning is simple: the upgrade direction is clear, but some details are still under active engineering judgment.<\/li>\n <\/ul>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>This distinction matters. It means some of the most exciting narratives around Glamsterdam are directionally fair but too confident in their details. The cleaner way to say it is that the upgrade has a very visible center of gravity, but the outer rings of scope are still being refined in public.<\/p>\n <p>And to your earlier example: <strong>EIP-7981<\/strong> is not a \u201cheadline feature\u201d a normal user needs to study. It is one of the gas repricing changes inside the broader package. That is exactly why grouping these items by purpose is more useful than listing naked proposal numbers.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"fees\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Fees and capacity<\/div>\n <h2>How Glamsterdam Could Affect Gas Fees<\/h2>\n <p>The honest answer is more interesting than \u201cfees up\u201d or \u201cfees down.\u201d Glamsterdam is a scaling foundation first.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>Ethereum.org explicitly says Glamsterdam will likely help lower fees for everyday users over time, partly because the roadmap pairs ePBS and BALs with future capacity growth and partly because it discusses intrinsic gas reduction through <strong>EIP-2780<\/strong>. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>]<\/span><\/p>\n <p>But here is the important scope check: <strong>EIP-2780 is currently Considered for Inclusion, not Scheduled for Inclusion, in EIP-7773<\/strong>. So the safest interpretation is not \u201cGlamsterdam definitely flips a cheaper-fee switch on day one.\u201d The safer reading is that Glamsterdam is supposed to make future capacity increases more realistic, and that can help fee pressure if the scoped proposals actually make it through testing and activation. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <p>Checkpoint #9 reinforces this cautious framing. It says implementation is well underway but also notes that both ePBS and gas repricing work are more complex than they first looked. That is exactly the kind of sentence users should want to hear from protocol engineers. It means they are not pretending a deep upgrade is easy just because the market wants a clean headline. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>]<\/span><\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"users\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> User impact<\/div>\n <h2>What Users and Infrastructure Teams Should Actually Do<\/h2>\n <p>For regular ETH holders, the most important action is usually not to take action at all.<\/p>\n <\/div>\n\n <div class=\"subgrid\">\n <article class=\"article-card prose\">\n <h3>For regular users<\/h3>\n <p>Glamsterdam does not require people to \u201cupgrade ETH,\u201d claim replacement tokens, or connect wallets to random sites. Any page asking you to manually migrate your ETH because of Glamsterdam should be treated as suspicious.<\/p>\n <p>That is the clean user takeaway: if you simply hold ETH in a normal wallet or on a platform that manages its own backend upgrades, you typically do nothing.<\/p>\n <\/article>\n\n <article class=\"article-card prose\">\n <h3>For node operators and platforms<\/h3>\n <p>The heavier lift belongs to client teams, exchanges, node operators, RPC providers, validators, explorers, and indexing infrastructure. Those teams need to track client releases, devnet results, data pipeline compatibility, and execution or consensus changes that alter the structure of blocks.<\/p>\n <p>That is where Glamsterdam becomes operationally real: not in retail wallet UI, but in the backend stack that keeps Ethereum readable and reliable.<\/p>\n <\/article>\n <\/div>\n\n <\/section>\n\n <section class=\"section\" id=\"timeline\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Timeline<\/div>\n <h2>What to Watch Next in 2026<\/h2>\n <p>The main signal is not hype. It is whether client teams keep converting the current scope into stable multi-client releases.<\/p>\n <\/div>\n\n <div class=\"timeline-grid\">\n <article class=\"timeline-card\">\n <span>April 10, 2026<\/span>\n <h3>Checkpoint: \u201cwell underway\u201d<\/h3>\n <p>Ethereum Foundation\u2019s Checkpoint #9 says Glamsterdam implementation is well underway, but ePBS is the major sticking point and gas repricing work also has its own complexities.<\/p>\n <\/article>\n <article class=\"timeline-card\">\n <span>June 8, 2026<\/span>\n <h3>ACDT #82 confirms devnet focus<\/h3>\n <p>The public testing call centers on <code>glamsterdam-devnet-5<\/code> and names the scope finalization for <code>glamsterdam-devnet-6<\/code> as the next step.<\/p>\n <\/article>\n <article class=\"timeline-card\">\n <span>Next phase<\/span>\n <h3>Client inclusion and scope freeze<\/h3>\n <ul>\n <li>Get all CL clients included in glamsterdam-devnet-5<\/li>\n <li>Finalize both-layer scope for glamsterdam-devnet-6<\/li>\n <li>Keep stabilizing the combined feature set<\/li>\n <\/ul>\n <\/article>\n <article class=\"timeline-card\">\n <span>Later phase<\/span>\n <h3>Testnets, releases, mainnet date<\/h3>\n <ul>\n <li>Public testnets come after a stable all-feature devnet<\/li>\n <li>Client releases and security review follow<\/li>\n <li>Mainnet date still depends on progress, not on marketing calendars<\/li>\n <\/ul>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>The most useful timeline takeaway from the primary sources is simple: there is no fixed public mainnet date yet, and the process still depends on stabilizing multi-client devnets. That makes Glamsterdam very important, but not yet date-certain. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>, <a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">ACDT #82<\/a>]<\/span><\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"risks\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Risks<\/div>\n <h2>Risks and Open Questions<\/h2>\n <p>Ambitious protocol upgrades always create a list of hard questions. Glamsterdam is honest enough to put them on the table in public.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <ul>\n <li><strong>ePBS liveness risk:<\/strong> EIP-7732 explicitly discusses the free option problem and the possibility that builders may withhold a payload if incentives change. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>]<\/span><\/li>\n <li><strong>Client coordination:<\/strong> Checkpoint #9 says every part of the stack has to reason about partial blocks and two-party coordination, which is why ePBS is harder than expected. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>]<\/span><\/li>\n <li><strong>Scope discipline:<\/strong> fee-relevant and networking proposals are still split between Scheduled and Considered, so scope management remains part of the engineering risk. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/li>\n <li><strong>Infrastructure adaptation:<\/strong> even if frontend apps do not change much, RPC providers, node operators, validators, explorers, and indexers still have real migration work.<\/li>\n <\/ul>\n <p>None of that means Glamsterdam is in trouble. It means Ethereum is treating a foundational upgrade like a foundational upgrade. That is exactly what careful protocol work is supposed to look like.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"takeaway\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Takeaway<\/div>\n <h2>Key Takeaway<\/h2>\n <p>The cleanest summary is that Glamsterdam is Ethereum\u2019s current attempt to scale Layer 1 by changing the machinery underneath block production and execution.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>Glamsterdam matters because it targets Ethereum\u2019s base-layer constraints directly. ePBS changes how blocks are proposed and validated. BALs change how the network can prepare and parallelize execution-related work. The surrounding scope includes gas repricing and capacity-related items that are meant to make higher throughput safer over time.<\/p>\n <ul>\n <li>It is one of Ethereum\u2019s most important planned 2026 upgrades.<\/li>\n <li>Its center of gravity is clearly L1 scaling, ePBS, and BALs.<\/li>\n <li>Its exact final scope is still public and still moving.<\/li>\n <li>Its timing depends on successful devnets, testnets, and client readiness rather than a fixed launch promise.<\/li>\n <\/ul>\n <p>If you want the shortest honest version, it is this: <strong>Glamsterdam is a serious scaling upgrade, not a simple fee patch<\/strong>. And that is exactly why it deserves close attention in 2026.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"faq\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> FAQ<\/div>\n <h2>FAQ<\/h2>\n <p>Short answers to the questions readers usually have once the acronym layer gets too thick.<\/p>\n <\/div>\n\n <div class=\"faq-list\">\n <details class=\"faq-card\" open>\n <summary>Is Glamsterdam already live on Ethereum mainnet?<\/summary>\n <p>No. As of June 17, 2026, Glamsterdam is still in the development and testing phase. EIP-7773 remains in Draft status, and the public process is still focused on devnets, scope confirmation, and multi-client readiness. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>, <a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">ACDT #82<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>What is an EIP in simple terms?<\/summary>\n <p>An EIP is an Ethereum Improvement Proposal. Think of it as a formal spec for one protocol change. Big upgrades like Glamsterdam are usually bundles of several EIPs rather than one single change.<\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>What are the two most important Glamsterdam proposals right now?<\/summary>\n <p>The headline pair is EIP-7732, Enshrined Proposer-Builder Separation, and EIP-7928, Block-Level Access Lists. One changes how blocks are built and validated; the other prepares Ethereum for more parallel work during execution-related processing. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>, <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Do I need to understand things like EIP-7981?<\/summary>\n <p>Usually no. For most readers, it is enough to know whether a proposal is a headline architecture change, a gas repricing change, or a lower-level developer\/infrastructure tweak. EIP-7981 falls into the repricing bucket, not the \u201cmust understand before using ETH\u201d bucket.<\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Will Glamsterdam automatically make ETH transactions cheap?<\/summary>\n <p>Not automatically and not instantly. The official roadmap frames Glamsterdam as helpful for lower fees over time, but some fee-relevant proposals are still only Considered for Inclusion, not Scheduled. The safer interpretation is that Glamsterdam is a scaling foundation, not a magic fee switch. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>, <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Why is ePBS considered hard to ship?<\/summary>\n <p>Because it changes the hot path of block production and moves more proposer-builder coordination inside the protocol. Checkpoint #9 explicitly says this is a major sticking point, and EIP-7732 itself discusses liveness and withholding risks. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>, <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>What did ACDT #82 actually tell us?<\/summary>\n <p>It showed that Glamsterdam had already moved into public devnet discussion around <code>glamsterdam-devnet-5<\/code>, and that the next steps included bringing in all CL clients and finalizing both-layer scope for <code>glamsterdam-devnet-6<\/code>. <span class=\"source-inline\">[<a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">ACDT #82<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Do normal ETH holders need to do anything before Glamsterdam?<\/summary>\n <p>Usually no. Protocol upgrades matter much more for node operators, validators, exchanges, RPC providers, and other infrastructure teams. Users should mainly avoid scams that claim ETH needs a manual \u201cupgrade.\u201d<\/p>\n <\/details>\n <\/div>\n <\/section>\n\n <section class=\"section\" id=\"reviewed-by\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Reviewed by<\/div>\n <h2>Who reviewed this article<\/h2>\n <p>A short reviewer note for editorial context.<\/p>\n <\/div>\n\n <div class=\"reviewer-card\">\n <div class=\"reviewer-avatar\">\n <img decoding=\"async\" src=\"https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/image.png\" alt=\"Agatha Willings\">\n <\/div>\n <div>\n <h3>Agatha Willings<\/h3>\n <div class=\"reviewer-role\">Crypto researcher<\/div>\n <p>\n Agatha Willings reviews long-form crypto market and protocol content with a focus on source-backed\n claims, roadmap precision, and the difference between what Ethereum plans to ship, what is already\n live, and what still depends on successful testing.\n <\/p>\n <\/div>\n <\/div>\n <\/section>\n\n <section class=\"section\" id=\"sources\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Sources<\/div>\n <h2>Verified Sources<\/h2>\n <p>The article below is based primarily on official Ethereum sources, EIP specifications, and public testing-call materials. External links are marked <code>nofollow<\/code>.<\/p>\n <\/div>\n\n <div class=\"table-card prose\">\n <div class=\"table-scroll\">\n <table class=\"source-table\">\n <thead>\n <tr>\n <th>Source<\/th>\n <th>Date<\/th>\n <th>Key point used in article<\/th>\n <\/tr>\n <\/thead>\n <tbody>\n <tr>\n <td><a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org \u2014 Glamsterdam roadmap page<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Official framing for Glamsterdam\u2019s goals: L1 scaling, parallelization, capacity growth, sustainability, and the user-facing explanation of why the upgrade matters.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773 \u2014 Hardfork Meta: Glamsterdam<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Primary source for the current Scheduled, Considered, and Proposed scope of the Glamsterdam upgrade.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732 \u2014 Enshrined Proposer-Builder Separation<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Defines the protocol-level ePBS design, builder role, delayed execution validation, and Payload Timeliness Committee.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928 \u2014 Block-Level Access Lists<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Defines BALs and explicitly states their role in parallel disk reads, validation, state root computation, and executionless state updates.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum Foundation Blog \u2014 Checkpoint #9<\/a><\/td>\n <td>Apr 10, 2026<\/td>\n <td>Confirms that Glamsterdam implementation is well underway while also noting ePBS and gas repricing complexity.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum PM \u2014 All Core Devs Testing #82<\/a><\/td>\n <td>Jun 8, 2026<\/td>\n <td>Public call agenda and next steps showing glamsterdam-devnet-5 status and the scope finalization target for glamsterdam-devnet-6.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/github.com\/ethereum\/execution-specs\/issues\/2915\" rel=\"nofollow noopener\" target=\"_blank\">Execution Specs \u2014 glamsterdam-devnet-6 tracker<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Concrete public tracker reference linked from ACDT #82 for the next execution-layer devnet release work.<\/td>\n <\/tr>\n <\/tbody>\n <\/table>\n <\/div>\n <\/div>\n <\/section>\n <\/div>\n\n <aside class=\"rail\">\n <div class=\"toc\">\n <h2>On this page<\/h2>\n <nav class=\"toc-links\">\n <a class=\"toc-link\" href=\"#overview\">Why Glamsterdam matters<\/a>\n <a class=\"toc-link\" href=\"#epbs\">What ePBS changes<\/a>\n <a class=\"toc-link\" href=\"#bals\">What BALs change<\/a>\n <a class=\"toc-link\" href=\"#scope\">Current EIP scope<\/a>\n <a class=\"toc-link\" href=\"#fees\">Gas fees and capacity<\/a>\n <a class=\"toc-link\" href=\"#users\">What users should do<\/a>\n <a class=\"toc-link\" href=\"#timeline\">Timeline to watch<\/a>\n <a class=\"toc-link\" href=\"#risks\">Risks and open questions<\/a>\n <a class=\"toc-link\" href=\"#takeaway\">Key takeaway<\/a>\n <a class=\"toc-link\" href=\"#faq\">FAQ<\/a>\n <a class=\"toc-link\" href=\"#reviewed-by\">Reviewed by<\/a>\n <a class=\"toc-link\" href=\"#sources\">Sources<\/a>\n <\/nav>\n <\/div>\n\n <div class=\"sidebar-cta\">\n <h3>Buy ETH<\/h3>\n <p>Open the Guardarian flow directly.<\/p>\n <a class=\"button button-primary\" href=\"https:\/\/guardarian.com\/buy-eth\">Buy ETH<\/a>\n <\/div>\n <\/aside>\n <\/div>\n <\/main>\n <\/div>\n\n <script>\n (function () {\n const mobileButton = document.getElementById('mobileTocButton');\n const mobilePanel = document.getElementById('mobileTocPanel');\n const tocLinks = Array.from(document.querySelectorAll('.toc-link'));\n const sections = Array.from(document.querySelectorAll('[data-section]'));\n const externalLinks = Array.from(document.querySelectorAll('a[href^=\"http\"]'));\n\n externalLinks.forEach(function (link) {\n try {\n const url = new URL(link.href);\n const isGuardarian = url.hostname === 'guardarian.com' || url.hostname === 'www.guardarian.com';\n if (isGuardarian) {\n link.setAttribute('rel', 'noopener noreferrer');\n link.setAttribute('target', '_blank');\n return;\n }\n } catch (error) {\n return;\n }\n\n link.setAttribute('rel', 'nofollow noopener noreferrer');\n link.setAttribute('target', '_blank');\n });\n\n if (mobileButton && mobilePanel) {\n mobileButton.addEventListener('click', function () {\n const isOpen = mobilePanel.classList.toggle('is-open');\n mobileButton.setAttribute('aria-expanded', String(isOpen));\n });\n }\n\n tocLinks.forEach(function (link) {\n link.addEventListener('click', function () {\n if (mobilePanel) {\n mobilePanel.classList.remove('is-open');\n }\n if (mobileButton) {\n mobileButton.setAttribute('aria-expanded', 'false');\n }\n });\n });\n\n if ('IntersectionObserver' in window) {\n const observer = new IntersectionObserver(function (entries) {\n entries.forEach(function (entry) {\n if (!entry.isIntersecting) {\n return;\n }\n\n const id = entry.target.getAttribute('id');\n tocLinks.forEach(function (link) {\n const isActive = link.getAttribute('href') === '#' + id;\n link.classList.toggle('is-active', isActive);\n });\n });\n }, {\n rootMargin: '-30% 0px -55% 0px',\n threshold: 0\n });\n\n sections.forEach(function (section) {\n observer.observe(section);\n });\n }\n }());\n <\/script>\n<\/body>\n<\/html>\n\n","protected":false},"excerpt":{"rendered":"<p>Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.<\/p>\n","protected":false},"author":13,"featured_media":9727,"comment_status":"closed","ping_status":"open","sticky":false,"template":"calculator","format":"standard","meta":{"_uag_custom_page_level_css":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[174],"tags":[],"class_list":["post-9725","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cryptocurrency-news-and-insights"],"uagb_featured_image_src":{"full":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false],"thumbnail":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170-300x74.png",300,74,true],"medium":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false],"medium_large":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170-768x190.png",768,190,true],"large":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false],"1536x1536":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170-1536x381.png",1536,381,true],"2048x2048":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false]},"uagb_author_info":{"display_name":"Ivan","author_link":"https:\/\/guardarian.com\/blog\/author\/ivan"},"uagb_comment_info":0,"uagb_excerpt":"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.","_links":{"self":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts\/9725","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/comments?post=9725"}],"version-history":[{"count":2,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts\/9725\/revisions"}],"predecessor-version":[{"id":9728,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts\/9725\/revisions\/9728"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/media\/9727"}],"wp:attachment":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/media?parent=9725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/categories?post=9725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/tags?post=9725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

{"id":9725,"date":"2026-06-17T16:35:02","date_gmt":"2026-06-17T13:35:02","guid":{"rendered":"https:\/\/guardarian.com\/blog\/?p=9725"},"modified":"2026-06-17T16:35:04","modified_gmt":"2026-06-17T13:35:04","slug":"eth-glamsterdam-update","status":"publish","type":"post","link":"https:\/\/guardarian.com\/blog\/eth-glamsterdam-update","title":{"rendered":"Ethereum\u2019s Glamsterdam Upgrade Ethereum\u2019s Glamsterdam Upgrade"},"content":{"rendered":"\n\n\n\n \n \n Ethereum Glamsterdam Upgrade: ePBS, Block-Level Access Lists and L1 Scaling in 2026 | Guardarian<\/title>\n <meta name=\"description\" content=\"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.\">\n <meta name=\"robots\" content=\"index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1\">\n <meta name=\"author\" content=\"Guardarian\">\n <link rel=\"canonical\" href=\"https:\/\/guardarian.com\/blog\/ethereum-glamsterdam-upgrade-2026\">\n <meta property=\"og:locale\" content=\"en_US\">\n <meta property=\"og:type\" content=\"article\">\n <meta property=\"og:site_name\" content=\"Guardarian\">\n <meta property=\"og:title\" content=\"Ethereum Glamsterdam Upgrade: ePBS, Block-Level Access Lists and L1 Scaling in 2026 | Guardarian\">\n <meta property=\"og:description\" content=\"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.\">\n <meta property=\"og:url\" content=\"https:\/\/guardarian.com\/blog\/ethereum-glamsterdam-upgrade-2026\">\n <meta property=\"og:image\" content=\"https:\/\/guardarian.com\/services\/meta-geo.jpg\">\n <meta property=\"og:image:alt\" content=\"Editorial article about Ethereum's Glamsterdam upgrade, ePBS, Block-Level Access Lists, and Layer 1 scaling in 2026.\">\n <meta name=\"twitter:card\" content=\"summary_large_image\">\n <meta name=\"twitter:title\" content=\"Ethereum Glamsterdam Upgrade: ePBS, Block-Level Access Lists and L1 Scaling in 2026 | Guardarian\">\n <meta name=\"twitter:description\" content=\"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.\">\n <meta name=\"twitter:image\" content=\"https:\/\/guardarian.com\/services\/meta-geo.jpg\">\n <meta name=\"theme-color\" content=\"#ffffff\">\n <link rel=\"preconnect\" href=\"https:\/\/fonts.googleapis.com\">\n <link rel=\"preconnect\" href=\"https:\/\/fonts.gstatic.com\" crossorigin>\n <link href=\"https:\/\/fonts.googleapis.com\/css2?family=Roboto:wght@400;500;700;900&display=swap\" rel=\"stylesheet\">\n <style>\n :root {\n --surface: rgba(255, 255, 255, 0.97);\n --line: #e4e4e4;\n --ink: #1d1d1d;\n --muted: #6f7783;\n --blue: #4c9de8;\n --blue-deep: #01268a;\n --orange: #f7931a;\n --shadow: 0 12px 28px rgba(1, 38, 138, 0.06);\n --radius-xl: 30px;\n --radius-lg: 22px;\n --content-width: min(1180px, calc(100vw - 40px));\n }\n\n * {\n box-sizing: border-box;\n }\n\n html {\n scroll-behavior: smooth;\n }\n\n body {\n margin: 0;\n font-family: \"Roboto\", sans-serif;\n color: var(--ink);\n background: linear-gradient(180deg, #ffffff 0%, #fbfbfb 52%, #f5f8fd 100%);\n }\n\n a {\n color: inherit;\n text-decoration: none;\n }\n\n img {\n display: block;\n max-width: 100%;\n }\n\n .page-shell {\n overflow-x: clip;\n }\n\n .container {\n width: var(--content-width);\n margin: 0 auto;\n }\n\n .eyebrow {\n display: inline-flex;\n align-items: center;\n gap: 10px;\n padding: 9px 14px;\n border-radius: 999px;\n border: 1px solid var(--line);\n background: #fff;\n color: var(--blue-deep);\n font-size: 0.8rem;\n font-weight: 700;\n letter-spacing: 0.03em;\n text-transform: uppercase;\n }\n\n .eyebrow-dot {\n width: 8px;\n height: 8px;\n border-radius: 999px;\n background: linear-gradient(135deg, var(--blue) 0%, #79bcff 100%);\n box-shadow: 0 0 0 6px rgba(76, 157, 232, 0.12);\n }\n\n .hero {\n margin-top: 18px;\n padding: 26px 26px 28px;\n border-radius: var(--radius-xl);\n border: 1px solid var(--line);\n background: var(--surface);\n box-shadow: var(--shadow);\n }\n\n .hero-grid {\n display: grid;\n grid-template-columns: minmax(0, 1.1fr) minmax(320px, 0.9fr);\n gap: 24px;\n align-items: stretch;\n }\n\n .hero-copy {\n display: flex;\n flex-direction: column;\n justify-content: flex-start;\n align-items: flex-start;\n min-height: 100%;\n padding-top: 4px;\n }\n\n .hero-copy-main {\n width: 100%;\n flex: 1;\n display: flex;\n flex-direction: column;\n align-items: center;\n justify-content: center;\n text-align: center;\n }\n\n .hero-copy h1 {\n margin: 22px 0 16px;\n font-size: clamp(2.7rem, 4.8vw, 4.8rem);\n line-height: 0.95;\n letter-spacing: -0.06em;\n text-wrap: balance;\n }\n\n .hero-copy p {\n margin: 0;\n max-width: 760px;\n font-size: 1rem;\n line-height: 1.66;\n color: var(--muted);\n }\n\n .hero-side {\n display: grid;\n gap: 14px;\n }\n\n .metric-card,\n .toc,\n .article-card,\n .quote-card,\n .table-card,\n .faq-card {\n background: var(--surface);\n border: 1px solid var(--line);\n box-shadow: var(--shadow);\n }\n\n .metrics-grid {\n display: grid;\n grid-template-columns: repeat(2, minmax(0, 1fr));\n gap: 14px;\n }\n\n .metric-card {\n min-height: 144px;\n padding: 18px;\n border-radius: var(--radius-lg);\n display: grid;\n align-content: start;\n }\n\n .metric-card span {\n font-size: 0.82rem;\n font-weight: 700;\n letter-spacing: 0.04em;\n text-transform: uppercase;\n color: var(--blue-deep);\n }\n\n .metric-card strong {\n margin-top: 10px;\n font-size: clamp(1.85rem, 2.8vw, 2.55rem);\n line-height: 0.96;\n letter-spacing: -0.05em;\n color: var(--ink);\n }\n\n .metric-card p {\n margin: 10px 0 0;\n color: var(--muted);\n line-height: 1.5;\n font-size: 0.92rem;\n }\n\n .layout {\n display: grid;\n grid-template-columns: minmax(0, 1fr) 260px;\n gap: 28px;\n align-items: start;\n padding-bottom: 80px;\n }\n\n .content {\n min-width: 0;\n }\n\n .rail {\n position: sticky;\n top: 28px;\n display: grid;\n gap: 14px;\n margin-top: 18px;\n align-self: start;\n }\n\n .toc {\n border-radius: 24px;\n padding: 18px;\n }\n\n .toc h2 {\n margin: 0 0 14px;\n font-size: 1rem;\n letter-spacing: -0.03em;\n }\n\n .toc-links {\n display: flex;\n flex-direction: column;\n gap: 8px;\n }\n\n .toc-link {\n display: block;\n padding: 10px 12px;\n border-radius: 14px;\n color: var(--muted);\n font-weight: 700;\n transition: background 0.18s ease, color 0.18s ease;\n }\n\n .toc-link:hover,\n .toc-link.is-active {\n background: rgba(227, 242, 255, 0.9);\n color: var(--blue-deep);\n }\n\n .mobile-toc-wrap {\n display: none;\n margin: 22px 0 10px;\n }\n\n .mobile-toc-button {\n width: 100%;\n justify-content: space-between;\n background: rgba(255, 255, 255, 0.96);\n color: var(--blue-deep);\n border: 1px solid var(--line);\n }\n\n .button {\n display: inline-flex;\n align-items: center;\n justify-content: center;\n gap: 10px;\n min-height: 50px;\n padding: 0 18px;\n border-radius: 999px;\n border: 1px solid transparent;\n font-family: \"Roboto\", sans-serif;\n font-weight: 700;\n font-size: 0.95rem;\n cursor: pointer;\n }\n\n .mobile-toc-panel {\n display: none;\n margin-top: 12px;\n padding: 14px;\n border-radius: 20px;\n background: rgba(255, 255, 255, 0.96);\n border: 1px solid var(--line);\n box-shadow: var(--shadow);\n }\n\n .mobile-toc-panel.is-open {\n display: block;\n }\n\n .mobile-toc-cta {\n margin-top: 14px;\n padding-top: 14px;\n border-top: 1px solid rgba(127, 152, 197, 0.16);\n }\n\n .section {\n display: grid;\n gap: 18px;\n padding: 34px 0;\n scroll-margin-top: 24px;\n }\n\n .section-head {\n margin-bottom: 0;\n }\n\n .section-head h2 {\n margin: 12px 0 10px;\n font-size: clamp(1.8rem, 3.2vw, 2.5rem);\n line-height: 1.02;\n letter-spacing: -0.05em;\n }\n\n .section-head p {\n margin: 0;\n max-width: 820px;\n color: var(--muted);\n line-height: 1.62;\n font-size: 0.98rem;\n }\n\n .article-card,\n .quote-card,\n .table-card {\n display: flex;\n flex-direction: column;\n gap: 14px;\n border-radius: 20px;\n padding: 22px;\n }\n\n .prose > * {\n margin: 0;\n }\n\n .prose p,\n .prose li {\n color: var(--muted);\n font-size: 0.98rem;\n line-height: 1.72;\n }\n\n .prose p strong,\n .prose li strong,\n .prose td strong,\n .prose blockquote strong {\n color: var(--ink);\n }\n\n .prose h3 {\n margin: 0;\n font-size: 1.34rem;\n line-height: 1.05;\n letter-spacing: -0.04em;\n color: var(--ink);\n }\n\n .prose ul,\n .prose ol {\n margin: 0;\n padding-left: 20px;\n }\n\n .prose li + li {\n margin-top: 8px;\n }\n\n .quote-card {\n background: linear-gradient(180deg, rgba(227, 242, 255, 0.56) 0%, rgba(255, 255, 255, 0.98) 100%);\n border-color: rgba(76, 157, 232, 0.18);\n }\n\n .quote-card blockquote {\n margin: 0;\n padding-left: 16px;\n border-left: 2px solid rgba(76, 157, 232, 0.3);\n }\n\n .quote-card p {\n margin: 0;\n color: var(--ink);\n font-size: 1rem;\n line-height: 1.72;\n }\n\n .source-inline {\n display: inline;\n white-space: normal;\n }\n\n .source-inline a,\n .source-table a {\n color: var(--blue-deep);\n text-decoration: underline;\n text-underline-offset: 0.12em;\n }\n\n .lead-metrics {\n display: grid;\n grid-template-columns: repeat(3, minmax(0, 1fr));\n gap: 12px;\n margin-top: 0;\n }\n\n .lead-metric {\n padding: 16px;\n border-radius: 16px;\n background: #fff;\n border: 1px solid var(--line);\n }\n\n .lead-metric strong {\n display: block;\n font-size: 1.18rem;\n line-height: 1;\n letter-spacing: -0.04em;\n color: var(--blue-deep);\n }\n\n .lead-metric span {\n display: block;\n margin-top: 8px;\n color: var(--muted);\n font-size: 0.88rem;\n line-height: 1.44;\n }\n\n .subgrid {\n display: grid;\n grid-template-columns: repeat(2, minmax(0, 1fr));\n gap: 14px;\n align-items: stretch;\n }\n\n .subgrid > .article-card,\n .subgrid > .quote-card {\n height: 100%;\n }\n\n .signal-grid,\n .compare-grid,\n .timeline-grid {\n display: grid;\n gap: 14px;\n }\n\n .signal-grid {\n grid-template-columns: repeat(4, minmax(0, 1fr));\n }\n\n .compare-grid,\n .timeline-grid {\n grid-template-columns: repeat(2, minmax(0, 1fr));\n }\n\n .signal-card,\n .compare-card,\n .timeline-card {\n padding: 18px;\n border-radius: 18px;\n border: 1px solid var(--line);\n background: rgba(255, 255, 255, 0.98);\n box-shadow: var(--shadow);\n }\n\n .signal-card span,\n .compare-card span,\n .timeline-card span {\n display: inline-flex;\n align-items: center;\n width: fit-content;\n min-height: 28px;\n padding: 0 10px;\n border-radius: 999px;\n background: rgba(227, 242, 255, 0.92);\n color: var(--blue-deep);\n font-size: 0.74rem;\n font-weight: 700;\n letter-spacing: 0.03em;\n text-transform: uppercase;\n }\n\n .signal-card strong,\n .compare-card h3,\n .timeline-card h3 {\n display: block;\n margin-top: 12px;\n font-size: 1.2rem;\n line-height: 1.06;\n letter-spacing: -0.04em;\n color: var(--ink);\n }\n\n .signal-card p,\n .compare-card p,\n .timeline-card p {\n margin: 10px 0 0;\n color: var(--muted);\n font-size: 0.93rem;\n line-height: 1.62;\n }\n\n .compare-card ul,\n .timeline-card ul {\n margin: 14px 0 0;\n padding-left: 18px;\n color: var(--muted);\n }\n\n .compare-card li + li,\n .timeline-card li + li {\n margin-top: 8px;\n }\n\n .status-pill-row {\n display: flex;\n flex-wrap: wrap;\n gap: 8px;\n margin-top: 12px;\n }\n\n .status-pill {\n display: inline-flex;\n align-items: center;\n min-height: 30px;\n padding: 0 12px;\n border-radius: 999px;\n border: 1px solid rgba(76, 157, 232, 0.16);\n background: #fff;\n color: var(--blue-deep);\n font-size: 0.78rem;\n font-weight: 700;\n }\n\n .scope-note {\n margin-top: 4px;\n color: var(--muted);\n font-size: 0.88rem;\n line-height: 1.58;\n }\n\n .bars {\n display: grid;\n gap: 12px;\n }\n\n .bar-row {\n display: grid;\n gap: 7px;\n }\n\n .bar-row label {\n font-size: 0.84rem;\n font-weight: 700;\n color: var(--ink);\n }\n\n .bar-track {\n position: relative;\n height: 10px;\n border-radius: 999px;\n background: rgba(227, 242, 255, 0.92);\n overflow: hidden;\n }\n\n .bar-fill {\n position: absolute;\n inset: 0 auto 0 0;\n border-radius: inherit;\n background: linear-gradient(135deg, var(--blue) 0%, #79bcff 100%);\n }\n\n .table-card {\n overflow: hidden;\n }\n\n .cta-band {\n display: grid;\n grid-template-columns: minmax(0, 1fr) auto;\n gap: 18px;\n align-items: center;\n padding: 24px 26px;\n border-radius: 24px;\n background: linear-gradient(135deg, rgba(227, 242, 255, 0.6) 0%, rgba(255, 255, 255, 0.98) 100%);\n border: 1px solid rgba(76, 157, 232, 0.18);\n box-shadow: var(--shadow);\n }\n\n .cta-band h3 {\n margin: 0 0 10px;\n font-size: clamp(1.45rem, 2.4vw, 2.05rem);\n line-height: 1;\n letter-spacing: -0.05em;\n }\n\n .cta-band p {\n margin: 0;\n max-width: 760px;\n color: var(--muted);\n line-height: 1.66;\n font-size: 0.96rem;\n }\n\n .cta-actions {\n display: flex;\n flex-wrap: wrap;\n gap: 10px;\n justify-content: flex-end;\n }\n\n .button-primary {\n background: linear-gradient(135deg, var(--orange) 0%, #ffad43 100%);\n color: #fff;\n box-shadow: 0 10px 22px rgba(247, 147, 26, 0.2);\n }\n\n .button-secondary {\n background: #ffffff;\n color: var(--blue-deep);\n border-color: rgba(76, 157, 232, 0.18);\n box-shadow: 0 10px 22px rgba(1, 38, 138, 0.06);\n }\n\n .sidebar-cta {\n padding: 16px;\n border-radius: 22px;\n border: 1px solid rgba(76, 157, 232, 0.16);\n background: linear-gradient(180deg, rgba(227, 242, 255, 0.52) 0%, rgba(255, 255, 255, 0.98) 100%);\n box-shadow: var(--shadow);\n }\n\n .sidebar-cta h3 {\n margin: 0 0 8px;\n font-size: 1.08rem;\n line-height: 1.04;\n letter-spacing: -0.04em;\n }\n\n .sidebar-cta p {\n margin: 0 0 12px;\n color: var(--muted);\n font-size: 0.86rem;\n line-height: 1.48;\n }\n\n .sidebar-cta .button {\n width: 100%;\n min-height: 44px;\n }\n\n .table-scroll {\n overflow-x: auto;\n margin-top: 0;\n padding-bottom: 6px;\n }\n\n table {\n width: 100%;\n min-width: 720px;\n border-collapse: collapse;\n }\n\n th,\n td {\n text-align: left;\n vertical-align: top;\n padding: 14px 12px;\n border-bottom: 1px solid rgba(127, 152, 197, 0.18);\n }\n\n th {\n font-size: 0.82rem;\n letter-spacing: 0.04em;\n text-transform: uppercase;\n color: var(--blue-deep);\n background: rgba(248, 248, 248, 1);\n }\n\n td {\n color: var(--muted);\n line-height: 1.62;\n font-size: 0.95rem;\n }\n\n .reviewer-card {\n display: grid;\n grid-template-columns: 88px minmax(0, 1fr);\n gap: 18px;\n align-items: start;\n border-radius: 22px;\n padding: 22px;\n background: rgba(255, 255, 255, 0.98);\n border: 1px solid var(--line);\n box-shadow: var(--shadow);\n }\n\n .reviewer-avatar {\n width: 88px;\n height: 88px;\n border-radius: 24px;\n background: linear-gradient(135deg, rgba(227, 242, 255, 0.92) 0%, rgba(248, 248, 248, 1) 100%);\n border: 1px solid var(--line);\n overflow: hidden;\n box-shadow: 0 10px 22px rgba(1, 38, 138, 0.08);\n }\n\n .reviewer-avatar img {\n width: 100%;\n height: 100%;\n object-fit: cover;\n }\n\n .reviewer-card h3 {\n margin: 0;\n font-size: 1.32rem;\n line-height: 1.04;\n letter-spacing: -0.04em;\n }\n\n .reviewer-role {\n display: inline-flex;\n align-items: center;\n width: fit-content;\n min-height: 30px;\n margin-top: 10px;\n padding: 0 11px;\n border-radius: 999px;\n background: rgba(227, 242, 255, 0.92);\n color: var(--blue-deep);\n font-size: 0.76rem;\n font-weight: 700;\n letter-spacing: 0.03em;\n text-transform: uppercase;\n }\n\n .reviewer-card p {\n margin: 12px 0 0;\n color: var(--muted);\n line-height: 1.68;\n font-size: 0.95rem;\n max-width: 760px;\n }\n\n .faq-list {\n display: grid;\n gap: 14px;\n }\n\n .faq-card {\n border-radius: 22px;\n overflow: hidden;\n background: rgba(255, 255, 255, 0.96);\n }\n\n .faq-card[open] {\n background: linear-gradient(180deg, rgba(227, 242, 255, 0.42) 0%, rgba(255, 255, 255, 0.98) 100%);\n border-color: rgba(76, 157, 232, 0.18);\n }\n\n .faq-card summary {\n list-style: none;\n cursor: pointer;\n display: flex;\n align-items: center;\n justify-content: space-between;\n gap: 18px;\n padding: 20px 24px;\n font-size: 1.04rem;\n font-weight: 700;\n line-height: 1.4;\n }\n\n .faq-card summary::after {\n content: \"\";\n width: 10px;\n height: 10px;\n border-right: 2px solid var(--blue-deep);\n border-bottom: 2px solid var(--blue-deep);\n transform: rotate(45deg);\n transition: transform 0.2s ease;\n flex-shrink: 0;\n margin-top: -4px;\n }\n\n .faq-card[open] summary::after {\n transform: rotate(225deg);\n margin-top: 2px;\n }\n\n .faq-card summary::-webkit-details-marker {\n display: none;\n }\n\n .faq-card p {\n margin: 0;\n padding: 0 24px 22px;\n color: var(--muted);\n line-height: 1.72;\n font-size: 0.96rem;\n }\n\n .source-table td:first-child {\n color: var(--ink);\n font-weight: 700;\n }\n\n @media (max-width: 1100px) {\n .hero-grid,\n .layout,\n .subgrid,\n .cta-band,\n .signal-grid,\n .compare-grid,\n .timeline-grid {\n grid-template-columns: 1fr;\n }\n\n .lead-metrics,\n .metrics-grid {\n grid-template-columns: repeat(2, minmax(0, 1fr));\n }\n\n .cta-actions {\n justify-content: flex-start;\n }\n\n .toc {\n display: none;\n }\n\n .rail {\n display: none;\n }\n\n .mobile-toc-wrap {\n display: block;\n }\n }\n\n @media (max-width: 860px) {\n .lead-metrics,\n .metrics-grid {\n grid-template-columns: 1fr;\n }\n\n .reviewer-card {\n grid-template-columns: 1fr;\n }\n\n .reviewer-avatar {\n width: 72px;\n height: 72px;\n border-radius: 20px;\n }\n }\n\n @media (max-width: 640px) {\n :root {\n --content-width: min(100vw - 24px, 100vw - 24px);\n }\n\n .hero {\n padding: 22px 18px 24px;\n }\n\n .article-card,\n .quote-card,\n .table-card,\n .faq-card summary {\n padding-left: 18px;\n padding-right: 18px;\n }\n\n .faq-card p {\n padding-left: 18px;\n padding-right: 18px;\n }\n\n th,\n td {\n padding: 12px 10px;\n }\n }\n <\/style>\n<\/head>\n<body>\n <div class=\"page-shell\">\n <main class=\"container\">\n <section class=\"hero\">\n <div class=\"mobile-toc-wrap\">\n <button class=\"button mobile-toc-button\" id=\"mobileTocButton\" type=\"button\" aria-expanded=\"false\" aria-controls=\"mobileTocPanel\">\n <span>On this page<\/span>\n <span>\u2630<\/span>\n <\/button>\n <div class=\"mobile-toc-panel\" id=\"mobileTocPanel\">\n <a class=\"toc-link\" href=\"#overview\">Why Glamsterdam matters<\/a>\n <a class=\"toc-link\" href=\"#epbs\">What ePBS changes<\/a>\n <a class=\"toc-link\" href=\"#bals\">What BALs change<\/a>\n <a class=\"toc-link\" href=\"#scope\">Current EIP scope<\/a>\n <a class=\"toc-link\" href=\"#fees\">Gas fees and capacity<\/a>\n <a class=\"toc-link\" href=\"#users\">What users should do<\/a>\n <a class=\"toc-link\" href=\"#timeline\">Timeline to watch<\/a>\n <a class=\"toc-link\" href=\"#risks\">Risks and open questions<\/a>\n <a class=\"toc-link\" href=\"#takeaway\">Key takeaway<\/a>\n <a class=\"toc-link\" href=\"#faq\">FAQ<\/a>\n <a class=\"toc-link\" href=\"#reviewed-by\">Reviewed by<\/a>\n <a class=\"toc-link\" href=\"#sources\">Sources<\/a>\n <div class=\"mobile-toc-cta\">\n <div class=\"sidebar-cta\">\n <h3>Buy ETH<\/h3>\n <p>Open the Guardarian flow directly.<\/p>\n <a class=\"button button-primary\" href=\"https:\/\/guardarian.com\/buy-eth\">Buy ETH<\/a>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n <div class=\"hero-grid\">\n <div class=\"hero-copy\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Research article<\/div>\n <div class=\"hero-copy-main\">\n <h1>Ethereum\u2019s Glamsterdam Upgrade<\/h1>\n <p>\n Ethereum\u2019s next major planned upgrade is focused on Layer 1 scaling, cleaner block production,\n parallelization foundations, and the infrastructure needed to raise capacity without giving up decentralization.\n <\/p>\n <\/div>\n <\/div>\n\n <div class=\"hero-side\">\n <div class=\"metrics-grid\">\n <article class=\"metric-card\">\n <span>Main focus<\/span>\n <strong>L1 scaling<\/strong>\n <p>Ethereum.org frames Glamsterdam around capacity expansion, parallelization and long-term network sustainability.<\/p>\n <\/article>\n <article class=\"metric-card\">\n <span>Headline features<\/span>\n <strong>ePBS + BALs<\/strong>\n <p>EIP-7732 changes block production while EIP-7928 adds block-level access lists for parallel work and faster validation paths.<\/p>\n <\/article>\n <article class=\"metric-card\">\n <span>Scope status<\/span>\n <strong>Draft meta EIP<\/strong>\n <p>EIP-7773 is still in draft, which means the current proposal set is real but the scope is not immutable yet.<\/p>\n <\/article>\n <article class=\"metric-card\">\n <span>Latest public signal<\/span>\n <strong>June 8, 2026<\/strong>\n <p>ACDT #82 focused on glamsterdam-devnet-5 and named glamsterdam-devnet-6 scope finalization as the next step.<\/p>\n <\/article>\n <\/div>\n <\/div>\n <\/div>\n <\/section>\n\n <div class=\"layout\">\n <div class=\"content\">\n <section class=\"section\" id=\"overview\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Overview<\/div>\n <h2>Ethereum\u2019s Next Big Upgrade Is About Scaling Layer 1<\/h2>\n <p>Glamsterdam is not a new chain or a user-facing app release. It is a protocol-level upgrade that goes deeper into Ethereum\u2019s base layer and the mechanics of block production.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>Ethereum\u2019s next major planned upgrade, <strong>Glamsterdam<\/strong>, is shaping up to be one of the most important protocol changes on the 2026 roadmap. While recent upgrades were easier to explain through blobs, rollups, or immediate user cost changes, Glamsterdam is more infrastructural. It changes how Ethereum prepares, builds, and validates blocks.<\/p>\n <p>The official <strong>ethereum.org<\/strong> roadmap page frames Glamsterdam around <strong>Layer 1 scaling<\/strong>, <strong>parallelization<\/strong>, <strong>capacity expansion<\/strong>, and <strong>sustainability<\/strong>. That is the cleanest summary of why it matters: Ethereum wants to handle more activity on the base layer without turning node operation into an arms race. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>]<\/span><\/p>\n <p>One quick decoding note before we go deeper: <strong>EIP<\/strong> means <strong>Ethereum Improvement Proposal<\/strong>. It is just Ethereum\u2019s name for a formal upgrade proposal. So when you see a number like <strong>EIP-7981<\/strong>, that does not mean users are expected to memorize it. It just means \u201cone specific change being considered inside the broader upgrade.\u201d<\/p>\n <p>At the same time, the current scope is still evolving. The meta EIP for the upgrade, <strong>EIP-7773<\/strong>, is in <strong>Draft<\/strong> status as of <strong>June 17, 2026<\/strong>. That means Glamsterdam is very real, but anyone speaking about it as if every feature and every activation detail is already final is getting ahead of the process. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <\/article>\n\n <div class=\"signal-grid\">\n <article class=\"signal-card\">\n <span>Roadmap focus<\/span>\n <strong>Capacity on L1<\/strong>\n <p>Ethereum.org positions Glamsterdam as a scaling and sustainability upgrade rather than a narrow UX patch.<\/p>\n <\/article>\n <article class=\"signal-card\">\n <span>Critical pair<\/span>\n <strong>ePBS + BALs<\/strong>\n <p>Those two proposals are doing much of the conceptual heavy lifting for block production and parallel work.<\/p>\n <\/article>\n <article class=\"signal-card\">\n <span>Current state<\/span>\n <strong>Still moving<\/strong>\n <p>The official scope is being tracked publicly, but both the meta EIP and several key proposals remain draft-stage items.<\/p>\n <\/article>\n <article class=\"signal-card\">\n <span>Mainnet date<\/span>\n <strong>Not announced<\/strong>\n <p>No public activation date is listed yet, so testing progress matters more than roadmap hype right now.<\/p>\n <\/article>\n <\/div>\n\n <div class=\"compare-grid\">\n <article class=\"compare-card\">\n <span>Quick glossary<\/span>\n <h3>Terms you actually need<\/h3>\n <ul>\n <li><strong>EIP:<\/strong> a formal Ethereum upgrade proposal.<\/li>\n <li><strong>ePBS:<\/strong> a new way to split who builds a block and who proposes it.<\/li>\n <li><strong>BALs:<\/strong> a map of what a block will touch in Ethereum\u2019s state.<\/li>\n <li><strong>Devnet:<\/strong> an early test network used by client teams before public testnets.<\/li>\n <\/ul>\n <\/article>\n <article class=\"compare-card\">\n <span>What not to worry about<\/span>\n <h3>You do not need every number<\/h3>\n <p>Most readers do not need to know what <strong>EIP-7981<\/strong> means line by line. The useful question is what category it belongs to. In this article, the important split is simple:<\/p>\n <ul>\n <li>a few proposals are foundational and user-relevant, like ePBS and BALs;<\/li>\n <li>many others are lower-level pricing, opcode, and execution cleanups that mostly matter to client teams and infrastructure.<\/li>\n <\/ul>\n <\/article>\n <\/div>\n <\/section>\n\n <section class=\"section\" id=\"epbs\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> ePBS<\/div>\n <h2>What ePBS Actually Changes<\/h2>\n <p>The most important Glamsterdam proposal is not a cosmetic tweak. It changes the shape of block validation itself.<\/p>\n <\/div>\n\n <div class=\"subgrid\">\n <article class=\"article-card prose\">\n <h3>From off-protocol habits to in-protocol rules<\/h3>\n <p><strong>EIP-7732<\/strong>, Enshrined Proposer-Builder Separation, separates the consensus side of the block from the execution side and introduces <strong>in-protocol builders<\/strong>. It also adds a <strong>Payload Timeliness Committee<\/strong>, a validator subset that attests whether the committed payload was revealed correctly and on time. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>]<\/span><\/p>\n <p>Today, Ethereum\u2019s proposer-builder separation largely exists through extra-protocol systems such as MEV-Boost. ePBS moves more of that flow into Ethereum itself. That makes block production less dependent on outside coordination and more explicitly defined by protocol rules.<\/p>\n <\/article>\n\n <article class=\"quote-card prose\">\n <h3>Why client teams treat it as the hard part<\/h3>\n <blockquote>\n <p>\n Checkpoint #9 says ePBS is proving trickier than anticipated because the protocol now has to handle two-party coordination and disagreement inside consensus rather than outside of it.\n <\/p>\n <\/blockquote>\n <p>That source-backed caution matters. Glamsterdam is not slow because teams forgot to ship it. It is slow because ePBS touches practically every layer of the block production path. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9, Apr 10 2026<\/a>]<\/span><\/p>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>The official roadmap page adds a useful operational angle: ePBS is intended to expand the tight propagation and validation window from roughly <strong>2 seconds<\/strong> to about <strong>9 seconds<\/strong>. That gives Ethereum more room to safely handle larger and more complex blocks if the rest of the stack can keep up. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>]<\/span><\/p>\n <p>The payoff, if it works, is straightforward: more efficient block production, better room for higher throughput, and less reliance on external builder infrastructure. The cost is complexity. And Ethereum is being unusually explicit that this complexity is real.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"bals\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> BALs<\/div>\n <h2>What Block-Level Access Lists Change<\/h2>\n <p>If ePBS is about cleaner block production, BALs are about making more of the execution path predictable and parallelizable.<\/p>\n <\/div>\n\n <div class=\"subgrid\">\n <article class=\"article-card prose\">\n <h3>What the spec says<\/h3>\n <p><strong>EIP-7928<\/strong> introduces <strong>Block-Level Access Lists<\/strong>, or BALs. The EIP says these lists record all accounts and storage locations accessed during block execution, along with their post-execution values. The stated goal is to enable <strong>parallel disk reads<\/strong>, <strong>parallel transaction validation<\/strong>, <strong>parallel state root computation<\/strong>, and even <strong>executionless state updates<\/strong>. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928<\/a>]<\/span><\/p>\n <p>In plain language, BALs give clients a much clearer map of what a block touches. That matters because Ethereum cannot safely parallelize more work if it has to discover every dependency too late in the process.<\/p>\n <\/article>\n\n <article class=\"quote-card prose\">\n <h3>Why this matters for scaling<\/h3>\n <blockquote>\n <p>\n BALs are not a cosmetic optimization. They are a preparation layer for a future where Ethereum can use modern hardware more intelligently instead of forcing every step through a strictly sequential bottleneck.\n <\/p>\n <\/blockquote>\n <p>The motivation section of the EIP makes this explicit: without knowing accessed addresses and storage slots ahead of time, clients cannot parallelize much of the work safely. BALs are the dependency map that makes more advanced execution strategies practical. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928<\/a>]<\/span><\/p>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <div class=\"bars\">\n <div class=\"bar-row\">\n <label>Parallel disk reads<\/label>\n <div class=\"bar-track\"><div class=\"bar-fill\" style=\"width: 82%;\"><\/div><\/div>\n <\/div>\n <div class=\"bar-row\">\n <label>Parallel transaction validation<\/label>\n <div class=\"bar-track\"><div class=\"bar-fill\" style=\"width: 88%;\"><\/div><\/div>\n <\/div>\n <div class=\"bar-row\">\n <label>Executionless state updates<\/label>\n <div class=\"bar-track\"><div class=\"bar-fill\" style=\"width: 74%;\"><\/div><\/div>\n <\/div>\n <\/div>\n <p class=\"scope-note\">These bars are illustrative, not measured performance numbers. They simply show the three workstreams BALs are meant to unlock based on the EIP\u2019s stated design goals.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"scope\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Scope snapshot<\/div>\n <h2>What Is Actually in the Current Glamsterdam Scope<\/h2>\n <p>The best source for \u201cwhat is in Glamsterdam right now\u201d is not social media or generic explainers. It is EIP-7773.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>As of <strong>June 17, 2026<\/strong>, EIP-7773 lists <strong>ten<\/strong> proposals as <strong>Scheduled for Inclusion<\/strong>: <strong>EIP-7708<\/strong>, <strong>EIP-7732<\/strong>, <strong>EIP-7778<\/strong>, <strong>EIP-7843<\/strong>, <strong>EIP-7928<\/strong>, <strong>EIP-7954<\/strong>, <strong>EIP-7976<\/strong>, <strong>EIP-7981<\/strong>, <strong>EIP-8024<\/strong>, and <strong>EIP-8037<\/strong>. That is already a useful fact-check, because some older summaries omit <strong>EIP-7708<\/strong> from the scheduled set. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <p>But that raw list is not the best way to understand the upgrade. In practice, you can group the current scheduled items into three buckets: <strong>big architecture changes<\/strong> like ePBS and BALs, <strong>developer or EVM quality-of-life changes<\/strong> like new opcodes and contract-size adjustments, and <strong>gas repricing items<\/strong> that change how certain actions are charged. That framing is much more useful than memorizing proposal numbers.<\/p>\n <\/article>\n\n <div class=\"compare-grid\">\n <article class=\"compare-card\">\n <span>Scheduled now<\/span>\n <h3>What the scheduled items really are<\/h3>\n <ul>\n <li><strong>Block-production overhaul:<\/strong> ePBS changes who builds the block and how the payload arrives.<\/li>\n <li><strong>Parallelization groundwork:<\/strong> BALs tell clients what state a block touches.<\/li>\n <li><strong>Gas repricing:<\/strong> proposals like EIP-7778, EIP-7976, EIP-7981, and EIP-8037 rebalance how certain operations are charged.<\/li>\n <li><strong>Developer-facing changes:<\/strong> EIP-7954 raises maximum contract size, EIP-7843 adds a <code>SLOTNUM<\/code> opcode, and EIP-8024 improves EVM instruction compatibility.<\/li>\n <li><strong>Small protocol cleanup:<\/strong> EIP-7708 makes ETH transfers emit a log, which is mainly a tooling and observability improvement.<\/li>\n <\/ul>\n <\/article>\n <article class=\"compare-card\">\n <span>Considered now<\/span>\n <h3>Why \u201cconsidered\u201d matters<\/h3>\n <ul>\n <li><strong>EIP-2780<\/strong> is the one often cited in \u201cfees may go down\u201d discussions, but it is still only considered, not scheduled.<\/li>\n <li>Other considered items are still real proposals, but they have not yet crossed the threshold where Ethereum is treating them as likely ship targets.<\/li>\n <li>That is why article summaries should separate \u201cvery likely\u201d from \u201cmaybe,\u201d even when both sound exciting.<\/li>\n <li>For readers, the practical meaning is simple: the upgrade direction is clear, but some details are still under active engineering judgment.<\/li>\n <\/ul>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>This distinction matters. It means some of the most exciting narratives around Glamsterdam are directionally fair but too confident in their details. The cleaner way to say it is that the upgrade has a very visible center of gravity, but the outer rings of scope are still being refined in public.<\/p>\n <p>And to your earlier example: <strong>EIP-7981<\/strong> is not a \u201cheadline feature\u201d a normal user needs to study. It is one of the gas repricing changes inside the broader package. That is exactly why grouping these items by purpose is more useful than listing naked proposal numbers.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"fees\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Fees and capacity<\/div>\n <h2>How Glamsterdam Could Affect Gas Fees<\/h2>\n <p>The honest answer is more interesting than \u201cfees up\u201d or \u201cfees down.\u201d Glamsterdam is a scaling foundation first.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>Ethereum.org explicitly says Glamsterdam will likely help lower fees for everyday users over time, partly because the roadmap pairs ePBS and BALs with future capacity growth and partly because it discusses intrinsic gas reduction through <strong>EIP-2780<\/strong>. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>]<\/span><\/p>\n <p>But here is the important scope check: <strong>EIP-2780 is currently Considered for Inclusion, not Scheduled for Inclusion, in EIP-7773<\/strong>. So the safest interpretation is not \u201cGlamsterdam definitely flips a cheaper-fee switch on day one.\u201d The safer reading is that Glamsterdam is supposed to make future capacity increases more realistic, and that can help fee pressure if the scoped proposals actually make it through testing and activation. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <p>Checkpoint #9 reinforces this cautious framing. It says implementation is well underway but also notes that both ePBS and gas repricing work are more complex than they first looked. That is exactly the kind of sentence users should want to hear from protocol engineers. It means they are not pretending a deep upgrade is easy just because the market wants a clean headline. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>]<\/span><\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"users\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> User impact<\/div>\n <h2>What Users and Infrastructure Teams Should Actually Do<\/h2>\n <p>For regular ETH holders, the most important action is usually not to take action at all.<\/p>\n <\/div>\n\n <div class=\"subgrid\">\n <article class=\"article-card prose\">\n <h3>For regular users<\/h3>\n <p>Glamsterdam does not require people to \u201cupgrade ETH,\u201d claim replacement tokens, or connect wallets to random sites. Any page asking you to manually migrate your ETH because of Glamsterdam should be treated as suspicious.<\/p>\n <p>That is the clean user takeaway: if you simply hold ETH in a normal wallet or on a platform that manages its own backend upgrades, you typically do nothing.<\/p>\n <\/article>\n\n <article class=\"article-card prose\">\n <h3>For node operators and platforms<\/h3>\n <p>The heavier lift belongs to client teams, exchanges, node operators, RPC providers, validators, explorers, and indexing infrastructure. Those teams need to track client releases, devnet results, data pipeline compatibility, and execution or consensus changes that alter the structure of blocks.<\/p>\n <p>That is where Glamsterdam becomes operationally real: not in retail wallet UI, but in the backend stack that keeps Ethereum readable and reliable.<\/p>\n <\/article>\n <\/div>\n\n <\/section>\n\n <section class=\"section\" id=\"timeline\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Timeline<\/div>\n <h2>What to Watch Next in 2026<\/h2>\n <p>The main signal is not hype. It is whether client teams keep converting the current scope into stable multi-client releases.<\/p>\n <\/div>\n\n <div class=\"timeline-grid\">\n <article class=\"timeline-card\">\n <span>April 10, 2026<\/span>\n <h3>Checkpoint: \u201cwell underway\u201d<\/h3>\n <p>Ethereum Foundation\u2019s Checkpoint #9 says Glamsterdam implementation is well underway, but ePBS is the major sticking point and gas repricing work also has its own complexities.<\/p>\n <\/article>\n <article class=\"timeline-card\">\n <span>June 8, 2026<\/span>\n <h3>ACDT #82 confirms devnet focus<\/h3>\n <p>The public testing call centers on <code>glamsterdam-devnet-5<\/code> and names the scope finalization for <code>glamsterdam-devnet-6<\/code> as the next step.<\/p>\n <\/article>\n <article class=\"timeline-card\">\n <span>Next phase<\/span>\n <h3>Client inclusion and scope freeze<\/h3>\n <ul>\n <li>Get all CL clients included in glamsterdam-devnet-5<\/li>\n <li>Finalize both-layer scope for glamsterdam-devnet-6<\/li>\n <li>Keep stabilizing the combined feature set<\/li>\n <\/ul>\n <\/article>\n <article class=\"timeline-card\">\n <span>Later phase<\/span>\n <h3>Testnets, releases, mainnet date<\/h3>\n <ul>\n <li>Public testnets come after a stable all-feature devnet<\/li>\n <li>Client releases and security review follow<\/li>\n <li>Mainnet date still depends on progress, not on marketing calendars<\/li>\n <\/ul>\n <\/article>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>The most useful timeline takeaway from the primary sources is simple: there is no fixed public mainnet date yet, and the process still depends on stabilizing multi-client devnets. That makes Glamsterdam very important, but not yet date-certain. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>, <a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">ACDT #82<\/a>]<\/span><\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"risks\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Risks<\/div>\n <h2>Risks and Open Questions<\/h2>\n <p>Ambitious protocol upgrades always create a list of hard questions. Glamsterdam is honest enough to put them on the table in public.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <ul>\n <li><strong>ePBS liveness risk:<\/strong> EIP-7732 explicitly discusses the free option problem and the possibility that builders may withhold a payload if incentives change. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>]<\/span><\/li>\n <li><strong>Client coordination:<\/strong> Checkpoint #9 says every part of the stack has to reason about partial blocks and two-party coordination, which is why ePBS is harder than expected. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>]<\/span><\/li>\n <li><strong>Scope discipline:<\/strong> fee-relevant and networking proposals are still split between Scheduled and Considered, so scope management remains part of the engineering risk. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/li>\n <li><strong>Infrastructure adaptation:<\/strong> even if frontend apps do not change much, RPC providers, node operators, validators, explorers, and indexers still have real migration work.<\/li>\n <\/ul>\n <p>None of that means Glamsterdam is in trouble. It means Ethereum is treating a foundational upgrade like a foundational upgrade. That is exactly what careful protocol work is supposed to look like.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"takeaway\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Takeaway<\/div>\n <h2>Key Takeaway<\/h2>\n <p>The cleanest summary is that Glamsterdam is Ethereum\u2019s current attempt to scale Layer 1 by changing the machinery underneath block production and execution.<\/p>\n <\/div>\n\n <article class=\"article-card prose\">\n <p>Glamsterdam matters because it targets Ethereum\u2019s base-layer constraints directly. ePBS changes how blocks are proposed and validated. BALs change how the network can prepare and parallelize execution-related work. The surrounding scope includes gas repricing and capacity-related items that are meant to make higher throughput safer over time.<\/p>\n <ul>\n <li>It is one of Ethereum\u2019s most important planned 2026 upgrades.<\/li>\n <li>Its center of gravity is clearly L1 scaling, ePBS, and BALs.<\/li>\n <li>Its exact final scope is still public and still moving.<\/li>\n <li>Its timing depends on successful devnets, testnets, and client readiness rather than a fixed launch promise.<\/li>\n <\/ul>\n <p>If you want the shortest honest version, it is this: <strong>Glamsterdam is a serious scaling upgrade, not a simple fee patch<\/strong>. And that is exactly why it deserves close attention in 2026.<\/p>\n <\/article>\n <\/section>\n\n <section class=\"section\" id=\"faq\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> FAQ<\/div>\n <h2>FAQ<\/h2>\n <p>Short answers to the questions readers usually have once the acronym layer gets too thick.<\/p>\n <\/div>\n\n <div class=\"faq-list\">\n <details class=\"faq-card\" open>\n <summary>Is Glamsterdam already live on Ethereum mainnet?<\/summary>\n <p>No. As of June 17, 2026, Glamsterdam is still in the development and testing phase. EIP-7773 remains in Draft status, and the public process is still focused on devnets, scope confirmation, and multi-client readiness. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>, <a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">ACDT #82<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>What is an EIP in simple terms?<\/summary>\n <p>An EIP is an Ethereum Improvement Proposal. Think of it as a formal spec for one protocol change. Big upgrades like Glamsterdam are usually bundles of several EIPs rather than one single change.<\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>What are the two most important Glamsterdam proposals right now?<\/summary>\n <p>The headline pair is EIP-7732, Enshrined Proposer-Builder Separation, and EIP-7928, Block-Level Access Lists. One changes how blocks are built and validated; the other prepares Ethereum for more parallel work during execution-related processing. <span class=\"source-inline\">[<a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>, <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Do I need to understand things like EIP-7981?<\/summary>\n <p>Usually no. For most readers, it is enough to know whether a proposal is a headline architecture change, a gas repricing change, or a lower-level developer\/infrastructure tweak. EIP-7981 falls into the repricing bucket, not the \u201cmust understand before using ETH\u201d bucket.<\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Will Glamsterdam automatically make ETH transactions cheap?<\/summary>\n <p>Not automatically and not instantly. The official roadmap frames Glamsterdam as helpful for lower fees over time, but some fee-relevant proposals are still only Considered for Inclusion, not Scheduled. The safer interpretation is that Glamsterdam is a scaling foundation, not a magic fee switch. <span class=\"source-inline\">[<a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org roadmap<\/a>, <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Why is ePBS considered hard to ship?<\/summary>\n <p>Because it changes the hot path of block production and moves more proposer-builder coordination inside the protocol. Checkpoint #9 explicitly says this is a major sticking point, and EIP-7732 itself discusses liveness and withholding risks. <span class=\"source-inline\">[<a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Checkpoint #9<\/a>, <a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>What did ACDT #82 actually tell us?<\/summary>\n <p>It showed that Glamsterdam had already moved into public devnet discussion around <code>glamsterdam-devnet-5<\/code>, and that the next steps included bringing in all CL clients and finalizing both-layer scope for <code>glamsterdam-devnet-6<\/code>. <span class=\"source-inline\">[<a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">ACDT #82<\/a>]<\/span><\/p>\n <\/details>\n <details class=\"faq-card\">\n <summary>Do normal ETH holders need to do anything before Glamsterdam?<\/summary>\n <p>Usually no. Protocol upgrades matter much more for node operators, validators, exchanges, RPC providers, and other infrastructure teams. Users should mainly avoid scams that claim ETH needs a manual \u201cupgrade.\u201d<\/p>\n <\/details>\n <\/div>\n <\/section>\n\n <section class=\"section\" id=\"reviewed-by\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Reviewed by<\/div>\n <h2>Who reviewed this article<\/h2>\n <p>A short reviewer note for editorial context.<\/p>\n <\/div>\n\n <div class=\"reviewer-card\">\n <div class=\"reviewer-avatar\">\n <img decoding=\"async\" src=\"https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/image.png\" alt=\"Agatha Willings\">\n <\/div>\n <div>\n <h3>Agatha Willings<\/h3>\n <div class=\"reviewer-role\">Crypto researcher<\/div>\n <p>\n Agatha Willings reviews long-form crypto market and protocol content with a focus on source-backed\n claims, roadmap precision, and the difference between what Ethereum plans to ship, what is already\n live, and what still depends on successful testing.\n <\/p>\n <\/div>\n <\/div>\n <\/section>\n\n <section class=\"section\" id=\"sources\" data-section>\n <div class=\"section-head\">\n <div class=\"eyebrow\"><span class=\"eyebrow-dot\"><\/span> Sources<\/div>\n <h2>Verified Sources<\/h2>\n <p>The article below is based primarily on official Ethereum sources, EIP specifications, and public testing-call materials. External links are marked <code>nofollow<\/code>.<\/p>\n <\/div>\n\n <div class=\"table-card prose\">\n <div class=\"table-scroll\">\n <table class=\"source-table\">\n <thead>\n <tr>\n <th>Source<\/th>\n <th>Date<\/th>\n <th>Key point used in article<\/th>\n <\/tr>\n <\/thead>\n <tbody>\n <tr>\n <td><a href=\"https:\/\/ethereum.org\/roadmap\/glamsterdam\/\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum.org \u2014 Glamsterdam roadmap page<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Official framing for Glamsterdam\u2019s goals: L1 scaling, parallelization, capacity growth, sustainability, and the user-facing explanation of why the upgrade matters.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7773\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7773 \u2014 Hardfork Meta: Glamsterdam<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Primary source for the current Scheduled, Considered, and Proposed scope of the Glamsterdam upgrade.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7732\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7732 \u2014 Enshrined Proposer-Builder Separation<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Defines the protocol-level ePBS design, builder role, delayed execution validation, and Payload Timeliness Committee.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/eips.ethereum.org\/EIPS\/eip-7928\" rel=\"nofollow noopener\" target=\"_blank\">EIP-7928 \u2014 Block-Level Access Lists<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Defines BALs and explicitly states their role in parallel disk reads, validation, state root computation, and executionless state updates.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/blog.ethereum.org\/2026\/04\/10\/checkpoint-9\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum Foundation Blog \u2014 Checkpoint #9<\/a><\/td>\n <td>Apr 10, 2026<\/td>\n <td>Confirms that Glamsterdam implementation is well underway while also noting ePBS and gas repricing complexity.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/github.com\/ethereum\/pm\/issues\/2103\" rel=\"nofollow noopener\" target=\"_blank\">Ethereum PM \u2014 All Core Devs Testing #82<\/a><\/td>\n <td>Jun 8, 2026<\/td>\n <td>Public call agenda and next steps showing glamsterdam-devnet-5 status and the scope finalization target for glamsterdam-devnet-6.<\/td>\n <\/tr>\n <tr>\n <td><a href=\"https:\/\/github.com\/ethereum\/execution-specs\/issues\/2915\" rel=\"nofollow noopener\" target=\"_blank\">Execution Specs \u2014 glamsterdam-devnet-6 tracker<\/a><\/td>\n <td>Accessed Jun 17, 2026<\/td>\n <td>Concrete public tracker reference linked from ACDT #82 for the next execution-layer devnet release work.<\/td>\n <\/tr>\n <\/tbody>\n <\/table>\n <\/div>\n <\/div>\n <\/section>\n <\/div>\n\n <aside class=\"rail\">\n <div class=\"toc\">\n <h2>On this page<\/h2>\n <nav class=\"toc-links\">\n <a class=\"toc-link\" href=\"#overview\">Why Glamsterdam matters<\/a>\n <a class=\"toc-link\" href=\"#epbs\">What ePBS changes<\/a>\n <a class=\"toc-link\" href=\"#bals\">What BALs change<\/a>\n <a class=\"toc-link\" href=\"#scope\">Current EIP scope<\/a>\n <a class=\"toc-link\" href=\"#fees\">Gas fees and capacity<\/a>\n <a class=\"toc-link\" href=\"#users\">What users should do<\/a>\n <a class=\"toc-link\" href=\"#timeline\">Timeline to watch<\/a>\n <a class=\"toc-link\" href=\"#risks\">Risks and open questions<\/a>\n <a class=\"toc-link\" href=\"#takeaway\">Key takeaway<\/a>\n <a class=\"toc-link\" href=\"#faq\">FAQ<\/a>\n <a class=\"toc-link\" href=\"#reviewed-by\">Reviewed by<\/a>\n <a class=\"toc-link\" href=\"#sources\">Sources<\/a>\n <\/nav>\n <\/div>\n\n <div class=\"sidebar-cta\">\n <h3>Buy ETH<\/h3>\n <p>Open the Guardarian flow directly.<\/p>\n <a class=\"button button-primary\" href=\"https:\/\/guardarian.com\/buy-eth\">Buy ETH<\/a>\n <\/div>\n <\/aside>\n <\/div>\n <\/main>\n <\/div>\n\n <script>\n (function () {\n const mobileButton = document.getElementById('mobileTocButton');\n const mobilePanel = document.getElementById('mobileTocPanel');\n const tocLinks = Array.from(document.querySelectorAll('.toc-link'));\n const sections = Array.from(document.querySelectorAll('[data-section]'));\n const externalLinks = Array.from(document.querySelectorAll('a[href^=\"http\"]'));\n\n externalLinks.forEach(function (link) {\n try {\n const url = new URL(link.href);\n const isGuardarian = url.hostname === 'guardarian.com' || url.hostname === 'www.guardarian.com';\n if (isGuardarian) {\n link.setAttribute('rel', 'noopener noreferrer');\n link.setAttribute('target', '_blank');\n return;\n }\n } catch (error) {\n return;\n }\n\n link.setAttribute('rel', 'nofollow noopener noreferrer');\n link.setAttribute('target', '_blank');\n });\n\n if (mobileButton && mobilePanel) {\n mobileButton.addEventListener('click', function () {\n const isOpen = mobilePanel.classList.toggle('is-open');\n mobileButton.setAttribute('aria-expanded', String(isOpen));\n });\n }\n\n tocLinks.forEach(function (link) {\n link.addEventListener('click', function () {\n if (mobilePanel) {\n mobilePanel.classList.remove('is-open');\n }\n if (mobileButton) {\n mobileButton.setAttribute('aria-expanded', 'false');\n }\n });\n });\n\n if ('IntersectionObserver' in window) {\n const observer = new IntersectionObserver(function (entries) {\n entries.forEach(function (entry) {\n if (!entry.isIntersecting) {\n return;\n }\n\n const id = entry.target.getAttribute('id');\n tocLinks.forEach(function (link) {\n const isActive = link.getAttribute('href') === '#' + id;\n link.classList.toggle('is-active', isActive);\n });\n });\n }, {\n rootMargin: '-30% 0px -55% 0px',\n threshold: 0\n });\n\n sections.forEach(function (section) {\n observer.observe(section);\n });\n }\n }());\n <\/script>\n<\/body>\n<\/html>\n\n","protected":false},"excerpt":{"rendered":"<p>Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.<\/p>\n","protected":false},"author":13,"featured_media":9727,"comment_status":"closed","ping_status":"open","sticky":false,"template":"calculator","format":"standard","meta":{"_uag_custom_page_level_css":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[174],"tags":[],"class_list":["post-9725","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cryptocurrency-news-and-insights"],"uagb_featured_image_src":{"full":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false],"thumbnail":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170-300x74.png",300,74,true],"medium":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false],"medium_large":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170-768x190.png",768,190,true],"large":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false],"1536x1536":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170-1536x381.png",1536,381,true],"2048x2048":["https:\/\/guardarian.com\/blog\/wp-content\/uploads\/2026\/06\/ig_0083aca75ed67a11016a328fae1d64819184a464c44b7984af-e1781703236170.png",1774,440,false]},"uagb_author_info":{"display_name":"Ivan","author_link":"https:\/\/guardarian.com\/blog\/author\/ivan"},"uagb_comment_info":0,"uagb_excerpt":"Ethereum\u2019s Glamsterdam upgrade is planned as a major 2026 network upgrade focused on L1 scaling, ePBS, Block-Level Access Lists, parallel processing and more efficient block production.","_links":{"self":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts\/9725","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/comments?post=9725"}],"version-history":[{"count":2,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts\/9725\/revisions"}],"predecessor-version":[{"id":9728,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/posts\/9725\/revisions\/9728"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/media\/9727"}],"wp:attachment":[{"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/media?parent=9725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/categories?post=9725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/guardarian.com\/blog\/wp-json\/wp\/v2\/tags?post=9725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}