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

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...

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

The other side of Musk's trillion-dollar fortune: 85% cannot be sold

The U.S. government prohibits foreigners from using Fable 5, Anthropic issues a rebuttal

Citibank releases "2030 Asset Tokenization Market Outlook": 6 major trends may create a $8.2 trillion market

The trillion-dollar valuation test: Are the three major super IPOs a celebration for tech stocks or a nightmare for the crypto market?

Morning Report | Digital Asset completes $355 million financing led by a16z Crypto; Meta completes operational separation from Manus

a16z Crypto Partner: Cash flow is the moat

Cryptocurrency market makers collectively seek change as it becomes increasingly difficult to make money

How TradeXYZ, xStocks, and Alpaca break down the SpaceX IPO into three different strategies

$75 billion in risk asset redistribution: How will SpaceX's IPO affect U.S. stocks and Bitcoin?

Why Is BlackRock Investing $5 Billion in the SpaceX IPO?

Morning News | CME Group launches Nasdaq Cryptocurrency Index futures; Asset management giant Janus Henderson strategically invests in Ethena

Bitcoin Layer 2 Network Botanix: Why Did We Choose to Dissolve?

Why did Oracle deliver the strongest financial report in history, yet its stock price fell?

When the P2P illicit funds from ten years ago turned into 60,000 bitcoins

Dialogue with OmenX Founder: Why does the prediction market need an evolution from "spot" to "derivatives"?

