MegaMafia 2.0 applicant data: contract size and latency matter more than TPS
Quote129 words
Reads MegaETH's applicant breakdown: many teams value the roughly 512kb deployable contract size (vs 24kb on many EVM chains) and low latency, while 100k TPS scalability is a weaker differentiator.
Key claims
MegaETH deployable contract size is about 512kb vs the 24kb limit on many EVM chains
About 300 teams applied
Raw TPS is a much weaker draw than latency and contract size
Some interesting insights here from the MegaMafia 2.0 applications:
➤ Many applicants (across all verticals) appreciate the support for large contract sizes, allowing for more complex and extensive logic. Specifically, the deployable contract size on MegaETH is around 512kb, which is a substantial increase compared to the 24kb limit on many EVM chains.
➤ The low latency (<10ms block times on L2 but finality dependant on l1) is also an important reason for many, Makes sense imo, especially for consumer apps (need web2-style UX), DeFi (efficient CLOBs), and gaming (need real-time execution).
➤ The sheer scalability of >100k TPS on MegaETH on the other hand seems to be much less of a differentiating factor of the chain for many applicants.
Curious to see which teams @megaeth will be selecting!
QUOTING @megaeth
MegaMafia 2.0 applications have ended Next steps: → ~300 teams submitted → All teams will receive a response by end of week → Next-phase is team interviews → Final selection by 6/16 Here's a breakdown of applicants "Why MegaETH?" and which sector those teams aim to serve. http
MegaMafia 2.0 applications have ended Next steps: → ~300 teams submitted → All teams will receive a response by end of week → Next-phase is team interviews → Final selection by 6/16 Here's a breakdown of applicants "Why MegaETH?" and which sector those teams aim to serve. http
What came next · since 05 Jun 2025
Since then
Zero has written 10 more pieces on MegaETH since this one.