CPC H04L 9/3236 (2013.01) [G06F 16/27 (2019.01); H04L 63/0876 (2013.01); H04L 9/50 (2022.05)] | 11 Claims |
1. A system for hardware authenticity and traceability, the system comprising;
a distributed trust computing network comprising a plurality of decentralized nodes, each decentralized node having a first memory and at least one first processing device in communication with the first memory, wherein the first memory of the decentralized nodes is configured to store one or more distributed ledgers, each distributed ledger comprising a plurality of blocks of data; and
a first computing platform including a second memory and at least one second processing device in communication with the second memory, wherein the second memory stores a hardware authenticity and traceability sub-system that includes first instructions that are executable by the at least one second processing device and are configured to:
in response to manufacturing each of a plurality of components for a hardware device and measuring authenticity characteristics for each of the plurality of components, generate, for each of the plurality of components, a component-based non-fungible token (NFT) associated with a corresponding component using at least one component identifier and the measured authenticity characteristics of the corresponding component as an input to a hash algorithm,
in response to manufacturing the hardware device including the plurality of components and measuring authenticity characteristics of the hardware device, generate (i) a hardware device-based NFT associated with the hardware device using at least one hardware device identifier and the measured authenticity characteristics of the hardware device as an input to a hash algorithm, and (ii) a principal hardware device NFT using at least one hardware device identifier as an input to the first hash algorithm or another hash algorithm, wherein the principal hardware device NFT links the hardware device-based NFT to each of the component-based NFTs,
in response to updating, during use, the hardware device by adding or deleting a component to the hardware device and re-measuring authenticity characteristics of the hardware device, generate an updated hardware device-based NFT associated with the hardware device using at least one hardware device identifier and the re-measured authenticity characteristics of the hardware device as an input to a hash algorithm, and
communicate the (i) component-based NFTs, (ii) the hardware device-based NFT, (iii) the principal hardware device NFT and (iv) the updated hardware device-based NFT to the distributed trust computing network;
wherein in response to the distributed trust computing network receiving (i) the component-based NFTs, (ii) the hardware device-based NFT, (iii) the principal hardware device NFT and (iv) the updated hardware device-based NFT, the decentralized nodes of the distributed trust computing network are configured to (a) reach a consensus on each of the component-based NFTs, the hardware device-based NFT, the principal hardware device NFT and the updated hardware device-based NFT to verify an authenticity and certifiable state of the corresponding component, the hardware device, the link and the updated hardware device and (b) generate blocks of data within at least one of the one or more distributed ledgers, each of the blocks of data storing (i) one of the verified component-based NFTs, (ii) the verified hardware device-based NFT, (iii) the verified principal hardware device NFT or (iv) the verified updated hardware device-based NFT.
|