Database Entry Signature Verification Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Centralized databases face issues such as single points of failure, dependency on network connectivity, bottlenecks during high traffic, and inefficiencies in data access due to minimal redundancy, which are exacerbated by the need for numerous signature verifications for new encrypted entries.
Innovation Solution
Implementing a system that reduces signature verifications by identifying blocks with multiple entries signed by the same member, allowing previously verified entries to be designated as committed without additional verification, using a blockchain-based approach with nodes that share hashes of previously signed entries to streamline the verification process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized database performs signature verifications for all new encrypted entries, then data security and integrity are maintained, but the verification process becomes time-consuming and reduces system efficiency
Solution Approach 1:
The system performs preliminary signature verifications by having multiple members sign entries before they are committed to the blockchain. The signatures are collected and verified in advance, allowing the commitment operation to proceed without repeating verifications. This preliminary action ensures security is established before the main operation.
Solution Approach 2:
The patent combines multiple signature verifications into a single verification operation. When multiple members sign the same entry, their signatures are aggregated and verified together in one step rather than individually. This merging reduces the total verification operations from O(n) to O(1) where n is the number of signers.
2Quantity of substance
If a centralized database maintains a single copy of data, then data redundancy is minimized, but the system creates a single point of failure and limits access availability
Solution Approach 1:
The system segments the centralized database into multiple decentralized nodes distributed across the network. Each node maintains a copy of the blockchain ledger, eliminating the single point of failure. Data is divided into blocks that are replicated across multiple members, providing both redundancy and fault tolerance while maintaining the integrity of the original data structure.
3Reliability
If a centralized database requires multiple signature verifications for each entry, then data integrity is ensured, but the verification process creates bottlenecks during high traffic
Solution Approach 1:
The system creates cryptographic copies of signature data in the form of hash values. Instead of storing and verifying full signature data for each entry, the system uses hash copies that can be quickly computed and compared. This copying approach maintains data integrity verification while significantly reducing the computational complexity and storage requirements.
Data Source
AI summary
An example operation may include one or more of identifying a new entry, receiving one or more new entry signatures to approve the new entry to, such that the one or more new entry signatures each include a signature of the new entry and hashes of previously signed entries for a common block, verifying the one or more new entry signatures for commit by performing a signature verification of the new entry, determining the common block has more than one entry with a hash signed by a same member, and responsive to the signature check being performed on the new entry and determining the common block has more than one entry with a hash signed by a same member, designating one or more previously received entries as verified for commit without performing a signature verification of the one or more previously received entries.