# Vision & Origin Story The founders nearly lost hope, until they discovered MegaETH, a then-emerging Ethereum L2 that broke all the rules in the name of performance and fairness. The Mega Buddies team was struck by MegaETH’s ethos: it promised to “Make Ethereum Great Again” by delivering Web2-like speed while shunning conventional limitations. More importantly, MegaETH’s leadership demonstrated a maverick spirit that resonated with Mega Buddies’ ideals – the MegaETH team even turned down a $1 billion VC investment offer in favor of community-focused funding. Instead of chasing inflated valuations, MegaETH raised funds through a fair community NFT sale, accumulating roughly $27 million from supporters at a modest \~$540M network valuation. This bold stance proved that MegaETH was “the only true fit” for Mega Buddies: a blockchain that embodies rebellion, innovation, and community empowerment. \ Thus, Mega Buddies was born on MegaETH in early January 2025, forged by frustration with old norms and inspired by the possibility of a new way. The narrative begins with the founders stepping away from Silicon Valley’s comforts, banding together as “outlaws” against the established order. Armed with a vision of meaningful community ownership, they launched Mega Buddies on MegaETH – not simply as a collection of pixel art, but as a rallying cry for those who believe crypto can be more. In this origin story, the Mega Buddies founders are akin to revolutionaries, rejecting the gatekeepers of tech and crypto and choosing to build on a chain that values breakneck innovation and community-first principles. This rebellious energy and innovative spirit set the tone for everything that follows. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mega-buddies.gitbook.io/mega-buddies-docs/getting-started/quickstart.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.