MaterialTrace

Demo

About

The problem it solves The Problem MaterialsTrace Solves 1. Lack of Transparency in Material Supply Chains Description: Traditional material supply chains (e.g., steel, raw materials) often suffer from opacity, making it difficult for buyers to verify the authenticity, origin, quality, or ownership of materials. Counterfeit goods, unclear provenance, and lack of trust between suppliers and buyers are common issues. 2. Inefficient and Centralized Trading Processes Description: Current material trading relies on centralized platforms or brokers, introducing high transaction fees, delays, and a lack of direct ownership transfer. Pricing is often static or manipulated, and buyers have limited access to real-time 3. Verification and Trust Issues Among Participants Description: Without a standardized verification process, suppliers and buyers face challenges in establishing trust. Unverified participants can flood markets with fraudulent goods, while legitimate suppliers struggle to prove their credibility.

How it's made

Challenges we ran into 1. Smart Contract Compilation Errors: You might have faced issues like modifier override conflicts when integrating OpenZeppelin’s Ownable contract, requiring adjustments to ensure compatibility with the latest standards. These errors can be tricky to debug but are critical for a functional deployment. 2. Integration with External Services: Setting up uploads to decentralized storage like Pinata or Thirdweb Storage could have led to environment-specific errors, such as missing process objects in the browser, necessitating careful configuration of environment variables and API keys. 3. Dynamic Pricing Implementation: Incorporating Chainlink for real-time pricing might have introduced complexities, such as scaling issues with price feeds or transaction reverts due to incorrect payment calculations, pushing you to refine the logic for accurate ETH conversions. Frontend-Smart Contract Synchronization: Ensuring the frontend accurately reflected on-chain data, like material supply or purchase status, could have been challenging, especially when dealing with incorrect price displays or supply updates that required frontend recalculations. 4. Time Constraints: With the hackathon deadline looming, balancing feature development (e.g., adding Chainlink CCIP for cross-chain functionality) with testing and debugging might have stretched your resources, leading to tough decisions on what to prioritize. 5. Testing and Debugging: Verifying end-to-end flows, such as verification, minting, and buying, on the Sepolia testnet could have been hampered by silent transaction failures or unexpected behavior, requiring detailed transaction tracing on Etherscan.