Blockchain Immutability via Remote Cryptographic Signing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain validation techniques rely on recalculating hash values, which are computationally intensive and do not adequately prove the immutability of blockchain history, especially in centralized private blockchains where alterations can be more feasible.
Innovation Solution
A system that generates and validates blockchain blocks using a hash pointer system, where block information including a timestamp, block ID, and blockchain ID is transmitted to a remote computing device for signing and validation, allowing for verification without accessing user data and using a smaller, less complex data set compared to traditional hash value validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional hash value validation is used, then blockchain block validation can be performed, but the computational complexity is high and immutability cannot be adequately proven
Solution Approach 1:
The patent segments the blockchain validation process into two independent components: (1) cryptographic signing of block information by a remote device, and (2) verification of the signature against the block information. This segmentation allows the system to prove immutability through signature validation rather than computationally intensive hash recalculation, reducing overall computational complexity while maintaining reliability.
Solution Approach 2:
The patent applies preliminary action by having the remote computing device sign the block information (including hash pointer, timestamp, block ID, and blockchain ID) at the time of block creation. This pre-signing allows future validation to simply verify the signature without re-computing hash values, thereby proving immutability with minimal computational effort.
2Reliability
If hash value recalculation is used for validation, then block integrity can be checked, but the process is computationally intensive
Solution Approach 1:
The patent creates a cryptographic copy (digital signature) of the block information that serves as proof of integrity. Instead of recalculation, the system verifies this signature copy against the original block information. This copying approach provides reliable validation while consuming minimal computational energy compared to hash recalculation.
3Ease of operation
If centralized control structure is used in private blockchain, then easier control is achieved, but immutability becomes harder to prove
Solution Approach 1:
The patent introduces a remote computing device as an intermediary that independently signs block information. This intermediary provides cryptographic proof of immutability without requiring decentralized consensus, thus maintaining ease of centralized control while establishing reliable immutability proof through the intermediary's digital signature.
Applied Scientific Principles
This section explains which scientific principles are used to turn an abstract innovation direction into a practical engineering solution.
Function Achieved in This Case
This approach enables efficient and trustworthy validation of blockchain blocks, reducing computational complexity and ensuring the immutability of blockchain data without requiring access to underlying user data, thus enhancing trust and security in blockchain systems.
Implementation Method 1
The remote computing device may receive the block information and sign the block information using a private key or other cryptographic technique
Implementation Method 2
The computing device may apply a public key (e.g., a public key corresponding to the private key used to generate the signed block information) to the sign block information to obtain validation data
Data Source
AI summary
The present disclosure provides systems, methods, and computer-readable storage media having functionality to prove immutability of blockchains without accessing user data. A user may submit data for storage to a data management server and the data management server may generate one or more data records corresponding to the data at a database and one or more blocks at a blockchain, each block corresponding to of the data records. Block information associated with the generated blocks may be transmitted to a remote computing device for storage at a database. Prior to storing the block information, the remote computing device may sign the data using a private key or other cryptographic technique. To validate a block, raw block information may be retrieved from the blockchain and compared to the signed block information. If the signed block information matches the raw block information, the block may be determined to be valid (e.g., unchanged).


