technology
Offchain Labs: Prysm Supports Duty Aware Shutdown for Beacon Nodes
By Roll · Chief of Staff · 19 Oct 2026
Offchain Labs published Prysm v7.3.0 on Oct. 16, 2026, an Ethereum consensus client release that adds an archive node mode and duty-aware validator shutdown.
Operators of Ethereum consensus nodes often weigh how new client updates affect daily routines for running beacon nodes and validators. Offchain Labs published Prysm v7.3.0 on Oct. 16, 2026 as an Ethereum consensus client release that adds an archive node mode and duty-aware validator shutdown. The release notes advise mainnet beacon node updates.
Release Overview
The notes describe the launch of Prysm v7.3.0 on GitHub. They focus on practical changes for beacon node operators. The notes advise that mainnet users apply the update. They list several new flags and behavior adjustments that affect how nodes handle data and signals.
Archive Node Mode
An enable-archive flag turns the beacon node into an archive node. The node backfills blocks to an origin state. Archive mode regenerates every historical state into the state-diff tree. Operators who activate this flag gain access to full historical reconstruction through the existing state-diff structure. The release notes separate this option from standard sync methods.
Shutdown Process
On a stop signal the validator client waits for the current slot’s duties such as attestations to finish. A second interrupt stops the process at once. A flag turns the duty-aware feature off when operators prefer immediate termination. The notes present these steps as a sequence that preserves ongoing validator responsibilities during controlled exits.
Additional Flags and Changes
The enable-state-diff flag no longer carries an experimental label. Checkpoint sync can start from a checkpoint that is not yet final. Payload gas limit and gas used metrics now come from each received execution payload. The doppelganger startup check logs at info level and reports its duration. The dev flag and the terminal override flags are deprecated now that the merge is done though they still function.
Practical Notes for Operators
The release notes group these items together as operational adjustments. They cover data handling, sync flexibility, metric collection, and signal response. Each item receives its own description without reference to prior versions. Operators can review the full list on the GitHub tag page for Prysm v7.3.0. The notes keep instructions direct and focused on the listed behaviors.
Implementation Path
The notes advise that mainnet beacon node updates follow standard procedures. They separate the archive mode activation from the shutdown sequence. They also distinguish the checkpoint sync change from the metric updates. This separation allows operators to test one area at a time if desired. The deprecation notices appear at the end of the list as a reminder that certain legacy flags remain usable for now.
The release centers on these specific additions to the Prysm client. The notes present each change as an independent setting or behavior update. They avoid linking the features to any broader timeline beyond the Oct. 16, 2026 publication date. Operators who need archive capabilities or adjusted shutdown handling can enable the relevant flags after the update. The notes conclude with the recommendation to apply the release on mainnet beacon nodes.