Blockchain Digital Identity for Software Artifact Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In software development projects involving globally distributed teams, identifying discrepancies in complex software applications is challenging due to the black-box nature of hashing algorithms, which can lead to delays, cost overruns, and security vulnerabilities.
Innovation Solution
A blockchain-based digital identity generation and verification method that generates a base composite identity for a software application by extracting sub-application artifacts, defining metadata attributes, generating hash tuples, and storing the composite identity in a blockchain, allowing for the identification and verification of altered components.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional hashing algorithms are used to verify software applications, then verification speed is maintained, but the ability to identify and localize specific discrepancies is lost due to the black-box nature of hashing
Solution Approach 1:
The patent segments the software application into individual artifacts and generates separate digital identities for each artifact. Instead of treating the entire application as a single hashed entity, each artifact (code files, configuration files, documentation, etc.) receives its own digital identity based on its hash value. This segmentation enables precise identification of which specific artifact has been modified or compromised, resolving the black-box limitation of traditional hashing.
Solution Approach 2:
The patent introduces a blockchain-based digital identity system as an intermediary layer between the software artifacts and the verification process. The blockchain stores and manages the digital identities of all artifacts, serving as a trusted mediator that enables verification without requiring direct computation or comparison of complex hash values. This intermediary system maintains verification capability while enabling precise discrepancy identification.
2Reliability
If comprehensive verification of all software artifacts is performed, then security is improved, but processing time and computational resources increase significantly
Solution Approach 1:
The patent performs preliminary actions by generating digital identities for all software artifacts during the build or deployment process, before verification is needed. These digital identities are stored in the blockchain in advance, so that during verification, the system only needs to retrieve and compare pre-computed identities rather than performing complex hash computations on all artifacts. This preliminary preparation significantly reduces verification time while maintaining comprehensive security.
3Measurement precision
If digital identities are generated for all sub-application artifacts with multiple metadata attributes, then verification accuracy is improved, but the complexity of identity management increases
Solution Approach 1:
The patent creates a universal digital identity structure that can accommodate multiple metadata attributes (artifact type, version, creator, timestamp, dependencies, etc.) within a single standardized format. This universal identity framework provides multi-functionality, allowing the same identity structure to handle various artifact types and metadata requirements without requiring separate management systems for each attribute type, thus reducing overall complexity.
Solution Approach 2:
The patent manages complexity by treating metadata attributes as configurable parameters within the digital identity structure. Rather than hardcoding specific attribute types, the system allows metadata parameters to be dynamically defined and adjusted based on the specific artifact and verification requirements. This parameter-based approach enables flexible, accurate identification while keeping the underlying management system simple and adaptable.
Data Source
AI summary
A device may obtain information identifying a base application. The device may extract a set of sub-application artifacts associated with the base application based on structural information associated with the base application. The device may define a set of metadata attributes associated with the set of sub-application artifacts associated with the base application. The device may generate a set of hash tuples for the set of metadata attributes associated with the set of sub-application artifacts associated with the base application. The device may generate a base composite identity of the base application based on the set of hash tuples. The device may store the base composite identity in a blockchain and in connection with storage of the base application in the blockchain to enable subsequent identification and verification of the base application.