Consortium Blockchain Verification Signature Mechanism
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing consensus methods for consortium blockchain systems are cumbersome and time-consuming, requiring extensive data tracing to verify block data validity, which leads to service delays in large information throughput scenarios.
Innovation Solution
A consensus method where a verification signature is sent between consensus nodes, allowing nodes to record proposal data and verification signatures in a block, enabling direct validity verification without tracing other block nodes, thus simplifying the verification process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If block data validity is verified by comparing with block data stored by other nodes, then verification reliability is ensured, but verification time and system overhead increase significantly
Solution Approach 1:
The patent applies preliminary action by having consensus nodes pre-generate and sign verification signatures for proposal data before block formation. These signatures are attached to the proposal data in advance, so that when verification is needed, the validity can be immediately confirmed by checking the pre-computed signatures rather than re-comparing entire block data sets across nodes.
Solution Approach 2:
The patent extracts the essential verification element (signature) from the complex block data comparison process. Instead of requiring nodes to compare and validate entire block data sets, the system extracts and utilizes only the critical signature component that proves data validity, significantly reducing verification complexity and time.
2Measurement precision
If comprehensive block data comparison is performed across multiple nodes, then verification accuracy is improved, but system complexity and computational overhead increase
Solution Approach 1:
The patent extracts the essential verification element (signature) from the complex block data comparison process. Instead of requiring nodes to compare and validate entire block data sets, the system extracts and utilizes only the critical signature component that proves data validity, significantly reducing verification complexity while maintaining accuracy.
Solution Approach 2:
The patent uses cryptographic signatures as compact copies or representations of verification information. Rather than storing and comparing full block data sets, each node holds and verifies against signature copies that encapsulate the essential validity proof, reducing the data handling burden while preserving verification accuracy.
3Reliability
If traditional consensus verification methods are used, then data security is maintained, but processing speed and throughput are reduced
Solution Approach 1:
The patent applies preliminary action by having consensus nodes pre-generate and sign verification signatures for proposal data before block formation. These signatures are attached to the proposal data in advance, so that when verification is needed, the validity can be immediately confirmed by checking the pre-computed signatures rather than re-comparing entire block data sets across nodes, thereby increasing throughput without compromising security.
Data Source
AI summary
A consensus method includes: when a first consensus node of a consortium blockchain performs a consensus operation on a consensus proposal, sending a verification signature to a second consensus node of the consortium blockchain, wherein the verification signature is configured to represent at least one consensus verification item set by the first consensus node sending the verification signature for the consensus proposal; receiving, by the first consensus node, a verification signature sent by at least one of the second consensus node or a third consensus node of the consortium blockchain for the consensus proposal; and after the first consensus node reaches a consensus on proposal data of the consensus proposal, generating a block recording the received verification signature corresponding to the consensus proposal and the proposal data, wherein the verification signature recorded in the block is configured to prove validity of the proposal data recorded in the block.