Offline Evidence Capture With Hash-Audited Blockchain Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for capturing and storing evidence on end-user devices fail to meet evidentiary requirements of a court of law, particularly when network connectivity is unavailable, and lack secure, immutable, and verifiable mechanisms for data sharing and editing.
Innovation Solution
A method involving secure hash values and Blockchain technology to create an immutable record, allowing data to be stored temporarily on end-user devices and later verified by a central server, with changes tracked and validated through Blockchain transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If evidence is stored on end-user devices for secure capture, then ease of operation is improved, but reliability deteriorates because the storage does not meet evidentiary requirements of a court of law
Solution Approach 1:
A server system acts as an intermediary between the end-user device and the Blockchain service. The server receives data from the end-user device, validates hash values to ensure integrity, stores data temporarily, and then commits verified data to the Blockchain. This intermediary approach allows evidence to be conveniently captured on end-user devices while ensuring court-admissible reliability through server-mediated verification and Blockchain immutability
Solution Approach 2:
The system segments the evidence storage process into distinct phases: initial capture on end-user device, temporary storage on server, and final immutable storage on Blockchain. Each segment serves a specific purpose - end-user devices provide convenient capture, servers provide verification and temporary storage, and Blockchain provides permanent immutable storage. This segmentation resolves the contradiction by allowing each component to optimize for its specific function
2Ease of operation
If data is stored temporarily on end-user devices until connectivity is re-established, then ease of operation is improved, but reliability deteriorates because the storage mechanism is not secure for evidentiary purposes
Solution Approach 1:
The system performs preliminary actions by capturing and temporarily storing evidence on end-user devices when connectivity is unavailable. The end-user device stores data locally with the understanding that it will be verified and transferred to the Blockchain once connectivity is restored. This preliminary capture maintains operational ease while the subsequent server verification and Blockchain commitment ensure reliability
3Reliability
If hash values are generated and stored on the Blockchain, then reliability is improved for verification purposes, but device complexity increases due to the need for hash generation and Blockchain integration
Solution Approach 1:
The system extracts the complex hash generation and Blockchain integration operations from the end-user device and relocates them to the server system. The end-user device only needs to capture data and transfer it to the server, while the server handles the computationally intensive tasks of hash generation, validation, and Blockchain communication. This extraction maintains reliability through Blockchain verification while reducing device complexity
4Productivity
If evidence is captured in situ at the scene of crime, then productivity is improved by immediate capture, but reliability deteriorates because network connectivity may be unavailable for verification
Solution Approach 1:
The system enables preliminary evidence capture at the scene of crime without requiring immediate network connectivity. Evidence is captured and stored on the end-user device in situ, maintaining productivity by allowing immediate capture. Once connectivity is restored, the server verifies the evidence through hash comparison and commits it to the Blockchain, ensuring reliability for court admissibility
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of facilitating generation of a verifiable and immutable record. The method comprises, at a user device, obtaining a data file, generating an audit file for the data file, and separately hashing the data file and the audit file. The method further comprises storing the data file, the audit file and the hash values in a secure memory location, access to which is controlled, and preventing changes to the stored data by a user. When access is available to a remote server system, the stored data is sent to the remote server system and, in response, a notification received over confirming that the remote server system has verified the data file and the audit file and has created an immutable record of both. The user is then permitted to change the stored data file and or audit file in the secure memory location.