The problem MonaLizard solves

Current Web3 marketing tools are great at onboarding new users but fall short on retention, once the rewards are claimed engagement is over, leaving a void in community connection, and having the participant’s name on a list or scoreboard is not enough to feel part of a community.

Monalizard revolutionizes Web3 marketing aiming to create stronger interactions for both new and seasoned dApps users by gamifying interactions and building stronger communities. Through an engaging NFT puzzle game, Monalizard keeps the conversation alive and buzzing, word of mouth has always been king, isn’t it?

Projects will post limited-time puzzle campaigns to airdrop pieces randomly to MonaLizard users on a time basis specified by the project, to improve awareness some pieces will be rewarded to users who complete tasks that bring brand awareness, such as using the dApp or having social media interactions. Bridge a token and mint a piece! or, Join Discord and grab a piece! The possibilities are as varied as the projects themselves.

Each puzzle brings its own dedicated chatroom, a hive of activity where campaign creators and users alike can shill the project, mutually motivating participants to complete the puzzle as soon as possible. It's a place where calls to action like, "Ey Lizards! Follow on Twitter for your next piece, WAGMI!" aren't just messages; they're rallying cries for communal success. Completion brings tangible rewards, with all piece collectors sharing in the bounty from the project's campaign USDC funds.

Monalizard recognizes diverse interests among users, they might want also to participate in different puzzles, a marketplace to trade pieces will be available for them to trade pieces in order to complete different puzzles, and also all chatrooms will be open for users to propose deals on puzzle pieces. After all, it is all about converting users to crypto degens!

This fosters genuine interactions and commitment, embracing crypto's collaborative culture.

Challenges I ran into

Writing the contract part was challenging due to its complexity, especially with the inclusion of various aspects. I was unable to integrate OnChainKit due to its reliance on deprecated dependencies.