Starknet explains the reasons for the 4-hour ban

Starknet Explains The Reasons For The 4-Hour Ban


Ethereum's layer-2 protocol, Starknet, has faced a block reorganization that has caused delays in transactions. The protocol's block monitoring tool Starkscan showed a four-hour outage in block production.

Starkscan shows a gap between blocks 630028 and 630029 on April 4, while Starknet's status page shows no outages on the network on the same day.

StarxScan's block display reflects the four-hour difference between lock 630028 and 630029. Source: StarxScan

Starknet subsequently released a statement on X, explaining that a rounding error caused the blocks to be rearranged. The company said production of the block continued as normal, but the restructuring meant that transaction delays prevented it from reaching its full potential.

D1924256 9Ea3 46E0 Aa7F 6D246D22A4A8
Source: Starknet

“Consequently, there were a few minutes when new transactions were not accepted for processing and were rejected. Moreover, some transactions were restored with variable parameters (eg timestamps),” the article explains.

bybit

Cointelegraph contacted Starknet to confirm the details of the incident and received no further information, and according to block information, if block production has been discontinued.

Starknet's status page was last seen on March 13th when the network suffered a slow block due to the Ethereum Denkun update.

Ee9813E9 82Ff 4581 A459 44Bc978F8C98
Starknet's status page shows the last major event on March 13 during the Ethereum Dencun update. Source: Starknet Status

The Starknet outage is a series of hiccups for some of the ecosystem's largest blockchain networks.

Solana experienced a major outage in early February 2024. A downtime in block production on the main network caused the network's block progress to stop for more than five hours.

It wasn't the first time Solana had gone down. Since January 2022, Solana has seen nearly half a dozen significant outages and 15 days of partial or major delays.

Solana-focused software development firm Anza released its latest outage postmortem on February 9.

Solana's just-in-time (JIT) compilation, which completes all programs before committing a transaction, had a cache problem, according to the report.

Related: Starknet expects major impact from Ethereum's Dencun hard fork

Austin Federa, chief strategy officer of the Solana Foundation, told Cointelegraph that while the process was underway to replace the old loader system with a new engine system, it was planned to be disabled in the updated version.

“It looks like someone deliberately invoked that old set of instructions, long since deprecated but still in the codebase. Encountered cases where the JIT compiler could not find what it was looking for. And that's what created the never-ending loop,” Federa told Cointelegraph.

Solana experienced problems again in early April, when nearly 75% of all transactions on the network crashed amid the flood of activity brought on by the recent memecoin mania.

Analysts suggest that these failed transactions are mainly due to bot activity on Solana by those seeking to execute arbitrage trades.

Magazine: Ethereum ERC-20 Design Flaws Are a Crypto Scammer's Best Friend

Leave a Reply

Pin It on Pinterest