The problem DeLogi(Decentralizing Logistics) solves

Problem Statement:
The decentralized logistics platform aims to address the following problems in the industry:

Lack of authenticity verification: In traditional logistics systems, it is challenging for companies to verify the authenticity of raw materials and track their journey accurately. This creates opportunities for counterfeit products and raises concerns about quality control and transparency.

Data tampering and manipulation: Existing centralized systems are vulnerable to data tampering, as records can be altered or deleted without leaving any trace. This makes it difficult to maintain a reliable and immutable record of the product's journey and history.

Limited transparency and trust: Customers and stakeholders often lack trust in the supply chain due to the lack of transparency and verifiable information. This leads to skepticism about the origin, quality, and handling of products.

Inefficient traceability: Traditional traceability methods rely on paper-based documentation or centralized databases, which are time-consuming, error-prone, and can result in delays and inefficiencies during audits or recalls.

Counterfeit prevention: The prevalence of counterfeit products poses a significant challenge for companies and consumers. Current systems lack robust mechanisms to prevent counterfeiting and protect brand reputation.

Inaccurate and incomplete information: Accurate and comprehensive data about the journey of products, including timestamps, locations, and environmental conditions, is crucial for quality control, compliance, and regulatory purposes. However, obtaining reliable data throughout the supply chain is often difficult.

Challenges I ran into

The flow chain was very new to use for me, I faced a lot of issues, getting a grasp of it. One of the major errors, which held me on for the longest was rather a silly one, there was a error which was constantly returning a error 404 api call and I had refactored the entire code like thrice, ran it through ChatGPT as well, yet no luck. finallly, after like 16-17 hours I sat down, and I had my cousins over, one of whom, just randomly looked at the screen and went like "The spelling of hash is wrong", He was 11. and I just looked at him and saw my entire life turn around, how I just wrote IPFSHash as IPFShassh and this was the longest error. While in the end, recording the demo video, something went wrong with the testnet possibly and our code stopped working, the way it did a day ago, so we kinda figured out an immediate alternative which kind of worked kind of didn't. Another big huddle was ipfs clients, our initial plan was to use Infura, as I had experience with it, but infura started throwing multiple errors, so we decided to switch to a new service called Piniata, which was really new and hence the lowest number of tutorials ever available for a technology, we kinda read the incomplete docs, which were not helpful at all, spent around 7-8 hours trying to do something or the other, at the end we ended up with it working well, and we haven't been more proud of ourselves, ever.