Lighthouse Adds Fast Confirmation Rule For Safe Tags

The Rust-based Ethereum client’s v8.3.0 update, published on Oct. 19, 2026, added an opt-in rule that confirmed blocks before finality and made partial data columns the default. NFA.

Release Details

Lighthouse v8.3.0, an Ethereum consensus client, was released on Oct. 19, 2026. The client is developed by Sigma Prime according to its GitHub organization. The release focused on two main changes that affect how nodes handle block data and confirmations.

Fast Confirmation Rule

The client added the Fast Confirmation Rule, under which blocks are confirmed before finality in normal network conditions. With the rule on, apps reading the safe block tag saw confirmations sooner. The rule was off by default and was switched on with a beacon node flag. The team advised using it only on nodes that do not serve validators, such as those for RPC providers, wallets and indexers. Apps that need stronger guarantees were told to keep reading only final blocks.

Finality Status

Ethereum finality was unchanged by the update. The release notes stated that the new rule operates under normal network conditions and does not alter the finality process itself. Nodes serving validators were directed to leave the rule off to avoid any impact on their operations.

Partial Data Columns

Partial data columns became the default on all networks, mainnet included, with an opt-out flag. The feature cut data-column bandwidth by reusing data the execution client already held. This change applies automatically unless an operator chooses to disable it through the provided flag.

Implementation Notes

The Fast Confirmation Rule requires a specific beacon node flag to activate. Once enabled, the rule allows earlier readings from the safe block tag for supported applications. Operators running validator nodes received clear guidance to keep the rule disabled. The partial data columns default requires no additional configuration unless an operator wants to revert the setting.

Network Impact

The changes target specific node types. RPC providers, wallets, and indexers can benefit from the faster safe tag readings when they enable the rule. Validator nodes remain unaffected in their core duties because the rule stays off by default for them. Bandwidth reduction from the partial data columns change applies across mainnet and other networks once the update is active.