Key Exchange Controller for Private-Public Blockchain Lineage Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing technologies face challenges in maintaining data lineage on private blockchains, particularly when third-party vendors need access to update data lineage on a corporation's private blockchain, due to the lack of interoperability between private and public blockchains.

Innovation Solution

A key exchange controller (KEC) is introduced to facilitate communication and access permission between private and public blockchains, generating smart contracts and key exchange protocols to allow entities on public blockchains to access and maintain data lineage on private blockchains.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a corporation stores sensitive data on a private blockchain, then data security and privacy are improved, but interoperability with public blockchains and access by third-party vendors deteriorate

Engineering Contradiction:
Improvedata securityVSAvoidinteroperability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a key exchange controller as an intermediary component that mediates between private and public blockchains. This controller manages key exchange protocols and smart contracts, enabling third-party vendors on public blockchains to access and maintain data lineage on private blockchains without compromising the security and privacy of the sensitive data stored on the private blockchain.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If third-party vendors are granted access to a private blockchain to maintain data lineage, then data lineage completeness is improved, but data security and privacy deteriorate

Engineering Contradiction:
Improvedata lineage completenessVSAvoiddata security
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent extracts the data lineage maintenance function from the core private blockchain system and implements it as a separate capability that can be performed by third-party vendors on public blockchains. The key exchange controller enables vendors to access only the necessary metadata for lineage tracking without exposing or accessing the actual sensitive data, thus maintaining data lineage completeness while preserving data security.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If data lineage is maintained on a private blockchain only, then data security is improved, but accessibility and ease of operation deteriorate

Engineering Contradiction:
Improvedata securityVSAvoidaccessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements a universal key exchange mechanism that enables multiple entities (corporations, third-party vendors, auditors) to interact with the private blockchain through a standardized interface on the public blockchain. The key exchange controller provides multi-functional capabilities including key management, access authorization, and lineage verification, making the system accessible to diverse users while maintaining the security boundaries of the private blockchain.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12483557B1Systems and methods for data lineage authentication
Publication Date: 2025.11.25 WELLS FARGO BANK NA
  • US12483557B1 patent drawing
  • US12483557B1 patent drawing
  • US12483557B1 patent drawing

AI summary

Systems, apparatuses, methods, and computer program products are disclosed for providing interoperability between private and public blockchains. An example method for providing interoperability between private and public blockchains includes, by a key exchange controller (KEC): receiving access key generation instructions; generating, based on the key generation instructions, an access key comprising access credentials; transmitting the access key to an access key target on a public blockchain network; receiving, from the access key target, a access request including the access credentials and information indicating a private blockchain on a private blockchain network; and providing, in response to receiving the access request, access for the access key target to access the private blockchain of the private blockchain network.