Blockchain Data Storage Integrity via Digital Signatures
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In centralized blockchain-type ledgers, users lack assurance that their data remains unaltered during storage, as the database server is not directly accessible, and they cannot verify the integrity of their data.
Innovation Solution
The application server digitally signs user data in a trusted execution environment using user private keys, generating data records with digital signatures, which are then stored in a centralized blockchain-type ledger, ensuring tamper-resistance and user data storage security by using a hash-based block generation method.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If data is stored in a centralized database server through an application server, then data storage is simplified and centralized, but users cannot verify the integrity of their data during storage
Solution Approach 1:
The system performs preliminary actions by computing and storing hash values of user data before the actual storage operation. The application server computes the hash value of user data, sends it to the database server for storage, and then stores the actual data. This preliminary hash computation enables subsequent integrity verification without requiring users to trust the storage process blindly.
Solution Approach 2:
The patent introduces hash values as an intermediary element between user data and the storage system. Instead of users directly verifying stored data, they verify the integrity through hash value comparison. The database server stores both the hash value and the actual data, acting as a mediator that provides verification capability while maintaining centralized storage simplicity.
2Reliability
If users directly access the database server to verify data, then data integrity can be verified, but system security and data privacy are compromised
Solution Approach 1:
The patent extracts the verification capability from the actual data storage system. Instead of requiring users to access the database server directly to verify data integrity, the system extracts and stores only the hash values separately. Users can verify integrity by comparing computed hashes with stored hashes without needing to access or trust the database server's stored data, thus separating verification from storage access.
Solution Approach 2:
The system changes the verification parameter from direct data comparison to hash value comparison. By transforming the verification process from checking actual data content to checking hash values, the system enables integrity verification while maintaining security. The hash function transforms complex data into compact representations that can be verified without exposing sensitive information.
3Reliability
If digital signatures are added to data records, then data authenticity and integrity are enhanced, but processing time and computational overhead increase
Solution Approach 1:
The system applies partial action by implementing digital signatures selectively rather than for all data operations. The patent shows that digital signatures are applied to specific data records that require enhanced authenticity verification, while other data operations can proceed without full signature verification. This partial application reduces overall processing overhead while maintaining security for critical operations.
Solution Approach 2:
The system performs preliminary action by pre-computing and storing digital signatures along with the data records. Instead of computing signatures on-demand during verification, the signatures are generated and stored in advance when data is initially stored. This preliminary computation shifts the time cost to the storage phase, enabling faster verification later without repeated computational overhead.
Data Source
AI summary
This disclosure relates to blockchain-type data storage. In one aspect, a method includes receiving, by a database server, multiple second data records. Each second data record includes a first data record having a user identifier and a digital signature of the first data record. Hash values of the second data records are determined. In response to a blockchain-type block generation condition being satisfied, the database server determines two or more second data records to be written in a data block. An Nth data block that includes a hash value and a block height is generated. N is a sequence number of the Nth data block in a sequence of data blocks. When N>1, generating the Nth data block includes determining the hash value for the Nth data block based on the hash values of the two or more second data records and a hash value of a (N−1)th data block.