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

SharpLink CEO: How to understand that Ethereum developers have just surpassed 1 million?

Morning Report | MiCA grace period expires on July 1; Kalshi's trading volume in the first week of the World Cup breaks $5.1 billion, setting a record

The foundation of SpaceX's trillion-dollar valuation: Who is dividing Musk's annual capital expenditure of tens of billions?

How to exit after asset tokenization?

The stablecoin positioning battle escalates: When compliance is just a ticket to entry, will USD1 become the biggest winner?

A16Z: The sun bears witness, SpaceX is worth 7.5 trillion

Mergers and acquisitions in the cryptocurrency market are exceptionally active

Concerns Behind the Binance Customer Service Controversy

SpaceX Stock Prediction After the IPO: Can SPCX Reach $200 Before QQQ Inclusion?

Congratulations to Carl Moon on His Historic Ferrari Challenge Le Mans Podium Triumph
Crypto influencer and racing enthusiast Carl Moon finished third in the Ferrari Challenge Le Mans Coppa Shell class, marking his best result of the year. As his racing partner and sponsor, WEEX celebrates this remarkable achievement and continues to lead crypto’s journey beyond boundaries, uniting the innovation of digital assets with the passion of motorsport.

Can the CLARITY Act Become Law by July 4? Everything You Need to Know About the Final Battle

France vs Senegal World Cup 2026: Mbappe’s New Era Begins Against a Historic Rival

What is the connection between Huang Zheng of Pinduoduo and blockchain?

Morning Report | Prediction market platforms like Kalshi and Polymarket jointly sue Kentucky over 14.25% trading tax; Bridgewater founder discusses decision-making in the AI era: principled thinking should run parallel to AI, human insight remains irre...

If the AI bubble has already burst, who will truly remain?

Paul Graham: How to Make a Billion Dollars

After 18 years, blockchain has finally started to head towards the main channel

