Transactional Database Management System for Blockchain Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain protocols are inefficient in transaction verification due to the increased time required as more computer systems participate in replicating the ledger, leading to scalability and availability issues.
Innovation Solution
Implementing a transactional database management system that enables concurrent prepare, commit, rollback, and verification of transactions using highly efficient, indexed, in-memory buffers for blockchain data storage, allowing for atomicity, consistency, isolation, and durability, and providing options for availability and eventual consistency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If more computer systems participate in replicating the blockchain ledger, then security and decentralization are improved, but transaction verification time increases
Solution Approach 1:
The patent segments the blockchain verification process into distinct phases: prepare, commit, rollback, and verification. Each phase can be handled by different computing nodes independently, allowing parallel processing while maintaining security. This segmentation enables the system to scale without linearly increasing verification time for all nodes.
Solution Approach 2:
The patent implements a prepare phase where transactions are validated and buffered before being committed to the ledger. This preliminary action allows computing nodes to pre-process and queue transactions, so that when commit time arrives, the actual ledger update is faster. This reduces the critical path time for verification while maintaining security through the multi-phase approach.
2Stability of the object's composition
If blockchain uses sequential data files for storage, then data integrity is maintained, but scalability and transaction throughput are limited
Solution Approach 1:
The patent transitions from sequential single-dimension data storage to a multi-dimensional storage architecture using indexed buffers and hash-based addressing. Transactions can be stored and retrieved through multiple access paths (sequential, random, indexed), enabling parallel operations and significantly improving throughput while maintaining data integrity through cryptographic hashing and consistency checks.
Solution Approach 2:
The patent implements replicated ledgers across multiple computing nodes, where each node maintains a copy of the blockchain data. This copying approach enables parallel verification and processing, as multiple nodes can simultaneously validate transactions without sequential dependencies, thereby improving scalability while maintaining data integrity through consensus mechanisms.
3Manufacturing precision
If blockchain implements strict consistency checks, then data accuracy is improved, but system availability and processing speed decrease
Solution Approach 1:
The patent implements dynamic consistency checking where the strictness of verification can be adjusted based on system conditions, transaction types, and node configurations. Critical transactions undergo full ACID-style verification, while less critical operations can use optimized paths with appropriate consistency levels. This dynamic approach maintains data accuracy for important operations while preserving system availability through flexible verification strategies.
Solution Approach 2:
The patent changes verification parameters based on transaction characteristics and system state. Different consistency levels, timeout values, and verification depths can be applied to different transaction types. This allows the system to maintain high data accuracy when needed while improving availability and throughput for operations that can tolerate relaxed consistency, effectively resolving the contradiction through parameter optimization.
Data Source
AI summary
A system, method, and computer readable storage medium configured for a transactional database management system shared by all computing nodes participating in a system based on a blockchain protocol. The transactional database management system includes transactions and blocks, where the transactions are data to be stored in the blockchain and the blocks are records that confirm when and in what sequence certain transaction became journaled as part of the blockchain. A request is received signed with a signature of a user system to include a new transaction with additional data in the blockchain. In response to the signature being verified and hash of batches of receive transaction into the block being verified. The block are added that records the new transaction with additional data in the blockchain using within the transactional database management system.