Blockchain Salt Storage for Transaction Integrity Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing transaction processing systems are complex and prone to halting due to changes in approval workflows, requiring re-coding and re-deployment of large software components, and face challenges in verifying the integrity of transaction data due to salt value rotation, necessitating a more efficient and reliable method for transaction processing and integrity verification.
Innovation Solution
A transaction exchange platform utilizing a blockchain to store salt values and timestamps, allowing microservices to generate hash signatures for transaction objects, ensuring data integrity and enabling dynamic reconfiguration of workflows and microservices for efficient transaction processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If salt value rotation is implemented to enhance security, then transaction security is improved, but the ability to verify transaction data integrity is lost
Solution Approach 1:
The patent stores salt values in a blockchain before they are rotated. This preliminary action preserves historical salt values, enabling verification of transaction data integrity even after salt rotation occurs. The blockchain acts as a pre-established repository that maintains the linkage between transactions and their original salt values.
Solution Approach 2:
The blockchain serves as an intermediary between the salt value rotation mechanism and the integrity verification process. It mediates by storing and providing access to historical salt values, allowing the system to rotate salts for security while maintaining the ability to verify transaction integrity through the blockchain's stored salt values.
2Adaptability or versatility
If monolithic software services are used to accommodate multiple transaction types, then system comprehensiveness is improved, but system complexity and deployment difficulty increase
Solution Approach 1:
The patent divides the monolithic payment processing system into separate microservices, each handling specific transaction types or processing steps. This segmentation reduces overall system complexity while maintaining versatility, as each microservice can be independently developed, deployed, and modified without affecting the entire system.
Solution Approach 2:
The patent implements a universal configuration mechanism that allows microservices to be dynamically configured to handle different transaction types. Through standardized interfaces and configuration files, the system achieves multi-functionality without requiring each microservice to be hard-coded for specific transaction types, thus reducing complexity while maintaining adaptability.
3Adaptability or versatility
If changes are made to transaction approval workflows, then workflow adaptability is improved, but re-coding and re-deployment requirements increase complexity
Solution Approach 1:
The patent implements dynamic configuration of transaction approval workflows through configuration files that can be modified without re-coding microservices. The system reads workflow definitions from external configuration sources, allowing workflows to be changed, added, or removed by simply updating configuration files and re-deploying the microservices, which then pick up the new configurations.
Solution Approach 2:
The patent uses configuration files as copies of workflow definitions that can be replicated and modified independently of the actual microservice code. These configuration copies allow workflow changes to be made by updating the configuration files rather than modifying the underlying software code, simplifying the deployment process.
Data Source
AI summary
Aspects described herein may relate to a transaction exchange platform using a streaming data platform (SDP) and microservices to process transactions in accordance with corresponding workflows. The transaction exchange platform may generate configuration transaction objects to reconfigure microservices with salt values and time periods of salt value validity. Further, the microservices may retrieve transaction objects from a streaming data platform and generate hash signatures as part of determining the validity of the transaction objects. Furthermore, in some aspects the microservices may retrieve salt values for transaction objects that cannot be verified due to the absence of a hash signature. The salt values may be retrieved from a blockchain associated with the streaming data platform and may be used to update the microservice to include the salt value.