Cross-Blockchain Authentication via Oracle Engine Intermediary
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain technologies face challenges in enabling seamless and secure cross-chain interactions between different blockchain systems, particularly in authenticating data across isolated blockchains, which hinders the establishment of scalable and low-complexity networks.
Innovation Solution
A cross-blockchain authentication method and apparatus that utilizes a subscribing client, a publishing client, and a cross-chain interaction end, where the subscribing client obtains a public key of an oracle engine connected to a second blockchain, uses it as an authentication data source, and performs data authentication on data signed by the oracle engine, reducing authentication complexity and enabling non-invasive sidechain anchoring between isolated blockchains.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional blockchain authentication methods are used, then data security is maintained within single blockchain, but cross-chain authentication capability is lost
Solution Approach 1:
The patent introduces an oracle engine as an intermediary component that operates on the second blockchain and signs data for the first blockchain. This mediator enables cross-chain authentication without requiring the first blockchain to directly interact with or trust nodes on the second blockchain, thus achieving cross-chain capability while maintaining relative system simplicity through a dedicated intermediary layer
Solution Approach 2:
The authentication system is segmented into distinct functional components: a first blockchain for subscription, a second blockchain for data storage, and an oracle engine for authentication. Each component operates independently on its own blockchain, and authentication is achieved through the oracle engine's signatures rather than direct inter-blockchain trust mechanisms, reducing overall system complexity
2Reliability
If full blockchain data is synchronized across chains, then authentication reliability is improved, but network complexity and resource consumption increase
Solution Approach 1:
Instead of synchronizing entire blockchain datasets across chains, the patent extracts only the essential authentication information (data signatures) from the second blockchain and makes them available to the first blockchain through the oracle engine. This extraction approach maintains authentication reliability by verifying signatures while avoiding the complexity of full data synchronization
Solution Approach 2:
The system performs partial authentication action by verifying only the cryptographic signatures of critical data rather than validating complete blockchain histories. This partial action suffices for authentication purposes while significantly reducing the computational and network resources required compared to full data synchronization
3Reliability
If complex authentication protocols are implemented, then data security is enhanced, but authentication time and processing speed decrease
Solution Approach 1:
The patent replaces complex multi-step authentication protocols with a streamlined cryptographic signature verification mechanism. Instead of implementing elaborate challenge-response or multi-factor authentication systems, the solution uses straightforward public-key infrastructure (PKI) where the oracle engine signs data and the first blockchain verifies signatures, achieving both security and speed through elegant cryptographic primitives rather than mechanical complexity
Data Source
Figure 1
Figure 2
Figure 3
AI summary
One or more implementations of the present specification provide cross-blockchain authentication. A subscribing client corresponding to a first blockchain and included in a system for cross-chain interaction obtains a public key of an oracle engine that is used as an authentication data source. By using a cross-chain interaction end, data to be authenticated in a second blockchain and is published by a publishing client corresponding to the second blockchain is obtained, where the data to be authenticated is signed by the oracle engine connected to the second blockchain based on a private key held by the oracle engine. Based on the authentication data source and a signature of the data to be authenticated, data authentication is performed on the data to be authenticated.