Distributed Logging for Non-Repudiable Transactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing environments lack methods for securely reconciling requests with results among disparate computing systems, leading to potential data tampering and repudiation issues during transactions, which are critical for auditing and integrity in complex computing systems.
Innovation Solution
Implementing distributed logging using blockchain technology, where each party maintains separate logs and a distributed ledger to record and verify transactions, ensuring non-repudiable and tamper-proof records by storing action items and responses in requestor and responder logs, and updating the blockchain log to indicate data transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If distributed logging with blockchain is implemented to ensure transaction integrity and non-repudiation, then reliability and security are improved, but device complexity and operational overhead increase
Solution Approach 1:
The system divides the logging function into separate requestor logs and responder logs maintained by different computing systems, with each log containing specific transaction data relevant to that party. This segmentation allows independent verification while reducing the complexity of a single centralized log.
Solution Approach 2:
The blockchain log acts as an intermediary distributed ledger that receives and verifies transaction data from both requestor and responder logs. This mediator enables trustless verification of transaction integrity without requiring direct trust between the requestor and responder systems.
2Ease of operation
If traditional centralized logging is used to maintain transaction records, then ease of operation is maintained, but vulnerability to tampering and repudiation increases
Solution Approach 1:
The system merges the separate requestor log and responder log with the blockchain log to create a unified, tamper-proof transaction record. Each log contains complementary information that, when combined through cryptographic verification, provides complete and immutable transaction evidence.
Solution Approach 2:
The system changes the state parameters of the logs by applying cryptographic hashing and blockchain consensus mechanisms. Once data is written to the requestor log, responder log, or blockchain log, it becomes immutable through hash chaining and distributed consensus, preventing any subsequent tampering.
3Reliability
If blockchain consensus is required for every transaction verification, then reliability is improved, but processing speed and scalability deteriorate
Solution Approach 1:
The system performs preliminary logging actions by recording transactions in the requestor log and responder log before submitting to the blockchain. This preliminary action captures transaction data locally with immediate effect, while the blockchain verification serves as a subsequent confirmation rather than a blocking step.
Solution Approach 2:
The system implements partial blockchain verification by requiring consensus only for critical transaction elements rather than full transaction verification. This partial action approach maintains security for essential data while allowing faster processing for less critical aspects of the transaction.
Data Source
AI summary
Disclosed herein are methods, systems, and processes for distributed logging for securing non-repudiable transactions. Credentials, request information, response information, and action items generated and received by a requesting computing system and a responding computing system, and transmitted between the requesting computing system and the responding computing system are separately recorded and stored in a requestor log maintained by the requesting computing system and in a responder log maintained by the responding computing system.