Technologie & IA
Grandine adds a local block hash check for Glamsterdam
On November 12, the Ethereum consensus client Grandine merged a check into its development branch that recalculates the execution block hash from the data received.

The client recalculates the received hash
On November 12, Grandine merged a change to its Ethereum consensus client into its development branch. It concerns execution payload envelopes under Gloas, the consensus portion of the Glamsterdam upgrade. The client computes the execution block hash itself from the data in the envelope. It then compares the result with the value declared in the incoming message. The change is recorded in the project repository under commit 242f10d.
The verification adds to an earlier check. The block builder commits to a hash in its bid and then sends the execution data in an envelope. Grandine already compared the value stated in that envelope with the value in the bid. Two declared values can still match even if the data does not produce that hash. The new calculation checks that link by reconstructing the header from the transmitted content before processing continues.
Incoming envelopes are checked after the signature
The calculation takes transactions, withdrawals, and execution requests into account, among other data. It rebuilds the values needed for the header, encodes them in the order specified for the execution block, and applies Keccak-256. Grandine performs this work after checking the envelope signature, avoiding the cost of recalculating the hash for data without a valid signature. A recalculated value that differs from the declared one produces a specific error.
In the merged code, the check applies to envelopes relayed by peers, requested from the network, received through the API, or used during back synchronization. The client skips this local check for its own envelopes, whose hashes come from the execution layer. It also skips certain test envelopes with placeholder values. A separate test uses an envelope from the eighth Glamsterdam development network to check the calculation against data that includes transactions and withdrawals.
A change in the development branch
Discussion in the Ethereum specifications repository explains why the timing matters. A node relays the first envelope it accepts for a given block and builder. An envelope accepted too early can therefore take the place of the one whose data actually matches the bid. In a November 12 comment, contributor Mikhail Kalinin points out that a later execution-layer validation result can signal invalidity without distinguishing a hash error from an invalid transaction.
The Grandine merge documents an implementation in this client. The corresponding specification change remained open in the Ethereum repository at the time of review. The Ethereum Foundation describes Glamsterdam as an upgrade being tested on networks separate from mainnet. Merging code into the development branch sets no Glamsterdam activation date or deadline for operators to upgrade their Grandine clients.
