A newly merged Ethereum proposal would retire the network’s 512-validator sync committee, remove its rewards, and make the current Altair light-client interface obsolete by replacing it with offchain zero-knowledge proofs of Casper FFG finality.
The draft EIP-8390 entered the official Ethereum Improvement Proposals repository on August 24, 2024 at 02:04 UTC. “The proposal entered the official EIPs repository at 02:04 UTC on Aug. 24, but its Draft status makes it a design for discussion, not an adopted upgrade,” according to reporting by CryptoSlate editors Liam ‘Akiba’ Wright and Gino Matos.
Sync Committee and Light-Client Architecture
A sync committee is a 512-validator sample whose messages allow light clients to track Ethereum without processing the full validator set. The committee currently receives a portion of consensus rewards, representing roughly 2/64 (or 1/32) of the consensus reward formula. EIP-8390 proposes eliminating both the committee’s validator duties and the rewards associated with it.
The proposal would remove sync-committee network messages, light-client data containers, and several Beacon API endpoints. Deployed Altair light clients using LightClientUpdate would stop working at the fork. Light-client implementations affected include Helios, embedded in wallets and dApps; Lodestar, a consumer-side light-client package; Nimbus, a light-client interface provider; and Datachain, an Ethereum IBC client provider.
Issuance Reduction and Replacement Mechanism
Removing the sync committee would reduce annual consensus issuance by an estimated 33,800 ETH. Current annual consensus issuance stands at approximately 1.082 million ETH across a validator set of 901,505 validators holding 42,328,615 ETH staked in total, according to snapshot data cited in the proposal.
EIP-8390 asserts that Casper FFG finality could be proved within one epoch on a single GPU and verified in milliseconds. However, the draft does not define the proving service, client interface, reliability model, operators, or funding mechanisms for the replacement infrastructure. “EIP-8390 would remove that flow without supplying a replacement Beacon API contract or client migration specification,” CryptoSlate reported.
Outstanding Design Questions
The proposal does not provide reproducible benchmarks or implementation details to support its claims about proof generation and verification timelines. No in-protocol incentive to produce finality proofs is proposed, leaving the economic sustainability of the replacement system unaddressed.
A separate proposal, EIP-7657, sought to add a slashing condition for validators signing malicious sync-committee messages. That proposal is now marked Stagnant. The threshold for applications requiring additional light-client protections is set at 16,384 ETH, though the proposal does not detail how this threshold would interact with the proposed zero-knowledge finality system.
As a Draft, EIP-8390 remains open for discussion and modification. No activation epoch or timeline has been specified.
