Blockchain Chain Mitosis for Transaction Bottleneck Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional blockchain implementations face inefficiencies in transaction processing due to high energy consumption and bias towards miners with access to cheap energy or excessive computing power, leading to potential bottlenecks when a popular application generates high transaction volumes, causing the blockchain to 'strangle' other transactions.

Innovation Solution

Implementing a single-leader election algorithm using a cryptographic sortition that involves a burn chain and a virtual chain, where miners participate by burning cryptocurrency to be selected as leaders, and introducing chain mitosis to split the blockchain when a specific application's load exceeds a threshold, creating a separate app chain to alleviate processing burdens.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional blockchain implementations process all transactions on a single chain, then all transactions are processed uniformly, but high transaction volumes from popular applications cause bottlenecks and energy consumption increases

Engineering Contradiction:
Improvetransaction processing capacityVSAvoidenergy consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The blockchain is segmented into multiple chains: a base chain that processes only critical transactions and maintains security consensus, and multiple application-specific chains (app chains) that handle different application transactions independently. This segmentation allows high-volume application transactions to be processed in parallel on separate chains, increasing overall throughput while reducing the energy burden on the base chain.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system transitions from a single-dimensional chain structure to a multi-dimensional hierarchical structure with base chains at the foundation and multiple app chains layered above them. App chains are anchored to base chains, creating a vertical dimension that enables independent transaction processing at different levels, thereby scaling capacity without proportionally increasing base chain energy consumption.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If miners use proof of work with high computing power, then transaction validation is secure, but bias towards miners with cheap energy or excessive computing power occurs

Engineering Contradiction:
Improvetransaction validation securityVSAvoidfair participation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Mining functionality is segmented and distributed across multiple base chains rather than concentrated on a single chain. Each base chain maintains its own set of miners and validation process. This segmentation allows participants to choose which base chain to mine on based on their resources and preferences, reducing the advantage of having excessive computing power on a single chain and promoting more equitable participation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically allows new base chains to be created and app chains to be spawned as needed based on transaction loads and participant requirements. This dynamic structure enables the network to adapt to changing conditions, allowing participants with varying resource levels to find suitable chains for their capabilities, thereby improving fairness while maintaining security through distributed validation.

Inventive Principle:
Principle #15Dynamics

3Speed

If the blockchain processes high-volume transactions from a single application, then that application gets fast service, but other applications experience bottlenecks and slower processing

Engineering Contradiction:
Improvetransaction processing speedVSAvoidoverall system throughput
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The system segments transaction processing by creating dedicated app chains for different applications. Each app chain handles transactions for its specific application independently, allowing high-volume applications to achieve fast processing speeds on their own chain without interfering with other applications. Meanwhile, the base chain continues processing critical transactions, maintaining overall system throughput across all applications.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Instead of having all transactions compete for resources on a single chain, the system creates copies of the blockchain structure tailored for specific applications. Each app chain is a copy that replicates essential blockchain functionality but is optimized for its specific application's transaction patterns, enabling parallel processing and preventing bottlenecks while maintaining high speeds for each application.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11515999B1Systems and methods for selectively processing blockchain data
Publication Date: 2022.11.29 HIRO SYST PBC
  • US11515999B1 patent drawing
  • US11515999B1 patent drawing
  • US11515999B1 patent drawing

AI summary

An improved blockchain implementation that reduces application transaction processing bottlenecks for applications that operate on a decentralized network. For example, if an application operating on a decentralized network becomes sufficiently popular, an existing blockchain can be split into the original blockchain and an application-specific chain (or app chain) that includes blocks that only store transactions for the sufficiently popular application. A peer that is not interested in tracking transactions for the sufficiently popular application, however, does not need to track the application-specific chain. Thus, the peer can reduce the number of computational operations that are performed by simply storing block data for blocks in the original blockchain and not for blocks in the application-specific chain.