{"id":91499,"date":"2025-11-27T16:07:39","date_gmt":"2025-11-27T13:07:39","guid":{"rendered":"https:\/\/forklog.com\/en\/?p=91499"},"modified":"2025-11-27T16:10:20","modified_gmt":"2025-11-27T13:10:20","slug":"operational-errors-lead-to-500-million-chaos-in-megaeth-launch","status":"publish","type":"post","link":"https:\/\/forklog.com\/en\/operational-errors-lead-to-500-million-chaos-in-megaeth-launch\/","title":{"rendered":"Operational Errors Lead to $500 Million Chaos in MegaETH Launch"},"content":{"rendered":"<p>On November 25th, the launch of the pre-deposit campaign for the <a href=\"https:\/\/forklog.com\/en\/news\/what-is-a-layer%e2%80%912-solution-in-blockchain\">L2<\/a> project <a href=\"https:\/\/forklog.com\/en\/news\/can-ethereum-outpace-solana-inside-megaeth-an-ambitious-new-rollup\">MegaETH<\/a> was marred by technical issues. Instead of the planned $250 million, the project attracted $500 million due to a loss of control over the smart contract management.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"zxx\" dir=\"ltr\"><a href=\"https:\/\/t.co\/hL0iIM0c3A\">https:\/\/t.co\/hL0iIM0c3A<\/a><\/p>\n<p>\u2014 MegaETH (@megaeth) <a href=\"https:\/\/twitter.com\/megaeth\/status\/1993395774164488361?ref_src=twsrc%5Etfw\">November 25, 2025<\/a><\/p><\/blockquote>\n<p> <script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>The cause was not a code hack but human error and incorrect handling of the <a href=\"https:\/\/forklog.com\/en\/news\/what-is-a-multisignature-what-is-a-ring-signature\">multisig<\/a>.<\/p>\n<h2 class=\"wp-block-heading\">Chronology of the Failure<\/h2>\n<p>The MegaETH team planned to gather liquidity before the mainnet launch in December. The conditions <a href=\"https:\/\/predeposit.megaeth.com\/\">seemed<\/a> simple: start at 9:00 am (ET), a $250 million cap, a first-come, first-served basis, and KYC via the Sonar platform.<\/p>\n<p>Problems began immediately after the start:<\/p>\n<ul class=\"wp-block-list\">\n<li>Sonar crash \u2014 the user verification infrastructure could not handle the load. Servers went down at 9:01 due to request limit exceedance. Load testing for such an amount was not conducted before the launch;<\/li>\n<li>smart contract error \u2014 even before the site crashed, deposits were not processed. The SaleUUID parameter in the contract did not match Sonar&#8217;s settings.<\/li>\n<\/ul>\n<p>It took the team 23 minutes to fix the error. They needed to gather signatures in the multisig wallet to update the parameters. During this time, thousands of users unsuccessfully attempted to send funds.<\/p>\n<p>Once the bridge was operational, the $250 million cap was filled in 156 seconds.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">Unfortunately our 3rd party provider received too many requests resulting in downtime.<\/p>\n<p>The $250M cap filled within 156 seconds upon resolution. <\/p>\n<p>We&#8217;ve decided to increase the cap to $1B in an effort to give users access to USDm day 1.<\/p>\n<p>Bridge will reopen at 11am EST.<\/p>\n<p>\u2014 MegaETH (@megaeth) <a href=\"https:\/\/twitter.com\/megaeth\/status\/1993336715566891232?ref_src=twsrc%5Etfw\">November 25, 2025<\/a><\/p><\/blockquote>\n<p> <script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Due to the lack of an official announcement about the fix, spots were taken by bots and users continuously refreshing the page.<\/p>\n<h2 class=\"wp-block-heading\">Incident with Safe Multisig<\/h2>\n<p>Following a wave of criticism, the team decided to increase the cap to $1 billion and reopen fund acceptance at 11:00. This required changing the contract parameters again via the Safe multisig wallet.<\/p>\n<p>The wallet management scheme required four out of six possible signatures, and developers gathered them in advance to simply send the transaction to the blockchain precisely at 11:00. This was the main mistake.<\/p>\n<p>In Safe wallets, once the required number of signatures is collected, anyone can execute the transaction. This is a documented feature of the protocol, ensuring decentralization.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">To explain what happened here:<\/p>\n<p>The increase to $1B was executed ~30m early by chud. When required signatures on a transaction in a <a href=\"https:\/\/twitter.com\/safe?ref_src=twsrc%5Etfw\">@safe<\/a> are reached, ANYONE (even people not on the multisig) can execute the transaction. It&#8217;s a core feature and it can&#8217;t be turned off.<\/p>\n<p>\u2014 YAM \ud83c\udf31 (@yieldsandmore) <a href=\"https:\/\/twitter.com\/yieldsandmore\/status\/1993344019628433700?ref_src=twsrc%5Etfw\">November 25, 2025<\/a><\/p><\/blockquote>\n<p> <script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>A user under the pseudonym chud.eth noticed the fully signed transaction in the mempool and <a href=\"https:\/\/etherscan.io\/tx\/0x7884fe71f118d2b2570de41e2f3becd127c04bf07471a373a601d95325979967\">executed<\/a> it himself 34 minutes ahead of the team&#8217;s schedule.<\/p>\n<h2 class=\"wp-block-heading\">Consequences of the Chaos<\/h2>\n<p>The unexpected opening of deposits triggered a new influx of funds. The team watched as the balance rapidly increased beyond their control:<\/p>\n<ul class=\"wp-block-list\">\n<li>an attempt to cap the collection at $400 million failed \u2014 the transaction was too late, as the amount had already exceeded this threshold;<\/li>\n<li>they managed to set the limit at $500 million.<\/li>\n<\/ul>\n<p>The developers admitted defeat and abandoned plans to raise the cap to $1 billion.<\/p>\n<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\">We&#8217;ve encountered unexpected issues throughout the process and are no longer moving forward with the $1B cap.<\/p>\n<p>We will be sharing a retro shortly.<\/p>\n<p>We&#8217;ll also be including the ability for users to withdraw who no longer wish to participate. <\/p>\n<p>Apologies for the turbulence.<\/p>\n<p>\u2014 MegaETH (@megaeth) <a href=\"https:\/\/twitter.com\/megaeth\/status\/1993349867343675687?ref_src=twsrc%5Etfw\">November 25, 2025<\/a><\/p><\/blockquote>\n<p> <script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>MegaETH acknowledged their fault, calling the incident &#8220;unacceptable.&#8221; The developers emphasized that the smart contracts worked perfectly, there were no vulnerabilities, and user funds were safe. The failure was due to human error and a lack of understanding of the documentation of the tools used.<\/p>\n<p>Despite the issues, less than 5% of users took advantage of the offered withdrawal option. The MegaETH mainnet launch is still scheduled for December, with the token release planned for early 2026.<\/p>\n<p>Back in October, MegaETH <a href=\"https:\/\/forklog.com\/en\/news\/megaeth-raises-27-8-billion-in-token-sale\">raised $1.39 billion<\/a> from its token sale, with oversubscription exceeding 27x.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The launch of MegaETH&#8217;s pre-deposit campaign was marred by technical issues<\/p>\n","protected":false},"author":1,"featured_media":91500,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"select":"1","news_style_id":"1","cryptorium_level":"","_short_excerpt_text":"MegaETH's pre-deposit campaign faced technical issues, leading to chaos.","creation_source":"","_metatest_mainpost_news_update":false,"footnotes":""},"categories":[3],"tags":[1301,1179],"class_list":["post-91499","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-news-and-analysis","tag-blockchain-vulnerabilities","tag-layer-2-solutions"],"aioseo_notices":[],"amp_enabled":true,"views":"287","promo_type":"1","layout_type":"1","short_excerpt":"MegaETH's pre-deposit campaign faced technical issues, leading to chaos.","is_update":"","_links":{"self":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/91499","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/comments?post=91499"}],"version-history":[{"count":1,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/91499\/revisions"}],"predecessor-version":[{"id":91501,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/posts\/91499\/revisions\/91501"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media\/91500"}],"wp:attachment":[{"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/media?parent=91499"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/categories?post=91499"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/forklog.com\/en\/wp-json\/wp\/v2\/tags?post=91499"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}