Ethereum Developers Review EIPs Ahead of Planned Heka Upgrade
Ethereum developers moved EIP-8070’s “sparse blob pool” forward for Glamsterdam and reported a 40% blob-space increase from Fusaka, while opening the Hegota proposal window through Feb. 5.
ETH
Fact Check
The evidence provided by all three sources consistently and directly supports the statement. Each source, from the same crypto-focused news outlet, confirms that Ethereum core developers are actively making decisions about the scope of a future network upgrade named 'Heka' (or 'HEKA'). Specifically, they all report that developers have decided to move an Ethereum Improvement Proposal (EIP) called 'FOCIL' to the 'Heka' upgrade. This action of reviewing and assigning EIPs to a planned upgrade is the core claim of the statement. The sources are highly relevant and internally consistent, with no contradictions. While all evidence comes from a single domain with a moderate authority score, the direct and corroborating nature of the information across multiple reports from that domain provides a high degree of confidence in the statement's truthfulness.
- Reference:
Summary
Ethereum core developers advanced EIP-8070, which proposes a “sparse blob pool,” as part of ongoing work for the Glamsterdam upgrade. Developers also said the Fusaka hard fork increased blob transaction block space by 40%. They announced that the Hegota upgrade proposal window is open until Feb. 5, with submissions posted on Ethereum Magicians and proposals presented during developer calls. The discussion also included ePBS testing issues, consensus-layer anti-censorship ideas, and planned improvements to the EIP governance process.
Terms & Concepts
- EIP-8070: An Ethereum Improvement Proposal discussed by core developers that introduces a “sparse blob pool” concept for future protocol upgrades.
- Blob transactions: A type of Ethereum transaction that carries blob data for scalability; developers referenced increased block space for these transactions after Fusaka.
- ePBS: Embedded proposer-builder separation; a protocol approach to separating block building from proposing that developers discussed in relation to testing issues.