Answers are grounded in this paper and cite their sources.
Digital Product Passports (DPPs) must preserve reliable component histories across repair, removal, and reuse, even when lifecycle updates are concurrent or reported retrospectively. This paper proposes an integrated model combining permanent identifiers, temporal containment relationships, causal versioning, and explicit acceptance decisions to ensure consistent lifecycle records. The model was implemented using Hyperledger Fabric, Java chaincode, and a Spring Boot REST API. Evaluation included blockchain-only and end-to-end tests covering concurrent lifecycle operations, transaction performance, historical reconstruction, and idempotency checks. The results confirmed correct lifecycle transitions and reconstruction of accepted product states. At 200 concurrent clients, sustained UPDATE and direct GET throughput reached 348.61 and 1210.98 requests/s, respectively. Across three contention experiments, 265 of 300 INSTALL requests were accepted, with no inconsistent component placements detected. On an expanded ledger, historical reconstruction averaged 1562.3 ms with one client and 4135.0 ms with ten clients, revealing a scalability limitation. All experiments were conducted on a single-machine Hyperledger Fabric prototype. Improved historical indexing and evaluation in physically distributed environments remain for future work.
No takes yet. Share an insight, caveat, or question.
Miron et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: