EIP-8390 would break existing Altair light client implementations without providing a migration path or replacement Beacon API specification
Too little corroboration in the last 3 days to call a trend (1 article). Watching for it to gain traction.
EIP-8390 would disable existing Altair light client implementations at the fork without providing a migration path or replacement Beacon API specification, forcing all deployed light clients that sync through LightClientUpdate to cease functioning. This represents a breaking change to critical infrastructure with no backward compatibility plan.
Breaking changes to core APIs without migration pathways fragment the developer ecosystem, increase operational costs for node operators and light client maintainers, and can trigger liquidity fragmentation as participants migrate to alternative infrastructure, reducing network effects and increasing systemic fragility.
"The proposal says deployed Altair light clients that sync through LightClientUpdate would stop working at the fork. EIP-8390 removes that flow without supplying a replacement Beacon API contract or client migration specification."