Project Β· supply-chain
mycelix-supplychain
- How you run it
- not recorded
- Holochain version
- 0.6.0
- Activity
- archived
- Checked
- 27 October 2026
What is mycelix-supplychain and what is it for?
mycelix-supplychain is a software project for keeping track of where goods come from, turning production and shipping events into signed records that link back to earlier ones. It exists so that the history of a product can be checked from those records instead of being taken on trust from one company's database.
mycelix-supplychain is the supply-chain part of Mycelix, a wider set of projects from Luminous Dynamics; its README names mycelix-identity, mycelix-dkg and mycelix-consensus as related work. It describes the supply-chain effort as verifiable provenance: software that turns everyday production and shipping events into signed records, so the history of a good can be checked afterwards. The repository is archived, so what follows describes an early reference implementation rather than software in active use.
The idea is a chain of evidence for physical things. When something happens that a supply chain needs to remember β a batch produced, a shipment moved β the software signs a record of it and links that record to the ones that came before, producing a portable credential that can travel with the product. A later reader can follow those links back and check the signatures, so provenance does not rest on one company's private database alone.
The README's worked example posts a sample "batch produced" event to a locally running service and gets back a claim with proofs. Uses it lists include tracing goods end to end, keeping auditable evidence of certifications and inspections, and working out which shipments a recall affects. The OpenAPI description, JSON schemas and example files in the repository's specs folder are where to read further.
How to get it
As a library
- Clone the repository and change into rust/service.
- Run the service from source with cargo run.
- Send an event to the service's local endpoint β the README uses the sample batch_produced.json from specs/examples.
Source: https://github.com/Luminous-Dynamics/mycelix-supplychain
Questions people ask
- Is mycelix-supplychain maintained?
- The GitHub repository is archived, and its README describes the work as an alpha reference implementation for pilots whose APIs may change. The notes here describe that early implementation rather than software in current use. source
- How do I run it?
- The README's quickstart runs the Rust service from rust/service with cargo, then posts an event to a local HTTP endpoint. Because the repository is archived, compatibility with current tooling is not guaranteed. source
- What is a Product Passport?
- The README describes exporting "Product Passport" bundles that gather a product's signed records so their lineage and signatures can be verified. source
From 1 public source, checked 23 September 2026.
Try mycelix-supplychain
- Code on GitHubOpen on GitHub βLast change 1 February 2026.
- ReleaseNo GitHub release recorded.
- The project's own files do not say how it is run.
Details & sources
Evidence
- Last change
- api.github.com/repos/Luminous-Dynamics/mycelix-supplychainlisted by a third party Β· seen since 20 October 2026 Β· github.repository@1
- Activity
- api.github.com/repos/Luminous-Dynamics/mycelix-supplychainlisted by a third party Β· seen since 20 October 2026 Β· liveness@1
Compatibility
- hdk
- 0.6.0 Β· holochain/Cargo.toml @ 7227c43
- hdi
- 0.7.0 Β· holochain/Cargo.toml @ 7227c43
- holochain-client
- β
- happ.yaml
- present Β· holochain/happ.yaml @ 7227c43
- web-happ.yaml
- absent