Blockchain Data Verification Smart Contract Origin Check
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In blockchain systems, there is a lack of security in ensuring that a data verification Smart Contract (SC) used for registering data in a distributed ledger is the same one generated within the blockchain, leading to potential misuse or invalid data verification.
Innovation Solution
A data verification apparatus that includes a data verification unit to check if registration data complies with a verification rule, a data control unit to verify if the corresponding program was generated in the blockchain, and a data registration unit to execute the registration process only if the program is valid, ensuring that the data verification SC used is the one generated in the blockchain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a data verification Smart Contract is generated outside the blockchain and used for data registration, then the data registration process can be performed, but the reliability and validity of the verification process is compromised because it cannot be ensured that the verification SC is the one generated within the blockchain
Solution Approach 1:
The patent applies preliminary action by requiring the data verification Smart Contract to be generated within the blockchain system before it can be used for verification. The generation process occurs in advance during blockchain initialization or through authorized deployment, ensuring that only pre-approved verification contracts can be used. This preliminary generation step prevents external or unauthorized verification contracts from being used, thereby maintaining reliability without requiring complex runtime verification of contract origins.
2Reliability
If the data verification SC generation process is restricted to within the blockchain only, then the reliability of verification is improved, but the ease of operation and flexibility of the system deteriorates
Solution Approach 1:
The patent implements feedback by having the data registration Smart Contract automatically verify whether the data verification Smart Contract was generated within the blockchain system. The verification process provides feedback information about the contract's origin, and based on this feedback, the system either permits or rejects the verification process. This automated feedback mechanism maintains reliability by ensuring only internally-generated contracts are used, while preserving ease of operation through automatic verification without requiring manual intervention.
3Reliability
If automatic verification of the verification SC origin is implemented, then the security and reliability of the system is improved, but the processing time and system complexity increases
Solution Approach 1:
The patent applies preliminary action by embedding the verification Smart Contract's origin information and generation status directly into the contract itself during the generation process. This preliminary embedding of verification data means that when the contract is later used for data verification, the origin verification can be performed by simply checking this pre-stored information rather than conducting a time-consuming analysis of the contract's creation history. This significantly reduces the time required for verification while maintaining security.
Solution Approach 2:
The patent uses copying by creating and storing a copy of the verification Smart Contract's generation status and origin information within the blockchain system. Instead of repeatedly verifying the contract's origin from scratch each time it is used, the system stores a verified copy of the contract's generation information that can be quickly referenced. This copying approach enables fast verification while maintaining the security guarantee that only internally-generated contracts are used.
Data Source
AI summary
A data verification apparatus (1) that verifies electronic data to be registered in a distributed ledger (5) includes a data verification unit (8), a data control unit (7), and a data registration unit (10). The data verification unit (8) determines whether or not registration data to be registered in the distributed ledger (5) complies with a verification rule which is a rule for verifying the electronic data to be registered in the distributed ledger (5). The data control unit (7) determines whether or not the data verification unit (8) has been generated in a blockchain. When it is determined that the data verification unit (8) has been generated in the blockchain and when it is determined that the registration data complies with the verification rule, the data registration unit (10) registers the registration data in the distributed ledger (5).