MegaETH Response to Community Concerns on Pre-Deposit Event: User Fund Security, Withdrawal Open
Source: MegaETH
Editor's Note: Yesterday, MegaETH held an open deposit event, during which temporary changes to the hard cap and user deposit difficulties led to some community dissatisfaction. Subsequently, MegaETH's official team responded on social media, apologizing and announcing the upcoming opening of withdrawals, emphasizing user fund security.
Below is MegaETH's recap of the event and response to the community:
The situation that occurred earlier was unacceptable to us. A series of minor technical issues compounded, resulting in a user experience below the expected standard.
We understand that some users may wish to withdraw their funds, especially those participants who deployed funds based on the expected $250 million limit. To address this, we will launch a withdrawal page in the coming days and simultaneously release detailed instructions on the deposit bridging event. User funds were never at risk, and we sincerely thank everyone for their support.
Event Recap
Given the scale of participation, we believe it is necessary and transparent to recount the events for collaborative planning of next steps. While the assets were always secure, this is not an excuse—we hold ourselves to a higher standard.
Below is a full retrospective of the event:
Preparation Phase
It is necessary to outline all steps involved in the event:
1. Deposit Website
→ Operated by MegaETH
→ Sent KYC validity verification request to Sonar API
2. Deposit Smart Contract
→ Managed by MegaETH through a Safe multi-signature wallet (4/6)
→ Responsible for setting the sale time, limit parameters, and Sonar Sale Unique Identifier (SaleUUID)
→ Only accepted valid signature deposits from the website, preventing bot operations
3. Sonar System
→ Operated by Echo
→ Responsible for validating KYC information for specific sales
Issue Root Cause
The following are issues encountered during the event:
SaleUUID Mismatch Exception
· Transaction initiation failed due to a mismatch between the SaleUUID stored in the prepayment contract and the system
· Correcting the erroneous value requires a multisig transaction (involving coordination of 4 out of 6 signers), consuming significant coordination time
Sonar Rate Limiting and System Downtime
· Sonar began blocking access requests due to misconfigured rate limits (threshold set too low)
· Users were unable to complete fund deposits
· Root cause identification and deployment of a fix took 23 minutes after the issue was discovered
Random Restart Mechanism
· After resolving all server issues, the system randomly restarted as per the predefined automation (designed to ensure fairness)
· However, upon system restart, the fundraising cap was instantly reached
Unexpected Influx of Funds
· A sudden surge of $250 million flooded the prepayment website continuously
· The team decided to increase the cap to $1 billion at the next hour mark (approximately 40 minutes later), requiring another 4 out of 6 multisig transaction to adjust the parameters
· The team has completed signature collection and is ready to submit at the scheduled time
· However, the operator executing the cap increase transaction is unfamiliar with the Safe wallet functionality
$500 Million Cap and Pause Decision
· At this point, more users constantly refreshing the website discovered the ability to resubmit deposits, while users following official channels did not promptly realize the cap adjustment
· The team initially attempted to set a $4 billion new cap to balance the advantage of early depositors, but deposits exceeded the expected amount during transaction confirmation
· The cap was eventually successfully set at $5 billion (currently fully allocated)
Due to the rapid changes in the final adjustment in the last hour, we have decided to pause the planned cap increase to $10 billion. As there is still a KYC verification obstacle that has not been fixed and is hindering user participation, we will no longer proceed with raising the fundraising cap.
This article is contributed content and does not represent the views of BlockBeats.
You may also like

Kalshi early employees: Whoever controls the traffic controls the market

Tether signs contracts with four major audits, Circle's compliance moat collapses, stock price plummets by 20%

Proudly Introducing Aethir Claw: Your AI Agent, Our Infrastructure

Why Buying Gold Can Lead to Bankruptcy

If the US Treasury yield rises above 5%, will Bitcoin drop below $50,000?

Circle Plunges 20%: Crypto Earthquake Triggered by Draft Proposal

After the Smoke Clears: 5 Possible Endings to the Middle East Conflict

Stablecoin Yields Discontinued, Circle Plunges 20% in One Day

AI Wired into War Machine | Rewire News Nightly

Web3 is sick, but the cure is not AI

Why must Web3 projects be included in RootData?

Fluid Announces Updates on Resolv Hack Recovery and Compensation Plan
Key Takeaways Fluid has repaid approximately $70 million related to USR debts on the BNB and Plasma chains.…

Binance to Delist Key Spot Trading Pairs: What You Need to Know
Key Takeaways Binance is set to remove several spot trading pairs on March 27, 2026, at 11:00 AM…

Whale Activities in the Crypto Market: A Deep Dive into Recent Trends
Key Takeaways A significant whale deposit occurred 3 hours ago when 5.5 million USDT was moved to Binance…

Circle and Tether Freeze Iranian Exchange Wallex Wallet with $2.49M Assets on Hold
Key Takeaways Circle and Tether have frozen a significant amount of assets from an Iranian exchange called Wallex,…

James Wynn Engages in High-Leverage Bitcoin Short Position
Key Takeaways James Wynn recently opened a 40x leveraged short position on Bitcoin. His position involves 2.69 BTC,…

Major Whale Opens Significant 20x Leveraged Positions in ETH and BTC
Key Takeaways Whale 0x049b has executed large 20x leverage positions on 9,256 ETH and 282.47 BTC, totaling over…

New Whale Activity: 33,998 ETH Withdrawn from Kraken
Key Takeaways A new Ethereum whale with the address starting 0xD77 has withdrawn 33,998 ETH from Kraken. The…
