# Known Glamsterdam execution-client conformance reports

Research snapshot: 2026-10-27 (UTC). This is an index of publicly documented reports found in the named client repositories, the execution-specs trackers, devnet notes, and searchable public pages. A row records an explicit bug, incompatibility, client-attributed test failure, or outstanding fix; implementation/release milestones alone are not treated as failures. “None found” means this search found no attributable record, not proof that no issue exists. Dates below are opening/publication dates where shown.

## Findings

| client | EIP | URL | title | state (open/closed/merged) | one-sentence summary of the behavior | date |
|---|---|---|---|---|---|---|
| Geth | Amsterdam (EIP not specified in PR) | [#36020](https://github.com/ethereum/go-ethereum/pull/36020) | eth/protocols/eth: fix minimal gas after amsterdam | merged | PR title records a post-Amsterdam minimal-gas correction; the rendered public page gives no further trigger details. | 2026-10-27 |
| Geth | EIP-8037 | [#35633](https://github.com/ethereum/go-ethereum/pull/35633) | core/vm: repay the outstanding debt first after absorbing child frame | merged | State-gas debt repayment ordering after child-frame absorption required correction. | 2026-09-04 |
| Besu | EIP-7928 / Amsterdam transition | [ACDT #95](https://github.com/ethereum/pm/issues/2209) | All Core Devs - Testing (ACDT) #95, September 7th, 2026 | reported in meeting; no Besu issue link | A devnet-8 Platåberget test reportedly knocked out 12 of 13 Besu nodes; the meeting excerpt attributes the impact to Besu nodes but does not specify a single EIP or root cause. | 2026-09-07 |
| Erigon | EIP-7732 / Engine API | [#22896](https://github.com/erigontech/erigon/issues/22896) | engine_forkchoiceUpdatedV4 rejects the spec's third parameter (custodyColumns) | closed (#22897) | Erigon's two-parameter method rejected the spec's third `custodyColumns` parameter in rpc-compat; issue says the same signature was on main at `4d6ef27f95`. | 2026-07-30 |
| Erigon | EIP-7928 / EIP-7732 | [#22254](https://github.com/erigontech/erigon/issues/22254) | [glamsterdam-devnet-6] erigon builder produces invalid payload (wrong state root) under ePBS reorg — slot 57122 / block 43132 | closed (#22617) | During an execution unwind/reorg, builder output carried a state root that disagreed with clean execution; the report says this recurred three times and blocks were rejected. | 2026-07-06 |
| Erigon | EIP-8282 / Gloas execution requests | [#22008](https://github.com/erigontech/erigon/issues/22008) | cl, execution: implement EIP-8282 (Builder Execution) for Gloas — builder_deposits & builder_exits in ExecutionRequests | open at time of page snapshot | Erigon's three-list execution-request layout was incompatible with devnet-6+ tooling expecting five lists, causing SSZ and JSON decode failures and stalling proposal checks. | 2026 (opened about four months before page crawl; exact day not surfaced) |
| Erigon | EIP-7928 | [#21651](https://github.com/erigontech/erigon/issues/21651) | [glamsterdam-devnet-5] non-deterministic parallel-exec BAL computation rejects canonical blocks as invalid, wedging the CL | closed (#21654) | Parallel execution could compute a nondeterministic BAL and reject canonical blocks; issue recommends serial execution as a temporary mitigation and says the fix merged. | 2026-06-06 |
| Reth | EIP-7928 | [#27206](https://github.com/paradigmxyz/reth/issues/27206) | BAL path hashes deployed contract code three times per block | open | Reth's BAL execution path hashes deployed code three times per block, an explicitly tracked Amsterdam engine performance issue. | 2026-09-13 |
| Geth, Nethermind, Besu, Erigon | EIP-7928 | [execution-apis #868](https://github.com/ethereum/execution-apis/issues/868) | eth_simulateV1: simulated block identity is undefined after Amsterdam | open | Hive rpc-compat observed client differences for simulated Amsterdam blocks: Besu always used `keccak(rlp([]))`, Geth used its computed BAL, Nethermind computed a different BAL from Geth, and Erigon produced a third value; the report says the spec was underspecified and real blocks agreed. | 2026-08-26 |

The #868 row is a cross-client spec ambiguity, explicitly described by its author as not a client bug. It is included because the brief asks for known conformance problems and dashboard/test-attributed failures; reviewers should not mislabel it as an implementation defect. Likewise, the ACDT Besu report is attributed at group level, not proven to be an EL bug or any single EIP. No candidate here is independently confirmed against source code in this item. A Nethermind search result displayed a BAL tracing issue as #12726, but opening that number returned an unrelated sync race, so that inconsistent snippet is excluded pending verification; no Nethermind client-specific finding is included in the table.

## Search coverage and empty results

The repository searches used GitHub-indexed public web search (issues and pull requests, including closed items), with repository-qualified queries for `EIP-2780`, `EIP-7708`, `EIP-7778`, `EIP-7843`, `EIP-7928`, `EIP-7954`, `EIP-7976`, `EIP-7981`, `EIP-7997`, `EIP-8024`, `EIP-8037`, `EIP-8038`, `EIP-8246`, `EIP-8282`, `EIP-7732`, and the wording `glamsterdam`, `amsterdam`, `gloas`, `devnet-8`, `bal`, `epbs`. Query strings were grouped to fit the public search interface; the precise web queries actually issued are listed below. Search engine coverage is not a complete GitHub issue database export.

| client | exact query strings run | EIP/topic terms that returned no client-repository result in those queries |
|---|---|---|
| Geth (`ethereum/go-ethereum`) | `site:github.com/ethereum/go-ethereum/issues EIP-7928 glamsterdam`; `site:github.com/ethereum/go-ethereum/issues OR site:github.com/ethereum/go-ethereum/pull EIP-7928 OR EIP-8037 OR glamsterdam`; `site:github.com/ethereum/go-ethereum/issues/ OR site:github.com/ethereum/go-ethereum/pull/ "EIP-2780" OR "EIP-7708" OR "EIP-7778" OR "EIP-7843" OR "EIP-7928"`; same with `"EIP-7954" OR "EIP-7976" OR "EIP-7981" OR "EIP-7997" OR "EIP-8024"`; same with `"EIP-8037" OR "EIP-8038" OR "EIP-8246" OR "EIP-8282" OR "EIP-7732"`; `site:github.com/ethereum/go-ethereum/issues/ "Amsterdam" "EIP-7928" bug`; `site:github.com/ethereum/go-ethereum/issues "Amsterdam" "EIP-8037" bug` | No directly surfaced repo issue/PR for 7708, 7778, 7843, 7954, 7976, 7981, 7997, 8024, 8038, 8246, 8282, or 7732 from these queries. The search did surface implementation PRs/releases, not defects, for several of these. |
| Nethermind (`NethermindEth/nethermind`) | `site:github.com/NethermindEth/nethermind/issues EIP-7928`; `site:github.com/NethermindEth/nethermind/issues OR site:github.com/NethermindEth/nethermind/pull EIP-7928 OR glamsterdam OR devnet-8`; `site:github.com/NethermindEth/nethermind/issues/ Glamsterdam OR Amsterdam "EIP-"`; `site:github.com/NethermindEth/nethermind/issues "EIP-7928"`; `site:github.com/NethermindEth/nethermind/issues "Amsterdam" BAL`; exact-title follow-up search for `"EIP-7928 BAL path bypasses debug's ChangeableTransactionProcessorAdapter" Nethermind` | The initial indexed issue listing showed a BAL tracing title under #12726, but its URL currently points to an unrelated sync-race issue; therefore no verified Nethermind-specific EIP result is reported. No other repo issue/PR surfaced for the named EIPs. |
| Besu (`hyperledger/besu`, repository now canonical as `besu-eth/besu`) | `site:github.com/hyperledger/besu/issues EIP-7928`; `site:github.com/hyperledger/besu/issues OR site:github.com/hyperledger/besu/pull EIP-7928 OR glamsterdam`; `site:github.com/hyperledger/besu/issues "glamsterdam"`; `site:github.com/hyperledger/besu/pull "Amsterdam" EIP`; `site:github.com/hyperledger/besu/issues "Amsterdam" "EIP-"`; `site:github.com/besu-eth/besu/issues "Amsterdam" EIP Glamsterdam` | No Besu-specific EIP issue/PR surfaced in these searches. The only client-attributed Besu failure found was the external ACDT devnet observation above. |
| Erigon (`erigontech/erigon`) | `site:github.com/erigontech/erigon/issues EIP-7928 glamsterdam`; `site:github.com/erigontech/erigon/issues OR site:github.com/erigontech/erigon/pull EIP-7928 OR glamsterdam`; `site:github.com/erigontech/erigon/issues/ Glamsterdam EIP failure OR bug OR devnet` | No directly surfaced repo result for 2780, 7708, 7778, 7843, 7954, 7976, 7981, 7997, 8024, 8037, 8038, or 8246. Found reports for 7928, 8282, and Engine API/ePBS. |
| Reth (`paradigmxyz/reth`) | `site:github.com/paradigmxyz/reth/issues EIP-7928 glamsterdam OR devnet`; `site:github.com/paradigmxyz/reth/issues/ "EIP-7928" OR "EIP-8037" OR "Amsterdam"`; `site:github.com/paradigmxyz/reth/issues/ Glamsterdam EIP failure OR bug OR devnet` | No directly surfaced repo result for the named EIPs other than the BAL performance tracking ticket #27206; no issue/PR alleging a functional conformance failure surfaced. |

For the trackers and external evidence, searches run were `site:github.com/ethereum/execution-specs/issues "glamsterdam-devnet" "Test Release Tracker"`, `site:github.com/ethereum/execution-specs/issues "Test Release Tracker" glamsterdam-devnet`, `site:github.com/ethereum/execution-specs/issues "glamsterdam-devnet@v8" tracker`, `site:github.com/ethereum/execution-specs/issues "glamsterdam-devnet-8" EIP failures client`, `site:github.com/ethereum/execution-specs/issues "Test Release Tracker" "v8.1.4"`, `site:hive.ethpandaops.io glamsterdam BAL failures client`, `ethpandaops glamsterdam-devnet-8 notes`. Trackers #3034, #3132, #3147, #3167 were read; they document spec/test changes and releases, not failures attributed to one of the five clients. Notes and ACDT minutes do surface failures, listed above. Hive dashboard opened, but its client result panels were not readable in this text-only page fetch (zero content lines); no dashboard-specific failure row was independently extracted. Thus no claim is made that Hive showed no failures.

## Default-branch commit pins at time read

Resolved from GitHub's public repository metadata and default-branch commit endpoint on 2026-10-27; pins identify the mutable branch tip snapshot for this research, not the revision of each historical issue.

| client repository | default branch | commit |
|---|---|---|
| [ethereum/go-ethereum](https://github.com/ethereum/go-ethereum) | `master` | [`8817f99f92852f8ac53e596de6202dd9e3494065`](https://github.com/ethereum/go-ethereum/commit/8817f99f92852f8ac53e596de6202dd9e3494065) |
| [NethermindEth/nethermind](https://github.com/NethermindEth/nethermind) | `master` | [`d48833af88ec4224c86afadd1c596e8f619c406b`](https://github.com/NethermindEth/nethermind/commit/d48833af88ec4224c86afadd1c596e8f619c406b) |
| [hyperledger/besu](https://github.com/hyperledger/besu) → canonical `besu-eth/besu` | `main` | [`aa06c4f8dfc461e483d46c6a1ac72b5bfef8d945`](https://github.com/besu-eth/besu/commit/aa06c4f8dfc461e483d46c6a1ac72b5bfef8d945) |
| [erigontech/erigon](https://github.com/erigontech/erigon) | `main` | [`f32a39d1e5f87a9ec3a9ce2858171c74acc3c242`](https://github.com/erigontech/erigon/commit/f32a39d1e5f87a9ec3a9ce2858171c74acc3c242) |
| [paradigmxyz/reth](https://github.com/paradigmxyz/reth) | `main` | [`e0378eb691aa2770bb96fd4ecec2f4445a2a3e7c`](https://github.com/paradigmxyz/reth/commit/e0378eb691aa2770bb96fd4ecec2f4445a2a3e7c) |

## Every public URL read

Client repositories, issues, PRs, releases, and commit records:

- https://github.com/ethereum/go-ethereum
- https://github.com/ethereum/go-ethereum/issues
- https://github.com/ethereum/go-ethereum/pulls
- https://github.com/ethereum/go-ethereum/releases
- https://github.com/ethereum/go-ethereum/releases?after=v1.6.5
- https://github.com/ethereum/go-ethereum/releases?after=v1.6.5 (release-note page; Amsterdam updates)
- https://github.com/ethereum/go-ethereum/releases?after=2
- https://github.com/ethereum/go-ethereum/milestone/202?closed=1
- https://github.com/NethermindEth/nethermind
- https://github.com/NethermindEth/nethermind/issues
- https://github.com/NethermindEth/nethermind/releases
- https://github.com/NethermindEth/nethermind/releases?after=1.8.62
- https://github.com/besu-eth/besu (canonical repo for hyperledger/besu)
- https://github.com/besu-eth/besu/releases
- https://github.com/besu-eth/besu/blob/main/REFERENCE_TESTS.md
- https://github.com/erigontech/erigon
- https://github.com/erigontech/erigon/issues/20587
- https://github.com/erigontech/erigon/issues/21651
- https://github.com/erigontech/erigon/issues/22008
- https://github.com/erigontech/erigon/issues/22254
- https://github.com/erigontech/erigon/issues/22896
- https://github.com/erigontech/erigon/releases
- https://github.com/erigontech/erigon/releases?after=v2020.11.02
- https://github.com/paradigmxyz/reth
- https://github.com/paradigmxyz/reth/issues
- https://github.com/paradigmxyz/reth/issues/27206
- https://github.com/ethereum/go-ethereum/issues/35860 (redirected to pull/35860; excluded, EIP-8070 is outside this assignment)
- https://github.com/ethereum/go-ethereum/pull/36020
- https://github.com/ethereum/go-ethereum/pull/35633
- https://github.com/ethereum/go-ethereum/issues/35860 (redirected to pull/35860; EIP-8070 is outside this assignment)
- https://github.com/NethermindEth/nethermind/issues/12726 (opened content is a sync race, conflicting with search snippet)
- https://github.com/paradigmxyz/reth/releases
- https://github.com/paradigmxyz/reth/releases? (release listing)
- https://github.com/ethereum/go-ethereum/commit/8817f99f92852f8ac53e596de6202dd9e3494065
- https://github.com/NethermindEth/nethermind/commit/d48833af88ec4224c86afadd1c596e8f619c406b
- https://github.com/besu-eth/besu/commit/aa06c4f8dfc461e483d46c6a1ac72b5bfef8d945
- https://github.com/erigontech/erigon/commit/f32a39d1e5f87a9ec3a9ce2858171c74acc3c242
- https://github.com/paradigmxyz/reth/commit/e0378eb691aa2770bb96fd4ecec2f4445a2a3e7c

Cross-client, specs, tracker, and test/devnet pages:

- https://hive.ethpandaops.io/
- https://notes.ethereum.org/@ethpandaops/glamsterdam-devnet-8
- https://github.com/ethereum/execution-specs/issues/3034
- https://github.com/ethereum/execution-specs/issues/3132
- https://github.com/ethereum/execution-specs/issues/3147
- https://github.com/ethereum/execution-specs/issues/3167
- https://github.com/ethereum/execution-specs/issues/3190 (redirected to pull/3190)
- https://github.com/ethereum/execution-specs/pull/3190
- https://github.com/ethereum/execution-specs/issues/3375
- https://github.com/ethereum/execution-specs/issues/3521
- https://github.com/ethereum/execution-specs/releases
- https://github.com/ethereum/execution-specs/issues/3020
- https://github.com/ethereum/execution-specs/issues/3205
- https://github.com/ethereum/execution-specs/issues/868 (redirected to execution-apis/issues/868)
- https://github.com/ethereum/execution-apis/issues/868
- https://github.com/ethereum/execution-apis/src/engine/amsterdam.md
- https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7773.md
- https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7928.md
- https://github.com/ethereumjs/execution-spec-tests-fixtures
- https://github.com/ethereum/pm/issues/2209
- https://github.com/ethspecs/pm/issues/99
- https://github.com/eth-act/eip-8025/blob/main/PROGRESS.md
- https://github.com/chippr-robotics/fukuii/issues/1415
- https://github.com/onflow/flow-go/issues/8553
- https://github.com/ethereum/ethereum-org-website/issues/19171
- https://github.com/ethereum-optimism/optimism/issues/23015
- https://github.com/ethereum/ethereumjs-monorepo/blob/master/packages/evm/src/message.ts
- https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8279.md
- https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8253.md
- https://github.com/ethereum/EIPs/blob/master/EIPS/eip-8347.md
- https://ethpandaops.io/posts/glamsterdam-data/
- https://lab.ethpandaops.io/

Search-result sources also opened/read as public pages:

- https://github.com/ethereum/EIPs/blob/master/EIPS/eip-7773.md
- https://github.com/ethereum/go-ethereum/blob/master/core/rawdb/accessors_chain.go
- https://github.com/ethereum/execution-specs/issues/1910
- https://github.com/ethereum/execution-specs/issues/2556
- https://github.com/ethereum/execution-specs/issues/3244
- https://github.com/ethereum/execution-specs/issues/3281
- https://github.com/ethereum/execution-specs/issues/3329
- https://github.com/ethereum/execution-specs/issues/3532
- https://github.com/ethereum/execution-specs/issues/3727
- https://github.com/ethereum/pm/issues/2225
- https://github.com/ethpandaops/glamsterdam-devnets
- https://github.com/ethereumjs/execution-spec-tests-fixtures
- https://geth.ethereum.org/downloads

The GitHub API was queried only for public repository default-branch names and commit SHAs; the requests were `https://api.github.com/repos/{owner/repo}` and `https://api.github.com/repos/{owner/repo}/commits/{default_branch}` for the five repositories listed above. No local client, node, or local repository source was inspected.