USB Build Deployment Using NFT Hash Tokens for Zero-Trust Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating software on resource machines, such as ATMs, via USB flash drives are vulnerable to tampering and lack a reliable verification system, necessitating a zero-trust technical method for secure deployment.
Innovation Solution
Utilizing non-fungible tokens (NFTs) to securely deploy software on resource machines by embedding a first NFT in a USB flash drive and generating a second NFT during interaction, combining them to create a third NFT that manages deployment with predefined rules, ensuring secure and verified deployment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If USB flash drives are used to transfer build packages, then ease of operation is improved, but reliability deteriorates due to vulnerability to tampering
Solution Approach 1:
A first NFT is embedded into the USB flash drive before it is used to transfer the build package. This preliminary action creates a cryptographic seal that will later be verified against a second NFT generated on the resource machine, preventing tampering during transfer while maintaining the simplicity of USB-based deployment.
Solution Approach 2:
Non-fungible tokens (NFTs) serve as an intermediary verification mechanism between the build package and the resource machine. The NFTs act as cryptographic mediators that prove the integrity and authenticity of the build package without requiring complex verification systems, thus maintaining ease of operation while improving reliability.
2Reliability
If a zero-trust verification system is implemented, then reliability is improved, but device complexity increases
Solution Approach 1:
The complex verification logic is extracted from the resource machine and implemented in the NFT smart contract on the blockchain. This extraction allows the resource machine to have a simple verification process (comparing NFTs) while maintaining zero-trust reliability, as the heavy cryptographic verification is performed by the blockchain network rather than the local device.
Solution Approach 2:
Instead of implementing complex verification systems on each resource machine, the patent uses cryptographic copies (NFTs) of the build package that can be easily verified. The first NFT is a cryptographic copy embedded in the USB drive, and the second NFT is a cryptographic copy generated on the resource machine, allowing simple comparison-based verification.
3Object-affected harmful factors
If NFT verification is implemented, then security against malfeasance is improved, but manufacturing precision requirements increase
Solution Approach 1:
The NFT verification system is self-service in that the blockchain network automatically performs the verification of build package integrity. The smart contract on the blockchain autonomously compares the first and second NFTs to verify authenticity, eliminating the need for manual verification processes and reducing the precision requirements for human operators while maintaining high security against malfeasance.
Data Source
AI summary
Systems, computer program products, and methods are described herein for secure apparatuses to share and deploy machine build programs utilizing unique hash tokens. The invention includes the steps of transforming a resource machine build-program into a first non-fungible token (NFT1) via a resource machine build orchestration module, embedding NFT1 into a flash drive using a flash drive preparation module, generating a second non-fungible token (NFT2) during an interaction of a resource machine with the USB flash drive via a dynamic NFT generator module, wherein NFT2 includes data representing an ownership certificate for the resource machine build owned by a vendor, generating a resultant integrated non-fungible token (NFT3) via a dynamic smart contract module, wherein NFT3 is generated by combining NFT1 and NFT2, and activating and deploying the resource machine build-program on the resource machine via a build activation module, wherein the activation is triggered by the generation of NFT3.