Starknet Encounters Block Reorganization Problem

user avatar

by Giorgi Kostiuk

2 years ago

Made with AI


The Ethereum Layer-2 protocol known as Starknet recently faced a challenge with a block reorganization issue. Starkscan, the block explorer for Starknet, displayed a disruption in block production lasting four hours. This disruption occurred between blocks numbered 630028 and 630029 on April 4th, though Starknet's status page did not report any disturbances on that day.

Notable Incident in Starknet Network

Following this event, the Starknet team released a statement on platform X, explaining that a rounding error caused the block reorganization. While block production continued as normal, the reorganization led to a backlog of transactions, causing the network to operate below full capacity.

The Starknet status page previously showed a significant disruption on March 13th due to Ethereum's Dencun update, resulting in slow block production. This recent disruption in the network is part of a series of challenges faced by major blockchain networks.

Similar issues have been observed with Solana, which encountered a significant disruption in early February 2024. This disruption halted the progress of blocks for over five hours on the main network, adding to a series of incidents that Solana has experienced since January 2022.

Recent Challenges in Solana Ecosystem

Anza, a software development firm focusing on Solana, published a technical report addressing the outage, revealing that an error in Solana's Just-in-Time compilation cache was the root cause. Plans are in place to replace the old loader system with a new engine system to prevent similar incidents.

Additionally, in early April, Solana experienced further issues, with a surge in failed transactions accounting for almost 75% of all transactions on the network. Analysts attribute these failures to bot activities engaging in arbitrage operations on Solana.

Tier I

Sector: #18291

Sealed Cache Room

Resource Cache

Resource Cache

Tier I

Requires 25% Tier Progress to Claim
Meme Cache

Meme Cache

Tier I

Requires 50% Tier Progress to Claim
Equipment Cache

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.

Other news

Zcash's Impressive Market Performance and ETF Launch

chest

Zcash has experienced a remarkable price increase, gaining over 2,300% in the past year, aided by the launch of Grayscale's Zcash ETF.

user avatarLucas Weissmann

Zcash Surpasses $1,000 Mark, Achieving New All-Time High

chest

Zcash's price broke above $1,000 for the first time in nearly a decade, marking a significant milestone in its market performance.

user avatarRajesh Kumar

Trezor Implements New Security Measures After Data Breach

chest

Trezor is enhancing security measures, including anonymous delivery options, in response to a data breach affecting 67,000 customers.

user avatarFilippo Romano

Data Breach Affects 67,000 Trezor Customers

chest

A data breach at shipping provider ShipMonk has exposed personal information of 67,000 Trezor customers in the US.

user avatarEmily Carter

BAI Establishes Global Settlement Layer for AI Agents to Enhance Collaboration

chest

BAI is building a global settlement layer to enhance collaboration and efficiency among AI agents across various workflows.

user avatarTomas Novak

BAI Launches Free Access to Premium AI Models, Surpassing 133 Trillion Daily Tokens

chest

BAI has launched free access to its premium AI models, leading to a significant increase in platform activity and user adoption.

user avatarKaterina Papadopoulou

Important disclaimer: The information presented on the Dapp.Expert portal is intended solely for informational purposes and does not constitute an investment recommendation or a guide to action in the field of cryptocurrencies. The Dapp.Expert team is not responsible for any potential losses or missed profits associated with the use of materials published on the site. Before making investment decisions in cryptocurrencies, we recommend consulting a qualified financial advisor.