Hyperledger Supply Chain
  • Hyperledger Supply-Chain
  • Hyperledger Overview
  • Business Case
  • Implementation
    • System Architecture
    • Governance
    • API Reference
    • Deploy/run dApp
    • User Interface
    • Development Tools
  • Contact
  • Appendix
  • MIT License
Powered by GitBook
On this page
  • About the project
  • Objective
  • Top factors considered for the project

Was this helpful?

Hyperledger Supply-Chain

Food supply-chain is a network to connect participants across the food supply through a permissioned, permanent and shared record of food system data.

NextHyperledger Overview

Last updated 3 years ago

Was this helpful?

About the project

Food supply chain is a Hyperledger blockchain-based solution that solves the tracking and tracing of food products in the supply chain so that any product can be traced back to its roots. Building a food tracking system is an effective way to solve food safety issues. Blockchain is well suited for building product tracking systems because of the inherent immutability and consistency of stored data maintained by encryption and consent mechanisms. We propose to build a tracking system that will unite all suppliers, including food warehouses, food processors, and grocery stores, into one store. Create business correspondence with this chain to enable reliable food tracking without disrupting your food supply chain. Implementation and testing are carried out to evaluate the performance of the proposed monitor. The result is a customizable suite of solutions that can increase food safety and freshness, unlock supply chain efficiencies, minimize waste, enhance your brand’s reputation, and contribute directly to your bottom line.

Objective

Bring transparency to the food supply chain with Hyperledger Fabric.

Top factors considered for the project

  • Security (protect API authentication, how to store data, API is the bottleneck)

  • Operation (VM (under/over resources), Kubernetes)

  • Cost (how much to spend, Firewall, IDS, etc)

  • Reliability (what if something goes down? Frontend and blockchain layers)

  • Performance (kind of storage, VM configuration, index in CouchDB, etc)