Pectra Upgrade on Sepolia: Issues and Solutions

by Giorgi Kostiuk

a year ago

The Pectra upgrade on the Sepolia testnet faced unexpected issues, including the production of empty blocks.

Problems with Pectra Upgrade

The Pectra upgrade on Ethereum's Sepolia testnet faced unexpected challenges. Developers experienced bugs in their geth nodes and mined empty blocks immediately upon deployment. The issue arose from an incorrect interaction with the deposit contract, leading to unintended log events and invalid blocks that hampered transaction processing. Developers quickly identified the root cause and proposed a fix to ignore invalid logs. However, the major task was deploying the fix without splitting the chain.

I wrote up the story of the Pectra incident on Sepolia, it's an interesting story about edge cases, coordination and an attacker who swooped in and made our lives much harder!Marius Van der Wijden

New Zero-Token Vulnerability

Even though developers believed the issue was resolved, empty blocks began reappearing. It was soon discovered that an external party exploited a lesser-known aspect of the ERC-20 standard: zero-token transfers. This method allowed anyone to trigger transfer events, bypassing the original fix. In response, developers quickly deployed a private patch blocking transactions with the deposit contract on a limited number of DevOps nodes.

Ethereum Developers' Plans

At 14:00 UTC, Sepolia nodes synchronized with the official patch, restoring normal block production. The developers found that the issue was due to the Sepolia deposit contract being token-gated, unlike the mainnet variant. The attack revealed an issue with the ERC-20 standard—zero-token transfers still emit events. In light of such risks, developers plan deeper reviews of smart contract interactions before deploying Pectra on the Ethereum mainnet.

As a result of the incident, developers have decided to conduct more comprehensive testing prior to deploying updates on the Ethereum mainnet.

Tier I

Sector: #18291

Sealed Cache Room

Resource Cache

Tier I

Requires 25% Tier Progress to Claim

Meme Cache

Tier I

Requires 50% Tier Progress to Claim

Equipment Cache

Tier I

Requires 75% Tier Progress to Claim

After collecting, caches will be stored in your inventory and can be opened with Keys.

Tier I

Sector: #18291

25%

50%

75%

100%

Tier II

Survivors rescued:

0 / 600

Survivors

0/0

Transmit Signal

Broadcast this sector's coordinates to other rescuers.

Other news

Bitcoin Red Team Established to Tackle AI-Driven Security Threats

The Bitcoin Red Team has been established to proactively identify AI-assisted security vulnerabilities in the Bitcoin ecosystem.

Tando Nkube6 minutes ago

TON Validators Prepare for Configuration Vote on New Collator Architecture

TON validators are updating their node software and mytonctrl tooling for a configuration vote on a new collator architecture scheduled for August 21 at 0800 UTC.

Kofi Adjeman7 hours ago

Aave's EMode: Efficiency and Risk in DeFi Lending

Aave's EMode feature allows for efficient borrowing among correlated assets but also increases the risk of liquidation during market stress.

Satoshi Nakamura7 hours ago

Avalanche Surpasses $3 Billion in Tokenized Real-World Assets

Avalanche's tokenized real-world asset value has surpassed $3 billion, marking a significant milestone in its development as a platform for institutional finance.

Nguyen Van Long7 hours ago

Aave's Debt Concentration Raises Concerns Amid Ethereum Volatility

Aave's debt profile shows that a small number of loan positions account for a significant portion of its total outstanding debt, raising concerns about risk concentration.