Masked-Melon

Screenshots

Problem Statement

Survey: 75% of crypto users express concern about exposing wallet addresses. Reasons cited:Fear of privacy breaches, scams, and security risks.Worries include being targeted by scammers, potential loss of anonymity, and compromising personal information.Reflects a growing trend of prioritizing privacy and security in crypto transactions among users.To solve this: Masked-Melons introduces a discreet payment protocol where you can receive funds without revealing your cryptocurrency wallet address. Through our platform, you create a one-of-a-kind payment link that shields your wallet address, ensuring the privacy of your on-chain history. This not only protects your financial details but also keeps your collection of delightful NFTs a secret from the sender.Our Core Features are: -Privacy Supreme: Generate payment links that cloak your wallet address, ensuring your on-chain history remains a mystery. -Sender Secrecy: Say goodbye to prying eyes! Senders won't catch a glimpse of your wallet's wealth or your whimsical NFT collection -No Wallet Exposure: Never worry about exposing your wallet address again! Mask-Melon ensures that only you hold the key to your crypto kingdom.Linkshttps://github.com/harsh-mr/Mask-Melon

Solution

Searching through the block: Initially, we encountered the challenge of sifting through extensive block histories to gather all commitments. To streamline this process, we optimized our approach by narrowing our block search range to a maximum of 1000, simplifying both the search and computational aspects significantly.ZK Dependency Issue: While incorporating ZK-Snarks to generate the proof in the front end, we encountered numerous dependency issues. Seeking assistance from various online resources and engaging in extensive debugging efforts, we successfully resolved these issues.Hash Function Issue: Initially, when constructing the Merkle tree for chains such as Polygon and Harmony, we employed Poseidon hashing. However, we encountered compatibility issues with ZK-EVM based chains. To address this, we had to switch to a specific version of the Poseidon hash function that was designed to be ZK-friendly.