Cross-Blockchain Authentication via Cross-Chain Client
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing blockchain systems face challenges in cross-blockchain authentication, particularly in verifying data from mutually isolated blockchains, which hinders the establishment of a low-complexity and high-expansibility cross-chain network.
Innovation Solution
A cross-blockchain authentication method and apparatus that utilizes a cross-chain client to synchronize data between blockchains through subscription and publishing, employing SPV data authentication based on authentication data sources and rules configured on each blockchain, allowing for non-invasive sidechain anchoring.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional blockchain systems are used for cross-blockchain authentication, then data verification between isolated blockchains can be achieved, but the system complexity increases and expansibility decreases
Solution Approach 1:
The patent segments the authentication system into independent components: subscribing clients, publishing clients, and cross-chain clients. Each component has a specific function - publishing clients publish authentication data, subscribing clients subscribe to relevant data, and cross-chain clients facilitate the interaction. This segmentation allows blockchains to remain isolated while enabling targeted authentication capabilities without increasing overall system complexity.
Solution Approach 2:
The cross-chain client acts as an intermediary between isolated blockchains, enabling authentication without direct integration. The intermediary publishes and subscribes to authentication data on behalf of different blockchains, allowing verification while maintaining isolation. This mediator approach resolves the contradiction by providing connectivity functionality without requiring complex direct connections between all blockchain nodes.
2Measurement precision
If comprehensive data synchronization is implemented between blockchains, then authentication accuracy improves, but the time consumption and computational resources increase
Solution Approach 1:
The patent extracts only the necessary authentication data (block headers, Merkle roots, transaction hashes) from the complete blockchain data, rather than synchronizing all data. Subscribing clients request specific authentication-related information from publishing clients, enabling accurate verification without the time and resource overhead of comprehensive data synchronization.
Solution Approach 2:
The system performs partial authentication by using selective data sampling (block headers and Merkle paths) rather than complete data verification. This partial action approach provides sufficient authentication accuracy for cross-chain operations while significantly reducing the time and computational resources required compared to verifying all blockchain data.
3Reliability
If direct connections between all blockchain nodes are established for authentication, then verification reliability improves, but the network complexity and maintenance difficulty increase
Solution Approach 1:
The cross-chain client is designed as a universal component that can interact with multiple different blockchains through a standardized interface. Rather than establishing unique direct connections between each pair of blockchain nodes, the universal cross-chain client handles authentication requests across different chains, simplifying network maintenance while maintaining verification reliability.
Solution Approach 2:
The cross-chain client serves as a mediator that manages all authentication interactions between isolated blockchains. Instead of requiring direct peer-to-peer connections between all nodes, the intermediary handles data publication, subscription, and verification centrally, reducing network complexity and easing maintenance while preserving authentication reliability through standardized protocols.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Implementations of the present specification provide for cross-blockchain authentication. A subscribing client, using a cross-blockchain interaction system cross-chain client, obtains data from a second blockchain published by a publishing client, to use the data as an authentication data source, the cross-blockchain interaction system comprises the subscribing client, the publishing client, and a cross-chain client, the subscribing client corresponds to a first blockchain, the publishing client corresponds to the second blockchain, the cross-chain client is separately interconnected with the subscribing client and the publishing client and the first blockchain are used as a sidechain that is anchored to the second blockchain that is used as a main chain. Data to be authenticated is received from the second blockchain. Data authentication is performed on the data to be authenticated based on the authentication data source and a data authentication rule configured on the first blockchain.