Cross-blockchain data processing method, device, system, apparatus and storage medium

Abstract

Embodiments of the present application disclose a cross-blockchain data processing method, device, system, equipment and storage medium. The method comprises: a cross-chain system receiving a first request sent by a first proxy component, the first request being used to request to initiate a cross-chain business; the first request at least comprising a first proof, the first proof being generated by the first proxy component based on a first execution result of a first business; sending a first credential to the first proxy component, the first proxy component sending a second request to each second proxy component, the second request at least comprising the first credential; receiving a second proof sent by each second proxy component, the second proof being generated by each second proxy component based on a second execution result of a corresponding second business; verifying the second proof sent by each second proxy component respectively, and generating a second credential in the case that all the second proofs are verified; and sending the second credential to the first proxy component and at least one second proxy component respectively, the second credential representing that the cross-chain business is executed.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, and in particular to a cross-blockchain data processing method, apparatus, system, device, and storage medium. Background Technology

[0002] Blockchain technology, with its decentralized, immutable, and traceable characteristics, has been widely applied in many fields such as finance, government affairs, and the judiciary. Blockchain has effectively solved the trust problem among chain participants, enabling collaborative sharing, and its industrial application exploration has shown explosive growth.

[0003] However, most enterprises initially built their blockchain platforms with "business" at the center, making each blockchain platform a new "island." As the business ecosystem develops, the need for secure and reliable interconnection between blockchain platforms becomes urgent, and cross-chain technology has emerged. Various blockchain vendors have proposed some usable enterprise-level cross-chain solutions, but currently, most cross-chain solutions adopt an interaction process based on relay systems.

[0004] Relay systems (typically relay gateways or relay chains) act as the medium between cross-chain parties. Every interaction between these parties relies on the relay system's verification capabilities and endorsement credibility, resulting in low cross-chain efficiency. This is especially true in scenarios involving multiple recipients in a single cross-chain transaction. The interaction process between the initiating and receiving blockchains is repeated multiple times, leading to a linear increase in transaction latency and further reducing efficiency. Furthermore, the need for secondary verification and forwarding of business data between cross-chain parties by the relay system can easily lead to security risks such as privacy breaches.

[0005] This shows that current cross-chain solutions cannot meet application requirements in terms of efficiency and security. Summary of the Invention

[0006] To address the existing technical problems, embodiments of the present invention provide a cross-blockchain data processing method, apparatus, system, device, and storage medium.

[0007] To achieve the above objectives, the technical solution of this invention is implemented as follows:

[0008] In a first aspect, embodiments of the present invention provide a cross-blockchain data processing method, applied in a cross-chain system; the method includes:

[0009] The system receives a first request sent by a first proxy component, the first request being used to request the initiation of a cross-chain service; the first request includes at least a first proof, the first proof being generated by the first proxy component based on a first execution result of the first service; wherein, the cross-chain service includes the first service and at least one second service, the first service being executed by a first blockchain associated with the first proxy component, and the at least one second service being executed by a second blockchain associated with at least one second proxy component;

[0010] Send a first credential to the first proxy component. The first credential is used by the first proxy component to send a second request to each second proxy component. The second request includes at least the first credential. The second request is used by the second blockchain associated with the second proxy component to execute a corresponding second business.

[0011] Receive a second proof sent by each second agent component, the second proof being generated by each second agent component based on the second execution result of the corresponding second service;

[0012] The second proof sent by each second proxy component is verified, and a second credential is generated if all second proofs are verified. The second credential is sent to the first proxy component and the at least one second proxy component, respectively, and the second credential indicates that the cross-chain business has been completed.

[0013] Secondly, embodiments of the present invention provide a cross-blockchain data processing method, applied in a first proxy component; the method includes:

[0014] Obtain the first execution result of the first business, and generate a first proof based on the first execution result;

[0015] Send a first request to the cross-chain system, the first request being used to request the initiation of a cross-chain service; the first request includes at least the first proof; wherein the cross-chain service includes the first service and at least one second service, the first service being executed by the first blockchain associated with the first proxy component, and the at least one second service being executed by the second blockchain associated with each of the at least one second proxy component;

[0016] The system receives a first credential sent by the cross-chain system and sends a second request to each second proxy component, wherein the second request includes at least the first credential; the second request is used to request the second blockchain associated with the second proxy component to execute a corresponding second business.

[0017] The system receives a second credential sent by the cross-chain system, the second credential indicating that the cross-chain business has been completed; the second credential is generated by the cross-chain system verifying the second proof sent by each of the at least one second proxy component, and when all the second proofs are verified successfully, the second proof is generated by each second proxy component based on the second execution result of the corresponding second business.

[0018] Thirdly, embodiments of the present invention provide a cross-blockchain data processing method, applied in a second proxy component; the method includes:

[0019] The system receives a second request sent by a first proxy component. The second request is used to request a second blockchain associated with the second proxy component to execute a corresponding second business. The second request includes at least a first credential, which is generated by the cross-chain system based on the first request sent by the first proxy component. The first request is used to request the initiation of a cross-chain business. The first request also includes at least a first proof, which is generated by the first proxy component based on the first execution result of the first business. The cross-chain business includes the first business and at least one second business. The first business is executed by the first blockchain associated with the first proxy component, and the at least one second business is executed by the second blockchain associated with each of the at least one second proxy component.

[0020] Obtain the second execution result of the second business, generate a second proof based on the second execution result, and send the second proof to the cross-chain system;

[0021] The system receives a second credential sent by the cross-chain system, the second credential indicating that the cross-chain business has been completed; the second credential is generated by the cross-chain system verifying the second proofs sent by each of the at least one second proxy component, and only when all the second proofs have been verified.

[0022] Fourthly, embodiments of the present invention provide a cross-blockchain data processing device, applied in a cross-chain system; the device includes a first communication module and a first processing module;

[0023] The first communication module is configured to receive a first request sent by a first proxy component, the first request being used to request the initiation of a cross-chain service; the first request includes at least a first proof, the first proof being generated by the first proxy component based on a first execution result of the first service; wherein, the cross-chain service includes the first service and at least one second service, the first service being executed by a first blockchain associated with the first proxy component, and the at least one second service being executed by a second blockchain associated with at least one second proxy component.

[0024] The first communication module is further configured to send a first credential to the first proxy component, the first credential being used by the first proxy component to send a second request to each second proxy component, the second request including at least the first credential; the second request being used to request the second blockchain associated with the second proxy component to execute a corresponding second business.

[0025] The first communication module is further configured to receive a second proof sent by each second agent component, the second proof being generated by each second agent component based on the second execution result of the corresponding second service;

[0026] The first processing module is used to verify the second proof sent by each second agent component, and generate a second credential if all second proofs are verified.

[0027] The first communication module is further configured to send the second credential to the first proxy component and the at least one second proxy component respectively, the second credential indicating that the cross-chain business has been completed.

[0028] Fifthly, embodiments of the present invention provide a cross-blockchain data processing device applied in a first proxy component; the device includes a second processing module and a second communication module; wherein,

[0029] The second processing module is used to obtain the first execution result of the first business of the cross-chain business, and generate a first proof based on the first execution result;

[0030] The second communication module is used to send a first request to the cross-chain system, the first request being used to request the initiation of a cross-chain service; the first request includes at least the first proof; wherein, the cross-chain service includes the first service and at least one second service, the first service is executed by the first blockchain associated with the first proxy component, and the at least one second service is executed by the second blockchain associated with each of the at least one second proxy component;

[0031] The second communication module is further configured to receive the first credential sent by the cross-chain system, and send a second request to each second proxy component, wherein the second request includes at least the first credential; the second request is used to request the second blockchain associated with the second proxy component to execute the corresponding second business.

[0032] The second communication module is further configured to receive a second credential sent by the cross-chain system, the second credential indicating that the cross-chain business has been completed; the second credential is generated by the cross-chain system verifying the second proof sent by each of the at least one second proxy component, and when all the second proofs are verified successfully, the second proof is generated by each second proxy component based on the second execution result of the corresponding second business.

[0033] Sixthly, embodiments of the present invention also provide a cross-blockchain data processing device applied in a second proxy component; the device includes a third communication module and a third processing module;

[0034] The third communication module is used to receive a second request sent by the first proxy component. The second request is used to request the second blockchain associated with the second proxy component to execute a corresponding second business. The second request includes at least a first credential, which is generated by the cross-chain system based on the first request sent by the first proxy component. The first request is used to request the initiation of a cross-chain business. The first request includes at least a first proof, which is generated by the first proxy component based on the first execution result of the first business. The cross-chain business includes the first business and at least one second business. The first business is executed by the first blockchain associated with the first proxy component, and the at least one second business is executed by the second blockchain associated with each of the at least one second proxy component.

[0035] The third processing module is used to obtain the second execution result of the second service and generate a second proof based on the second execution result;

[0036] The third communication module is further configured to send the second proof to the cross-chain system; and to receive the second credential sent by the cross-chain system, the second credential indicating that the cross-chain business has been completed; the second credential is generated by the cross-chain system verifying the second proof sent by each of the at least one second proxy component, and when all the second proofs have been verified.

[0037] In a seventh aspect, embodiments of the present invention provide a cross-blockchain data processing system, including a cross-chain system, a first proxy component, and at least one second proxy component; wherein, the cross-chain system is used to implement the steps of the method described in the first aspect; the first proxy component is used to implement the steps of the method described in the second aspect; and the second proxy component is used to implement the steps of the method described in the third aspect.

[0038] Eighthly, embodiments of the present invention provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect; or, when executed by a processor, implements the steps of the method described in the second aspect; or, when executed by a processor, implements the steps of the method described in the third aspect.

[0039] In a ninth aspect, embodiments of the present invention provide a communication device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the steps of the method described in the first aspect; or, when the processor executes the program, it implements the steps of the method described in the second aspect; or, when the processor executes the program, it implements the steps of the method described in the third aspect.

[0040] This invention provides a cross-blockchain data processing method, apparatus, system, device, and storage medium. It employs a cross-chain system in a bypass-assisted manner to participate in cross-chain business processing. After the first blockchain executes its assigned first business, a first proxy component associated with the first blockchain generates a first proof based on the first execution result of the first business and initiates a cross-chain business request. The cross-chain system receives the first proof and sends a first credential to the first proxy component. Thus, the first proxy component can directly initiate the execution of a second business to a second proxy component. After the second blockchain associated with the second proxy component executes its corresponding second business, it sends a second proof to the cross-chain system. After verifying all second proofs, the cross-chain system issues a second credential indicating the completion of the cross-chain business execution to both the first and second proxy components. During this process, the cross-chain system does not participate in data forwarding between blockchain systems, avoiding security risks such as privacy leaks introduced by cross-chain systems. By ensuring credibility through two proofs and two credentials, the cross-chain system's involvement in the transaction processing is reduced. Simultaneously, the second blockchain associated with the second proxy component can asynchronously execute its assigned second business, reducing the cross-chain waiting latency of the first blockchain and improving the efficiency of cross-chain business execution. Attached Figure Description

[0041] Figure 1 This is a flowchart illustrating the cross-blockchain data processing method according to an embodiment of the present invention. Figure 1 ;

[0042] Figure 2 This is a flowchart illustrating the cross-blockchain data processing method according to an embodiment of the present invention. Figure 2 ;

[0043] Figure 3 This is a flowchart illustrating the cross-blockchain data processing method according to an embodiment of the present invention. Figure 3 ;

[0044] Figure 4 This is a schematic diagram of the composition structure of a cross-blockchain data processing system according to an embodiment of the present invention;

[0045] Figure 5 This is a model example diagram of cross-blockchain implementation according to an embodiment of the present invention;

[0046] Figure 6This is a schematic diagram illustrating the interaction process of the cross-blockchain data processing method according to an embodiment of the present invention applied to a cross-chain transaction scenario;

[0047] Figure 7 This is a schematic diagram of the composition structure of a cross-blockchain data processing device according to an embodiment of the present invention. Figure 1 ;

[0048] Figure 8 This is a schematic diagram of the composition structure of a cross-blockchain data processing device according to an embodiment of the present invention. Figure 2 ;

[0049] Figure 9 This is a schematic diagram of the composition structure of a cross-blockchain data processing device according to an embodiment of the present invention. Figure 3 ;

[0050] Figure 10 This is a schematic diagram of the structure of a communication device according to an embodiment of the present invention. Detailed Implementation

[0051] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

[0052] In the description of this invention, it should be noted that the terms "first," "second," "third," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. These terms are merely used to distinguish one element (or threshold, application, instruction, or operation) from another element (or threshold, application, instruction, or operation). For example, a first operation may be referred to as a second operation, and a second operation may be referred to as a first operation, without departing from the scope of this invention. Both the first and second operations are operations, but they are not the same operation.

[0053] In this embodiment of the invention, the term "and / or" refers to any and all possible combinations including one or more of the associated enumerated items. It should also be noted that, when used in this specification, "comprising / including" specifies the presence of the stated features, integers, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, and / or components and / or groups thereof.

[0054] The steps in the embodiments of the present invention are not necessarily processed in the described order. The steps can be selectively rearranged, deleted, or added as needed. The step descriptions in the embodiments of the present invention are only optional combinations of order and do not represent all possible combinations of steps in the embodiments of the present invention. The order of steps in the embodiments should not be considered as a limitation of the present invention.

[0055] This invention provides a cross-blockchain data processing method, which is applied to a cross-chain system; Figure 1 This is a flowchart illustrating the cross-blockchain data processing method according to an embodiment of the present invention. Figure 1 ,like Figure 1 As shown, the method includes:

[0056] Step 101: Receive a first request sent by the first proxy component. The first request is used to request the initiation of a cross-chain service. The first request includes at least a first proof, which is generated by the first proxy component based on the first execution result of the first service. The cross-chain service includes the first service and at least one second service. The first service is executed by the first blockchain associated with the first proxy component, and the at least one second service is executed by the second blockchain associated with each of the at least one second proxy component.

[0057] Step 102: Send a first credential to the first proxy component. The first credential is used by the first proxy component to send a second request to each second proxy component. The second request includes at least the first credential. The second request is used to request the second blockchain associated with the second proxy component to execute the corresponding second business.

[0058] Step 103: Receive the second proof sent by each second agent component, wherein the second proof is generated by each second agent component based on the second execution result of the corresponding second service;

[0059] Step 104: Verify the second proof sent by each second proxy component, and generate a second credential if all second proofs are verified successfully; send the second credential to the first proxy component and the at least one second proxy component respectively, the second credential indicating that the cross-chain business has been completed.

[0060] In the various embodiments of this invention, the cross-chain business involves at least two blockchains participating in the business data processing. Each participating blockchain is responsible for a portion of the processing content, which can be referred to as a sub-business. The blockchain that initially initiates the cross-chain business request can be called the initiating blockchain, and the remaining participating blockchains can be called the receiving blockchains.

[0061] In this embodiment, the cross-chain system can be a gateway device, a server, or a blockchain, blockchain system, etc. The cross-chain system can communicate with a first proxy component and a second proxy component respectively. The first proxy component is associated with a first blockchain, and each second proxy component is associated with each second blockchain. For example, the first proxy component can be integrated into the associated first blockchain, and the first blockchain can communicate with the cross-chain system based on the associated first proxy component. The second proxy component can be integrated into the associated second blockchain, and the second blockchain can communicate with the cross-chain system based on the associated second proxy component. Optionally, in various embodiments of the present invention, the first proxy component can also be installed, deployed, set, or configured in the first blockchain, or the first proxy component can communicate with the first blockchain, etc. The second proxy component can also be installed, deployed, set, or configured in the second blockchain, or the second proxy component can communicate with the second blockchain, etc. The name indicating "association" can be equivalent or replaced as needed.

[0062] In one embodiment, the first blockchain may be, for example, the initiating blockchain of a cross-chain transaction, and the first transaction is a sub-transaction executed by the initiating blockchain; the at least one second blockchain may be, for example, any other blockchain participating in the cross-chain transaction besides the initiating blockchain, i.e., the receiving blockchain of the cross-chain transaction, and the at least one transaction is a sub-transaction executed by the at least one second blockchain respectively. As an example, the cross-chain transaction may be, for example, a cross-chain transaction transaction, where the first transaction may be a sub-transaction initiating a transaction, and the second transaction may be any other sub-transactions of the cross-chain transaction transaction besides the transaction initiating sub-transaction.

[0063] In step 101, the cross-chain system receives a first request sent by the first proxy component. The first request includes at least a first proof, which is generated by the first proxy component based on the first execution result of the first business performed on the associated first blockchain. In other words, the first blockchain can first perform the first business, obtain the first execution result, and then generate the first proof from the first proxy component associated with the first blockchain. The first proxy component then sends a first request to the cross-chain system based on the first proof to initiate a cross-chain business.

[0064] In some embodiments, the first proxy component may generate the first proof based on agreed rules or data formats.

[0065] In this embodiment, the first proof can be used by the cross-chain system to verify the first execution result. In step 102, the cross-chain system sends a first credential to the first proxy component, and the first proxy component can send a second request to the at least one second proxy component based on the first credential to request the second blockchain associated with each second proxy component to execute the second business corresponding to the second blockchain.

[0066] In some embodiments, the first proof may include at least the index information of the first service, the first hash value generated by the first proxy component based on the first execution result, and the signature information of the first blockchain. For example, the first proof may include the index number index1 of the first service, the hash H(tx1) of the execution result of the first service, and the signature Sig1 of the first blockchain, etc.

[0067] In some embodiments, the index information of the first service can be used to identify the first service, or it can be used to identify the cross-chain service and the first service.

[0068] In some embodiments, the first request may also include identification information of the first blockchain.

[0069] In some embodiments, the first credential may include at least index information of the first business and signature information of the cross-chain system, wherein the signature information may include the signature and timestamp of the cross-chain system.

[0070] In some embodiments, the cross-chain system may also send the address information of the second blockchain associated with each of the at least one second proxy component to the first proxy component, so that the first proxy component sends a second request to the at least one second proxy component, wherein the address information may be, for example, the cross-chain port address of the second blockchain or the contract address between the second blockchain and the cross-chain system.

[0071] In some embodiments, the second request may also include business data required for the second blockchain associated with the second proxy component to perform the corresponding second business.

[0072] In step 103, the cross-chain system receives second proofs sent by each of the at least one second proxy component. Each second proof is generated by each second proxy component based on the second execution result of the corresponding second business. Further, the cross-chain system verifies the second proofs sent by each second proxy component, and generates a second credential representing the completion of the cross-chain business execution if all second proofs pass verification. The system then sends the second credential to the first proxy component and at least one second proxy component. It is understood that the cross-chain system in this embodiment does not participate in the forwarding of business data between the two parties, thus avoiding risks such as privacy leaks introduced by the cross-chain system. The credibility of the cross-chain business execution is ensured by issuing the first credential and verifying the execution result proofs obtained from the respective business executions (i.e., the first and second proofs).

[0073] In step 104, the cross-chain system can generate and issue a unique second credential. Based on the first credential and the second credential, they can be associated through the index information of the first business or each second business. The first proxy component and the second proxy component can obtain the execution status of the cross-chain business through the first credential or the second credential.

[0074] In some embodiments, the second proof includes a hash value generated by the second proxy component based on the second execution result of the second business, and the cross-chain system can verify the second proof based on the hash value.

[0075] The cross-blockchain data processing method of this invention employs a cross-chain system in a bypass-assisted manner to participate in cross-chain business processing. After the first blockchain executes the first business it is responsible for, the first proxy component associated with the first blockchain generates a first proof based on the first execution result of the first business and initiates a cross-chain business request. After receiving the first proof, the cross-chain system sends a first credential to the first proxy component, thereby allowing the first proxy component to directly initiate the execution of a second business to the second proxy component. After the second blockchain associated with the second proxy component executes the corresponding second business, it sends a second proof to the cross-chain system. After verifying all second proofs, the cross-chain system issues a cross-chain business representation to the first and second proxy components. The second credential is executed, and during this process, the cross-chain system does not participate in data forwarding between blockchain systems, thus avoiding security risks such as privacy leaks introduced by the cross-chain system. Under the premise of ensuring credibility through two proofs and two credentials, the participation of the cross-chain system in the transaction processing is reduced, avoiding the impact of cross-chain system forwarding failure on the normal operation of cross-chain business. At the same time, when the business data is large, the transmission latency is large, or the communication between the second blockchain and the cross-chain system fails, the cross-chain system can first issue the first credential to the first blockchain. The second blockchain associated with the second proxy component can asynchronously execute the second business it is responsible for, reducing the cross-chain waiting latency of the first blockchain and improving the execution efficiency of cross-chain business.

[0076] In an optional embodiment of the present invention, the first proof includes at least the index information of the first service, the first hash value generated by the first proxy component based on the first execution result, and the signature information of the first blockchain; the method may further include: verifying the first proof, and generating the first credential if the verification is successful, wherein the first credential includes at least the index information of the first service and the signature information of the cross-chain system.

[0077] For example, the first proof may include the index number index1 of the first business, the hash H(tx1) of the execution result of the first business, the signature Sig1 of the first blockchain, etc.

[0078] In some embodiments, the cross-chain system verifies the first proof, which may include: the cross-chain system verifies the first hash value.

[0079] In some embodiments, the first credential may include at least index information of the first business and signature information of the cross-chain system, wherein the signature information may include the signature and timestamp of the cross-chain system.

[0080] In this embodiment, after the cross-chain system verifies the first proof corresponding to the first business, it issues a first credential indicating that the cross-chain business has been successfully initiated. The credibility of the cross-chain business is guaranteed by the first proof and the first credential.

[0081] In an optional embodiment of the present invention, the second proof includes at least the index information of the second service, the second hash value generated by the second proxy component based on the second execution result, and the signature information of the second blockchain.

[0082] In this embodiment, each of the at least one second proxy components can obtain the second execution result of the second business corresponding to the second blockchain execution, and generate a corresponding second proof based on the second execution result, and send the second proof to the cross-chain system.

[0083] For example, the second proof may include at least the index number index2 of the second business, the hash H(tx2) of the execution result of the second business, and the signature Sig2 of the second blockchain.

[0084] In some embodiments, the index information of the second service can be used to identify the second service, or it can be used to identify the cross-chain service and the second service.

[0085] In some embodiments, the second hash value can be used by the cross-chain system to verify the second execution result of the second business, that is, to verify the second proof.

[0086] In some embodiments, the second proof has the same data structure as the first proof. It is understood that the second proxy component can generate the corresponding proof (i.e., the first proof or the second proof) based on the same agreed rules or data format as the first proxy component.

[0087] The cross-blockchain data processing method of this invention avoids the risks of privacy leakage introduced by the cross-blockchain system by not participating in the forwarding of business data between blockchain systems. Moreover, the business execution result returned by the receiver and the verification of the business execution result proof can be completed by different entities and can be executed synchronously. The business execution result of the receiver does not need to be re-verified by the cross-blockchain system each time before being resent to the initiator. The cross-blockchain efficiency is high and it can be applied to one-to-one and one-to-many cross-blockchain scenarios. Especially in the one-to-many scenario, the execution and execution result verification of multiple second business are completed by different entities. That is, the second blockchain executes the second business, and the cross-blockchain system verifies the execution results of each second business, which significantly improves the efficiency of cross-blockchain.

[0088] In an optional embodiment of the present invention, the second credential includes at least the index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain, the identification information of each of the second blockchains, and the signature information of the cross-chain system.

[0089] In this embodiment, the cross-chain system verifies the second proof sent by each of the at least one second proxy component, and generates a second certificate when all second proofs are verified. The second certificate represents the completion of the cross-chain business and can be used by the first blockchain or the second blockchain to confirm the completion of the cross-chain business.

[0090] In some embodiments, the verification of the second proof sent by each second proxy component may include: the cross-chain system may verify the second hash value in the second proof sent by each second proxy component.

[0091] In some embodiments, the signature information of the cross-chain system may include the signature and signature timestamp of the cross-chain system.

[0092] The cross-blockchain data processing method of this invention employs a cross-chain system in a bypass auxiliary manner to participate in cross-chain business processing. When a first proxy component integrated in the first blockchain initiates a cross-chain business request, it first needs to execute the first business handled by the first blockchain. The first proxy component sends the execution result proof (i.e., the first proof) corresponding to the first business to the cross-chain system, and based on the first credential sent by the cross-chain system, it initiates the execution of a second business to a second proxy component. The second blockchain asynchronously executes the second business it is responsible for, and submits the execution result proof (i.e., the second proof) of the second business to the cross-chain system through the integrated second proxy component. The cross-chain system receives the execution result proofs of all businesses sent by the first proxy component and all second proxy components. After the cross-chain business is confirmed to be completed, a transaction completion certificate (i.e., the second certificate) is issued to the first and second proxy components. This process enables asynchronous execution of the cross-chain business initiated by the first blockchain (i.e., the cross-chain business initiator) and the business executed by the second blockchain (i.e., the other participants in the cross-chain business). The first blockchain does not need to wait for the response from the second blockchain to confirm whether the cross-chain business has been successfully initiated. At the same time, the atomicity of the cross-chain business execution is guaranteed by issuing the first and second certificates in two separate transactions. This decouples the cross-chain business initiation and confirmation processes, reduces the number of interactions in the cross-chain business execution, and reduces the waiting time of the business initiator blockchain. The cross-chain business execution is more efficient, has lower latency, and is more robust.

[0093] Based on the foregoing embodiments, this invention also provides a cross-blockchain data processing method. In this embodiment, the method may further include: receiving a third request sent by a proxy component, the third request being used to request blockchain registration and / or address information registration; sending first information to the proxy component, the first information including identification information of the blockchain associated with the proxy component and / or address information of the blockchain associated with the proxy component, the address information including the cross-chain port address of the blockchain or the contract address between the blockchain and the cross-chain system; wherein the proxy component is the first proxy component and / or the second proxy component.

[0094] In this embodiment, the third request can be used to request blockchain registration, and the cross-chain system sends first information to the proxy component, the first information including the identification information of the blockchain associated with the proxy component; or, the third request can be used to request address information registration, and the cross-chain system sends first information to the proxy component, the first information including the address information of the blockchain associated with the proxy component; or, the third request can be used to request both blockchain registration and address information registration, and the cross-chain system sends first information to the proxy component, the first information including the identification information and address information of the blockchain associated with the proxy component; wherein, the address information includes the cross-chain interface address of the blockchain associated with the proxy component or the contract address between the blockchain associated with the proxy component and the cross-chain system.

[0095] In some embodiments, the cross-chain system may store the identification information and / or address information of the blockchains associated with each proxy component, or it may store the association between the identification information and address information of the blockchains associated with each proxy component, so that the corresponding address information can be obtained by querying the identification information of the blockchain.

[0096] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain; the method may further include: obtaining address information of the at least one second blockchain based on the identification information of the at least one second blockchain, and sending the address information of the at least one second blockchain to the first proxy component. In this embodiment, the address information of each second blockchain can be used by the first proxy component to send the second request to a second proxy component associated with each second blockchain.

[0097] In this embodiment, the cross-chain system does not participate in the forwarding of business execution result data between blockchain systems, thus avoiding security risks such as privacy leaks introduced by the cross-chain system. It also significantly reduces the involvement of the cross-chain system in the cross-chain business processing, effectively reducing the total time consumed by cross-chain business.

[0098] In some embodiments, the cross-chain system may store a first proof corresponding to a first business, a second proof corresponding to a second business, and a first and second credential for the cross-chain business. Optionally, the cross-chain system may provide query services to the first proxy component and the at least one second proxy component.

[0099] For example, the cross-chain system can also receive a fourth request sent by a proxy component. This fourth request is used to query cross-chain services and send the corresponding query results to the proxy component. The proxy component can be a first proxy component or a second proxy component. Optionally, the fourth request may include index information of the first service or index information of the second service.

[0100] This invention also provides a cross-blockchain data processing method, which is applied in a first proxy component; Figure 2 This is a flowchart illustrating the cross-blockchain data processing method according to an embodiment of the present invention. Figure 2 ,like Figure 2 As shown, the method includes:

[0101] Step 201: Obtain the first execution result of the first business, and generate a first proof based on the first execution result;

[0102] Step 202: Send a first request to the cross-chain system. The first request is used to request the initiation of a cross-chain service. The first request includes at least the first proof. The cross-chain service includes the first service and at least one second service. The first service is executed by the first blockchain associated with the first proxy component, and the at least one second service is executed by the second blockchain associated with each of the at least one second proxy component.

[0103] Step 203: Receive the first credential sent by the cross-chain system, and send a second request to each second proxy component, wherein the second request includes at least the first credential; the second request is used to request the second blockchain associated with the second proxy component to execute the corresponding second business.

[0104] Step 204: Receive the second credential sent by the cross-chain system. The second credential indicates that the cross-chain business has been completed. The second credential is generated by the cross-chain system after verifying the second proof sent by each of the at least one second proxy component and after all the second proofs have been verified. The second proof is generated by each second proxy component based on the second execution result of the corresponding second business.

[0105] In this embodiment, the relevant descriptions of steps 201 to 204 can be referred to the detailed descriptions of steps 101 to 104 in the previous embodiments. To save space, they will not be repeated here.

[0106] In this embodiment, the first proxy component may be integrated, installed, deployed, set up, or configured in the associated first blockchain; alternatively, the first proxy component may be communicatively connected to the first blockchain. The first blockchain may communicate with the cross-chain system based on the associated first proxy component.

[0107] In some embodiments, the first proxy component may be in the form of a module, component, node, device, or smart contract.

[0108] In an optional embodiment of the present invention, generating the first proof based on the first execution result may include: generating a first hash value based on the first execution result, wherein the first hash value is used by the cross-chain system to verify the first execution result; generating the first proof according to the index information of the first business, the first hash value, and the signature information of the first blockchain; the first credential being generated by the cross-chain system verifying the first proof and, if the verification is successful; the first credential including at least the index information of the first business and the signature information of the cross-chain system.

[0109] In one embodiment, the first hash value can also be used by the cross-chain system to verify the first proof.

[0110] In an optional embodiment of the present invention, the second credential includes at least index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain and the identification information of each of the second blockchains, and the signature information of the cross-chain system; the second proof includes at least index information of the second service, a second hash value generated by the second proxy component based on the second execution result, and the signature information of the second blockchain.

[0111] In an optional embodiment of the present invention, the method may further include: sending a third request to the cross-chain system, the third request being used to request blockchain registration and / or address information registration; receiving first information sent by the cross-chain system, the first information including the identification information of the first blockchain and / or the address information of the first blockchain, the address information including the cross-chain interface address of the first blockchain or the contract address between the first blockchain and the cross-chain system.

[0112] In this embodiment, the third request can be used to request blockchain registration, whereby the first proxy component receives first information sent by the cross-chain system, the first information including the identifier information of the first blockchain associated with the first proxy component; or, the third request can be used to request address information registration, whereby the first proxy component receives first information sent by the cross-chain system, the first information including the address information of the first blockchain associated with the first proxy component; or, the third request can be used to request both blockchain registration and address information registration, whereby the first proxy component receives first information sent by the cross-chain system, the first information including the identifier information and address information of the first blockchain associated with the first proxy component; wherein the address information includes the cross-chain interface address of the first blockchain associated with the first proxy component or the contract address between the first blockchain associated with the first proxy component and the cross-chain system.

[0113] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain; the method may further include: receiving address information of the at least one second blockchain sent by the cross-chain system; the step of sending a second request to each second proxy component may include: sending the second request to a second proxy component associated with the second blockchain based on the address information of each second blockchain.

[0114] In an optional embodiment of the present invention, the method may further include: establishing an association between the first credential and the second credential, wherein the association is stored by the first blockchain.

[0115] In some embodiments, the first proxy component may establish an association between the first credential and the second credential based on the index information of the first service.

[0116] In an optional embodiment of the present invention, the second request further includes service data of the second service corresponding to each second proxy component; the method may further include: receiving the second execution result of the second service sent by the second proxy component.

[0117] In this embodiment, the business data of the second service includes, for example, the business data required by the second blockchain associated with each second agent component to execute the second service.

[0118] In some embodiments, the first proxy component may send a fourth request to the cross-chain system, the fourth request being used to request a query for cross-chain services and receive the query results sent by the cross-chain system. Optionally, the fourth request may include index information of the first service executed by the first blockchain associated with the first proxy component.

[0119] This invention also provides a cross-blockchain data processing method, which is applied to a second proxy component; Figure 3 This is a flowchart illustrating the cross-blockchain data processing method according to an embodiment of the present invention. Figure 3 ,like Figure 3 As shown, the method includes:

[0120] Step 301: Receive a second request sent by the first proxy component. The second request is used to request the second blockchain associated with the second proxy component to execute a corresponding second business. The second request includes at least a first credential, which is generated by the cross-chain system based on the first request sent by the first proxy component. The first request is used to request the initiation of a cross-chain business. The first request includes at least a first proof, which is generated by the first proxy component based on the first execution result of the first business. The cross-chain business includes the first business and at least one second business. The first business is executed by the first blockchain associated with the first proxy component, and the at least one second business is executed by the second blockchain associated with each of the at least one second proxy component.

[0121] Step 302: Obtain the second execution result of the second business, generate a second proof based on the second execution result, and send the second proof to the cross-chain system;

[0122] Step 303: Receive the second credential sent by the cross-chain system. The second credential indicates that the cross-chain business has been completed. The second credential is generated by the cross-chain system after verifying the second proof sent by each of the at least one second proxy component and after all the second proofs have been verified.

[0123] In this embodiment, the relevant descriptions of steps 301 to 303 can be referred to the detailed descriptions of steps 101 to 104 in the previous embodiments. To save space, they will not be repeated here.

[0124] In this embodiment, the second proxy component can be integrated, installed, deployed, set up, or configured in the associated second blockchain; alternatively, the second proxy component can communicate with the second blockchain. The second blockchain can communicate with the cross-chain system based on the associated second proxy component.

[0125] In some embodiments, the second proxy component may be in the form of a module, component, node, device, or smart contract.

[0126] It should be noted that the second proxy component in this embodiment has the same function as the first proxy component. Any function or method implemented by the first proxy component should be applicable to the second proxy component, and similarly, any function or method implemented by the second proxy component should also be applicable to the first proxy component.

[0127] In an optional embodiment of the present invention, the first proof includes at least the index information of the first service, the first hash value generated by the first proxy component based on the first execution result, and the signature information of the first blockchain; the first credential is generated by the cross-chain system after verifying the first proof and if the verification is successful; the first credential includes at least the index information of the first service and the signature information of the cross-chain system.

[0128] In some embodiments, the first hash value can be used by the cross-chain system to verify the first proof, or by the cross-chain system to verify the first execution result of the first business.

[0129] In an optional embodiment of the present invention, generating a second proof based on the second execution result may include: generating a second hash value based on the second execution result, the second hash value being used by the cross-chain system to verify the second execution result; generating a second proof based on the index information of the second business, the second hash value, and the signature information of the second blockchain; the second proof being used by the cross-chain system to verify the completion status of the cross-chain business.

[0130] In this embodiment, after each second blockchain executes the corresponding second business and obtains the second execution result, the second proxy component generates the corresponding second proof based on the second execution result and sends the second proof to the cross-chain system so that the cross-chain system can verify the existence of the second business undertaken by each second blockchain.

[0131] In some embodiments, the second hash value can be used by the cross-chain system to verify the second proof, or the second hash value can be used by the cross-chain system to verify the second execution result of the second business.

[0132] In an optional embodiment of the present invention, the second credential includes at least the index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain, the identification information of each of the second blockchains, and the signature information of the cross-chain system.

[0133] In an optional embodiment of the present invention, the method may further include: sending a third request to the cross-chain system, the third request being used to request blockchain registration and / or address information registration; receiving first information sent by the cross-chain system, the first information including the identification information of the second blockchain and / or the address information of the second blockchain, the address information including the cross-chain interface address of the second blockchain or the contract address between the second blockchain and the cross-chain system.

[0134] In this embodiment, the third request can be used to request blockchain registration, and the second proxy component receives first information sent by the cross-chain system, the first information including the identification information of the second blockchain associated with the second proxy component; or, the third request can be used to request address information registration, the second proxy component receives first information sent by the cross-chain system, the first information including the address information of the second blockchain associated with the second proxy component; or, the third request can be used to request both blockchain registration and address information registration, the second proxy component receives first information sent by the cross-chain system, the first information including the identification information and address information of the second blockchain associated with the second proxy component; wherein, the address information includes the cross-chain interface address of the second blockchain associated with the second proxy component or the contract address between the second blockchain associated with the second proxy component and the cross-chain system.

[0135] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain, wherein the identification information of the at least one second blockchain is used by the cross-chain system to determine the address information of each second blockchain, and the address information of each second blockchain is used by the first proxy component to send the second request to the second proxy component associated with the second blockchain.

[0136] In an optional embodiment of the present invention, the method may further include: establishing an association between the first credential and the second credential, wherein the association is stored by the second blockchain.

[0137] In some embodiments, the second proxy component may establish an association between the first credential and the second credential based on the index information of the second service.

[0138] In an optional embodiment of the present invention, the second request further includes business data of the second service corresponding to the second proxy component; the method may further include: sending the second execution result to the first proxy component.

[0139] In this embodiment, the business data of the second service includes, for example, the business data required by the second blockchain associated with each second agent component to execute the second service.

[0140] In some embodiments, the second proxy component may send a fourth request to the cross-chain system, the fourth request being used to request a query for cross-chain services and receive the query results sent by the cross-chain system. Optionally, the fourth request may include index information of the second service executed by the second blockchain associated with the second proxy component.

[0141] This invention also provides a cross-blockchain data processing system. Figure 4 This is a schematic diagram of the composition structure of a cross-blockchain data processing system according to an embodiment of the present invention, as shown below. Figure 4 As shown, the cross-blockchain data processing system 400 may include a cross-chain system 410, a first proxy component 420, and at least one second proxy component. Figure 4 Only one second agent component 430 is shown in the diagram; where,

[0142] The first proxy component 420 is used to generate a first proof based on the first execution result of the first business, and send a first request to the cross-chain system 410. The first request is used to request the initiation of a cross-chain business. The first request includes at least the first proof.

[0143] The cross-chain system 410 is used to receive a first request sent by the first proxy component 420 and send a first credential to the first proxy component 420.

[0144] The first proxy component 420 is further configured to send a second request to each second proxy component, wherein the second request includes at least the first credential; the second request is used to request the second blockchain associated with the second proxy component to execute a corresponding second business.

[0145] The second proxy component 430 is used to receive a second request sent by the first proxy component 420; obtain a second execution result of the second service; generate a second proof based on the second execution result; and send the second proof to the cross-chain system 410.

[0146] The cross-chain system 410 is further configured to receive a second proof sent by each second proxy component, verify the second proof sent by each second proxy component, generate a second credential if all second proofs are verified, and send the second credential to the first proxy component 420 and the at least one second proxy component respectively, wherein the second credential indicates that the cross-chain business has been completed.

[0147] The first proxy component 420 and the second proxy component 430 are also used to receive the second credential sent by the cross-chain system 410;

[0148] The cross-chain service includes the first service and at least one second service. The first service is executed by the first blockchain associated with the first proxy component, and the at least one second service is executed by the second blockchain associated with each of the at least one second proxy component.

[0149] In an optional embodiment of the invention, the first proxy component 420 is configured to generate a first hash value based on the first execution result, the first hash value being used by the cross-chain system 410 to verify the first execution result; and to generate the first proof based on the index information of the first business, the first hash value, and the signature information of the first blockchain.

[0150] The cross-chain system 410 is used to verify the first proof and generate the first credential if the verification is successful; the first credential includes at least the index information of the first business and the signature information of the cross-chain system.

[0151] In an optional embodiment of the present invention, the second proxy component 430 is configured to generate a second hash value based on the second execution result, the second hash value being used by the cross-chain system to verify the second execution result; and to generate a second proof based on the index information of the second business, the second hash value, and the signature information of the second blockchain.

[0152] In an optional embodiment of the present invention, the second credential includes at least the index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain, the identification information of each of the second blockchains, and the signature information of the cross-chain system.

[0153] In an optional embodiment of the present invention, the cross-chain system 410 is further configured to receive a third request sent by a proxy component, the third request being used to request blockchain registration and / or address information registration; and to send first information to the proxy component, the first information including the identification information of the blockchain associated with the proxy component and / or the address information of the blockchain associated with the proxy component, the address information including the cross-chain interface address of the blockchain or the contract address between the blockchain and the cross-chain system; wherein the proxy component is the first proxy component 420 and / or the second proxy component 430.

[0154] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain; the cross-chain system 410 is further configured to obtain address information of at least one second blockchain based on the identification information of at least one second blockchain, and send the address information of at least one second blockchain to the first proxy component 420.

[0155] The first proxy component 420 is further configured to receive address information of at least one second blockchain sent by the cross-chain system 410, and send the second request to the second proxy component associated with each second blockchain based on the address information of each second blockchain.

[0156] In an optional embodiment of the present invention, the first proxy component 420 is further configured to send a third request to the cross-chain system 410, the third request being used to request blockchain registration and / or address information registration; and to receive first information sent by the cross-chain system 410, the first information including the identification information of the first blockchain and / or the address information of the first blockchain, the address information including the cross-chain interface address of the first blockchain or the contract address between the first blockchain and the cross-chain system.

[0157] In an optional embodiment of the present invention, the second proxy component 430 is further configured to send a third request to the cross-chain system 410, the third request being used to request blockchain registration and / or address information registration; and to receive first information sent by the cross-chain system 410, the first information including the identification information of the second blockchain and / or the address information of the second blockchain, the address information including the cross-chain interface address of the second blockchain or the contract address between the second blockchain and the cross-chain system.

[0158] In an optional embodiment of the present invention, the first proxy component 420 is further configured to establish an association between the first credential and the second credential, the association being stored by the first blockchain.

[0159] In an optional embodiment of the present invention, the second proxy component 430 is further configured to establish an association between the first credential and the second credential, the association being stored by the second blockchain.

[0160] In an optional embodiment of the present invention, the second request further includes service data of the second service corresponding to each second proxy component; the second proxy component 430 is further configured to send the second execution result of the second service to the first proxy component 420; the first proxy component 420 is further configured to receive the second execution result of the second service sent by the second proxy component 430.

[0161] In some embodiments, the first proxy component 420 or the second proxy component 430 is further configured to send a fourth request to the cross-chain system 410, the fourth request being used to request a query for cross-chain services; the cross-chain system 410 is further configured to send query results to the first proxy component 420 or the second proxy component 430. Optionally, the fourth request may include index information of the first service or index information of the second service.

[0162] The cross-chain system 410 in the various embodiments of the present invention is the same as the cross-chain system in the aforementioned method embodiments, the first proxy component 420 is the same as the first proxy component in the aforementioned method embodiments, and the second proxy component 430 is the same as the second proxy component in the aforementioned embodiments, as can be referred to in the description of the aforementioned embodiments.

[0163] The cross-blockchain data processing solution of the present invention will be described in detail below with specific application scenarios.

[0164] This example uses cross-chain transactions as an illustration. Specifically, a cross-chain system is introduced to assist business interactions between different blockchains. The cross-chain system can verify the existence of sub-transactions handled by each blockchain through sub-transaction execution proofs (i.e., the aforementioned first proof and second proof). At the same time, the atomicity of cross-chain transactions is guaranteed by issuing certificates twice (i.e., the aforementioned first certificate and second certificate), and the cross-chain transaction initiation process and transaction confirmation process are decoupled, reducing the number of interactions in cross-chain transaction processing and reducing the waiting time of the initiating blockchain (i.e., the first blockchain).

[0165] Figure 5 This is an example diagram of a cross-blockchain model according to an embodiment of the present invention, such as... Figure 5 As shown, the cross-chain transaction in this example involves at least two blockchain systems in the transaction processing. Each participating blockchain system is responsible for processing a portion of the transaction content, referred to as a sub-transaction. In this example, the blockchain that initially initiates the cross-chain transaction request is called the initiating blockchain, and the other participating blockchains are called the receiving blockchains. A cross-chain system is introduced to participate in the cross-chain transaction processing in a bypass manner.

[0166] In this example, the cross-chain system 510 can be an independent gateway or a blockchain system. If the cross-chain system 510 is a gateway device, it must possess the essential functions for cross-chain interaction. If the cross-chain system 510 is a blockchain system, it must ensure its own security and persistently store the cross-chain process data on the blockchain to further ensure the trustworthiness of the cross-chain process and the traceability of cross-chain transactions. The functions of the cross-chain system 510 may include: receiving and verifying cross-chain requests; verifying the proof of sub-transaction execution results; generating cross-chain transaction certificates; registering and managing blockchain system identifiers; registering and managing blockchain cross-chain interface addresses; storing and uploading cross-chain transaction execution result proofs and cross-chain transaction certificates to the blockchain; and querying cross-chain transactions.

[0167] like Figure 5As shown, the initiating blockchain system 520 may include an initiating blockchain integrated with a cross-chain proxy component, and the receiving blockchain system 530 may include a receiving blockchain integrated with a cross-chain proxy component to support other functions required during cross-chain interaction besides sub-transaction execution. For example, the cross-chain proxy component may include the following functions: cross-chain request generation; sub-transaction execution result proof generation; blockchain system identifier storage and use; transaction certificate reception, association, and storage; cross-chain data encapsulation and interface calls, etc. It can be understood that the initiating blockchain system 520 in this example may specifically include the first blockchain and the first proxy component associated with the first blockchain in the aforementioned embodiments, and the first proxy component is integrated into the first blockchain; the receiving blockchain system 530 may specifically include the second blockchain and the second proxy component associated with the second blockchain in the aforementioned embodiments, and the second proxy component is integrated into the second blockchain.

[0168] In this example, when the initiating blockchain system 520 initiates a cross-chain transaction, it first executes the sub-transactions it is responsible for, and sends the sub-transaction execution result proof (i.e., the first proof) to the cross-chain system 510 to request the sub-transaction certificate (i.e., the first certificate) and the receiving blockchain interface address. Then, it calls the receiving blockchain to start the sub-transaction on the other end. The receiving blockchain system 530 asynchronously executes the sub-transactions it is responsible for and returns the sub-transaction execution result to the initiating blockchain system 520. At the same time, it submits the execution result proof (i.e., the second proof) to the cross-chain system 510. After receiving the sub-transaction execution result proofs from the initiating blockchain system 520 and all receiving blockchain systems 530, the cross-chain system 510 returns the final transaction certificate (i.e., the second certificate).

[0169] Reference Figure 5 The cross-chain model shown, Figure 6 This is a schematic diagram illustrating the interaction process of the cross-blockchain data processing method of this invention applied to a cross-blockchain transaction scenario (the receiving blockchain can be one or more). Figure 6 (Taking only one receiver's blockchain as an example, such as...) Figure 6 As shown, the process can be divided into three stages, each of which can be executed asynchronously. In other words, the execution of any two stages in this example does not require them to be completely consecutive in time.

[0170] In the first phase, the blockchain initiating the cross-chain transaction first executes the sub-transactions it is responsible for, and the cross-chain proxy component integrated on the initiating blockchain ( Figure 6 To distinguish it from the recipient, the initiator (a cross-chain proxy component) sends a cross-chain request to the cross-chain system carrying the sub-transaction execution result proof. After the cross-chain system verifies the sub-transaction execution result proof, it returns a transaction certificate indicating successful cross-chain transaction initiation and the cross-chain interface address of the recipient's blockchain. Details are as follows:

[0171] Step 611: The initiating blockchain executes the sub-transaction, and the initiating cross-chain proxy component generates an execution result proof. Specifically, the initiating blockchain (i.e., the first blockchain) first executes the sub-transaction (i.e., the first business) it is responsible for, obtains the execution result data, and the initiating cross-chain proxy component (i.e., the first proxy component) integrated on the initiating blockchain generates an execution result proof Proof1 (i.e., the first proof) according to an agreed format. For example, the data structure of the execution result proof Proof1 may include the sub-transaction index number index1, the sub-transaction execution result hash H(tx1), the initiating blockchain node signature Sig1, etc.

[0172] Step 612: The initiating cross-chain proxy component sends a cross-chain request to the cross-chain system. For example, this cross-chain request (i.e., the first request) may carry proof of the sub-transaction execution result, Proof1, and the identifier ID of the receiving blockchain, etc.

[0173] Step 613: The cross-chain system verifies the cross-chain request and the proof of the sub-transaction execution result, generating Transaction Certificate 1 (i.e., the first certificate). Specifically, after receiving the cross-chain request, the cross-chain system verifies the proof of the sub-transaction execution result, Proof1. If the verification is successful, it generates Transaction Certificate 1 (Evi1) indicating successful cross-chain transaction initiation, and retrieves the corresponding cross-chain interface address based on the identifier ID of the recipient's blockchain. For example, the data structure of Transaction Certificate 1 (Evi1) may include the sub-transaction index number index1, the signature of the cross-chain system, and a timestamp, etc.

[0174] Step 614: The cross-chain system returns transaction certificate 1 and the recipient's blockchain interface address to the initiating cross-chain proxy component. The recipient's blockchain interface address can be, for example, the cross-chain interface address of the recipient's blockchain or the contract address between the recipient's blockchain and the cross-chain system.

[0175] In the second phase, the cross-chain proxy component integrated on the initiating party's blockchain, carrying transaction credentials and relevant cross-chain business interaction data, sends them to the cross-chain proxy component integrated on the receiving party's blockchain. Figure 6 The receiving blockchain (marked as the cross-chain proxy component) initiates an interaction request. The receiving blockchain executes the sub-transaction it is responsible for and returns the transaction result data to the initiating blockchain (the specific data interaction can be handled by the cross-chain proxy component). Simultaneously, it generates a proof of the sub-transaction execution result and submits it to the cross-chain system. Specifically:

[0176] Step 621: The initiating blockchain calls the cross-link interface of the receiving blockchain, carrying the transaction certificate Evi1 and the business data required for the execution of the receiving sub-transaction, and initiates an interaction request to the receiving blockchain.

[0177] Step 622: The receiving blockchain executes the sub-transaction, and the receiving cross-chain proxy component generates the execution result proof. Specifically, the receiving blockchain (i.e., the second blockchain) executes the sub-transaction (i.e., the second business) it is responsible for, obtains the execution result data, and the receiving cross-chain proxy component (i.e., the second proxy component) integrated on the receiving blockchain generates the execution result proof Proof2 (i.e., the second proof) according to the agreed format.

[0178] Step 623: The receiving cross-chain proxy component returns the sub-transaction execution result to the initiating cross-chain proxy component. Optionally, if the cross-chain transaction itself does not require feedback, then no feedback is needed or a pre-agreed execution completion response needs to be returned. That is, step 623 can be omitted, or the receiving cross-chain proxy component can return a pre-agreed execution completion response to the initiating cross-chain proxy component.

[0179] Step 624: The receiving cross-chain proxy component sends the sub-transaction execution result proof to the cross-chain system. For example, the receiving cross-chain proxy component submits Proof2 (the second proof) to the cross-chain system, which may include the transaction credential Evi1. If the cross-chain transaction involves multiple receiving blockchains, the receiving cross-chain proxy component integrated on each receiving blockchain must submit its own sub-transaction execution result proof.

[0180] In the third stage, after the cross-chain system verifies the execution result of the sub-transaction, it issues transaction certificate two for cross-chain transaction confirmation to the initiator and receiver blockchains (specifically, to the cross-chain proxy components integrated on each blockchain).

[0181] Step 631: The cross-chain system verifies the sub-transaction execution result proof and generates transaction certificate two (i.e., the second certificate). For example, after receiving the sub-transaction execution result proof Proof2 from the receiving blockchain, the cross-chain system verifies Proof2. Upon successful verification, transaction certificate two (Evi2) confirming the cross-chain transaction is generated. The data structure of transaction certificate two (Evi2) may include the sub-transaction index numbers (index1 / index2) of both parties, the identifiers of the initiating and receiving blockchains, the signature of the cross-chain system, and a timestamp. If the cross-chain transaction involves multiple receiving blockchains, all sub-transaction execution result proofs submitted by all receiving blockchains must be collected and verified. Transaction certificate two (Evi2) is generated only after all sub-transaction execution result proofs of each receiving blockchain have been verified. If the cross-chain transaction involves multiple receiving blockchains, transaction certificate two (Evi2) may include the sub-transaction index numbers of the initiating blockchain and all receiving blockchains, the identifiers of the initiating blockchain and all receiving blockchains, the signature of the cross-chain system, and a timestamp.

[0182] Step 632: The cross-chain system issues Transaction Certificate 2 to both the initiating and receiving cross-chain proxy components. Upon receiving the certificate, each cross-chain proxy component can associate Transaction Certificate 1 (Evi1) with Transaction Certificate 2 (Evi2), which is then stored by the corresponding blockchain. Each blockchain can use Transaction Certificate 2 (Evi2) as the final proof of a successful cross-chain transaction.

[0183] This example of a cross-blockchain data processing solution supports cross-blockchain transaction processing through a cross-blockchain system-assisted verification method. In the first and third stages of cross-blockchain transaction processing, the cross-blockchain system is responsible for verifying the authenticity and integrity of cross-blockchain requests and the execution proofs of sub-transactions within the cross-blockchain transaction. Upon successful verification, it generates corresponding cross-blockchain transaction initiation success certificates or cross-blockchain transaction confirmation certificates, providing them to each participating blockchain as markers of successful cross-blockchain initiation or transaction completion. This solution can be applied to one-to-one and one-to-many cross-blockchain scenarios. Particularly in one-to-many scenarios, since the return of sub-transaction execution data and the verification of execution result proofs are completed by different entities—the former being sent directly from the receiving party's cross-blockchain proxy component to the initiating party's cross-blockchain proxy component, and the latter being completed by the cross-blockchain system—the improvement in cross-blockchain efficiency is particularly significant. This solution can be applied to scenarios with high cross-blockchain efficiency requirements, such as high-profile transactions in the financial sector, and also to scenarios where the transaction initiator generates business value upon completing a sub-transaction, such as multi-party collaborative approval.

[0184] When conducting cross-blockchain transactions, related technologies typically employ a relay system (usually a relay gateway or relay chain) as the intermediary between the two parties. The main functions of this relay system include: verifying the authenticity and integrity of the initiator's cross-blockchain request, endorsing the initiator's request data signature, data routing, verifying the authenticity and integrity of the receiver's execution result data, and endorsing the receiver's execution result data signature. In some cases, it may also include functions such as structural transformation of forwarded data. Correspondingly, both the initiator's and receiver's blockchains must have the ability to verify the sent and received data.

[0185] It is understandable that in related technologies, the relay system acts as a trusted medium between the initiating blockchain and the receiving blockchain. Every interaction between the initiating and receiving blockchains relies on the verification capabilities and endorsement credibility of the relay system. This results in the initiating blockchain, after initiating a cross-chain request, needing to go through processes such as relay system verification (data structure conversion), relay system endorsement, forwarding to the receiving blockchain, the receiving blockchain executing the corresponding sub-transaction, the sub-transaction execution result returning to the relay system, relay system verification (data structure conversion), relay system endorsement, forwarding to the initiating blockchain, and initiating blockchain verification. The latency of this entire process includes the time consumed by blockchain transaction execution, network transmission, signature verification, and data processing, thus resulting in low cross-chain efficiency. In one-to-many cross-chain transaction scenarios (i.e., the completion of a single cross-chain transaction involves multiple recipients), the above verification, endorsement, and forwarding processes will be repeated multiple times, and the transaction latency will increase linearly, further reducing efficiency. Furthermore, if the relay system fails, it will severely impact the normal operation of cross-chain services.

[0186] Reference Figure 6 This example divides the cross-chain transaction processing into three time-independent stages through the interaction between the cross-chain system and the cross-chain proxy component. This reduces the probability of cross-chain transaction failures due to asynchronous online status. Furthermore, the cross-chain system issues cross-chain transaction initiation success certificates and cross-chain transaction confirmation certificates in stages, providing strong support for application scenarios requiring unilateral transaction confirmation or rapid initiation of hot transactions. On the other hand, compared to related cross-chain transaction solutions, this example significantly reduces the involvement of the cross-chain system in the cross-chain transaction processing, effectively reducing the total transaction processing time. Additionally, in this example, the transmission of sub-transaction execution result data and the verification of sub-transaction execution result proofs are completed by different entities (transmitted by the receiving blockchain and verified by the cross-chain system, respectively), allowing for synchronous execution without requiring secondary verification and forwarding by the cross-chain system. This results in high cross-chain efficiency, especially in one-to-many cross-chain scenarios where processing efficiency will be significantly increased. Furthermore, in this example, the cross-chain system does not participate in data forwarding between blockchain systems. This avoids security risks such as privacy leaks introduced by the cross-chain system, and also prevents the normal operation of cross-chain business from being affected by cross-chain system forwarding failures. Conversely, when the business data is large, the transmission latency is high, or the communication between the initiating blockchain and the receiving blockchain fails, the cross-chain system can also issue a transaction confirmation certificate to the initiating blockchain first, shortening the transaction waiting time of the initiating blockchain.

[0187] This invention also provides a cross-blockchain data processing device, which is applied in a cross-chain system; Figure 7 This is a schematic diagram of the composition structure of a cross-blockchain data processing device according to an embodiment of the present invention. Figure 1 ,like Figure 7As shown, the cross-blockchain data processing device 700 includes a first communication module 701 and a first processing module 702;

[0188] The first communication module 701 is used to receive a first request sent by the first proxy component, the first request being used to request the initiation of a cross-chain service; the first request includes at least a first proof, the first proof being generated by the first proxy component based on a first execution result of the first service; wherein, the cross-chain service includes the first service and at least one second service, the first service being executed by a first blockchain associated with the first proxy component, and the at least one second service being executed by a second blockchain associated with at least one second proxy component.

[0189] The first communication module 701 is further configured to send a first credential to the first proxy component, the first credential being used by the first proxy component to send a second request to each second proxy component, the second request including at least the first credential; the second request being used to request the second blockchain associated with the second proxy component to execute a corresponding second business.

[0190] The first communication module 701 is further configured to receive a second proof sent by each second agent component, the second proof being generated by each second agent component based on the second execution result of the corresponding second service;

[0191] The first processing module 702 is used to verify the second proof sent by each second agent component, and generate a second credential if all second proofs are verified.

[0192] The first communication module 701 is further configured to send the second credential to the first proxy component and the at least one second proxy component respectively, wherein the second credential indicates that the cross-chain business has been completed.

[0193] In an optional embodiment of the present invention, the first proof includes at least the index information of the first service, the first hash value generated by the first proxy component based on the first execution result, and the signature information of the first blockchain; the first processing module 702 is used to verify the first proof and generate the first credential if the verification is successful, the first credential including at least the index information of the first service and the signature information of the cross-chain system.

[0194] In an optional embodiment of the present invention, the second proof includes at least the index information of the second service, the second hash value generated by the second proxy component based on the second execution result, and the signature information of the second blockchain.

[0195] In an optional embodiment of the present invention, the second credential includes at least the index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain, the identification information of each of the second blockchains, and the signature information of the cross-chain system.

[0196] In an optional embodiment of the present invention, the first communication module 701 is further configured to receive a third request sent by the proxy component, the third request being used to request blockchain registration and / or address information registration; and to send first information to the proxy component, the first information including the identification information of the blockchain associated with the proxy component and / or the address information of the blockchain associated with the proxy component, the address information including the cross-chain port address of the blockchain or the contract address between the blockchain and the cross-chain system; wherein, the proxy component is the first proxy component and / or the second proxy component.

[0197] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain; the first processing module is further configured to obtain address information of the at least one second blockchain based on the identification information of the at least one second blockchain, and send the address information of the at least one second blockchain to the first proxy component.

[0198] In this embodiment of the invention, the first processing module in the cross-blockchain data processing device 700 can be implemented in practical applications by a central processing unit (CPU), digital signal processor (DSP), microcontroller unit (MCU), or field-programmable gate array (FPGA) in the cross-blockchain system; the first communication module 701 in the cross-blockchain data processing device 700 can be implemented in practical applications by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and transceiver antenna.

[0199] This invention also provides a cross-blockchain data processing device, which is applied in a first proxy component; Figure 8 This is a schematic diagram of the composition structure of a cross-blockchain data processing device according to an embodiment of the present invention. Figure 2 ,like Figure 8 As shown, the cross-blockchain data processing device 800 includes a second processing module 801 and a second communication module 802; wherein,

[0200] The second processing module 801 is used to obtain the first execution result of the first business of the cross-chain business, and generate a first proof based on the first execution result;

[0201] The second communication module 802 is used to send a first request to the cross-chain system. The first request is used to request the initiation of a cross-chain service. The first request includes at least the first proof. The cross-chain service includes the first service and at least one second service. The first service is executed by the first blockchain associated with the first proxy component, and the at least one second service is executed by the second blockchain associated with each of the at least one second proxy component.

[0202] The second communication module 802 is further configured to receive the first credential sent by the cross-chain system, and send a second request to each second proxy component, wherein the second request includes at least the first credential; the second request is used to request the second blockchain associated with the second proxy component to execute the corresponding second business.

[0203] The second communication module 802 is further configured to receive a second credential sent by the cross-chain system, the second credential indicating that the cross-chain business has been completed; the second credential is generated by the cross-chain system verifying the second proof sent by each of the at least one second proxy component, and when all the second proofs are verified successfully, the second proof is generated by each second proxy component based on the second execution result of the corresponding second business.

[0204] In an optional embodiment of the present invention, the second processing module 801 is further configured to generate a first hash value based on the first execution result, the first hash value being used by the cross-chain system to verify the first execution result; and to generate the first proof based on the index information of the first business, the first hash value, and the signature information of the first blockchain; the first credential is generated by the cross-chain system verifying the first proof and if the verification is successful; the first credential includes at least the index information of the first business and the signature information of the cross-chain system.

[0205] In an optional embodiment of the present invention, the second credential includes at least index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain and the identification information of each of the second blockchains, and the signature information of the cross-chain system; the second proof includes at least index information of the second service, a second hash value generated by the second proxy component based on the second execution result, and the signature information of the second blockchain.

[0206] In an optional embodiment of the present invention, the second communication module 802 is further configured to send a third request to the cross-chain system, the third request being used to request blockchain registration and / or address information registration; and to receive first information sent by the cross-chain system, the first information including the identification information of the first blockchain and / or the address information of the first blockchain, the address information including the cross-chain interface address of the first blockchain or the contract address between the first blockchain and the cross-chain system.

[0207] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain; the second communication module 802 is further configured to receive address information of the at least one second blockchain sent by the cross-chain system; and to send the second request to a second proxy component associated with the second blockchain based on the address information of each second blockchain.

[0208] In an optional embodiment of the present invention, the second processing module 801 is further configured to establish an association between the first credential and the second credential, the association being stored by the first blockchain.

[0209] In an optional embodiment of the present invention, the second request further includes service data of the second service corresponding to each second proxy component; the second communication module 802 is also used to receive the second execution result of the second service sent by the second proxy component.

[0210] In some embodiments, the second communication module 802 is further configured to send a fourth request to the cross-chain system, the fourth request being used to request a query of cross-chain services and to receive the query results sent by the cross-chain system. Optionally, the fourth request may include index information of the first service executed by the first blockchain associated with the first proxy component.

[0211] In this embodiment of the invention, the second processing module 801 in the cross-blockchain data processing device 800 can be implemented by the CPU, DSP, MCU or FPGA in the first proxy component in practical applications; the second communication module 802 in the cross-blockchain data processing device 800 can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and transceiver antenna in practical applications.

[0212] This invention also provides a cross-blockchain data processing device, which is applied in a second proxy component; Figure 9 This is a schematic diagram of the composition structure of a cross-blockchain data processing device according to an embodiment of the present invention. Figure 3 ,like Figure 9As shown, the cross-blockchain data processing device 900 includes a third communication module 901 and a third processing module 902;

[0213] The third communication module 901 is used to receive a second request sent by the first proxy component. The second request is used to request the second blockchain associated with the second proxy component to execute a corresponding second business. The second request includes at least a first credential, which is generated by the cross-chain system based on the first request sent by the first proxy component. The first request is used to request the initiation of a cross-chain business. The first request includes at least a first proof, which is generated by the first proxy component based on the first execution result of the first business. The cross-chain business includes the first business and at least one second business. The first business is executed by the first blockchain associated with the first proxy component, and the at least one second business is executed by the second blockchain associated with each of the at least one second proxy component.

[0214] The third processing module 902 is used to obtain the second execution result of the second service and generate a second proof based on the second execution result;

[0215] The third communication module 901 is further configured to send the second proof to the cross-chain system; and to receive the second credential sent by the cross-chain system, the second credential indicating that the cross-chain business has been completed; the second credential is generated by the cross-chain system verifying the second proof sent by each of the at least one second proxy component, and when all the second proofs have been verified.

[0216] In an optional embodiment of the present invention, the first proof includes at least the index information of the first service, the first hash value generated by the first proxy component based on the first execution result, and the signature information of the first blockchain; the first credential is generated by the cross-chain system after verifying the first proof and if the verification is successful; the first credential includes at least the index information of the first service and the signature information of the cross-chain system.

[0217] In an optional embodiment of the present invention, the third processing module is configured to generate a second hash value based on the second execution result, the second hash value being used by the cross-chain system to verify the second execution result; and to generate a second proof based on the index information of the second business, the second hash value, and the signature information of the second blockchain; the second proof being used by the cross-chain system to verify the completion status of the cross-chain business.

[0218] In an optional embodiment of the present invention, the second credential includes at least the index information corresponding to each of the services included in the cross-chain service, the identification information of the first blockchain, the identification information of each of the second blockchains, and the signature information of the cross-chain system.

[0219] In an optional embodiment of the present invention, the third communication module 901 is further configured to send a third request to the cross-chain system, the third request being used to request blockchain registration and / or address information registration; and to receive first information sent by the cross-chain system, the first information including the identification information of the second blockchain and / or the address information of the second blockchain, the address information including the cross-chain interface address of the second blockchain or the contract address between the second blockchain and the cross-chain system.

[0220] In an optional embodiment of the present invention, the first request further includes identification information of at least one second blockchain, wherein the identification information of the at least one second blockchain is used by the cross-chain system to determine the address information of each second blockchain, and the address information of each second blockchain is used by the first proxy component to send the second request to the second proxy component associated with the second blockchain.

[0221] In an optional embodiment of the present invention, the third processing module 902 is further configured to establish an association between the first credential and the second credential, the association being stored by the second blockchain.

[0222] In an optional embodiment of the present invention, the second request further includes service data of the second service corresponding to the second proxy component; the third communication module 901 is further configured to send the second execution result to the first proxy component.

[0223] In this embodiment of the invention, the third processing module 902 in the cross-blockchain data processing device 900 can be implemented by the CPU, DSP, MCU or FPGA in the second proxy component in practical applications; the third communication module 901 in the cross-blockchain data processing device 900 can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and transceiver antenna in practical applications.

[0224] It should be noted that the cross-blockchain data processing device provided in the above embodiments is only illustrated by the division of the above program modules when performing cross-blockchain data processing. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the cross-blockchain data processing device and the cross-blockchain data processing method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0225] Figure 10 This is a schematic diagram of the structure of a communication device according to an embodiment of the present invention. The communication device 1000 may be a mobile phone, computer, digital broadcasting terminal, information transceiver, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc. Figure 10 The communication device 1000 shown includes at least one processor 1001, a memory 1002, and at least one network interface 1003. The various components in the communication device 1000 are coupled together via a bus system 1004. It is understood that the bus system 1004 is used to implement communication between these components. In addition to a data bus, the bus system 1004 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 10 The general labeled all buses as Bus System 1004.

[0226] It is understood that memory 1002 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 1002 described in this embodiment of the invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0227] The memory 1002 in this embodiment of the invention is used to store various types of data to support the operation of the communication device 1000. Examples of such data include any computer program for operation on the communication device 1000, such as a program that implements the method of this embodiment of the invention.

[0228] The methods disclosed in the above embodiments of the present invention can be applied to or implemented by processor 1001. Processor 1001 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 1001 or by instructions in the form of software. The processor 1001 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 1001 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present invention can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory 1002. Processor 1001 reads the information in memory 1002 and completes the steps of the aforementioned method in conjunction with its hardware.

[0229] In an exemplary embodiment, the communication device 1000 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0230] In an exemplary embodiment, the present invention also provides a computer-readable storage medium, such as a memory 1002 including a computer program, which can be executed by a processor 1001 of a communication device 1000 to complete the steps described in the foregoing method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; or it may be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0231] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0232] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0233] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0234] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0235] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0236] In addition, in the various embodiments of the present invention, each functional unit can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0237] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0238] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0239] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for cross-blockchain data processing, characterized in that, The method is applied to a cross-chain system; the method comprises: receiving a first request sent by a first proxy component, the first request being used to request initiation of a cross-chain service; the first request at least comprising a first proof, the first proof being generated by the first proxy component based on a first execution result of a first service; wherein the cross-chain service comprises the first service and at least one second service, the first service being executed by a first blockchain associated with the first proxy component, and the at least one second service being executed by a second blockchain associated with each of at least one second proxy component; sending a first credential to the first proxy component, the first credential being used for the first proxy component to send a second request to each of the second proxy components, the second request at least comprising the first credential; the second request being used to request the second blockchain associated with the second proxy component to execute a corresponding second service; receiving a second proof sent by each of the second proxy components, the second proof being generated by each of the second proxy components based on a second execution result of the corresponding second service; verifying the second proof sent by each of the second proxy components respectively, and generating a second credential in a case where all the second proofs are verified; and sending the second credential to the first proxy component and the at least one second proxy component respectively, the second credential representing completion of execution of the cross-chain service.

2. The method of claim 1, wherein, The first proof at least comprises index information of the first service, a first hash value generated by the first proxy component based on the first execution result, and signature information of the first blockchain; the method further comprises: verifying the first proof, and generating the first credential in a case where the verification is passed, the first credential at least comprising index information of the first service and signature information of the cross-chain system.

3. The method of claim 1, wherein, The second proof at least comprises index information of the second service, a second hash value generated by the second proxy component based on the second execution result, and signature information of the second blockchain.

4. The method of claim 3, wherein, The second credential at least comprises index information corresponding to all services included in the cross-chain service respectively, identification information of the first blockchain, identification information of each of the second blockchains, and signature information of the cross-chain system.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: receiving a third request sent by a proxy component, the third request being used to request blockchain registration and / or address information registration; sending first information to the proxy component, the first information comprising identification information of a blockchain associated with the proxy component and / or address information of the blockchain associated with the proxy component, the address information comprising a cross-chain interface address of the blockchain or a contract address of the blockchain and the cross-chain system; wherein the proxy component is the first proxy component and / or the second proxy component.

6. The method of claim 5, wherein, The first request further comprises identification information of each of the at least one second blockchain; the method further comprises: obtaining address information of each of the at least one second blockchain based on the identification information of each of the at least one second blockchain, and sending the address information of each of the at least one second blockchain to the first proxy component. 7.A method for processing data across blockchains, characterized in that, The method is applied to a first agent component; the method comprises: obtaining a first execution result of a first service, and generating a first proof based on the first execution result; sending a first request to a cross-chain system, the first request being used to request initiation of a cross-chain service; the first request at least comprising the first proof; wherein the cross-chain service comprises the first service and at least one second service, the first service being executed by a first blockchain associated with the first agent component, and the at least one second service being executed by a second blockchain associated with at least one second agent component; receiving a first credential sent by the cross-chain system, and sending a second request to each second agent component, the second request at least comprising the first credential; the second request being used to request the second agent component-associated second blockchain to execute a corresponding second service; receiving a second credential sent by the cross-chain system, the second credential representing completion of execution of the cross-chain service; the second credential being generated by the cross-chain system based on verification of second proofs sent by the at least one second agent component respectively, and in a case where all the second proofs are verified.

8. The method of claim 7, wherein, The method further comprises: generating a first hash value based on the first execution result, the first hash value being used for verification of the first execution result by the cross-chain system; generating the first proof according to index information of the first service, the first hash value, and signature information of the first blockchain; the first credential being generated by the cross-chain system based on verification of the first proof, and in a case where the verification is passed; the first credential at least comprising index information of the first service and signature information of the cross-chain system.

9. The method of claim 7, wherein, The second credential at least comprises index information corresponding to all services included in the cross-chain service respectively, identification information of the first blockchain, identification information of each of the second blockchains, and signature information of the cross-chain system; the second proof at least comprises index information of the second service, a second hash value generated by the second agent component based on the second execution result, and signature information of the second blockchain.

10. The method according to any one of claims 7 to 9, characterized in that, The method further comprises: sending a third request to the cross-chain system, the third request being used to request blockchain registration and / or address information registration; receiving first information sent by the cross-chain system, the first information comprising identification information of the first blockchain and / or address information of the first blockchain, the address information comprising a cross-chain interface address of the first blockchain or a contract address of the first blockchain and the cross-chain system.

11. The method of claim 10, wherein, The first request further comprises identification information of each of the at least one second blockchain; the method further comprises: receiving address information of each of the at least one second blockchain sent by the cross-chain system; The method further comprises: sending the second request to the second agent component associated with each second blockchain based on address information of each second blockchain.

12. The method of claim 9, wherein, The method further comprises: establishing an association relationship of the first credential and the second credential, the association relationship being stored by the first blockchain.

13. The method of claim 7, wherein, The second request further comprises service data of a second service corresponding to each second proxy component; the method further comprises: receiving a second execution result of the second service sent by a second proxy component. 14.A method for processing data across blockchains, the method comprising: The method is applied to a second proxy component; the method comprises: receiving a second request sent by a first proxy component, the second request being used to request a second blockchain associated with the second proxy component to execute a corresponding second service; the second request at least comprises a first credential, the first credential being generated by a cross-chain system based on a first request sent by the first proxy component, the first request being used to request to initiate a cross-chain service, the first request at least comprising a first proof, the first proof being generated by the first proxy component based on a first execution result of a first service; wherein the cross-chain service comprises the first service and at least one second service, the first service being executed by a first blockchain associated with the first proxy component, and the at least one second service being executed by a second blockchain associated with at least one second proxy component respectively; obtaining a second execution result of a second service, generating a second proof based on the second execution result, and sending the second proof to the cross-chain system; receiving a second credential sent by the cross-chain system, the second credential representing that the cross-chain service is executed completely; the second credential being generated by the cross-chain system based on verification of second proofs sent by the at least one second proxy component respectively, and in a case that all the second proofs are verified successfully.

15. The method of claim 14, wherein, The first proof at least comprises index information of the first service, a first hash value generated by the first proxy component based on the first execution result, and signature information of the first blockchain; the first credential is generated by the cross-chain system based on verification of the first proof, and in a case that the verification is passed; the first credential at least comprises the index information of the first service and signature information of the cross-chain system.

16. The method of claim 14, wherein, The generating of the second proof based on the second execution result comprises: generating a second hash value based on the second execution result, the second hash value being used for verification of the second execution result by the cross-chain system; generating a second proof according to the index information of the second service, the second hash value, and signature information of the second blockchain; the second proof being used for verification of completion of the cross-chain service by the cross-chain system.

17. The method of claim 16, wherein, The second credential at least comprises index information corresponding to all services included in the cross-chain service respectively, identification information of the first blockchain, identification information of each second blockchain in all second blockchains, and signature information of the cross-chain system.

18. The method according to any one of claims 14 to 17, characterized in that, The method further comprises: sending a third request to the cross-chain system, the third request being used to request to perform blockchain registration and / or address information registration; receive first information sent by the cross-chain system, the first information including identification information of the second blockchain and / or address information of the second blockchain, the address information including a cross-chain interface address of the second blockchain or a contract address of the second blockchain and the cross-chain system.

19. The method of claim 18, wherein, The first request further includes identification information of at least one second blockchain, which is used by the cross-chain system to determine address information of each second blockchain, and the address information of each second blockchain is used by the first proxy component to send the second request to a second proxy component associated with the second blockchain.

20. The method of claim 17, wherein, The method further includes: establishing an association between the first credential and the second credential, and storing the association by the second blockchain.

21. The method of claim 16, wherein, The second request further includes service data of a second service corresponding to the second proxy component; and the method further includes: sending the second execution result to the first proxy component. 22.A data processing apparatus across blockchains, characterized in that, The device is applied to a cross-chain system; and the device includes a first communication module and a first processing module. The first communication module is configured to receive a first request sent by a first proxy component, the first request being used to request initiation of a cross-chain service; the first request includes at least a first proof, which is generated by the first proxy component based on a first execution result of a first service; the cross-chain service includes the first service and at least one second service, the first service being executed by a first blockchain associated with the first proxy component, and the at least one second service being executed by a second blockchain associated with at least one second proxy component; The first communication module is further configured to send a first credential to the first proxy component, the first credential being used by the first proxy component to send a second request to each second proxy component, the second request including at least the first credential; the second request is used to request the second blockchain associated with the second proxy component to execute a corresponding second service; The first communication module is further configured to receive a second proof sent by each second proxy component, the second proof being generated by each second proxy component based on a second execution result of a corresponding second service; The first processing module is configured to verify the second proof sent by each second proxy component respectively, and generate a second credential in a case where all the second proofs are verified successfully; The first communication module is further configured to send the second credential to the first proxy component and the at least one second proxy component respectively, the second credential representing that the cross-chain service is executed completely. 23.A data processing apparatus across blockchains, characterized in that, The device is applied to a first proxy component; and the device includes a second processing module and a second communication module; wherein The second processing module is configured to obtain a first execution result of a first service of a cross-chain service, and generate a first proof based on the first execution result. The second communication module is configured to send a first request to a cross-chain system, the first request being used to request initiation of a cross-chain service; the first request at least includes the first proof; wherein the cross-chain service includes the first service and at least one second service, the first service being executed by a first blockchain associated with the first agent component, and the at least one second service being executed by a second blockchain associated with each of at least one second agent component; The second communication module is further configured to receive a first voucher sent by the cross-chain system, and send a second request to each second agent component, the second request at least including the first voucher; the second request being used to request the second blockchain associated with the second agent component to execute a corresponding second service; The second communication module is further configured to receive a second voucher sent by the cross-chain system, the second voucher indicating that the cross-chain service is executed completely; the second voucher being generated by the cross-chain system based on verification of second proofs sent by the at least one second agent component respectively, and in a case where all the second proofs are verified successfully. 24.A data processing apparatus across blockchains, characterized in that, The device is applied to a second agent component; and the device includes a third communication module and a third processing module; The third communication module is configured to receive a second request sent by a first agent component, the second request being used to request a second blockchain associated with the second agent component to execute a corresponding second service; the second request at least includes a first voucher, the first voucher being generated by a cross-chain system based on a first request sent by the first agent component, the first request being used to request initiation of a cross-chain service, the first request at least including a first proof, the first proof being generated by the first agent component based on a first execution result of a first service; wherein the cross-chain service includes the first service and at least one second service, the first service being executed by a first blockchain associated with the first agent component, and the at least one second service being executed by a second blockchain associated with each of at least one second agent component; The third processing module is configured to obtain a second execution result of the second service, and generate a second proof based on the second execution result; The third communication module is further configured to send the second proof to the cross-chain system, and receive a second voucher sent by the cross-chain system, the second voucher indicating that the cross-chain service is executed completely; the second voucher being generated by the cross-chain system based on verification of second proofs sent by the at least one second agent component respectively, and in a case where all the second proofs are verified successfully.

25. A cross-blockchain data processing system, characterized in that, The system includes a cross-chain system, a first agent component, and at least one second agent component; wherein The cross-chain system is configured to implement steps of the method according to any one of claims 1 to 6; The first agent component is configured to implement steps of the method according to any one of claims 7 to 13; The second agent component is configured to implement steps of the method according to any one of claims 14 to 21.

26. A computer readable storage medium having stored thereon a computer program, characterized in that, the program, when executed by a processor, implements the steps of the method of any one of claims 1 to 6; or the program, when executed by a processor, implements the steps of the method of any one of claims 7 to 13; or the program, when executed by a processor, implements the steps of the method of any one of claims 14 to 21.

27. A communication device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein, the program, when executed by a processor, implements the steps of the method of any one of claims 1 to 6; or the program, when executed by a processor, implements the steps of the method of any one of claims 7 to 13; or the program, when executed by a processor, implements the steps of the method of any one of claims 14 to 21.

Images