Here’s Why Solana Ceased Block Production for 7 Hours on Saturday
Millions of transactions per second and heavy traffic contributed to the network’s disruption, developers explained on Tuesday.

Bots tied to a new non-fungible token (NFT) project built on Solana caused a seven-hour network outrage on Saturday, project developers confirmed in a post on Tuesday. No new blocks were produced by the network during that time.
On April 30th, Solana's Mainnet Beta cluster suffered a 7 hour outage caused by stalled consensus. Below is an investigation into the cause of the outage, and the steps core developers are taking to increase network resiliency and stability. https://t.co/pfkMTEwPda
— Solana Status (@SolanaStatus) May 3, 2022
Solana processes an average of 2,700 transactions per second (tps), blockchain explorers show, with an upper peak of over 710,000 tps on a standard network, as per developer documents.
However, on Saturday night millions of transactions flooded the network each second. This led to network validators – or entities that process transactions on and support the network – to run out of memory and crash, developers said.
“An enormous amount of inbound transactions (6 million per second) flooded the network, surpassing 100 Gbps of traffic at individual nodes,” developers wrote. “There is no evidence of a denial of service attack, but instead evidence indicates bots tried to programmatically win a new NFT being minted using the popular Candy Machine program.”
Validators ran out of memory while trying to clear up transactions in other, abandoned blocks. The number of total forks that validators had to evaluate exceeded their capacity to do so automatically, which led to a manual intervention to fix the issue.
Bots had swarmed the popular NFT minting tool known as Candy Machine on Saturday, as reported. This was mainly to take part in a new NFT project mint.
However, that mint used a fixed price for users instead of a Dutch auction – the usual process followed by crypto projects – which incentivized bots to send a huge number of transactions in hopes of winning the mint. This caused spam on the network.
Meanwhile, developers noted Solana has suffered intermittent congestion issues several times in the past months – with most of these resulting from bot activity targeted at NFT mints.
Changes are coming to combat those problems. Developers said the upcoming v1.10 release, currently stabilizing on testnet, includes memory use improvements to prolong the time nodes can endure slow or stalled consensus, which would help mitigate issues like those seen on Saturday.
Fees for prioritizing transactions are coming to Solana as well, developers added. This could help mitigate the entirety of Solana getting affected because of a single project.
Solana's SOL tokens trade at over $88 at writing time, as per CoinGecko data. Prices are down a nominal 1.8% in the past 24 hours.
Meer voor jou
Protocol Research: GoPlus Security

Wat u moet weten:
- As of October 2025, GoPlus has generated $4.7M in total revenue across its product lines. The GoPlus App is the primary revenue driver, contributing $2.5M (approx. 53%), followed by the SafeToken Protocol at $1.7M.
- GoPlus Intelligence's Token Security API averaged 717 million monthly calls year-to-date in 2025 , with a peak of nearly 1 billion calls in February 2025. Total blockchain-level requests, including transaction simulations, averaged an additional 350 million per month.
- Since its January 2025 launch , the $GPS token has registered over $5B in total spot volume and $10B in derivatives volume in 2025. Monthly spot volume peaked in March 2025 at over $1.1B , while derivatives volume peaked the same month at over $4B.
Meer voor jou
ZKsync Lite to Shut Down in 2026 as Matter Labs Moves On

The company framed the move, happening in early 2026, as a planned sunset.
Wat u moet weten:
- Matter Labs plans to deprecate ZKsync Lite, the first iteration of its Ethereum layer-2 network, the team said in a post on X over the weekend.
- The company framed the move, happening in early 2026, as a planned sunset for an early proof-of-concept that helped validate their zero-knowledge rollup design choices before newer systems went live.











