# Minting Strategy & NFT Distribution Mega Buddies will launch a collection of unique Buddy NFTs, and our minting strategy is carefully designed for fairness, inclusivity, and alignment with the MegaETH community. Instead of a chaotic free-for-all or a heavily insider-gated launch, we’re dividing the mint into distinct phases to ensure a wide and fair distribution. The breakdown will be roughly as follows ### GTD Whitelist Early Supporters & Contributors. A portion of the Buddies supply is allocated to whitelisted addresses. These include early community members, contributors in the MegaETH ecosystem, and partners who share our vision. By rewarding early supporters with guaranteed mints, we acknowledge those who helped bootstrap the community and align incentives with long-term holders. Notably, our community Ambassador Program (see Section 5) allows active participants to earn whitelist spots through contributions, ensuring the whitelist is populated by true believers and creators in the community, not just insiders or friends of the team. ### FCFS Whitelist First-Come, First-Served. There are no significant differences from the GTD stage, except for the distribution method. Here, the allocation of wallets slightly exceeds the number of places for minting. This allows us to reach a wider community ### Public Sale First-Come, First-Served. The next segment of Buddies is made available in an open public sale, operating on a first-come, first-served (FCFS) basis. This FCFS round ensures that after rewarding our core supporters and running the raffle, there’s still a significant opportunity for the broader public to join in. We expect high demand, so we’ll implement safeguards (like per-wallet mint limits and bot protection) to keep this as fair as possible. The public sale embodies the permissionless ethos of MegaETH – anyone with interest and quick reflexes can join the Buddy family. ### Team & Ecosystem Allocation A very small allocation (a single-digit percentage of the collection) is reserved for the Mega Buddies core team, the MegaETH core team, and an ecosystem treasury. This tiny allocation is a nod to our close alignment with MegaETH’s builders and ensures the people driving the underlying network also partake in the Mega Buddies community, fostering mutual support. These NFTs may also be used for promotional events, cross-project collaborations, or developer incentives within MegaETH. We have kept this allocation minimal – just enough to align MegaETH’s core stakeholders with our success, without introducing sell pressure or any perception of insider advantage. This balanced minting strategy is aimed at cultivating a diverse holder base. One-part of the collection rewards early believers (who often become the community’s backbone), one-part brings in community members via FCFS, and one-part allows open market participation. We have intentionally kept each category approximately equal (with the exception of the tiny team reserve) to avoid over-reliance on any single distribution method. The \~1% team allocation is minimal – just enough to align MegaETH’s core stakeholders with our success, without introducing sell pressure or perceptions of insider advantage. It’s worth noting that these percentages are approximate; we retain some flexibility to adjust if, for example, not all whitelist spots are used or to respond to community feedback. However, the guiding principle stands - Mega Buddies will be distributed as broadly and fairly as possible to seed a large and vibrant community from day one. --- # 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/minting-strategy-and-nft-distribution.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.