Blockchain Data Authenticity Verification via Signed Relationship Values
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Decentralized blockchain systems face challenges in verifying the authenticity of external data modifications, as they rely on untrusted peer nodes and lack mechanisms to ensure the reliability and integrity of data changes.
Innovation Solution
A mechanism is introduced where a data provider signs the initial and modified states of a data file with private keys, and a data modifier generates a relationship value describing the modification, which is then signed and stored on a blockchain, allowing smart contracts to authenticate the data file's authenticity by comparing hashes and relationship values.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a decentralized blockchain system is used to store data, then data redundancy and availability are improved, but the ability to verify authenticity of external data modifications deteriorates
Solution Approach 1:
The patent introduces a third-party authentication service as an intermediary between the blockchain and external data sources. This service verifies the authenticity of data modifications by comparing hashes and relationship values, then records the verification result on the blockchain. The intermediary resolves the contradiction by providing a trusted verification mechanism without requiring the blockchain itself to directly verify external data, thus maintaining decentralization while improving authenticity verification capability.
Solution Approach 2:
The system performs preliminary verification of data authenticity before the modification is recorded on the blockchain. The authentication service pre-verifies the relationship between initial and modified data states, generates verification results in advance, and stores them on the blockchain. This preliminary action ensures that only authenticated modifications are recorded, resolving the contradiction by enabling accurate authenticity verification while maintaining the decentralized storage structure.
2Device complexity
If external data sources are trusted without verification, then system complexity is reduced, but security and trust of data modifications deteriorate
Solution Approach 1:
The patent extracts the verification function from the main blockchain system and places it in a separate authentication service. This extraction reduces the complexity of the blockchain itself while adding verification capability. The authentication service operates independently, handling the complex verification logic externally, thus resolving the contradiction by maintaining simple blockchain architecture while improving data modification trust through external verification.
Solution Approach 2:
The system creates a copy of the verification process by having the authentication service independently verify data modifications and record the results on the blockchain. Instead of requiring the blockchain to directly verify external data, the system copies the verification function to a separate service that does interact with external sources. This copying approach maintains blockchain simplicity while ensuring reliable verification of data modifications.
3Stability of the object's composition
If multiple peer nodes store distributed ledger, then fault tolerance is improved, but the ability to ensure consistent data modifications deteriorates
Solution Approach 1:
The patent merges the verification function across all peer nodes by having the authentication service record verification results on the shared blockchain. All peer nodes access the same verified relationship values stored on the blockchain, ensuring consistent data modification verification across the distributed system. This merging resolves the contradiction by maintaining fault tolerance through distributed storage while ensuring modification consistency through a shared verification record.
Solution Approach 2:
The system changes the parameter of verification from local peer-node based to blockchain-based verification. Instead of relying on individual peer nodes to verify data consistency, the system uses the immutable blockchain as the source of truth for verification parameters. This parameter change maintains the fault tolerance benefits of distributed storage while ensuring consistent data modification verification through the immutable blockchain record.
Data Source
AI summary
An example operation may include one or more of modifying content of a data file from an initial content state to a modified content state, determining a relationship value which identifies a relationship of the modified content state with respect to the initial content state of the data file, signing the relationship value with a private key of a data modifier, and transmitting the signed relationship value to a blockchain peer node for inclusion within one or more data blocks among a hash-linked chain of data blocks.