The development of CryptoSafeSend posed several challenges that I encountered throughout the process:

1. Wallet Integration and Smart Contract Communication
   One of the initial challenges was achieving seamless connectivity between MetaMask and my deployed smart contract. This endeavor involved addressing issues such as ABI mismatches and incorrect contract addresses, which resulted in transaction failures without informative error messages.
   To address this, I meticulously verified the ABI export from Remix and cross-checked the contract address on both my local Ganache network and the Polygon Mumbai testnet to ensure consistency.

2. Faucet Access Limitations
   Conducting tests with actual blockchain transactions necessitated the acquisition of testnet tokens; however, several faucets imposed stringent social media requirements or imposed limitations on the number of tokens that could be claimed.
   To mitigate this issue, I established a custom RPC and identified a public faucet that did not enforce such restrictions, thereby providing the necessary flexibility for ongoing testing.

3. Conditional Fund Release Logic
   A particularly complex challenge involved developing a smart contract capable of holding funds in escrow until the correct passcode was provided. The contract needed to ensure the following:

   • Funds could be claimed only once.
   • The intended recipient exclusively held the right to claim the funds.
   • Any unclaimed funds were eligible for refund.
     After multiple iterations and thorough research, I successfully implemented an effective solution utilizing mapping-based logic, hashed passcodes for verification purposes, and a robust refund mechanism.

4. Non-Clickable UI Elements
   A significant bug I encountered was related to the homepage cards, which were designed to be clickable but did not route correctly. This issue persisted despite having implemented the appropriate logic.
   I resolved this challenge by rewriting the card components to utilize React Router’s

   <Link>

   functionality, ensuring that the entire card became clickable and routed correctly.

5. Airdrop Feature and Secure Claiming Mechanism
   The implementation of an airdrop feature was a goal for the platform; however, I recognized the importance of ensuring security to prevent double claiming or replay attacks.
   Consequently, I updated the smart contract to accommodate code-based redemptions, ensuring that each recipient could claim their tokens only once through the verification of hashed passcodes prior to the release of funds.