Technical issues plagued the recent launch of the Shibarium layer-2 blockchain, which caused about $1.7 million in ETH to become locked in the Shibarium cross-chain bridge for several hours.
Additionally, there were complaints of a “non-functional” RPC (remote procedure call) system, an “awful” blockchain explorer, and an overall “sloppy” user experience for the SHIB community.
Technical Glitches Caused by High Traffic
However, the Shiba Inu team has issued a statement clarifying the events surrounding Shibarium’s launch. They claimed that an unexpectedly high traffic volume was the leading cause of the network’s technical issues during its initial run.
“Shibarium received millions of “compute units” of traffic within moments,” the statement said. It added that an investigation revealed that thousands of contracts had been created in just one block, causing Shibarium to enter a failsafe mode and stop automatically.
Shiba Inu lead developer Shytoshi Kusama made similar clarifications in an Aug. 17 blog post. In the post, Kusama said there were no bridge issues with Shibarium and that the network only collapsed because of a massive influx of transactions and users after it went live.
In its latest statement, the team added that it sought outside help to scale Shibarium’s operations to enable higher traffic on the network without further glitches. According to SHIB developer Kaal Dhairya, the team has identified several possible ways of accomplishing the network upscaling, stating that he will inform the Shiba Inu community of whatever action will be taken in due time.
Fake Screenshot Causing FUD
Dhairya also took issue with what he called a “fake screenshot,” allegedly showing an internal conversation between Shiba Inu developers that has been doing the rounds on social media. The developer stated that they were in contact with X (formerly Twitter) to help identify the source of the screenshot to bring them to justice.