Starknet Strikes Again: Ethereum’s Layer 2 Network Goes Down for 2nd Time in 2 Months!

by

Oh dear, here we go again! Ethereum‘s scaling superhero, Starknet, had another hiccup on Tuesday, leaving the blockchain community scratching their heads and investors biting their nails. For a solid 2 hours and 44 minutes, the mainnet was as useful as a broken pencil. Transactions ground to a halt, and block creation became as slow as a sloth on a Sunday stroll. 🐢

So, what went wrong? Well, it turns out the “sequencer” – the trusty traffic cop of the blockchain world – had a little meltdown. This poor fellow is supposed to organize all the on-chain transactions, lining them up neatly in blocks like an army of ants. But during the outage, the sequencer couldn’t recognize the “Cairo0 code.” Who knew code could be so fussy, right? 😜

This is the second time Starknet has experienced a “major” mainnet failure in just two months! Investors are starting to wonder if they can rely on Starknet to keep their billions safe. With a total value locked (TVL) of $548 million, you’d think they’d have their ducks in a row. But nope, instead, we’ve got a big ol’ traffic jam on the blockchain freeway. 🚧

Remember the last time? On July 18, the mainnet suffered a teeny-tiny 13-minute blip. Nothing major, just a few slow block creation times and a sluggish gateway. That’s all. Just a small, little, “minor” issue. 😆

Now, L2 networks like Starknet are supposed to be Ethereum’s fancy sidekick, speeding up transactions and taking some of the load off Ethereum’s shoulders. They’re secondary blockchains that do the heavy lifting offchain, making things faster and cheaper. But with all these outages, one has to wonder: is Starknet really up to the task? 😏

Starknet claims it’s back online, “fully operational” now, though. Less than three hours into the outage, they pulled a rabbit out of the hat and restored full functionality, according to their community-run X account. Phew! 😅

“Block production is back to normal. Most RPC providers are up-and-running, and the remaining ones will upgrade shortly.”

Here’s the kicker: any transactions submitted between 2:23 AM and 4:36 AM UTC didn’t get processed. Oops. A little hiccup, no biggie. Blockchain reorganization was required from block 1960612, and users now need to resubmit all transactions from that point forward. No big deal. It’s not like this is your money on the line, right? 💸

And don’t worry, the Starknet team promises to publish a full timeline, root cause, and some fancy long-term prevention measures soon. Fingers crossed! 🤞

CryptoMoon has reached out to Starknet to ask more about this latest tech disaster. Stay tuned, folks, it’s not over yet!

Read More

2025-09-02 14:43