Blockchain Consensus Nodes Digest Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain network methods for processing service requests lead to increased computation loads and reduced efficiency due to the need for consensus nodes to encrypt and store service data, which can be avoided by storing only the digest of the service data in the blockchain.
Innovation Solution
Each consensus node stores the digest of the service data in the blockchain instead of the service data itself after passing consensus verification, ensuring authenticity verification without the need for encryption and reducing computation loads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If each consensus node encrypts the service data included in each service request passing consensus verification, then the service data is protected from unauthorized access, but the computation load on each consensus node is greatly increased
Solution Approach 1:
The patent extracts only the essential authentication element (digest) from the complete service data and stores it in the blockchain, while the full service data is stored externally. This separation allows consensus nodes to verify authenticity without handling or encrypting the complete data set, significantly reducing computation load while maintaining security.
Solution Approach 2:
The patent uses a digest (hash copy) of the service data instead of the original service data for blockchain storage and verification. This digital fingerprint serves as a lightweight representation that enables authentication without requiring the expensive encryption operations on the full data set.
2Reliability
If each consensus node encrypts the service data, then data confidentiality is maintained, but the efficiency of performing consensus verification is reduced
Solution Approach 1:
The patent separates the authentication function from the data storage function by extracting only the digest for blockchain storage. This allows consensus verification to operate on small, fixed-size hash values rather than large service data sets, dramatically improving verification efficiency while confidentiality is maintained through the one-way nature of hashing.
Solution Approach 2:
The patent transforms the service data into a different parameter representation (digest/hash) that is computationally efficient for verification. The digest serves as a compact parameter that enables rapid consensus verification without requiring processing of the original large-scale service data.
3Loss of information
If the service data is stored in the blockchain, then complete information is preserved, but blockchain nodes irrelevant to the service can obtain private information in the service data
Solution Approach 1:
The patent extracts only the authentication-critical digest from the service data and places it in the blockchain, while the sensitive complete service data is stored in external systems accessible only to authorized nodes. This selective extraction prevents unauthorized access to private information while preserving verification capability.
Solution Approach 2:
The patent segments the service data into two parts: the digest (stored in blockchain for verification) and the complete service data (stored externally with restricted access). This segmentation allows the system to maintain information completeness for verification purposes while preventing unauthorized access to sensitive details through controlled distribution.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
Implementations of the present application disclose a method and device for processing a service request. If a service request passes consensus verification, each consensus node stores a digest of service data in a blockchain, instead of storing the service data in the blockchain. As such, the digest of the service data is stored in the trustworthy blockchain, and authenticity of the service data can still be verified. In addition, the service data is not stored in the blockchain so that the service data cannot be obtained by a blockchain node irrelevant to the target service. Therefore, each consensus node does not need to consume computing resources to encrypt the service data any more, thereby improving efficiency of performing consensus verification on the service request by each consensus node.