Modular Blockchain Kernel Architecture for Scalable Consensus
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional blockchain implementation schemes are primarily suited for digital currencies, making them less applicable and more costly to adapt for other business scenarios, requiring significant framework reconstruction that is difficult and costly to maintain.
Innovation Solution
A modular blockchain kernel architecture that includes a kernel engine and consensus components, allowing for flexible configuration and extension of kernel engines and consensus mechanisms, enabling seamless integration of various components to support different application scenarios without invasive framework changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional blockchain schemes are used for digital currencies, then they work well for digital currency applications, but they have poor applicability and high reconstruction costs when adapted to other business scenarios
Solution Approach 1:
The blockchain system is segmented into independent modules: kernel engine, consensus component, business component, and data storage component. Each module can be independently selected and configured based on specific business scenario requirements, avoiding the need for comprehensive framework reconstruction when adapting to different applications.
Solution Approach 2:
The kernel engine is designed as a universal foundation that can support multiple types of consensus mechanisms and business components. The standardized interfaces allow the same kernel engine to work with different consensus algorithms (e.g., PoW, PoS, PBFT) and various business logic components, enabling one system to serve multiple purposes across different industries.
2Adaptability or versatility
If framework reconstruction is performed to adapt blockchain to new business scenarios, then applicability improves, but development cost and technical threshold increase significantly
Solution Approach 1:
The system employs dynamic component configuration where consensus components and business components can be dynamically selected, added, or removed based on specific scenario needs. This dynamic architecture allows businesses to start with a basic configuration and incrementally add only the components necessary for their specific use case, reducing initial development cost and technical threshold.
Solution Approach 2:
Standardized interfaces act as intermediaries between the kernel engine and various consensus/business components. These interfaces abstract the complexity of different components, providing a unified interaction mechanism that lowers the technical threshold for integration and reduces development costs by eliminating the need for custom integration logic for each new scenario.
3Adaptability or versatility
If deep framework reconstruction is performed, then the system can be adapted to new scenarios, but the system cannot automatically follow up with latest framework updates after reconstruction
Solution Approach 1:
By segmenting the system into standardized modules with well-defined interfaces, the kernel engine can be independently updated without affecting the consensus or business components. This modular segmentation allows the core framework to receive security patches and performance improvements while custom business logic remains intact, ensuring the system can follow framework updates while maintaining customization.
Solution Approach 2:
The universal standardized interfaces ensure that updated kernel engines remain compatible with existing consensus and business components. This universality allows the system to upgrade to the latest framework version while maintaining the same business logic and consensus mechanisms, automatically following updates without requiring re-customization.
Data Source
AI summary
Provided are a method and apparatus for operating a blockchain system, a device and a storage medium. The method is described below. To-be-processed blockchain data is acquired through a kernel engine of the blockchain system. The to-be-processed blockchain data is processed through the kernel engine, a consensus component call request is generated according to a consensus component interface during a processing process of the to-be-processed blockchain data, and a corresponding consensus component is called according to the consensus component call request, where the corresponding consensus component is configured to execute a consensus mechanism between blockchain nodes.