Database Ledger Immutability via Segmentation and Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Emerging blockchain technologies lack the ability to support high volume concurrent transactions and complex query/analytics while also lacking the immutability of database management systems.
Innovation Solution
A method that includes receiving a new entry record, encrypting it using optional encryption keys, and updating the record in a database to make it unchangeable from subsequent modification attempts, enabling support for high volume transactions and immutability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If blockchain technology is used to ensure data immutability and security, then data security and immutability are improved, but the system cannot support high volume concurrent transactions and complex queries
Solution Approach 1:
The patent segments the ledger data into immutable blocks that are stored in a database management system. Each block contains hashed references to previous blocks, maintaining the chain structure, while the database engine handles high-volume transactions efficiently. This segmentation allows the system to maintain immutability guarantees while leveraging the database's high throughput capabilities.
Solution Approach 2:
The patent introduces a database management system as an intermediary layer between the blockchain protocol and the actual data storage. The DBMS acts as a mediator that enforces immutability constraints while providing high-performance transaction processing and complex query capabilities, bridging the gap between blockchain's security guarantees and database's performance advantages.
2Productivity
If traditional database management systems are used to support high volume transactions and complex queries, then productivity and query capability are improved, but the system lacks data immutability
Solution Approach 1:
The patent changes the immutability parameter enforcement from a protocol-level constraint to a database-level constraint. By using SQL constraints, triggers, and database security features, the system maintains data immutability through database mechanisms rather than blockchain consensus, enabling high-volume transactions and complex queries while preserving immutability guarantees.
Solution Approach 2:
The patent replaces the mechanical blockchain consensus mechanism with database-level immutability enforcement. Instead of relying on distributed consensus and cryptographic chaining for every transaction, the system uses database constraints, transactions, and security features to enforce immutability, substituting the blockchain's mechanical immutability enforcement with more efficient database mechanisms.
3Reliability
If encryption keys are used to secure private data records, then data security is improved, but the system complexity increases
Solution Approach 1:
The patent implements self-service encryption key management where each user or organization generates and manages their own encryption keys. The database system provides automated key storage, retrieval, and rotation capabilities without requiring manual intervention. This self-service approach maintains high data security while reducing operational complexity through automation.
Solution Approach 2:
The patent implements nested encryption where data records are encrypted with user-specific keys, and those keys are themselves encrypted and stored in the database with additional layers of protection. This nested structure provides multiple layers of security while centralizing key management within the database system, reducing the overall complexity of key management infrastructure.
Data Source
AI summary
A business application may provide a secure ledger update while maintaining anonymity and security from unauthorized third parties. One example may include receiving a new entry transaction to save data in a database/ledger. The example may also include receiving a request to add a record stored in a database with a new entry, adding the record by inserting the new entry, and enabling the new entry to be unchangeable from subsequent modification attempts based on an immutable attribute.