The problem Minibuild solves

MiniBuild addresses the steep learning curve and accessibility barriers in blockchain development. It provides an interactive, gamified platform where users can learn to build on Base through hands-on challenges, tutorials, and mini-projects. This makes learning safer and easier by offering a guided environment with immediate feedback, reducing the risks of real-world errors like smart contract vulnerabilities. Users can earn $MB tokens as rewards, incentivizing participation and turning education into an engaging experience. People can use it to:

• Acquire practical blockchain skills without prior experience.
• Prototype and test ideas in a low-stakes setting.
• Collaborate and share mini-projects within the community.
  Overall, it democratizes blockchain education, making it fun and rewarding for beginners and experienced developers alike

Challenges I ran into

One major hurdle was deploying the Farcaster Mini App to Vercel, as the initial attempts failed due to the absence of a detectable app or pages directory in the root, leading to build errors. I overcame this by running the deployment command from the minibuild subdirectory, which contains the Next.js structure, ensuring Vercel correctly identified the project setup.

Another challenge was fixing broken image URLs and the infinite loading splash screen. This was resolved by installing the @farcaster/miniapp-sdk , adding absolute paths for images in layout.tsx , and implementing sdk.actions.ready() in page.tsx to signal app readiness.

Additionally, configuring the app icon and sharing embeds required updating metadata to comply with Farcaster's specifications, including adding fc:miniapp and fc:frame tags with proper version and action types.

Smart Contract Address(es)

The project is powered by the following smart contracts on Base:

• MiniBuild Token Contract: (Please provide the actual address if available; based on the app's token-earning feature, it likely involves an ERC-20 contract for $MB tokens. If not deployed yet, this can be updated post-deployment.)
• Challenge Verification Contract: (Similarly, a contract for onchain proof of challenge completion.)
  Note: Ensure these are the core contracts, not token addresses. If specific addresses are missing, I recommend deploying and verifying them on Basescan.

Other Onchain Proof

• Onchain activity includes user interactions with challenges, token minting, and leaderboard updates verifiable on Base. For example, transaction hashes from token rewards can be queried on Basescan.
• Traction is shown through deployments and interactions; for instance, the app's webhook at /api/webhook handles onchain notifications, with potential logs of user engagements.
• Additional proof: NFT mints or badges earned via the app's gamified system, trackable on OpenSea or Base explorers.