Cascading Blockchain Instances for Multi-Step Process Tracking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain systems lack an efficient method to align and link multiple blockchain instances for tracking multi-step processes, leading to suboptimal execution times and resource utilization.

Innovation Solution

Creating a system that allows for the creation of first and second blockchain instances, linking blocks between them, and updating based on change evidence data, enabling cascading blockchains for parallel or serial execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple blockchain instances are created to track different process steps, then the system can handle multi-step processes, but the execution time increases due to sequential processing

Engineering Contradiction:
Improveability to track multi-step processesVSAvoidexecution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent divides a multi-step process into separate blockchain instances, where each instance corresponds to a specific process step. This segmentation allows independent processing of each step while maintaining overall process tracking through alignment mechanisms between instances.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a temporal dimension to blockchain execution by allowing different blockchain instances to operate at different times and then aligning them. This enables parallel execution of process steps across different time periods, reducing total execution time while maintaining process integrity.

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

2Reliability

If blockchain instances are linked sequentially, then process tracking is maintained, but resource utilization is suboptimal

Engineering Contradiction:
Improveprocess tracking accuracyVSAvoidresource utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements dynamic alignment between blockchain instances based on change evidence data. The alignment mechanism adjusts the relationship between instances according to actual process state changes, allowing flexible resource allocation and optimal execution timing while maintaining accurate process tracking.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent uses change evidence data as feedback to dynamically adjust and realign blockchain instances. This feedback mechanism ensures that resources are allocated optimally based on actual process progress, improving both reliability of tracking and productivity of resource utilization.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If blockchain instances are updated independently, then flexibility is maintained, but alignment between instances becomes complex

Engineering Contradiction:
Improveupdate flexibilityVSAvoidalignment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces change evidence data as an intermediary mechanism that mediates between independently updated blockchain instances. This intermediary allows each instance to be updated flexibly while providing a standardized reference point for maintaining alignment, simplifying the complexity of coordinating multiple instances.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12174825B2Cascading family of blockchains
Publication Date: 2024.12.24 BOARDWALKTECH INC
  • US12174825B2 patent drawing
  • US12174825B2 patent drawing
  • US12174825B2 patent drawing

AI summary

A system, method, and computer-readable storage medium is provided for creating first and second blockchain instances, each comprising representative blocks corresponding to steps in first and second multistep processes, respectively; performing a linking operation to link a block in the first blockchain instance to a block in the second blockchain instance; receiving change evidence data pertaining to steps in one of the first and second multi-step processes; and performing an update operation comprising updating one of the first and second blockchain instances based on said change evidence data.