Blockchain Transaction Forwarding with Whitelist and Hop Count

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex supply chain systems involving multiple blockchains, tracking and forwarding transactions between disparate blockchains pose significant challenges, including the need for efficient notification and control mechanisms to ensure secure and valid transaction routing.

Innovation Solution

A blockchain transactions forwarding mechanism that includes a whitelist for approved blockchains and nodes, along with a predetermined hop count to limit transaction forwarding, allowing for secure and controlled transaction tracking and notification across multiple blockchains, utilizing a distributed ledger system with hash generation and digital signatures for security and validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If transactions are forwarded across multiple blockchains without restrictions, then tracking capability is improved, but security and control are worsened

Engineering Contradiction:
Improvetransaction tracking capabilityVSAvoidtransaction security
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent applies preliminary action by establishing whitelists of approved blockchains and nodes before transactions are forwarded. The hop count parameter is predetermined and attached to transactions in advance, limiting their propagation depth. These preventive measures are configured beforehand to ensure security while enabling tracking, resolving the contradiction between information loss prevention and security maintenance.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If hop count is increased to allow more forwarding, then transaction routing flexibility is improved, but system control and security are worsened

Engineering Contradiction:
Improvetransaction routing flexibilityVSAvoidsystem control complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent changes the parameter of hop count to a controlled variable that can be adjusted based on transaction requirements. By making hop count a configurable parameter with default values and validation rules, the system achieves routing flexibility while maintaining control through parameter constraints. This resolves the contradiction by allowing adaptability within bounded parameters rather than uncontrolled flexibility.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If whitelist validation is implemented for all transactions, then security is improved, but processing speed and efficiency are worsened

Engineering Contradiction:
Improvetransaction securityVSAvoidtransaction processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial action by implementing whitelist validation selectively rather than universally. The validation is performed based on the transaction's hop count and current blockchain context, not on every single transaction uniformly. This partial validation approach maintains security for high-risk transactions while allowing faster processing for trusted transactions, resolving the contradiction between security and processing speed.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11381401B2Blockchain transaction forwarding
Publication Date: 2022.07.05 SEAGATE TECH LLC
  • US11381401B2 patent drawing
  • US11381401B2 patent drawing
  • US11381401B2 patent drawing

AI summary

The technology disclosed herein provides a blockchain transactions forwarding mechanism that allows for tracking and notification from the originating blockchain through to a last blockchain and back again. An implementation of the system disclosed herein also provides a whitelist mechanism to provide a list of acceptable blockchains or nodes that may receive transactions. Yet another implementation provides a predetermined hop count that may be used as the maximum allowable hop counts that provides the number of times a transaction is allowed to be forwarded.