Virtual Distributed Ledger Network Hybrid Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain systems lack flexibility to adapt to specific use-cases and do not support dynamically configurable platforms that allow different types of distributed ledger technology (DLT) networks to be created as needed, nor do they enable interaction between various DLTs.
Innovation Solution
The implementation of virtual distributed ledger networks (vDLT) using a microservices-based architecture, where virtual DLT nodes can participate in multiple DLT/blockchain networks, interoperate across different networks, and leverage compute, storage, and network resources dynamically, enabling the creation of various DLTs and their interaction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a specific type of blockchain technology is used, then the system achieves stability and reliability, but it loses flexibility to adapt to different use-cases
Solution Approach 1:
The system dynamically configures blockchain parameters such as consensus mechanism, block size, and transaction fee based on the specific use-case requirements. This allows the same underlying blockchain infrastructure to adapt its behavior and characteristics to different applications while maintaining operational stability through controlled parameter adjustment rather than fundamental system changes.
Solution Approach 2:
The patent implements the ability to modify key blockchain parameters including consensus algorithm selection, block confirmation time, and network configuration based on the intended use-case. This parameter flexibility enables the system to optimize for different requirements (e.g., speed vs. security vs. scalability) without requiring complete system redesign, thus resolving the contradiction between stability and adaptability.
2Ease of operation
If a single DLT network is created, then the system maintains simplicity and ease of operation, but it cannot support multiple DLT networks or enable interoperability between them
Solution Approach 1:
The system implements a universal DLT network creation capability that can instantiate multiple different types of distributed ledger networks within a single platform. The underlying infrastructure provides multi-functional support for various consensus mechanisms, data structures, and network configurations, allowing users to create and manage multiple DLT networks while the platform maintains a unified interface and management layer that preserves operational simplicity.
3Adaptability or versatility
If different types of DLT networks are created, then the system achieves versatility and adaptability, but it increases device complexity and architectural overhead
Solution Approach 1:
The system segments the complexity of supporting multiple DLT types by separating the configuration layer from the execution layer. Each DLT network type is configured through modular parameter sets that define consensus mechanisms, data structures, and operational characteristics. This segmentation allows the platform to support diverse DLT implementations while maintaining a consistent underlying architecture, reducing the perceived complexity for users and simplifying system management.
Data Source
AI summary
The present disclosure relates to systems and methods for hybrid synchronization in virtual distributed ledger networks. In one embodiment, a processor-implemented method is disclosed, comprising receiving, at the first virtual machine or container associated with a master ledger, a transaction request comprising transaction information; updating the master ledger with the transaction information; upon determining to perform a synchronous update of the slave ledgers, updating the slave ledgers based on the updated master ledger with the transaction information using a consensus protocol; and upon determining to perform an asynchronous update of the slave ledgers, communicating by the first virtual machine or container, with one or more additional virtual machines or containers associated with the slave ledgers, an update of the slave ledgers at one or more times determined based on a delay tolerance associated with each of the one or more additional virtual machines or containers.