Ethereum
Prysm 7.3.2 strengthens safeguards for Ethereum validators
The release published on November 18 fixes stalls and protection flaws in the consensus client. It also changes data-distribution settings without altering the fork schedule.

Log streams that could stall the client
Prysm, the Ethereum consensus client developed by Offchain Labs, released version 7.3.2 on November 18, 2026. The maintainers recommend that mainnet operators update both the beacon node and validator client. This is software maintenance for the different networks, rather than an announcement of a new fork date. The official documentation still distinguishes between networks: Glamsterdam is shown as live on Sepolia since October 6, while mainnet and Hoodi remain without a scheduled date.
One fix concerns streaming logs to an interface or another client. According to the corresponding change request, a recipient that stopped reading could block all logging calls. Validator duties would then stop, gRPC calls would time out, and the process would ignore the SIGTERM termination signal. The change prevents this general wait: a log line is dropped for the recipient whose buffer is full. It therefore protects the software’s operation against a log consumer that can no longer keep up with the stream.
Attestation writes are better synchronized
Another fix addresses the recording of attestations in the slashing-protection database. Previously, acknowledgment of a save could arrive when the next batch was written, even if that batch did not contain the relevant attestation. The validator could therefore submit it before its own protection record had been written. Each save now has its own result channel; acknowledgment corresponds to the requests included in the batch actually recorded. The fix concerns this ordering of operations, without by itself establishing that an operator suffered a penalty.
The release notes attribute twelve fixes to reports from Anthropic’s OSS Scanner. Their areas include validator protection, validation of RPC inputs and messages exchanged between peers, and potential node stalls. This attribution describes the origin of reports received by the project. It is neither an account of observed attacks nor an estimate of financial losses. The technical documents examined describe flaws and their fixes without providing either of those measures.
Two changes to anticipate in existing tools
Partial data-column dissemination is disabled by default again. The disable-partial-data-columns parameter takes the value true; exchanges therefore use full columns unless an explicit alternative is chosen. The change request presents this as a way to avoid difficulties associated with the partial feature and says it does not truly resolve the underlying problems. This preventive measure must be distinguished from a definitive fix for their cause.
Finally, the nonstandard validator_count API is removed. The maintainers ask tools that use it to switch to the standard validator endpoints before updating. These adaptations concern the behavior of the client and its operating environment. Improvements relating to Gloas, light clients and historical block backfill also appear in the release; they should not be interpreted as a new activation of Glamsterdam on mainnet.
