Bitget App
Trade smarter
Buy cryptoMarketsTradeFuturesEarnWeb3SquareMore
Trade
Spot
Buy and sell crypto with ease
Margin
Amplify your capital and maximize fund efficiency
Onchain
Going Onchain, without going Onchain!
Convert
Zero fees, no slippage
Explore
Launchhub
Gain the edge early and start winning
Copy
Copy elite trader with one click
Bots
Simple, fast, and reliable AI trading bot
Trade
USDT-M Futures
Futures settled in USDT
USDC-M Futures
Futures settled in USDC
Coin-M Futures
Futures settled in cryptocurrencies
Explore
Futures guide
A beginner-to-advanced journey in futures trading
Futures promotions
Generous rewards await
Overview
A variety of products to grow your assets
Simple Earn
Deposit and withdraw anytime to earn flexible returns with zero risk
On-chain Earn
Earn profits daily without risking principal
Structured Earn
Robust financial innovation to navigate market swings
VIP and Wealth Management
Premium services for smart wealth management
Loans
Flexible borrowing with high fund security
Sepolia testnet’s Pectra upgrade encounters error after an attacker uses “edge case” to mine empty blocks

Sepolia testnet’s Pectra upgrade encounters error after an attacker uses “edge case” to mine empty blocks

CointimeCointime2025/03/10 07:00
By:Cointime

Ethereum recently encountered an issue during the Pectra test on the Sepolia fork, which was exacerbated by an unknown user sending zero-generation token transfers. An Ethereum developer said that the recent Pectra upgrade on the Sepolia testnet encountered an error, and the situation worsened after an attacker exploited an "edge case" causing empty blocks to be mined.

Pectra was launched on its final testnet Sepolia on March 5 at 7:29 a.m., but Ethereum developer Marius van der Wijden said in a post on March 8 that the team immediately began seeing error messages on its geth node and mined empty blocks.

According to Van der Wijden, the reason for the error was that the deposit contract triggered the wrong event type - a transfer event instead of a deposit event. Although a fix was released, van der Wijden said they missed an edge case where an unknown user exploited the vulnerability by sending 0 tokens to the deposit address, triggering the error again.

1

Disclaimer: The content of this article solely reflects the author's opinion and does not represent the platform in any capacity. This article is not intended to serve as a reference for making investment decisions.

PoolX: Earn new token airdrops
Lock your assets and earn 10%+ APR
Lock now!