# Experienced Builders Mega Buddies is developed by a team of anonymous yet seasoned individuals who have come together under a shared vision. In the true spirit of decentralization and letting a project stand on its own merits, our team has chosen to remain pseudonymous for now. However, anonymity does not mean inexperience. On the contrary, our core members bring a unique blend of backgrounds. #### Silicon Valley Tech Veterans Several team members cut their teeth in the tech industry, having worked at major tech companies and nimble startups alike. They’ve built user-centric products that scaled to millions of users (from mobile apps to social platforms). This gives Mega Buddies a strong foundation in product design, user experience, and growth strategy. We understand how to build robust applications and engaging front-ends, which is why, for example, our games and bots feel polished and our platform runs smoothly. #### Crypto-Native Experts. Other members have been deep in the crypto/web3 space for years – contributing to open-source blockchain projects, running DAOs, and even launching prior NFT or DeFi projects. They bring crucial knowledge of smart contract development, tokenomics design, and community governance. ### Why Anonymous? The decision to remain anonymous (at least in the early phase of the project) is intentional. We want the focus to be on the product and community rather than on the individuals. In many crypto projects, personalities can overshadow purpose – we wish to avoid that. Additionally, anonymity is a nod to crypto’s roots (like Satoshi Nakamoto’s anonymity or the culture of pseudonymous developers on forums) and it fits our theme of early internet nostalgia. It’s almost as if the team themselves are like Buddy characters – known by cool nicknames and avatars rather than real-world identities. We believe this adds to the mystique and fun, without compromising accountability. To address trust, we are open about our credentials and we let our work speak for itself. Over time, as the project matures, the team may gradually reveal more (or even fully dox) if needed, but our hope is that the community’s trust is earned through consistent delivery and transparency in process, rather than just identity. ### Cultural Blend. The mix of Silicon Valley and crypto-native culture in our team results in a best-of-both-worlds approach. From Silicon Valley, we carry values of user-centric design, rapid iteration, and disruption – but we reject the parts of that culture that became overly centralized or profit-focused. From the crypto-native side, we carry values of decentralization, open collaboration, and meme-driven growth, while striving to avoid the pitfalls of chaos or lack of structure that some purely decentralized teams face. The team often jokes that Mega Buddies is what happens when a hackathon project by nerdy friends accidentally gets the soul of a punk rock band. ### Advisors and MegaETH Connection. While the core team is small, we’re not building in isolation. We have informal advisors from the MegaETH community – including some folks involved in MegaMafia projects or even MegaETH’s development team – who we consult for guidance. Their insights ensure we remain aligned with MegaETH’s roadmap (for example, if MegaETH is introducing a new feature or standard, we want to be early adopters). They also help with introductions for collaborations. These advisors are not in control of Mega Buddies, but their experience in both crypto and community-building is invaluable. In summary, the team behind Mega Buddies is driven, capable, and deeply passionate about the mission. We maintain a low profile individually because we want Mega Buddies to develop its own identity – one that eventually is run by the community. However, we are committed to the project’s success full-time. Our promise is that we will continue to ship features, nurture the community, and steer Mega Buddies in a direction that stays true to its values. In every interaction, even if our real names aren’t known, our integrity and dedication should be evident. We consider ourselves members of the Mega Buddies community first, team second – building this world alongside everyone else. --- # 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/team/experienced-builders.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.