• Ethereum News
• Highlights of Ethereum Devs Call
• Tech Articles
• Podcasts
• Tech Explainers
• ELI5 Explainers
• Client Upgrades
• Events
• Jobs

Ethereum News

• What is EIPsInsight? How is it Changing the Way We Approach Ethereum Governance
  • EIPsInsight streamlines the complex process of analyzing Ethereum Improvement Proposals (EIPs) by offering tools to track changes, review pull requests, and visualize proposal data. These features help developers and editors save time and make more informed decisions about Ethereum’s evolving governance.
  • With a mission to improve Ethereum governance, EIPsInsight provides detailed insights into EIP status changes, helping users understand proposal trends and statuses. Our platform supports the Ethereum principles of decentralization and transparency by making data accessible and easy to understand, ensuring that all stakeholders can participate meaningfully in Ethereum’s governance processes.
• Chainlink Launched Private Blockchain Transactions for Institutions
  • Blockchain Privacy Manager allows institutions to integrate their private blockchain networks with existing systems, such as traditional enterprise backends, while limiting onchain data exposure. This capability enables private chains to be integrated with the public Chainlink Platform, providing access to crucial offchain data such as Proof of Reserve (PoR), Net Asset Value (NAV), market prices, and identity data, without exposing sensitive private chain data to third parties.
• Fault proofs are now live on Base Mainnet
  • Fault proofs are now live on Base Mainnet, marking a key milestone on our path to decentralization. With this upgrade, anyone can now participate in securing Base, creating a more trusted and open economy for everyone.
• Starknet Reaches a New Peak of 857 TPS on Starknet Mainnet
  • Starknet: Records are meant to be broken.
• Vitalik Shares "Some important next steps"
  • Helios (or alternatives) being integrated into user wallets, on mobile and desktop
  • L2 configs moving onchain (first step: https://github.com/ethereum/ERCs/pull/669)
  • L2 configs including specification of state proof verification rules (a possible starting point: https://eips.ethereum.org/EIPS/eip-3668)

Consensus-layer Call 145

The call started with Barbanas sharing the exciting launch of the Mekong testnet, which went live just hours before. This public testnet, based on the Pectra spec, will run for around three months with 100,000 validators on board. The focus here is testing a new tool that supports larger deposits over 32 ETH and allows for consolidating two validators. While it’s still in development, this tool could really streamline node management.

Stokes then moved the conversation to devnet progress. Devnet-4 seems solid, so the team is already looking at devnet-5. They discussed the “Separate type for unaggregated network attestations” (PR 3900), which will be integrated in devnet-5, and the TTFB/RESP_TIMEOUT changes (PR 3767), which are backward-compatible and set to roll out in devnet-5.

One of the crucial topics was EIP-7742. This proposal aims to decouple blob handling between the consensus layer (CL) and execution layer (EL), giving more control over blob counts. However, concerns arose around the base fee calculation—currently set at a “target blob count”—which could impact performance if changed. They discussed quick adjustments like updating the base fee scaling, balancing simplicity and effectiveness. Gajinder suggested adding a max blob count to the header for better symmetry, sparking some debate over whether this added complexity was necessary.

As a resolution, they decided to proceed with the more manageable PR 8994 update for the Pectra fork. While not an ideal solution, it provides enough flexibility for now without overcomplicating things.

Pectra updates included a fix to ensure smooth voluntary exits during consolidation (EIP-7251), resolving overlooked checks. A team also shared progress on blob scaling tests, measuring bandwidth across nodes, which could inform future blob size standards.

There was a proposal to allow more flexibility in withdrawal credentials on the execution layer, potentially simplifying future policy management.

They also addressed a significant reorg issue on Devnet 3 with around 100,000 slots, leading to a temporary shutdown as they worked on stabilizing the EVM Object Format (EOF) for Fulu.

Finally, with Devcon approaching, a lot of the core team will be attending, so more discussions and updates are expected after the conference.