Data processing method and apparatus based on multiple blockchains, device, and medium

WO2024230062A1PCT designated stage expired Publication Date: 2024-11-14TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/123772
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-06
Filing Date
2023-10-10
Publication Date
2024-11-14

Smart Images

  • Figure CN2023123772_14112024_PF_FP_ABST
    Figure CN2023123772_14112024_PF_FP_ABST
Patent Text Reader

Abstract

A data processing method based on multiple blockchains. The multiple blockchains comprise a first blockchain and a second blockchain, the first blockchain corresponds to a first blockchain network, the second blockchain corresponds to a second blockchain network, and the first blockchain network is independent of the second blockchain network. The method is executed by a computer device that maintains a first blockchain node in the first blockchain network, and comprises: acquiring a full-chain asset transfer request transmitted by a first service object for a service transaction, and when the service transaction is determined as a cross-chain asset transfer transaction on the basis of the full-chain asset transfer request, invoking a target full-chain service contract on the first blockchain, and using a full-chain asset associated with the cross-chain asset transfer transaction as a full-chain asset to be transferred, the cross-chain asset transfer transaction being used for instructing to transfer, from the first blockchain to the second blockchain, the full-chain asset to be transferred (S101); invoking a full-chain contract protocol in the target full-chain service contract, and determining a target remote contract address bound with the target full-chain service contract, the full-chain contract protocol being determined on the basis of a full-chain contract protocol interface provided by a full-chain service parent contract on the first blockchain, and a target remote full-chain service contract corresponding to the target remote contract address being a full-chain service contract integrating the full-chain contract protocol on the second blockchain (S102); and when a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated on the basis of the target remote contract address and the full-chain asset to be transferred, transmitting a cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to a second blockchain node in the second blockchain network by means of an off-chain cross-chain service device, so that the second blockchain node determines, on the second blockchain on the basis of the cross-chain asset reconstruction transaction, the target remote full-chain service contract corresponding to the target remote contract address, and invokes the target remote full-chain service contract to generate, on the second blockchain, a full-chain mapping asset corresponding to the full-chain asset to be transferred, wherein the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain asset to be transferred (S103).
Need to check novelty before this filing date? Find Prior Art

Description

Data processing method, device, equipment and medium based on multiple blockchains

[0001] Related applications

[0002] This application claims priority to Chinese patent application No. 2023105051827, filed on May 6, 2023, entitled “Data processing method, device, equipment and medium based on multiple blockchains,” the entire text of which is hereby incorporated by reference. Technical Field

[0003] The present application relates to the field of blockchain technology, and in particular to a data processing method, apparatus, device, and medium based on multiple blockchains. Background Art

[0004] Currently, in some cross-chain digital asset transfer scenarios, a digital asset (for example, digital asset P) can be transferred from blockchain A to blockchain B. However, in the process of transferring this digital asset P from blockchain A to blockchain B, it is necessary to re-determine a mapping asset (for example, digital asset P') on blockchain B that has the same asset content as digital asset P based on the asset determination rules on blockchain B.

[0005] However, in practice, it has been found that since blockchain A is independent of blockchain B, and the asset determination rules on blockchain A are fundamentally different from those on blockchain B, there is a phenomenon that the mapped asset (for example, digital asset P') ultimately determined on blockchain B is different from the digital asset P transferred from blockchain A, posing a security risk.

[0006] Summary of the Invention

[0007] According to an embodiment of the present application, a multi-blockchain-based data processing method, apparatus, device, and medium are provided.

[0008] In one aspect, the present application provides a data processing method based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the first blockchain corresponds to a first blockchain network, and the second blockchain corresponds to a second blockchain network, wherein the first blockchain network is independent of the second blockchain network, and the method is performed by a computer device that maintains a first blockchain node in the first blockchain network, and includes:

[0009] Obtaining a full-chain asset transfer request sent by the first business object for a business transaction, and when determining based on the full-chain asset transfer request that the business transaction is a cross-chain asset transfer transaction, invoking a target full-chain business contract on the first blockchain, using the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred, wherein the cross-chain asset transfer transaction is used to instruct the transfer of the full-chain asset to be transferred from the first blockchain to the second blockchain;

[0010] Calling the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract, wherein the full-chain contract protocol is determined based on the full-chain contract protocol interface provided by the full-chain business parent contract on the first blockchain, and the target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and

[0011] When a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred, the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is sent to the second blockchain node in the second blockchain network through the off-chain cross-chain service device, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, and the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred.

[0012] On the other hand, the present application provides a data processing method based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the first blockchain corresponds to a first blockchain network, and the second blockchain corresponds to a second blockchain network, which is independent of the first blockchain network. The method is performed by a computer device that maintains a second blockchain node in the second blockchain network, and includes:

[0013] Obtaining a cross-chain asset reconstruction transaction, the cross-chain asset reconstruction transaction corresponding to a cross-chain asset transfer event, the cross-chain asset transfer event being sent by the first blockchain node in the first blockchain network via an off-chain cross-chain service device. The cross-chain asset transfer event is an event corresponding to a cross-chain asset transfer transaction generated by the first blockchain node based on a target remote contract address bound to a target full-chain business contract and the full-chain asset to be transferred. The target remote contract address is obtained by the first blockchain node via the full-chain contract protocol in the target full-chain business contract. The full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node obtains a full-chain asset transfer request sent by the first business object for a business transaction and determines, based on the full-chain asset transfer request, that the business transaction is a cross-chain asset transfer transaction. The target full-chain business contract is a full-chain business contract on the first blockchain that integrates the full-chain contract protocol, and the remote full-chain business contract corresponding to the target remote contract address is a full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and

[0014] Based on the cross-chain asset reconstruction transaction, the target remote full-chain business contract corresponding to the target remote contract address is determined on the second blockchain, and the target remote full-chain business contract is called to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain. The asset data information of the full-chain mapping asset is consistent with the asset data information of the target full-chain asset.

[0015] In another aspect, the present application provides a data processing device based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, the blockchain network corresponding to the first blockchain is a first blockchain network, the blockchain network corresponding to the second blockchain is a second blockchain network, the first blockchain network is independent of the second blockchain network, and the device runs on a first blockchain node in the first blockchain network, the device comprising:

[0016] A full-chain asset acquisition module is configured to acquire a full-chain asset transfer request sent by a first business object for a business transaction. When determining, based on the full-chain asset transfer request, that the business transaction is a cross-chain asset transfer transaction, the module invokes a target full-chain business contract on the first blockchain and uses the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred. The cross-chain asset transfer transaction is used to instruct the transfer of the full-chain asset to be transferred from the first blockchain to the second blockchain.

[0017] A contract address determination module is configured to call the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract, wherein the full-chain contract protocol is determined based on the full-chain contract protocol interface provided by the full-chain business parent contract on the first blockchain, and the target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and

[0018] The transfer event generation module is configured to, when a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred, send the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to the second blockchain node in the second blockchain network through an off-chain cross-chain service device, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, where the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred.

[0019] In another aspect, the present application provides a data processing device based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the blockchain network corresponding to the first blockchain is a first blockchain network, and the blockchain network corresponding to the second blockchain is a second blockchain network, and the second blockchain network is independent of the first blockchain network. The device runs on a second blockchain node in the second blockchain network, including:

[0020] a reconstruction transaction acquisition module, configured to acquire a cross-chain asset reconstruction transaction, wherein the cross-chain asset reconstruction transaction corresponds to a cross-chain asset transfer event, which is sent by a first blockchain node in the first blockchain network via an off-chain cross-chain service device. The cross-chain asset transfer event corresponds to a cross-chain asset transfer transaction generated by the first blockchain node based on a target remote contract address bound to a target full-chain business contract and the full-chain asset to be transferred. The target remote contract address is acquired by the first blockchain node via the full-chain contract protocol in the target full-chain business contract. The full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node acquires a full-chain asset transfer request sent by the first business object for a business transaction and determines that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request. The target full-chain business contract is a full-chain business contract on the first blockchain that integrates the full-chain contract protocol, and the remote full-chain business contract corresponding to the target remote contract address is a full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and

[0021] A mapping asset generation module is configured to reconstruct a transaction based on the cross-chain assets, determine a target remote full-chain business contract corresponding to the target remote contract address on the second blockchain, call the target remote full-chain business contract, and generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, wherein the asset data information of the full-chain mapping asset is consistent with the asset data information of the target full-chain asset.

[0022] On the other hand, the present application provides a computer device, including a memory and a processor, wherein the memory stores computer-readable instructions, and the processor is configured to execute the computer-readable instructions to perform the method of any embodiment of the present application.

[0023] On the other hand, the present application provides a computer-readable storage medium, which stores computer-readable instructions. When the computer-readable instructions are executed by a processor, the method of any embodiment of the present application is implemented.

[0024] On the other hand, the present application provides a computer program product, which includes computer-readable instructions. When the computer-readable instructions are executed by a processor, the method of any embodiment of the present application is implemented.

[0025] The details of one or more embodiments of the present application are set forth in the accompanying drawings and the description below. Other features and advantages of the present application will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or traditional technical descriptions. Obviously, the drawings described below are merely embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the disclosed drawings without any creative work.

[0027] FIG1 is a schematic diagram of a hierarchical structure of a blockchain network provided in an embodiment of the present application;

[0028] FIG2 is a schematic diagram of a multi-blockchain data processing scenario provided by an embodiment of the present application;

[0029] FIG3 is a schematic diagram of a scenario of multi-blockchain-based data processing provided by an embodiment of the present application;

[0030] FIG4 is a flowchart of a multi-blockchain-based data processing method according to an embodiment of the present application;

[0031] FIG5 is a schematic diagram of a cross-chain asset transfer scenario provided by an embodiment of the present application;

[0032] FIG6 is a second flow chart of a multi-blockchain-based data processing method provided in an embodiment of the present application;

[0033] FIG7 is a schematic diagram of a scenario of contract update provided in an embodiment of the present application;

[0034] FIG8 is a third flow chart of a multi-blockchain-based data processing method provided in an embodiment of the present application;

[0035] FIG9 is a schematic diagram of an interaction method for multi-blockchain data processing provided by an embodiment of the present application;

[0036] FIG10 is a schematic diagram of an interaction for contract updating provided in an embodiment of the present application;

[0037] FIG11 is a first structural diagram of a multi-blockchain-based data processing device provided in an embodiment of the present application;

[0038] FIG12 is a second structural diagram of a multi-blockchain-based data processing device provided in an embodiment of the present application;

[0039] FIG13 is a schematic structural diagram of a computer device provided in an embodiment of the present application;

[0040] Figure 14 is a schematic diagram of a multi-blockchain-based data processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0042] Please refer to Figure 1, which is a schematic diagram of the hierarchical structure of a blockchain network provided by an embodiment of the present application. The hierarchical structure shown in Figure 1 is applied to a blockchain data system, such as a blockchain digital asset system. The blockchain digital asset system can be a system composed of multiple blockchain networks. The digital assets can be digital collections, electronic bills, etc. Digital assets can be transferred and circulated in multiple blockchain networks, that is, the full-chain circulation of digital assets can be achieved in multiple blockchain networks. At this time, digital assets can be called full-chain assets. In the blockchain network corresponding to the blockchain digital asset system, a business network and multiple blockchain networks (i.e., consensus networks) are included. The business network is in the public network, and the blockchain network is in the private network (such as deployed in a private cloud). As shown in Figure 1, the business network can be represented as the business network 100 shown in Figure 1, and the multiple blockchain networks can be specifically represented as the first blockchain network 200 and the second blockchain network 300 shown in Figure 1.

[0043] In the business network 100 shown in FIG1 , multiple business nodes are deployed. Specifically, the multiple business nodes may include the business node 10a, the business node 10b, ..., the business node 10n shown in FIG1 . It is understood that there is no limit on the number of business nodes deployed in the business network 100. As business needs change, the number of business nodes can continue to change. It should be understood that the business nodes in the business network 100 do not need to be accounted for. In addition, as shown in FIG1 , for each business node running in the business network 100, one or more of the above-mentioned multiple consensus networks can be accessed through network communication. There is no limit on the number of consensus networks that each business object can access through the corresponding business node. It is understandable that data exchange can also be carried out between the various consensus networks through network communication.

[0044] It should be understood that in the first blockchain network 200 shown in Figure 1, multiple blockchain nodes are deployed. The multiple blockchain nodes here can specifically include blockchain node 20a, blockchain node 20b, blockchain node 20c, and blockchain node 20d shown in Figure 1. It should be noted that there is no limit on the number of blockchain nodes deployed in the first blockchain network 200. As business needs change, the number of blockchain nodes here can continue to change, and the number can be 3 or more. In addition, as shown in Figure 1, for the multiple consensus nodes running in the first blockchain network 200, the blockchain they jointly maintain is specifically blockchain 20e shown in Figure 1.

[0045] Accordingly, in the second blockchain network 300 shown in FIG1 , multiple blockchain nodes are deployed. Specifically, the multiple blockchain nodes may include blockchain node 30a, blockchain node 30b, blockchain node 30c, and blockchain node 30d shown in FIG1 . It should be noted that there is no limit on the number of blockchain nodes deployed in the second blockchain network 300. As business needs change, the number of blockchain nodes can vary, and the number can be three or more. Furthermore, as shown in FIG1 , for the multiple consensus nodes operating in the second blockchain network 300, the blockchain they jointly maintain is specifically blockchain 30e shown in FIG1 .

[0046] For ease of understanding, in this embodiment of the present application, the first blockchain network 200 in the above-mentioned blockchain digital asset system may be referred to as the first blockchain network, the blockchain 20e maintained by the first blockchain network 200 may be referred to as the first blockchain, and the blockchain nodes in the first blockchain network 200 may be referred to as first blockchain nodes; and the second blockchain network 300 in the above-mentioned blockchain digital asset system may be referred to as the second blockchain network, the blockchain 30e maintained by the second blockchain network 300 may be referred to as the second blockchain, and the blockchain nodes in the second blockchain network 300 may be referred to as second blockchain nodes. The first blockchain network and the second blockchain network are independent of each other, and the first blockchain and the second blockchain are independent blockchains. It is understood that the first blockchain and the second blockchain can be blockchains constructed in any business scenario. The blockchain digital asset system may include multiple blockchain networks, each of which is used to maintain its own blockchain (i.e., business chain). The number of blockchain networks in the multiple blockchain networks (the number of business chains in the multiple blockchains) is not limited here, and the number of blockchain networks here can change continuously as business needs change. Here, the digital asset transfer process in multiple blockchains is described using the example of multiple blockchains including the first blockchain and the second blockchain.

[0047] Furthermore, the blockchains in a multi-blockchain can be of any type, such as layer 1 or layer 2, without limitation. Layer 1 refers to the underlying blockchain, which serves as the foundation upon which various layer 2 networks are built. Layer 1 functions include: a network of node managers (for securing and validating the network), a network of block producers, the blockchain itself, historical transaction data, and the network's consensus mechanism. Layer 2 refers to the blockchains within a second-layer blockchain network, built on top of the layer 1 public blockchain to optimize transaction processing and computation.

[0048] It should be understood that the blockchain involved in the embodiments of this application is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. It is primarily used to organize data in chronological order and encrypt it into a ledger to make it tamper-proof and forge-proof, while also enabling data verification, storage, and updates. Blockchain is essentially a decentralized database in which each node stores an identical blockchain.

[0049] In the above-mentioned blockchain digital asset system, a blockchain node can be responsible for consensus in the blockchain network where the corresponding blockchain is located, that is, the blockchain node can be a consensus node in the blockchain network where the corresponding blockchain is located. For any of the two blockchain networks mentioned above, the specific process of writing transaction data in the blockchain network into the corresponding blockchain ledger (e.g., a distributed database) can be that the business client sends the transaction data to a business node, and then the transaction data is transmitted between the business nodes in the business network within the above-mentioned blockchain network until the blockchain node in the above-mentioned blockchain network (e.g., blockchain node 20b in the first blockchain network 200) receives the transaction data. At this time, the blockchain node (e.g., blockchain node 20b in the first blockchain network 200) then packages the transaction data into a block so that it can subsequently reach consensus with other blockchain nodes. After the consensus is passed, the consensus-passed block can be written into the distributed database of its own blockchain network (e.g., the first blockchain network 200). Optionally, the aforementioned business client can be a payment client, entertainment client (e.g., game client), multimedia client (e.g., video client), smart home client, browser, or other application with the function of displaying data information such as text, images, audio, and video.

[0050] Optionally, it is understandable that, after consensus is passed, the embodiment of the present application can also write the block carrying the transaction data and multiple other blocks associated with the block into a distributed database in parallel through the storage layer of its own blockchain network (for example, the first blockchain network 200). This can fundamentally break through the limitations of the blockchain structure of the blockchain, thereby effectively improving the storage efficiency of data storage.

[0051] It is understood that, in the aforementioned blockchain digital asset system, a smart contract can be deployed on the blockchain of a blockchain network. In the blockchain digital asset system, the smart contract can be understood as a code executed by each blockchain node, and arbitrary logic can be executed and results can be obtained through the smart contract. For example, a business object (such as a user) can initiate a transaction service request (such as a full-chain asset transfer request for a cross-chain asset transfer transaction) through a business client to call a smart contract (such as a target full-chain business contract for a cross-chain asset transfer transaction) that has been deployed on the blockchain (such as the aforementioned blockchain 20e) of the corresponding blockchain network (such as the aforementioned first blockchain network 200).

[0052] Specifically, the business node in the business network can send the transaction business request to the blockchain node in the blockchain network (for example, the blockchain node 20a shown in Figure 1) to authenticate the identity of the business object that sends the transaction business request through the blockchain entrance of the blockchain network, and when the identity authentication is successful, the transaction business request sent by the business object is allowed to be sent to other blockchain nodes in the blockchain network (for example, the consensus node 20b shown in Figure 1) to call the smart contracts running in these blockchain nodes (for example, the blockchain node 20a and the blockchain node 20b shown in Figure 1) to execute the transaction business requested by the business object.

[0053] It should be understood that one or more smart contracts can be deployed on the blockchain (e.g., the blockchain 20e) of the above-mentioned blockchain network (e.g., the above-mentioned first blockchain network 200). These smart contracts can be distinguished by the contract call address (also called contract address), contract identification number (Identity document, ID) or contract name, and the transaction service request initiated by the business client can also carry the contract call address or contract identification number or contract name of the smart contract to specify the smart contract to be run.

[0054] It should be understood that in the aforementioned blockchain digital asset system, any two blockchain nodes in any blockchain network (e.g., first blockchain network 200 or second blockchain network 300) can form a peer-to-peer (P2P) network. This peer-to-peer network can utilize the P2P protocol, which is an application layer protocol running on top of the Transmission Control Protocol (TCP). In a distributed system, any device, such as a server or terminal, can join and become a blockchain node. Each blockchain node can include a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0055] It is understood that, in embodiments of the present application, any object (e.g., any individual user, any enterprise, any organization, or other entity object) connected to a blockchain network can configure a blockchain node. Therefore, in the business network 100 shown in FIG1 , business nodes 10a, 10b, 10c, 10d, ..., 10n can each have a one-to-one correspondence with the corresponding object that needs to be connected to the blockchain network.

[0056] Among them, it can be understood that, since each entity object can correspond to a blockchain node, the embodiment of the present application can take the entity object as the above-mentioned enterprise (i.e., the aforementioned enterprise) as an example. At this time, the blockchain node associated with each enterprise can be the same blockchain node (for example, the business node 10c shown in Figure 1 can interact with the business terminals corresponding to multiple enterprises to realize the transfer of digital assets). For example, in the above-mentioned blockchain digital asset system, the business requested by the first business object (for example, the transfer of digital assets and other businesses) can be collectively referred to as a transaction business. Among them, when the above-mentioned enterprise requests a cross-chain transfer of digital assets through the first blockchain network (for example, the above-mentioned first blockchain network 200), the business node 10c shown in Figure 1 can interact with the blockchain node (for example, blockchain node 20b) in the above-mentioned first blockchain network 200 to request the completion of the corresponding transaction, so as to realize the transfer of the digital assets to be transferred to the second blockchain network (for example, the above-mentioned second blockchain network 300).

[0057] It is understood that when the business node associated with the first business object receives a transaction request, it may forward the transaction request initiated by the first business object to the blockchain node associated with the first blockchain network, so that the blockchain node associated with the first blockchain network can verify the legitimacy of the transaction request initiated by the first business object. In this way, the blockchain node associated with the first blockchain network can process the transaction if the legitimacy verification passes.

[0058] For ease of understanding, further, please refer to Figure 2, which is a schematic diagram of a scenario of multi-blockchain data processing provided by an embodiment of the present application. It should be understood that in the above-mentioned blockchain digital asset system, it includes a first blockchain, a second blockchain, and an off-chain cross-chain service device. Among them, a full-chain business parent contract 21 (also known as a full-chain business agreement base contract) is deployed on the first blockchain. The full-chain business parent contract provides a full-chain contract agreement interface. The full-chain contract agreement 22 provided by the full-chain business parent contract can be obtained through the full-chain contract agreement interface. The full-chain contract agreement can provide a unified asset transfer rule; through the full-chain business parent contract, a target full-chain business contract 1 (23) for cross-chain asset transfer can be deployed on the first blockchain. The target full-chain business contract 1 is integrated with the aforementioned full-chain contract agreement 23. In addition, the full-chain business parent contract on the first blockchain can also provide a remote address setting interface 24 and a key information disclosure interface 25. The remote address setting interface is used to set The remote contract address corresponding to the target full-chain business contract 1 is set. It can be understood that the remote contract address bound to the target full-chain business contract 1 can be used to indicate the full-chain business contract corresponding to the target full-chain business contract 1 on the second blockchain (for the target full-chain business contract 1 on the first blockchain, on the second blockchain, the full-chain business contract corresponding to the target full-chain business contract 1 is the target remote full-chain business contract 1 corresponding to the target full-chain business contract 1, that is, the target full-chain business contract 2 is the target remote full-chain business contract 1 corresponding to the target full-chain business contract 1); the key information disclosure interface is used to disclose the node port information associated with the target full-chain business contract 1 on the first blockchain for security verification. In addition, a full-chain service contract 26 can also be deployed on the first blockchain. The full-chain service contract can include a full-chain event identifier generation protocol 27 and a full-chain identifier allocation protocol 28. The full-chain event identifier generation protocol can be used to generate a full-chain unique event identifier when generating a cross-chain asset transfer event. The full-chain identifier allocation protocol can be used to perform initialization operations such as allocation of a full-chain unique blockchain identifier on the blockchain. In addition, a full-chain token airdrop contract 29 can also be deployed on the first blockchain to simultaneously transfer cross-chain tokens when transferring digital assets.

[0059] Correspondingly, the same full-chain business parent contract 210 (also known as the full-chain business agreement base contract) is deployed on the second blockchain. The full-chain business parent contract provides a full-chain contract agreement interface, and the full-chain contract agreement 211 provided by the full-chain business parent contract can be obtained through the full-chain contract agreement interface. The full-chain contract agreement 211 can provide a unified asset transfer rule; through the full-chain business parent contract, the target full-chain business contract 2 (212) for cross-chain asset transfer can be deployed on the second blockchain. The target full-chain business contract 2 is integrated with the aforementioned full-chain contract agreement. In addition, the full-chain business parent contract on the second blockchain can also provide a remote address setting interface 213 and a key information disclosure interface 214. The remote address setting interface 213 and the key information disclosure interface 214 are provided. The interface is used to set the remote contract address corresponding to the target full-chain business contract 2. It can be understood that the remote contract address bound to the target full-chain business contract 2 can be used to indicate the full-chain business contract corresponding to the target full-chain business contract 2 on the first blockchain (for the target full-chain business contract 2 on the second blockchain, the full-chain business contract corresponding to the target full-chain business contract 2 on the first blockchain is the target remote full-chain business contract 2 corresponding to the target full-chain business contract 2, that is, the target full-chain business contract 1 is the target remote full-chain business contract 2 corresponding to the target full-chain business contract 2); the key information disclosure interface is used to disclose the node port information associated with the target full-chain business contract 2 on the second blockchain for security verification. In addition, a full-chain service contract 215 can also be deployed on the second blockchain. The full-chain service contract can include a full-chain event identifier generation protocol 216 and a full-chain identifier allocation protocol 217. The full-chain event identifier generation protocol can be used to generate a full-chain unique event identifier when generating a cross-chain asset transfer event. The full-chain identifier allocation protocol can be used to perform initialization operations such as allocating a full-chain unique blockchain identifier to the blockchain. In addition, a full-chain token airdrop contract 218 may be deployed on the second blockchain to simultaneously transfer cross-chain tokens when transferring digital assets.

[0060] The services deployed on the chain are as follows: The aforementioned full-chain business parent contract can provide a standard, unified full-chain contract protocol interface, a method for obtaining a business chain's unique full-chain blockchain identifier across multiple blockchains, and a method for obtaining a unique full-chain event identifier for events corresponding to business transactions across multiple blockchains, thereby ensuring the security of cross-chain transfers of full-chain assets. The target full-chain business contract, which integrates the full-chain contract protocol provided by the full-chain business parent contract, can be pre-deployed on each business chain to execute cross-chain asset transfer transactions. The target full-chain business contract can use off-chain full-chain cross-chain services to perform logic such as initializing the business chain's blockchain identifier, generating asset identifiers, and event identifiers. The full-chain token airdrop contract can provide an airdrop service for basic tokens. When a full-chain asset is to be transferred across chains, it is necessary to obtain some basic tokens from the corresponding contract address on the target chain after the transfer (to facilitate the submission of business transactions to operate the full-chain asset on the target chain). The target full-chain business contract can then call the full-chain token airdrop contract when executing the cross-chain asset transfer transaction. The full-chain token airdrop contract pays a certain airdrop fee to complete the token airdrop after the cross-chain transfer. The full-chain business parent contract is the parent contract of all target full-chain business contracts. That is, the target full-chain business contract on each business chain must integrate the full-chain asset protocol indicated by the full-chain asset protocol interface provided by the full-chain business parent contract, so that the standard logic of cross-chain transfer of full-chain assets can be implemented through the target full-chain business contract. In addition, the full-chain business parent contract provides a remote address setting interface, which can be used to bind the remote contract address of the target full-chain business contract on each business chain. The full-chain business parent contract also provides a remote address and a key information disclosure interface, which can be used to disclose the node port information involved in the cross-chain transfer of full-chain assets by the target full-chain business contract to facilitate external audit and verification. Among them, the certificate airdrop can refer to the free distribution (i.e., gift) of a certain amount of digital assets to specific objects.

[0061] It can be understood that a multi-blockchain network can include multiple blockchains, and the above information can be deployed on each blockchain. The target full-chain business contract on each blockchain can be bound to the contract address corresponding to the target full-chain business contract on the remaining blockchains. At this time, the digital assets on one blockchain can be circulated on each blockchain in the multi-blockchain network. For example, a multi-blockchain network includes a first blockchain, a second blockchain, and a third blockchain. The target full-chain business contract 1 is deployed on the first blockchain, the target full-chain business contract 2 is deployed on the second blockchain, and the target full-chain business contract 3 is deployed on the third blockchain. The contract address corresponding to the target full-chain business contract 2 and the contract address corresponding to the target full-chain business contract 3 can be bound to the target full-chain business contract 1 deployed on the first blockchain. At this time, the remote contract address bound to the target full-chain business contract 1 includes the contract address corresponding to the target full-chain business contract 2 and the contract address corresponding to the target full-chain business contract 3. The target full-chain business contract 2 and the target full-chain business contract 3 serve as the remote full-chain business contracts of the target full-chain business contract 1. It can be understood that when digital assets need to be transferred from the first blockchain to the second blockchain, the target full-chain business contract 2 serves as the target remote full-chain business contract corresponding to the target full-chain business contract 1, and the contract address corresponding to the target full-chain business contract 2 is the target remote contract address corresponding to the target full-chain business contract 1. Accordingly, the contract address corresponding to the target full-chain business contract 1 and the contract address corresponding to the target full-chain business contract 3 can be bound to the target full-chain business contract 2 deployed on the second blockchain. At this time, the remote contract address bound to the target full-chain business contract 2 includes the contract address corresponding to the target full-chain business contract 1 and the contract address corresponding to the target full-chain business contract 3. The target full-chain business contract 1 and the target full-chain business contract 3 serve as the remote full-chain business contracts of the target full-chain business contract 2. Similarly, the contract address corresponding to the target full-chain business contract 1 and the contract address corresponding to the target full-chain business contract 2 can be bound to the target full-chain business contract 3 deployed on the third blockchain. At this time, the remote contract address bound to the target full-chain business contract 3 includes the contract address corresponding to the target full-chain business contract 1 and the contract address corresponding to the target full-chain business contract 2. The target full-chain business contract 1 and the target full-chain business contract 2 serve as the remote full-chain business contracts of the target full-chain business contract 3.

[0062] It can be understood that, as shown in Figure 2, any two blockchains in the multi-blockchain network (such as the first blockchain and the second blockchain) interact with each other through the off-chain cross-chain service device (also known as the cross-chain relay), and the off-chain cross-chain service device can be deployed with the off-chain full-chain cross-chain service 219. The off-chain full-chain cross-chain service may include a full-chain unified registration service 220, an information management and verification service 221, and a cross-chain event verification and forwarding service 222. Among them, the full-chain unified registration service can be used to interact with the full-chain identity allocation protocol in the full-chain service contract, implement initialization operations such as the relevant blockchain identity allocation operation in the full-chain identity allocation protocol, and maintain the management of multiple blockchains (such as the addition, deletion, modification, and query of any blockchain in the multiple blockchains). The information management and verification service can be used to interact with the key information disclosure interface in the full-chain business parent contract to achieve continuous security verification of the node port information disclosed by the key information disclosure interface to ensure the correctness and consistency of the node port information. The cross-chain event verification and forwarding service can be used to forward events between any two blockchains (such as a first blockchain and a second blockchain) in a multi-blockchain network (for example, when a cross-chain asset transfer event is detected on a first blockchain node of a first blockchain, a cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is constructed and forwarded to a second blockchain node of a second blockchain).

[0063] For ease of understanding, please further refer to Figure 3, which is a schematic diagram of a scenario of data processing based on multiple blockchains provided in an embodiment of the present application. In this scenario, a cross-chain transfer mechanism for digital assets is proposed, through which the full-chain assets to be transferred can be transferred from the first blockchain to the second blockchain. The first blockchain network for maintaining the first blockchain proposed in the embodiment of the present application can be the first blockchain network 200 in Figure 1 above, and the first blockchain node in the first blockchain network can be any blockchain node of the first blockchain network 200 in Figure 1 (such as the blockchain node 20a in the first blockchain network 200), and the second blockchain network for maintaining the second blockchain can be the second blockchain network 300 in Figure 1 above, and the second blockchain node in the second blockchain network can be any blockchain node of the second blockchain network 300 in Figure 1 (such as the blockchain node 30a in the second blockchain network 300). Among them, the cross-chain transfer process for full-chain assets can be: the first blockchain node obtains the full-chain asset transfer request 30 sent by the first business object for the business transaction, and when the business transaction is determined to be a cross-chain asset transfer transaction 31 based on the full-chain asset transfer request, the target full-chain business contract on the first blockchain is called, and the full-chain assets associated with the cross-chain asset transfer transaction are used as the full-chain assets to be transferred 32. The cross-chain asset transfer transaction indicates that the full-chain assets to be transferred are transferred from the first blockchain to the second blockchain. The first blockchain node can call the full-chain contract protocol integrated in the target full-chain business contract, and determine the target remote contract address 33 bound to the target full-chain business contract through the cross-chain asset transfer transaction (for example, the contract address corresponding to the target full-chain business contract deployed on the second blockchain), and generate a cross-chain asset transfer event 34 corresponding to the cross-chain asset transfer transaction based on the target remote contract address and the full-chain assets to be transferred. When the off-chain cross-chain service device reads the cross-chain asset transfer event from the first blockchain node, it constructs a cross-chain asset reconstruction transaction 35 corresponding to the cross-chain asset transfer event, and sends the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to the second blockchain node in the second blockchain network. The second blockchain node can determine the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction (the target remote full-chain business contract integrates the full-chain contract protocol), and call the target remote full-chain business contract to generate a full-chain mapping asset 36 corresponding to the full-chain asset to be transferred on the second blockchain. The asset content and asset data information of the full-chain mapping asset are consistent with those of the full-chain asset to be transferred.

[0064] It is understood that the first blockchain and the second blockchain can realize the cross-chain transfer of full-chain assets based on the unified asset transfer rules specified in the full-chain contract agreement in the target full-chain business contract, and at the same time, the asset content and asset data information of the full-chain mapped assets can be consistent with the full-chain assets to be transferred. Therefore, the full-chain mapped assets generated on the second blockchain and the full-chain assets to be transferred on the first blockchain can be regarded as the same asset, thereby realizing the full-chain circulation of full-chain assets in multiple blockchains to improve the liquidity of full-chain assets. Among them, the above-mentioned full-chain assets can be any type of on-chain assets, such as digital collections, game points in game scenarios, etc. It is understood that if the technical solution of this application is applied to the game scenario, the full-chain assets can be game points to be exchanged. For example, the game points of game players can be circulated in the first blockchain, and the exchange business for game points (such as game points exchanged for character equipment, etc.) can be deployed on the second blockchain. Therefore, when game players need to perform game points exchange business, the above-mentioned technical solution can be used to realize the cross-chain transfer of the game points to be transferred to the second blockchain, so that game players can perform related exchange business on the transferred game points (i.e., mapped game points) on the second blockchain.

[0065] It can be understood that the first blockchain node and the second blockchain node involved in the embodiments of the present application can be the computer devices mentioned above. The computer device can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0066] It should be noted that when the first blockchain node or the second blockchain node in the embodiment of the present application obtains the object data of the business object (for example, the above-mentioned personal object or enterprise object) across the chain (such as the object information of the business object or the full-chain assets owned by it), a prompt interface or pop-up window can be displayed. The prompt interface or pop-up window is used to prompt the business object that the object data is currently being collected. Only after the business object issues a confirmation operation on the prompt interface or pop-up window, the relevant steps of data acquisition are started, otherwise it ends.

[0067] In addition, it is understandable that in the specific implementation of this application, object data of business objects (for example, object information of business objects or the full-chain assets owned) may be involved. When the above embodiments of this application are applied to specific products or technologies, it is necessary to obtain the permission or consent of business objects such as business objects, and the collection, use and processing of relevant data need to comply with relevant laws and standards in relevant regions.

[0068] The specific process of realizing cross-chain circulation of full-chain assets in a multi-blockchain network can be referred to the embodiment shown below.

[0069] Further, please refer to Figure 4, which is a schematic flow chart of a multi-blockchain data processing method provided in an embodiment of the present application. The multi-blockchain includes at least a first blockchain and a second blockchain. The first blockchain corresponds to a first blockchain network, and the second blockchain corresponds to a second blockchain network. The first blockchain network is independent of the second blockchain network. The blockchain network corresponding to the first blockchain is referred to as the first blockchain network. "First blockchain corresponds to the first blockchain network," indicating that the first blockchain is maintained by the first blockchain network. The blockchain network corresponding to the second blockchain is referred to as the second blockchain network. "Second blockchain corresponds to the second blockchain network," indicating that the first blockchain is maintained by the second blockchain network.

[0070] As shown in FIG4 , the method can be executed by the first blockchain node in the first blockchain network mentioned above, specifically by the computer device that maintains the first blockchain node. The first blockchain node refers to a blockchain node in the first blockchain, to distinguish it from a blockchain node in the second blockchain. For example, the first blockchain node can be any blockchain node in the first blockchain network 200 shown in FIG1 above. The method can specifically include the following steps S101-S103:

[0071] S101. Obtain a full-chain asset transfer request sent by the first business object for a business transaction. When determining that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request, call the target full-chain business contract on the first blockchain and use the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred.

[0072] A cross-chain asset transfer transaction is used to transfer a full-chain asset from a first blockchain to a second blockchain. The first business object is the object to which the full-chain asset to be transferred belongs. The object can be a user or a computer device. A full-chain asset transfer request can be a request to transfer a full-chain asset from at least one blockchain in multiple blockchains. A full-chain asset can be a digital asset that is unique across multiple blockchains.

[0073] It can be understood that the first business object can initiate a cross-chain asset transfer transaction for the full-chain assets to be transferred, and the terminal where the first business object is located generates a full-chain asset transfer request based on the cross-chain asset transfer transaction, and sends the full-chain asset transfer request to the first blockchain node in the first blockchain network. When the first blockchain node determines that the business transaction indicated by the full-chain asset transfer request is a cross-chain asset transfer transaction for the full-chain assets, it executes the cross-chain asset transfer transaction to achieve the transfer of the full-chain assets to be transferred on the first blockchain to the second blockchain. For example, when the first business object needs to transfer a specified digital asset (such as one or more digital collections) from the first blockchain to the second blockchain, it can generate a cross-chain asset transfer transaction for the specified digital asset, and then generate a cross-chain asset transfer request corresponding to the cross-chain asset transfer transaction so that the specified digital asset (that is, the full-chain asset to be transferred) is transferred from the first blockchain to the second blockchain. It can be understood that the full-chain assets associated with the cross-chain asset transfer transaction are the assets to be transferred indicated by the cross-chain asset transfer transaction.

[0074] It is understood that the full-chain asset to be transferred can be a native asset determined on the first blockchain, or it can be a mapped asset generated by the first blockchain node on the first blockchain and transferred across the chain from another business chain to the first blockchain. When the full-chain asset to be transferred is a native asset determined on the first blockchain, the asset identifier of the full-chain asset to be transferred is generated by the first blockchain node. When the full-chain asset to be transferred is an asset transferred across the chain from another business chain to the first blockchain, the asset identifier of the full-chain asset to be transferred is generated by the blockchain node associated with the other business chain. In other words, the asset identifier of the full-chain asset to be transferred is generated by the blockchain node associated with the business chain where the full-chain asset to be transferred is the native full-chain asset. For example, taking the example of the asset identifier of the full-chain asset to be transferred being generated by the first blockchain node, the full-chain asset to be transferred can belong to part or all of the full-chain assets determined on the first blockchain for cross-chain transfer. It is understood that the full-chain asset determined on the first blockchain for cross-chain transfer here refers to the full-chain asset whose asset identifier is generated by the first blockchain node and is used for cross-chain transfer.

[0075] Therefore, the process of determining the full-chain assets for cross-chain transfer on the first blockchain may be to obtain a full-chain asset determination request for the full-chain asset determination transaction, call the target full-chain business contract on the first blockchain based on the full-chain asset determination request, and determine the number of determined assets involved in the full-chain asset determination transaction as the number of assets to be determined; call the full-chain contract protocol in the target full-chain business contract, obtain the identification prefix associated with the first blockchain, and generate the full-chain asset identification to be determined corresponding to the number of assets to be determined based on the identification prefix associated with the first blockchain and the asset identification template configured in the full-chain contract protocol; the full-chain asset identification to be determined includes the identification prefix associated with the first blockchain; call the asset determination contract in the target full-chain business contract, determine the full-chain asset corresponding to the full-chain asset identification to be determined on the first blockchain, and use the determined full-chain asset as the full-chain asset determined on the first blockchain for cross-chain transfer. It is possible

[0076] It is understood that the full-chain asset determination transaction can be used to indicate the number of full-chain assets that need to be determined on the first blockchain (for example, 100 digital collections). The first blockchain node needs to assign an asset identifier to each full-chain asset to be determined (for example, assign an asset identifier to each of the 100 digital collections). The asset identifier is used to uniquely identify the corresponding full-chain asset. Through the asset identifier, it can be determined which business chain the full-chain asset originally belongs to and which business chain-related blockchain node determined it. In this way, when the full-chain asset circulates on multiple blockchains, it can still be known which business chain the full-chain asset originally belonged to.

[0077] The identification prefix associated with the first blockchain can be the blockchain identifier of the first blockchain, or it can be identification information generated based on the blockchain identifier of the first blockchain. For example, the hash value obtained by hashing the blockchain identifier of the first blockchain can be used as the identification prefix associated with the first blockchain. This is not limited here. The asset identification template is used to define the identification format of the generated asset identifier, such as the length of the asset identifier and whether the asset identifier contains uppercase and lowercase letters. This is not limited here. It can be understood that this allows the full-chain assets determined on a business chain (it should be noted that the full-chain assets here do not refer to the full-chain mapping assets generated in the cross-chain transfer scenario, but the native full-chain assets generated by the full-chain asset determination transaction submitted by the relevant business objects) to have a unique asset identifier for the entire chain. In other words, the asset identifiers of the native full-chain assets determined by the target full-chain business contracts on any two business chains cannot be the same. In this way, the full-chain assets can maintain their uniqueness when they are circulated on multiple blockchains. There will be no conflict between a full-chain asset and an existing asset on another business chain when it circulates from one business chain to another. It can also be known which blockchain node associated with which business chain the full-chain asset was originally determined. It can be understood that the identification prefix of the asset identification depends on the identification prefix provided by the business chain in which it is located. The asset identification template can be specified on the full-chain business parent contract and can be obtained through the full-chain contract agreement in the target full-chain business contract.

[0078] S102. Call the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract.

[0079] Among them, the full-chain contract agreement is determined based on the full-chain contract agreement interface provided by the full-chain business parent contract on the first blockchain. The target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that is integrated with the full-chain contract agreement. It can be understood that each blockchain in the multi-blockchain can be deployed with a full-chain business parent contract and a target full-chain business contract, and the target full-chain business contract on each blockchain is integrated with the full-chain contract agreement indicated by the full-chain contract agreement interface provided by the full-chain business parent contract. The full-chain contract agreement defines processing rules related to full-chain assets (such as full-chain asset transfer rules, full-chain asset determination rules, etc.), so that each blockchain in the multi-blockchain can realize asset transfer with unified rules, thereby realizing the full-chain circulation of assets.

[0080] It can be understood that the target full-chain business contract on the first blockchain is bound to the contract address of the target full-chain business contract on other business chains in multiple blockchains. That is to say, the remote contract address bound to the target full-chain business contract on the first blockchain includes the contract address of the target full-chain business contract on other business chains. At this time, the target full-chain business contract on other business chains is the remote full-chain business contract corresponding to the target full-chain business contract on the first blockchain. It can be understood that the target full-chain business contract on the blockchain (second blockchain) of the asset to be transferred in the cross-chain asset transfer transaction is the target remote full-chain business contract here, and the contract address of the target full-chain business contract on the blockchain (second blockchain) of the asset to be transferred in is the target remote contract address here. In addition, it should be noted that when the target full-chain business contract on one blockchain is bound to the contract address of the target full-chain business contract on another blockchain, the full-chain assets on the blockchain can be transferred to another blockchain.

[0081] Among them, the cross-chain asset transfer transaction is used to indicate that the full-chain assets to be transferred are transferred from the first blockchain to the second blockchain, that is, the cross-chain asset transfer transaction carries the second blockchain identifier of the second blockchain. Therefore, calling the full-chain contract agreement in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract can be, calling the full-chain contract agreement in the target full-chain business contract to obtain the remote contract address bound to the target full-chain business contract; the remote contract address bound to the target full-chain business contract includes the contract address corresponding to the full-chain business contract integrated with the full-chain contract agreement on the reference business chain; the reference business chain is a blockchain other than the first blockchain in the multi-blockchain (that is, the other business chain mentioned above); the reference business chain includes the second blockchain; among the remote contract addresses bound to the target full-chain business contract, the remote contract address associated with the second blockchain identifier is determined as the target remote contract address.

[0082] S103. When a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain assets to be transferred, the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is sent to the second blockchain node in the second blockchain network through the off-chain cross-chain service device.

[0083] The first blockchain node may generate a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction based on the target remote contract address and the full-chain asset to be transferred. It is understood that the cross-chain asset transfer event may be used to indicate the cross-chain transfer of the full-chain asset to be transferred from the target full-chain business contract on the first blockchain to the target full-chain business contract indicated by the target remote contract address on the second blockchain.

[0084] It can be understood that when the full-chain asset to be transferred is transferred from the first blockchain to the second blockchain, the full-chain asset to be transferred on the first blockchain is actually locked, and the full-chain mapping asset corresponding to the full-chain asset to be transferred is determined on the second blockchain. Therefore, generating a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction can be to call the target full-chain business contract to switch the asset state of the full-chain asset to be transferred from the first state to the second state; the second state is the asset locked state, and the first state is the asset unlocked state; when the asset state of the full-chain asset to be transferred is in the second state, a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred. In other words, the full-chain asset to be transferred can be locked through the target full-chain business contract, and the cross-chain asset transfer event is generated when the full-chain asset to be transferred on the first blockchain is locked. At this time, although the full-chain asset to be transferred is actually on the first blockchain, business operations on the full-chain asset to be transferred cannot be performed on the first blockchain.

[0085] Furthermore, when generating a cross-chain asset transfer event, the first blockchain can also generate a chain-wide unique event identifier (event nonce) for the cross-chain asset transfer event across multiple blockchains to facilitate event querying. Therefore, generating a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction can include obtaining the first blockchain identifier of the first blockchain; for example, obtaining the first blockchain identifier through the full-chain identifier allocation protocol in the full-chain service contract; the first blockchain identifier being a blockchain identifier configured for the first blockchain via the full-chain unified registration service in the off-chain full-chain cross-chain service; invoking the full-chain event identifier generation protocol in the full-chain service contract based on the first blockchain identifier to generate an event identifier associated with the first blockchain identifier; and generating a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction based on the event identifier, the target remote contract address, and the full-chain asset to be transferred. This cross-chain asset transfer event carries the aforementioned event identifier. Since the blockchain identifiers configured for each blockchain on multiple blockchains are different, the event identifier can be generated based on the blockchain identifier of the business chain to which it belongs. In this way, the generated event identifier can be used to indicate that it was generated on the aforementioned business chain. Therefore, when forwarding events, event querying across multiple blockchains is possible. For example, relevant business objects or third parties can easily match business transactions on the source chain (such as the first blockchain) and the target chain (such as the second blockchain) based on the event identifier, thereby achieving management and maintenance of the entire life cycle of the relevant business or full-chain assets on the entire chain.

[0086] The off-chain cross-chain service device is a device that is independent of the first and second blockchain networks. It is understood that the off-chain cross-chain service device is used to forward events between the first and second blockchains. The off-chain cross-chain service device is deployed with an off-chain full-chain cross-chain service, which includes a cross-chain event verification and forwarding service. This cross-chain event verification and forwarding service can be used to verify and forward cross-chain asset transfer events when the off-chain cross-chain service device reads them from the first blockchain node. The event verification process can include both asset verification and transaction verification.

[0087] It is understood that the cross-chain asset transfer event carries the asset identifier of the full-chain asset to be transferred, and the asset identifier of the full-chain asset to be transferred is generated based on the identifier prefix associated with the first blockchain and the asset identifier template configured in the full-chain contract agreement. The cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is constructed by the off-chain cross-chain service device after verifying the asset identifier of the full-chain asset to be transferred carried in the cross-chain asset transfer event based on the identifier prefix and the asset identifier template, and the verification is successful.

[0088] Among them, it can be understood that the asset verification process can refer to the identification verification of the asset identification of the full-chain asset to be transferred carried by the cross-chain asset transfer event based on the identification prefix and the asset identification template. In other words, it can be verified whether the identification prefix in the asset identification of the full-chain asset to be transferred is consistent with the identification prefix associated with the first blockchain, and whether the asset identification of the full-chain asset to be transferred matches the asset identification template, so as to realize the identification verification of the asset identification of the full-chain asset to be transferred. It can be understood that when the off-chain cross-chain service device determines that the identification prefix in the asset identification of the full-chain asset to be transferred is consistent with the identification prefix associated with the first blockchain, and the asset identification of the full-chain asset to be transferred matches the asset identification template, it is determined that the identification verification is successful.

[0089] Furthermore, the off-chain cross-chain service device can be used to isolate the first blockchain network from the second blockchain network. The first blockchain node may generate a cross-chain asset transfer event by signing the cross-chain asset transfer transaction using the private key information negotiated with the off-chain cross-chain service device, using the signed cross-chain asset transfer transaction as the event signature information, and generating a cross-chain asset transfer event based on the event signature information and the cross-chain asset transfer transaction. The cross-chain asset transfer event read by the off-chain cross-chain service device from the first blockchain node may include the event signature information and the cross-chain asset transfer transaction. Therefore, the transaction verification process may involve verifying the event signature information in the cross-chain asset transfer event using the public key information corresponding to the private key information of the first blockchain. Upon successful signature verification, the transaction parameters to be verified corresponding to the event signature information are obtained. The cross-chain asset transfer transaction carried in the cross-chain asset transfer event and the transaction parameters to be verified are then compared to obtain a transaction comparison result to determine the transaction verification result. It is understood that if the cross-chain asset transfer transaction carried in the cross-chain asset transfer event and the transaction parameters to be verified are the same, the transaction comparison result indicates that the transaction verification is successful; if the cross-chain asset transfer transaction carried in the cross-chain asset transfer event and the transaction parameters to be verified are different, the transaction comparison result indicates that the transaction verification is unsuccessful. It is understood that the off-chain cross-chain service device will only construct the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event when it determines that the identity verification is successful and the transaction verification is successful. This cross-chain asset reconstruction transaction is used to indicate the transfer of the full-chain assets to be transferred from the first blockchain to the second blockchain.

[0090] Furthermore, the off-chain cross-chain service device may verify and forward each cross-chain asset transfer event it reads using the cross-chain event verification and forwarding service. Alternatively, the off-chain cross-chain service device may verify and forward each cross-chain asset transfer event it reads using the cross-chain event verification and forwarding service. Specifically, the off-chain cross-chain service device may read cross-chain asset transfer events associated with a target full-chain business contract generated within the target period. Upon reading a cross-chain asset transfer event associated with a target full-chain business contract, the off-chain cross-chain service device may verify the cross-chain asset transfer event using the cross-chain event verification and forwarding service within the off-chain full-chain cross-chain service. The verified cross-chain asset transfer event may then be forwarded using the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event. Specifically, the off-chain cross-chain service device generates a cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event and transmits the cross-chain asset reconstruction transaction to the second blockchain node. A cycle can be one hour, two hours, etc., and there is no limit on the length of the cycle.

[0091] It is understandable that after the first business object transfers the full-chain asset to be transferred from the first blockchain to the second blockchain, if it wants to use the full-chain asset to be transferred (i.e., the full-chain mapped asset) on the second blockchain, it is necessary to transfer the additional native fuel (also known as the basic token) to the second blockchain. At this time, the full-chain token airdrop contract on the first blockchain can be used to generate a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction, and carry the full-chain token to be airdropped in the cross-chain asset transfer event.

[0092] Therefore, before generating a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction, the first blockchain node can call the full-chain token airdrop contract on the first blockchain through the target full-chain business contract to obtain the first blockchain token (i.e., the source chain token) associated with the full-chain asset to be transferred, and use the obtained first blockchain token as the full-chain token to be airdropped. In this way, when the first blockchain node generates a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction, the full-chain token to be airdropped is written into the cross-chain asset transfer event. It can be understood that through the full-chain token airdrop contract, the first blockchain node does not need to take additional steps to realize the transfer of the basic token, but instead uses the full-chain token to be airdropped as the airdrop fee directly and simultaneously completes the process of cross-chain transfer of the full-chain assets, thereby realizing cross-chain operations on the source chain (first blockchain) side when the full-chain assets are transferred across the chain.

[0093] Among them, the off-chain cross-chain service device can send the cross-chain asset reconstruction transaction generated based on the cross-chain asset transfer event to the second blockchain node in the second blockchain network, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate the full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred. At the same time, the second blockchain node can determine the second blockchain airdrop token corresponding to the full-chain token to be airdropped carried by the cross-chain asset reconstruction transaction through the full-chain token airdrop contract, and use the second blockchain airdrop token as the full-chain token of the full-chain mapping asset on the second blockchain. The relevant operations of the second blockchain node can refer to the relevant description of the following embodiment.

[0094] It is understood that assets circulating on a first blockchain can be transferred across chains to a second blockchain (i.e., inter-chain transfers) and can be transferred within the first blockchain (i.e., intra-chain transfers, such as transfers and other business transactions). In other words, the first blockchain includes both assets that require cross-chain circulation and assets that circulate within the blockchain. Assets transferred from a first blockchain to a second blockchain across chains can circulate on the second blockchain. In other words, assets circulating within the second blockchain can include native assets determined by the second blockchain itself and assets transferred from the first blockchain (it is understood that these assets are essentially determined by the second blockchain, but the determined assets are fully mapped assets. This asset data information is asset data information related to the first blockchain, while the asset data information of the native assets determined on the second blockchain is asset data information related to the second blockchain). It is understood that, under the requirements of specific business scenarios, assets on the second blockchain can also be transferred across chains to the first blockchain for circulation on the first blockchain. The process and principles for cross-chain asset transfers on the second blockchain are the same as those on the first blockchain. Please refer to the description of cross-chain transfers of full-chain assets on the first blockchain above and will not be repeated here.

[0095] For example, the assets on the first blockchain include the full-chain assets to be transferred (P11) for cross-chain transfer and the assets (P12) circulated within the first blockchain. Here, P12 is regarded as the native asset determined by the first blockchain. It can be understood that the asset data information of P12 is associated with the first blockchain, and accordingly, the asset data information of P11 is associated with the first blockchain; the assets on the second blockchain include the full-chain mapped assets (P11') determined for P11 for circulation on the second blockchain and the assets (P21) circulated within the second blockchain; here, P21 is regarded as the native asset determined by the second blockchain. It can be understood that the asset data information of P21 is associated with the second blockchain, and the asset data information of P11' and P11 are consistent, that is, the asset data information of P11' is associated with the first blockchain, and P11' and P11 can be regarded as the same asset with the same asset content and the same asset data information. It can be understood that the assets on the second blockchain can also include full-chain assets to be transferred (P22) for cross-chain transfer, and the asset data information of P22 is associated with the second blockchain; at this time, the assets on the first blockchain can also include full-chain mapping assets (P22') determined for P22 for circulation on the first blockchain. At this time, the asset data information of P22' and P22 are consistent, that is, the asset data information of P22' is associated with the second blockchain, and P22' and P22 can be regarded as the same asset with the same asset content and the same asset data information.

[0096] For example, as shown in FIG5 , FIG5 is a schematic diagram of a scenario of a cross-chain asset transfer provided by an embodiment of the present application; wherein, S51, the first business object sends a full-chain asset transfer request for a cross-chain asset transfer transaction through the client; S52, the first blockchain node (the first blockchain node as shown in FIG2 ) calls the target full-chain business contract on the first blockchain and uses the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred, calls the full-chain contract protocol in the target full-chain business contract, and determines the target remote contract address bound to the target full-chain business contract; S53, the first blockchain node calls the full-chain identifier allocation protocol in the full-chain service contract through the target full-chain business contract to obtain the first blockchain identifier of the first blockchain; S54, the first blockchain node calls the full-chain event identifier generation protocol in the full-chain service contract based on the first blockchain identifier to generate an event identifier associated with the first blockchain identifier. Identification; S55. The first blockchain node calls the full-chain token airdrop contract on the first blockchain through the target full-chain business contract to obtain the first blockchain token associated with the full-chain asset to be transferred as the full-chain token to be airdropped; S56. The first blockchain node generates a cross-chain asset transfer event based on the event identifier, the target remote contract address, the full-chain asset to be transferred, and the full-chain token to be airdropped; S57. When the off-chain cross-chain service device (the off-chain cross-chain service device as shown in Figure 2) reads the cross-chain asset transfer event from the first blockchain node, it verifies the cross-chain asset transfer event through the cross-chain event verification and forwarding service in the deployed off-chain full-chain cross-chain service, and generates a cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event after the event verification passes; S58. The off-chain cross-chain service device forwards the cross-chain asset reconstruction transaction to the second blockchain node to realize the event forwarding of the cross-chain asset transfer event. It can be understood that the off-chain cross-chain service device can send the cross-chain asset reconstruction transaction to the second blockchain node in the second blockchain network (the second blockchain node as shown in Figure 2); S59, the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; S510, the second blockchain node calls the full-chain token airdrop contract through the target remote full-chain business contract to determine the second blockchain airdrop token corresponding to the full-chain token to be airdropped carried by the cross-chain asset reconstruction transaction.

[0097] It can be understood that since the asset data information (such as asset identification information) of the full-chain mapped assets is consistent with the asset data information of the full-chain resources to be transferred, the full-chain mapped assets and the full-chain assets to be transferred can be regarded as the same assets, and thus can be regarded as the full-chain assets to be transferred being circulated to the second blockchain, realizing the full-chain circulation of digital assets. Since a full-chain asset can be circulated to any blockchain in multiple blockchains, such as circulating the full-chain asset to be transferred from the first blockchain to the second blockchain, and then circulating from the second blockchain to the third business chain in multiple blockchains, etc., at this time, the full-chain asset to be transferred circulated to the third business chain can still be understood as the native asset on the first blockchain.

[0098] In an embodiment of the present application, the multiple blockchains may include a first blockchain and a second blockchain, and the cross-chain asset transfer transaction corresponding to the full-chain asset transfer request is used to indicate that the full-chain assets to be transferred (such as digital assets, specifically digital collections) are transferred from the first blockchain to the second blockchain; this solution can realize the cross-chain transfer of the full-chain assets to be transferred by deploying full-chain business contracts integrated with the same full-chain contract protocol on the first blockchain and the second blockchain; it can be understood that a target full-chain business contract for executing the cross-chain asset transfer transaction is deployed on the first blockchain, and the full-chain business contract corresponding to the target full-chain business contract on the second blockchain is a target remote full-chain business contract, and the target full-chain business contract and the target remote full-chain business contract are integrated with the same full-chain contract protocol, that is, the target full-chain business contract and the target remote full-chain business contract are integrated with the same asset transfer method (such as asset transfer-related method, asset determination-related method), that is, the asset determination rule on the first blockchain is the same as that on the second blockchain. The asset determination rules on the two blockchains are the same. Therefore, the first blockchain node can call the full-chain contract agreement in the target full-chain business contract to generate a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction to realize the cross-chain transfer of the full-chain assets to be transferred. The second blockchain node can call the full-chain contract agreement in the target remote full-chain business contract based on the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to perform asset determination of the full-chain assets to be transferred. Since the first blockchain node and the second blockchain node use the asset transfer method uniformly specified in the same full-chain contract agreement to realize the transfer and determination of digital assets, the asset data information of the full-chain mapped assets determined by the second blockchain node can be consistent with the asset data information of the full-chain assets to be transferred. At this time, the full-chain assets to be transferred in the first blockchain and the mapped assets on the second blockchain can be regarded as the same asset, so that the full-chain liquidity of the same digital asset between different blockchains can be safely realized, thereby improving the liquidity of digital assets in multiple blockchains.

[0099] Further, please refer to Figure 6, which is a flow chart of a multi-blockchain data processing method provided in an embodiment of the present application. As shown in Figure 6, the method can be executed by the first blockchain node in the first blockchain network mentioned above. For example, the first blockchain node can be any blockchain node in the first blockchain network 200 shown in Figure 1 above. The method can specifically include the following steps S201-S203:

[0100] S201. Obtain a contract lock request sent by a second business object for a target remote full-chain business contract deployed on a second blockchain.

[0101] In certain scenarios, there are contract updates (or upgrades). At this time, in order to ensure that the full-chain assets will not be lost, the target full-chain business contract can be locked through the remote contract address locking mechanism to suspend the cross-chain transfer of full-chain assets. The remote contract address locking mechanism is used to lock the specified remote contract address on another business chain in the target full-chain business contract on one business chain. The contract update process on each business chain is the same. Here, the execution process of this scenario is described by taking the contract update on the second blockchain as an example, and taking the first blockchain and the second blockchain in the multi-blockchain as an example. That is to say, when the contract status of the target remote full-chain business contract on the second blockchain is in the contract update state, steps S201-S203 in the embodiment of the present application can be executed.

[0102] Among them, the second business object is the business object corresponding to the target remote full-chain business contract on the second blockchain. The contract lock request is generated by the second business object after the contract address corresponding to the target full-chain business contract is remotely locked in the target remote full-chain business contract deployed on the second blockchain. It can be understood that the second business object can be the contract owner corresponding to the target remote full-chain business contract on the second blockchain. When the second business object updates the contract of the target remote full-chain business contract on the second blockchain, it will first execute the remote address lock in the target remote full-chain business contract on the second blockchain, and after the remote address lock is completed in the target remote full-chain business contract on the second blockchain (for example, by calling the full-chain contract protocol in the target remote full-chain business contract to perform remote address lock), the remote address lock can be executed in the target full-chain business contract on the first blockchain, that is, the second blockchain node generates a contract lock request and sends the contract lock request to the first blockchain node. The process of executing remote address lock in the target remote full-chain business contract on the second blockchain can refer to the relevant description of the following embodiment.

[0103] S202. Obtain the target remote contract address corresponding to the target remote full-chain business contract to be locked on the second blockchain from the contract locking request.

[0104] Among them, the contract locking request can carry the blockchain identifier of the second blockchain and the target remote contract address corresponding to the target remote full-chain business contract on the second blockchain, indicating that it is necessary to contract lock the target remote full-chain business contract on the second blockchain in the target full-chain business contract on the first blockchain, that is, to address lock the target remote contract address corresponding to the target remote full-chain business contract on the second blockchain.

[0105] S203. Through the remote contract address locking mechanism associated with the target full-chain business contract, a remote contract address locking method for remotely locking the target remote contract address is determined in the target full-chain business contract, the remote contract address locking method is called to remotely lock the target remote contract address corresponding to the target remote full-chain business contract, and the address state of the target remote contract address after remote address locking is configured as an address locked state in the target full-chain business contract.

[0106] The target remote contract address in the locked address state is used to suspend the reception of full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer. In other words, at this time, full-chain assets on the first blockchain cannot be transferred cross-chain to the target remote full-chain business contract on the second blockchain through the target full-chain business contract, i.e., the contract is locked. This prevents the loss of full-chain assets on the first blockchain.

[0107] Optionally, the first blockchain node may generate contract lock completion information corresponding to the contract lock request after the remote address is locked, and return the contract lock completion information to the second blockchain node, so that the second business object determines that the target full-chain business contract in the first blockchain has executed the remote address lock.

[0108] The remote contract address locking mechanism can be implemented by introducing a contract address locking function (e.g., pauseMove(chainID)). It should be understood that in the contract address locking function, the chainID is the blockchain identifier of the business chain to be locked, that is, the chainID here can refer to the blockchain identifier of the second blockchain. The contract address locking function represents a remote contract address locking method. By executing the contract address locking function, the target remote contract address associated with the blockchain identifier indicated by chainID can be remotely locked, and the address state of the target remote contract address after the remote address is locked can be configured to the address locked state, which means that the business object on the first blockchain cannot transfer the entire chain assets to the second blockchain. It can be understood that by executing the contract address locking function indicated by the remote contract address locking method, it means that the contract locking of the target remote business contract on the second blockchain is performed in the target full-chain business contract on the first blockchain, or it can be described as performing chain locking of the second blockchain in the target full-chain business contract on the first blockchain, or it can be described as performing address locking of the target remote contract address corresponding to the target remote business contract on the second blockchain in the target full-chain business contract on the first blockchain. At the same time, by executing the contract address locking function indicated by the remote contract address locking method, the address status of the target remote contract address will also be set to the address locked state.

[0109] It can be understood that by performing an address lock operation in the target full-chain business contract on the first blockchain, it is possible to prevent the transfer of full-chain assets on the first blockchain to the second blockchain. At the same time, by performing an address lock operation in the target remote full-chain business contract on the second blockchain, it is possible to suspend the transfer of full-chain assets on the first blockchain to the second blockchain. At this time, the target remote full-chain business contract can be securely updated on the second blockchain.

[0110] Optionally, when the contract status of the target remote full-chain business contract is adjusted from the contract update status to the contract update completion status, the target remote full-chain business contract in the contract update completion status is the updated target remote full-chain business contract, that is, the new target full-chain business contract on the second business. At the same time, the contract address of the updated target remote full-chain business contract is the updated target remote contract address, that is, the contract address of the new target full-chain business contract on the second business. It can be understood that for both the target remote full-chain business contract before the update and the target remote full-chain business contract after the update on the second blockchain, the remote address lock of the target contract address is required. In other words, the target contract address is in the address lock state in both the target remote full-chain business contract before the update and the target remote full-chain business contract after the update.

[0111] It can be understood that when the target remote full-chain business contract deployed on the second blockchain is updated, it is necessary to set the contract address of the updated target remote full-chain business contract as the remote contract address in the target full-chain business contract on the first blockchain, and set the contract address of the target full-chain business contract on the first blockchain as the remote contract address in the target full-chain business contract on the second blockchain, that is, to bind the contract addresses to each other in the two aforementioned full-chain business contracts. That is, after the target remote full-chain business contract on the second blockchain is updated, the first blockchain node obtains the first contract binding request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain; the first contract binding request is generated by the second business object after performing remote address binding on the target contract address in the updated target remote full-chain business contract deployed on the second blockchain; the updated target remote contract address corresponding to the updated target remote full-chain business contract to be bound on the second blockchain is obtained from the first contract binding request; the remote address setting interface is called through the full-chain contract protocol in the target full-chain business contract, and the updated target remote contract address is set in the remote contract address bound to the target full-chain business contract, so as to realize the binding of the target remote full-chain business contract on the second blockchain (this is the new target remote full-chain business contract) in the target full-chain business contract on the first blockchain. It can be understood that for step S102 in the above embodiment, the target remote contract address bound to the target full-chain business contract can be the contract address of the target remote full-chain business contract on the second blockchain that has not been updated, or it can be the contract address of the new target remote full-chain business contract on the second blockchain after the contract update is completed.

[0112] Optionally, the first blockchain node can generate contract binding completion information corresponding to the first contract binding request after the remote address binding, and return the contract binding completion information to the second blockchain node, so that the second business object can determine that the target full-chain business contract in the first blockchain has executed the remote address binding.

[0113] Among them, it can be understood that since the address of the target remote contract address (i.e. the contract address of the old target remote full-chain business contract) was locked before, the full-chain assets on the first blockchain cannot be transferred to the second blockchain. It can be understood that the contract address of the updated target remote full-chain business contract on the second blockchain is also locked at this time. Therefore, the address unlocking is required here to restore the asset circulation between the first blockchain and the second blockchain. That is to say, the first contract unlocking request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain is obtained; the first contract unlocking request is generated by the second business object after remote address unlocking of the target contract address in the updated target remote full-chain business contract deployed on the second blockchain, that is, in the updated target remote full-chain business contract on the second blockchain, the target full-chain business contract on the first blockchain will also be unlocked; the updated target remote contract address corresponding to the updated target remote full-chain business contract to be unlocked on the second blockchain is obtained from the first contract unlocking request. The first contract unlocking request can also carry the blockchain identifier of the second blockchain; through the remote contract address associated with the target full-chain business contract The remote contract address unlocking mechanism is used to unlock the specified remote contract address on another business chain in the target full-chain business contract on one business chain. The remote contract address unlocking method for remotely unlocking the updated target remote contract address is determined in the target full-chain business contract. The remote contract address unlocking method is called to remotely unlock the updated target remote contract address corresponding to the updated target remote full-chain business contract, and the address state of the updated target remote contract address after remote address unlocking is configured as an address unlocked state in the target full-chain business contract. The updated target remote contract address in the address unlocked state is used to restart receiving the full-chain assets for cross-chain transfer sent by the first business object through the target full-chain business contract.

[0114] The remote contract address unlocking mechanism can be implemented by introducing a contract address unlocking function (e.g., unpauseMove(chainID)). In the contract address unlocking function, the chainID can be the blockchain identifier of the business chain locked by the contract address unlocking function, that is, the chainID here can refer to the blockchain identifier of the second blockchain. The contract address unlocking function can specifically be a method for unlocking the remote contract address of the target remote contract contained in the current business contract. By executing the contract address unlocking function, the target remote contract address associated with the blockchain identifier indicated by the chainID can be remotely unlocked, and the address state of the target remote contract address after the remote address is unlocked can be configured to an unlocked address state. This means that at this time, the business object on the first blockchain can transfer the entire chain assets to the second blockchain again. It can be understood that by executing the contract address unlocking function indicated by the remote contract address unlocking method, it is indicated that the contract unlocking of the updated target remote business contract on the second blockchain is performed in the target full-chain business contract on the first blockchain, or it can be described as performing chain unlocking of the second blockchain in the target full-chain business contract on the first blockchain, or it can be described as performing address unlocking of the updated target remote contract address corresponding to the updated target remote business contract on the second blockchain in the target full-chain business contract on the first blockchain. At the same time, by executing the contract address unlocking function indicated by the remote contract address unlocking method, the address state of the updated target remote contract address will also be set to the address unlocked state. Among them, remote address unlocking of the updated target remote contract address corresponding to the updated target remote full-chain business contract can refer to deleting the target remote contract address after the remote address is locked in the target full-chain business contract, and adding the target remote contract address to the target full-chain business contract.

[0115] Optionally, the first blockchain node may generate contract unlocking completion information corresponding to the first contract unlocking request after the remote address is unlocked, and return the contract unlocking completion information to the second blockchain node, so that the second business object determines that the target full-chain business contract in the first blockchain has executed the remote address unlocking.

[0116] It can be understood that by performing the address unlock operation in the target full-chain business contract on the first blockchain, the full-chain assets on the first blockchain can be re-transferred to the second blockchain. At the same time, by performing the address unlock operation in the updated target remote full-chain business contract on the second blockchain, the full-chain assets on the first blockchain can be re-received and transferred to the second blockchain. At this point, all update processes for the target remote full-chain business contract can be completed on the second blockchain, and the target remote full-chain business contract on the second blockchain is successfully replaced by the updated target remote full-chain business contract.

[0117] For example, as shown in FIG7 , FIG7 is a schematic diagram of a scenario of contract update provided by an embodiment of the present application; wherein, the blockchain identifier of the first blockchain is A, the blockchain identifier of the second blockchain is B, the contract address of the target full-chain business contract deployed on the first blockchain is the target contract address, and the contract address of the target remote full-chain business contract deployed on the second blockchain is the target remote contract address; S71, when it is necessary to update the contract of the target remote full-chain business contract on the second blockchain, first, the second blockchain node executes pauseMove(A) in the target remote full-chain business contract of the second blockchain to remotely lock the target contract address in the target remote full-chain business contract of the second blockchain; S72, the second blockchain node can generate a contract lock request and send it to the first blockchain node. point; S73, the first blockchain node executes pauseMove(B) in the target remote full-chain business contract of the first blockchain to remotely lock the target remote contract address in the target full-chain business contract of the first blockchain; S74, the contract update of the target remote full-chain business contract on the second blockchain of the second blockchain node is completed, and the updated target remote full-chain business contract is obtained. It is necessary to execute pauseMove(A) in the updated target remote full-chain business contract on the second blockchain to remotely lock the target contract address in the updated target remote full-chain business contract on the second blockchain, so that it is temporarily impossible to circulate assets through the target full-chain business on the first blockchain and the updated target remote full-chain business contract on the second blockchain.

[0118] At this time, S75, the second blockchain node performs remote contract address binding in the updated target remote full-chain business contract on the second blockchain, that is, the target contract address of the target full-chain business contract on the first blockchain is set to the remote contract address in the updated target remote full-chain business contract; S76, the second blockchain node can generate a first contract binding request and send it to the first blockchain node; S77, the first blockchain node performs remote contract address binding in the target full-chain business contract on the first blockchain based on the first contract binding request, that is, the updated target remote contract address corresponding to the updated target full-chain business contract on the second blockchain is set to the remote contract address in the target full-chain business contract.

[0119] It can be understood that, at S78, it is necessary to perform contract unlocking on the updated target remote full-chain business contract and the target full-chain business contract. That is, the second blockchain node must execute unpauseMove(A) in the updated target remote full-chain business contract on the second blockchain to remotely lock the updated target contract address in the updated target remote full-chain business contract on the second blockchain; S79, the second blockchain node can generate a first contract unlock request and send it to the first blockchain node; S710, the first blockchain node executes unpauseMove(B) in the target remote full-chain business contract on the first blockchain to remotely unlock the updated target remote contract address in the target full-chain business contract on the first blockchain, so that assets can be circulated again through the target full-chain business on the first blockchain and the updated target remote full-chain business contract on the second blockchain.

[0120] In other words, the remote contract address locking mechanism can be used to automatically suspend asset circulation during the contract update process, ensuring business consistency and asset security during the setup process of the full-chain business contract. At the same time, after the remote contract address, assets cannot be circulated between the first blockchain and the second blockchain. There is no restriction on the execution order of related operations on the first blockchain and the second blockchain, and not following the characteristic execution order will not cause loss to assets on either business chain. For example, in the above-described process, the binding of the remote contract address is completed in the target full-chain business contract on the first blockchain after the binding of the remote contract address is completed after the updated target remote full-chain business contract on the second blockchain. Optionally, the binding of the remote contract address can also be completed in the target full-chain business contract on the first blockchain before the binding of the remote contract address is completed in the updated target remote full-chain business contract on the second blockchain. This is not limited here.

[0121] Among them, it can be understood that the concept of remote contract address is: set the target full-chain business contract on business chain A (such as contract a), and the target full-chain business contract of the same type on device business chain B (such as contract b). Contract b is the remote business contract of contract a on business chain B. That is, they can manage the same type of full-chain assets. Therefore, the remote business contract must be set up first so that the target full-chain business contract on business chain A can clearly correspond to the target full-chain business contract on business chain B that manages the same type of full-chain assets. Only in this way can the cross-chain circulation of full-chain assets begin. If the contract owner wants to update contract a on business chain A to contract c, in such a scenario, the full-chain flow of the full-chain assets in the target full-chain business contract can be locked through the remote contract address locking mechanism first, and then the contract can be updated, thus protecting the data consistency and security capabilities.

[0122] For example, a pauseMove function is introduced that accepts a blockchain identifier parameter, chainId. The pauseMove function can be used to lock the business chain indicated by chainId. For example, executing pauseMove(B) in the target full-chain business contract of business chain A means that business objects on business chain A are temporarily unable to send full-chain assets to business chain B. This design allows contract owners to handle ongoing business contract updates. Specifically, the contract owner can call pauseMove(A) in the target full-chain business contract of business chain B. This prevents business objects on business chain B from sending full-chain assets to business chain A, while business objects on business chain A can continue to send full-chain assets to business chain B. In other words, contract B can still correctly receive full-chain assets from contract A. The contract owner then calls pauseMove(B) on contract a in business chain A. This prevents business objects on business chain A from sending full-chain assets to business chain B. Similarly, after contract a in business chain A is updated to contract c, pauseMove(B) needs to be called on contract c in business chain A. At this time, the contract owner can set the remote contract address on contract b and contract c in any order. After confirming that the remote contract address settings on contract c on business chain A and contract b on business chain B are complete, the contract owner can call unPauseMove(B) in contract c on business chain A to unlock the address, and call unPauseMove(A) in contract b on business chain B to unlock the address, so that the business object on business chain A can continue to send full-chain assets to business chain B. It is understandable that this design is also applicable to other scenarios. For example, when a full-chain asset deployed on business chain A and already in use wants to be deployed on business chain B, the contract owner must first set the remote contract address corresponding to business chain A on business chain B, otherwise the full-chain asset cannot be transferred. At this point, the contract owner can first call pauseMove(B) in the business contract of business chain A and call pauseMove(A) in the business contract of business chain B through the remote contract address locking mechanism, and then set the contract address of the other contract as the remote contract address on the business contract of business chain A or the business contract of business chain B without having to worry about the impact of the remote address setting order.

[0123] It is understood that when the multi-blockchain includes a first blockchain, a second blockchain, and a third business chain, the contract update process on the second blockchain is similar to the above. In other words, when the contract is updated on the second blockchain, the interaction between the second blockchain and the first blockchain will also be performed between the second blockchain and the third business chain. This will not be detailed here.

[0124] In some embodiments, security verification can also be performed through the information management and verification service in the off-chain full-chain cross-chain service. For example, when it is determined that the remote contract address bound to the target full-chain business contract has been updated, the updated target remote contract address in the remote contract address bound to the target full-chain business contract is used as the updated remote contract address; the key information disclosure interface is called through the full-chain contract protocol in the target full-chain business contract to obtain the node port information associated with the updated remote contract address; the node port information associated with the updated remote contract address is securely verified through the information management and verification service in the off-chain full-chain cross-chain service. In other words, every time a change is detected in the remote contract address bound to the target full-chain business contract on a business chain, the relevant information of the changed remote contract address (such as the port address, contract address, etc. associated with the updated remote contract address) can be disclosed through the key information disclosure interface to facilitate security verification of the relevant information of the changed remote contract address. In this way, any business object and third party can detect whether the node port information comes from the tax chain official, or whether the contract address is set correctly, etc. Therefore, third parties can easily implement a checking mechanism for the contract correctness of the entire chain and multi-chain binding relationships to protect business objects from potential financial losses.

[0125] In other words, this application provides a cross-chain mechanism for full-chain assets (a cross-chain protocol for full-chain assets) that can help business parties quickly launch and deploy assets on multiple blockchains that can be managed and circulated simultaneously on multiple blockchains. The cross-chain mechanism for full-chain assets provides standardized interfaces for business operations such as the deployment of target full-chain business contracts, the determination and transfer of full-chain assets, and provides logical consistency, usage security, and continuity of full-chain assets across multiple chains for full-chain asset management. In addition, full-chain business transaction queries can be achieved through full-chain unique event identification, and the convenience of full-chain asset business services is improved through token airdrop support of the full-chain token airdrop contract. In addition, features such as the remote contract address locking mechanism and the node port information disclosure mechanism provide higher security for full-chain asset business services. At the same time, it can achieve cross-chain interoperability and composability of full-chain assets, unlock new design areas and possibilities for crypto networks, and reduce the cross-chain cost of full-chain assets. That is to say, in a business scenario composed of multiple chains, a full-chain asset cross-chain protocol that is adaptable to multiple chains is provided, allowing business contracts to be accessed in the form of a "full-chain contract", that is, the target full-chain business contract deployed on each business chain is integrated with the same full-chain contract protocol, providing standard contract protocols and cross-chain services to realize the full-chain distribution and circulation of full-chain assets.

[0126] In an embodiment of the present application, a remote contract address locking mechanism is proposed, which can lock the remote contract address when the contract is updated, preventing asset losses caused by full-chain asset circulation when the contract in use is updated, thereby ensuring the security of assets on the chain.

[0127] Further, please refer to Figure 8, which is a flowchart of a multi-blockchain data processing method provided in an embodiment of the present application. As shown in Figure 8, the method can be executed by the second blockchain node in the second blockchain network mentioned above. For example, the second blockchain node can be any blockchain node in the second blockchain network 300 shown in Figure 1 above. The method can specifically include the following steps S301-S302:

[0128] S301. Obtain a cross-chain asset reconstruction transaction. The cross-chain asset reconstruction transaction corresponds to a cross-chain asset transfer event. The cross-chain asset transfer event is sent by a first blockchain node in a first blockchain network through an off-chain cross-chain service device.

[0129] The cross-chain asset reconstruction transaction is the transaction in the cross-chain transaction request sent by the off-chain cross-chain service device. The cross-chain asset reconstruction transaction can be constructed based on the cross-chain asset transfer transaction indicated by the cross-chain asset transfer event. Furthermore, the constructed cross-chain asset reconstruction transaction corresponds to the cross-chain asset transfer event that indicates the cross-chain asset transfer transaction based on which the reconstruction was constructed. A cross-chain asset transfer event is an event that indicates a cross-chain asset transfer transaction; a cross-chain asset transfer transaction is a transaction that indicates a cross-chain asset transfer. A cross-chain asset transfer can be a digital asset transfer transaction between a first blockchain and a second blockchain, or a digital asset transfer involving both the first and second blockchains. A cross-chain asset transfer transaction can be generated by a first blockchain node based on the target remote contract address bound to the target full-chain business contract and the full-chain asset to be transferred. The target remote contract address is obtained by the first blockchain node through the full-chain contract protocol in the target full-chain business contract. The full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node obtains a full-chain asset transfer request sent by the first business object for a business transaction and determines, based on the full-chain asset transfer request, that the business transaction is a cross-chain asset transfer transaction. The target full-chain business contract is the full-chain business contract on the first blockchain that integrates the full-chain contract protocol. The remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol.

[0130] S302: Determine the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and call the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain.

[0131] Among them, the asset data information of the full-chain mapped assets is consistent with the asset data information of the target full-chain assets, and the asset content is consistent with the asset content of the target full-chain assets.

[0132] It can be understood that calling the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain can be: calling the target remote full-chain business contract, performing transaction verification on the cross-chain asset reconstruction transaction, and obtaining a transaction verification result; when the transaction verification result indicates that the transaction verification is successful, determining an asset on the second blockchain that has the same asset content and the same asset data information as the full-chain asset to be transferred, and using the determined asset as the full-chain mapping asset. At this point, the full-chain asset can be transferred from the first blockchain to the second blockchain, that is, the full-chain circulation of the full-chain asset can be completed.

[0133] The cross-chain transaction request carries the transaction signature information obtained by the off-chain cross-chain service device using the private key information to sign the cross-chain asset reconstruction transaction. The target remote full-chain business contract is called to perform transaction verification on the cross-chain asset reconstruction transaction. The transaction verification result can be: the cross-chain asset reconstruction transaction obtained from the cross-chain transaction request is used as the transaction to be compared; the target remote full-chain business contract is called to obtain the public key information corresponding to the private key information of the off-chain cross-chain service device, and the transaction signature information is verified based on the public key information. When the signature verification is successful, the cross-chain asset reconstruction transaction corresponding to the transaction signature information is used as the transaction to be matched; the transaction to be compared and the transaction to be matched are compared to obtain a transaction comparison result, which is used as the transaction verification result.

[0134] Among them, the cross-chain asset reconstruction transaction carries the full-chain token to be airdropped; the full-chain token to be airdropped is the first blockchain token obtained by the first blockchain node through the full-chain token airdrop contract on the first blockchain for the full-chain asset to be transferred. Therefore, when calling the target remote full-chain business contract to generate the full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, the second blockchain node can also call the full-chain token airdrop contract on the second blockchain through the target remote full-chain business contract to determine the second blockchain airdrop token corresponding to the full-chain token to be airdropped, and assign the second blockchain airdrop token to the business object corresponding to the full-chain mapping asset. The business object corresponding to the full-chain mapping asset can be the first business object or other objects; the second blockchain airdrop token is used to support the business object corresponding to the full-chain mapping asset to perform business operations on the full-chain mapping asset on the second blockchain, so as to realize the airdrop of the first blockchain token on the first blockchain to the second blockchain when performing cross-chain transfer of the full-chain asset, as the basic token of the full-chain mapping asset.

[0135] In some embodiments, when a contract update is required for a target remote full-chain business contract on the second blockchain, a remote contract address locking mechanism may be employed. Specifically, the method may include obtaining a contract update request sent by the second business object for the target remote full-chain business contract, performing contract update processing on the target remote full-chain business contract based on the contract update request, and setting the contract state of the target remote full-chain business contract to the contract update state. The second business object is a business object corresponding to the target remote full-chain business contract on the second blockchain, for example, it may be the contract owner of the target remote full-chain business contract. When it is detected that the target remote full-chain business contract is in the contract update state, the target contract address corresponding to the target full-chain business contract to be locked on the first blockchain is obtained. Through the remote contract address locking mechanism associated with the target remote full-chain business contract, a remote contract address locking method for remotely locking the target contract address is determined in the target remote full-chain business contract, the remote contract address locking method is called to remotely lock the target contract address, and the address state of the target contract address after the remote address is locked is configured as the address locked state in the target remote full-chain business contract. The target contract address in the address locked state is used to suspend receiving full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer. That is, at this time, the full-chain assets on the second blockchain cannot be transferred cross-chain to the first blockchain. Among them, the specific description and principle of the remote contract address locking mechanism can be found in the relevant description of the above embodiment.

[0136] It is understood that when the second blockchain node remotely locks the target contract address of the target full-chain business contract, it can generate a contract lock request for the target remote full-chain business contract deployed on the second blockchain, and send the contract lock request to the first blockchain node, so that the first blockchain node remotely locks the target remote contract address of the target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain. After the remote address is locked, the first blockchain node can generate contract lock completion information corresponding to the contract lock request and return the contract lock completion information to the second blockchain node, so that the second business object can determine that the target full-chain business contract in the first blockchain has executed the remote address lock.

[0137] At the same time, the second blockchain node can perform a contract update on the target remote full-chain business contract on the second blockchain. When the contract update is completed, the target remote full-chain business contract is adjusted from the contract update state to the contract update completion state. Therefore, when it is detected that the contract state of the target remote full-chain business contract is adjusted from the contract update state to the contract update completion state, the target remote full-chain business contract in the contract update completion state is used as the updated target remote full-chain business contract; the target contract address corresponding to the target full-chain business contract to be locked on the first blockchain is obtained; through the remote contract address locking mechanism associated with the updated target remote full-chain business contract, the remote contract address locking method for remotely locking the target contract address is determined in the updated target remote full-chain business contract, the remote contract address locking method is called to remotely lock the target contract address, and the address state of the target contract address after the remote address is locked is configured as the address locked state in the updated target remote full-chain business contract; the target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer. That is to say, for the updated target remote full-chain business contract, the target contract address of the target full-chain business contract must also be remotely locked.

[0138] It can be understood that when the second business object determines that the target remote full-chain business contract on the second blockchain has completed the contract update, and the target full-chain business contract on the first blockchain has performed remote address locking, and the updated target remote full-chain business contract on the second blockchain has performed remote address locking, remote address binding can be performed. For example, the second business object can achieve this by initiating a second contract binding request. Specifically, it can be to obtain the second contract binding request sent by the second business object for the updated target remote full-chain business contract, obtain the target contract address corresponding to the target full-chain business contract to be bound on the first blockchain from the second contract binding request; call the remote address setting interface through the full-chain contract protocol in the target remote full-chain business contract, and set the target contract address to the remote contract address bound to the updated target remote full-chain business contract. That is, the address binding of the target contract address is performed in the updated target remote full-chain business contract.

[0139] Among them, the second blockchain node may also generate a first contract binding request sent by the second business object to the updated target remote full-chain business contract deployed on the second blockchain, and send the first contract binding request to the first blockchain node, so that the first blockchain node performs remote address binding on the updated target remote contract address corresponding to the updated target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain. Optionally, the first blockchain node may generate contract binding completion information corresponding to the first contract binding request after the remote address binding, and return the contract binding completion information to the second blockchain node, so that the second business object determines that the target full-chain business contract in the first blockchain has executed remote address binding.

[0140] It is understood that after the second business object determines that the target full-chain business contract on the first blockchain is remotely bound to the address and the updated target remote full-chain business contract on the second blockchain is remotely bound to the address, the remote address unlocking can be performed. For example, the second business object can achieve this by initiating a second contract unlocking request. Specifically, the second business object can obtain the second contract unlocking request sent by the second business object for the updated target remote full-chain business contract, and obtain the target contract address corresponding to the target full-chain business contract to be unlocked on the first blockchain from the second contract unlocking request; through the remote contract address unlocking mechanism associated with the updated target remote full-chain business contract, determine the remote contract address unlocking method for remotely unlocking the target contract address in the updated target remote full-chain business contract, call the remote contract address unlocking method to remotely unlock the target contract address corresponding to the target full-chain business contract, and configure the address state of the target contract address after remote address unlocking to the address unlocked state in the updated target remote full-chain business contract; the target contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer. That is, the target contract address is unlocked in the updated target remote full-chain business contract. The specific description and principle of the remote contract address unlocking mechanism can be found in the relevant description of the above embodiment.

[0141] The second blockchain node may also generate a first contract unlock request sent by the second business object to the updated target remote full-chain business contract deployed on the second blockchain, and send the first contract unlock request to the first blockchain node, so that the first blockchain node performs remote address unlocking on the updated target remote contract address corresponding to the updated target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain. Optionally, after the remote address is unlocked, the first blockchain node may generate contract unlock completion information corresponding to the first contract unlock request, and return the contract unlock completion information to the second blockchain node, so that the second business object determines that the target full-chain business contract in the first blockchain has executed remote address unlocking.

[0142] For example, as shown in FIG9 , FIG9 is an interactive diagram of data processing based on multiple blockchains provided by an embodiment of the present application; wherein, S90, the first blockchain node obtains a full-chain asset transfer request sent by the first business object for a business transaction, and when the business transaction is determined to be a cross-chain asset transfer transaction based on the full-chain asset transfer request, the target full-chain business contract on the first blockchain is called, and the full-chain assets associated with the cross-chain asset transfer transaction are used as the full-chain assets to be transferred; S91, the first blockchain node calls the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract; S92, the first blockchain node calls the target full-chain business contract to switch the asset state of the full-chain assets to be transferred from the first state to the second state; S93, the first blockchain node obtains the first blockchain identifier of the first blockchain, and based on the first blockchain identifier, calls the full-chain event identifier generation protocol in the full-chain service contract to generate an event identifier associated with the first blockchain identifier; S94, the first blockchain node calls the full-chain token airdrop contract on the first blockchain through the target full-chain business contract to obtain the first blockchain token associated with the full-chain assets to be transferred, The obtained first blockchain token is used as the full-chain token to be airdropped; S95, the first blockchain node generates a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction based on the event identifier, the target remote contract address, the full-chain assets to be transferred and the full-chain token to be airdropped; S96, the off-chain cross-chain service device reads the cross-chain asset transfer event from the first blockchain node; S97, the off-chain cross-chain service device verifies the cross-chain asset transfer event, and generates a cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event when the event verification passes; S98, the off-chain cross-chain service device reconstructs the cross-chain asset The transaction is sent to the second blockchain node; S99, the second blockchain node reconstructs the transaction based on the cross-chain assets, determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; S910, the second blockchain node calls the full-chain token airdrop contract on the second blockchain through the target remote full-chain business contract, determines the second blockchain airdrop token corresponding to the full-chain token to be airdropped, and allocates the second blockchain airdrop token to the business object corresponding to the full-chain mapping asset.

[0143] For another example, as shown in Figure 10, Figure 10 is an interactive diagram of a contract update provided by an embodiment of the present application; wherein, S1001, the second blockchain node obtains a contract update request, performs contract update processing on the target remote full-chain business contract based on the contract update request, and when it is detected that the target remote full-chain business contract is in the contract update state, obtains the target contract address to be locked, and calls the remote contract address locking method to remotely lock the target contract address; S1002, the second blockchain node generates a contract lock request; S1003, the second blockchain node sends the contract lock request to the first blockchain node; S1004, the first blockchain node obtains the contract lock request, obtains the target remote contract address to be locked from the contract lock request, and calls the remote contract address locking method to remotely lock the target remote contract address; S1005, the first blockchain node generates contract lock completion information; S1006, the first blockchain node sends the contract lock completion information to the second blockchain node; S1007, the second blockchain node adjusts the contract state of the target remote full-chain business contract from the contract update state to the contract update completion state when it is detected that the contract state of the target remote full-chain business contract is adjusted from the contract update state to the contract update completion state. When the state is completed, the target remote full-chain business contract in the contract update completion state is used as the updated target remote full-chain business contract, the target contract address to be locked on the first blockchain is obtained, and the remote contract address locking method is called to remotely lock the target contract address; S1008, the second blockchain node obtains the second contract binding request, obtains the target contract address corresponding to the target full-chain business contract to be bound from the second contract binding request, calls the remote address setting interface, and sets the target contract address to the remote contract address bound to the updated target remote full-chain business contract; S1009, the second blockchain node generates the first contract binding request; S1010, the second blockchain node sends the first contract binding request to the first blockchain node; S1011, the first blockchain node obtains the first contract binding request, obtains the updated target remote contract address to be bound from the first contract binding request, and sets the updated target remote contract address to the remote contract address bound to the target full-chain business contract by calling the remote address setting interface; S1012, the first blockchain node generates contract binding completion information; S1013, The first blockchain node sends the contract binding completion information to the second blockchain node; S1014, the second blockchain node obtains the second contract unlock request, obtains the target contract address to be unlocked from the second contract unlock request, and calls the remote contract address unlock method to remotely unlock the target contract address corresponding to the target full-chain business contract; S1015, the second blockchain node generates the first contract unlock request; S1016, the second blockchain node sends the first contract unlock request to the first blockchain node;S1017. The first blockchain node obtains the first contract unlock request, obtains the updated target remote contract address to be unlocked from the first contract unlock request, and calls the remote contract address unlock method to remotely unlock the updated target remote contract address corresponding to the updated target remote full-chain business contract; S1018. The first blockchain node generates contract unlock completion information; S1019. The first blockchain node sends the contract unlock completion information to the second blockchain node.

[0144] In an embodiment of the present application, the multiple blockchains may include a first blockchain and a second blockchain, and the cross-chain asset transfer transaction corresponding to the full-chain asset transfer request is used to indicate that the full-chain assets to be transferred (such as digital assets, specifically digital collections) are transferred from the first blockchain to the second blockchain; this solution can realize the cross-chain transfer of the full-chain assets to be transferred by deploying full-chain business contracts integrated with the same full-chain contract protocol on the first blockchain and the second blockchain; it can be understood that a target full-chain business contract for executing the cross-chain asset transfer transaction is deployed on the first blockchain, and the full-chain business contract corresponding to the target full-chain business contract on the second blockchain is a target remote full-chain business contract, and the target full-chain business contract and the target remote full-chain business contract are integrated with the same full-chain contract protocol, that is, the target full-chain business contract and the target remote full-chain business contract are integrated with the same asset transfer method (such as asset transfer-related method, asset determination-related method), that is, the asset determination rule on the first blockchain is the same as that on the second blockchain. The asset determination rules on the two blockchains are the same. Therefore, the first blockchain node can call the full-chain contract agreement in the target full-chain business contract to generate a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction to realize the cross-chain transfer of the full-chain assets to be transferred. The second blockchain node can call the full-chain contract agreement in the target remote full-chain business contract based on the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to perform asset determination of the full-chain assets to be transferred. Since the first blockchain node and the second blockchain node use the asset transfer method uniformly specified in the same full-chain contract agreement to realize the transfer and determination of digital assets, the asset data information of the full-chain mapped assets determined by the second blockchain node can be consistent with the asset data information of the full-chain assets to be transferred. At this time, the full-chain assets to be transferred in the first blockchain and the mapped assets on the second blockchain can be regarded as the same asset, so that the full-chain liquidity of the same digital asset between different blockchains can be safely realized, thereby improving the liquidity of digital assets in multiple blockchains.

[0145] Further, please refer to Figure 11, which is a structural diagram of a data processing device based on multiple blockchains provided in an embodiment of the present application. As shown in Figure 11, the data processing device 1 based on multiple blockchains can be applied to a computer device. It should be understood that the data processing device 1 based on multiple blockchains can be a computer-readable instruction running in a computer device, for example, the data processing device 1 based on multiple blockchains can be an application software; it can be understood that the data processing device 1 based on multiple blockchains can be used to execute the corresponding steps in the method provided in an embodiment of the present application. As shown in Figure 11, the data processing device 1 based on multiple blockchains may include: a full-chain asset acquisition module 11, a contract address determination module 12, and a transfer event generation module 13;

[0146] The full-chain asset acquisition module 11 is configured to acquire a full-chain asset transfer request sent by the first business object for a business transaction. When the business transaction is determined to be a cross-chain asset transfer transaction based on the full-chain asset transfer request, the module calls the target full-chain business contract on the first blockchain and uses the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred. The cross-chain asset transfer transaction is used to instruct the transfer of the full-chain asset to be transferred from the first blockchain to the second blockchain.

[0147] The contract address determination module 12 is used to call the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract; the full-chain contract protocol is determined based on the full-chain contract protocol interface provided by the full-chain business parent contract on the first blockchain; the target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol;

[0148] The transfer event generation module 13 is used to, when generating a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction based on the target remote contract address and the full-chain asset to be transferred, send the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to the second blockchain node in the second blockchain network through the off-chain cross-chain service device, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred.

[0149] Among them, the cross-chain asset transfer transaction carries the second blockchain identifier of the second blockchain;

[0150] The contract address determination module 12 includes:

[0151] The contract address acquisition unit 121 is used to call the full-chain contract protocol in the target full-chain business contract to obtain the remote contract address bound to the target full-chain business contract; the remote contract address bound to the target full-chain business contract includes the contract address corresponding to the full-chain business contract integrated with the full-chain contract protocol on the reference business chain; the reference business chain is a blockchain other than the first blockchain in the multiple blockchains; the reference business chain includes the second blockchain;

[0152] The contract address determination unit 122 is used to determine the remote contract address associated with the second blockchain identifier as the target remote contract address among the remote contract addresses bound to the target full-chain business contract.

[0153] The transfer event generation module 13 includes:

[0154] The state switching unit 131 is used to call the target full-chain business contract to switch the asset state of the full-chain asset to be transferred from the first state to the second state; the second state is the asset locked state;

[0155] The transfer event generating unit 132 is configured to generate a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction based on the target remote contract address and the full-chain asset to be transferred when the asset state of the full-chain asset to be transferred is the second state.

[0156] The transfer event generation module 13 includes:

[0157] The blockchain identifier acquisition unit 133 is configured to acquire a first blockchain identifier of the first blockchain; the first blockchain identifier is a blockchain identifier configured for the first blockchain through the full-chain unified registration service in the off-chain full-chain cross-chain service;

[0158] The blockchain identifier generation unit 134 is configured to call the full-chain event identifier generation protocol in the full-chain service contract based on the first blockchain identifier to generate an event identifier associated with the first blockchain identifier;

[0159] The transfer event generation unit 132 is further configured to generate a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction based on the event identifier, the target remote contract address, and the full-chain assets to be transferred.

[0160] Among them, the cross-chain asset transfer event carries the asset identification of the full-chain asset to be transferred, and the asset identification of the full-chain asset to be transferred is generated based on the identification prefix associated with the first blockchain and the asset identification template configured in the full-chain contract agreement; the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is constructed by the off-chain cross-chain service device based on the identification prefix and the asset identification template to verify the asset identification of the full-chain asset to be transferred carried by the cross-chain asset transfer event, and the identification verification is successful.

[0161] The transfer event generating module 13 further includes:

[0162] The full-chain token acquisition unit 135 is configured to call the full-chain token airdrop contract on the first blockchain through the target full-chain business contract, obtain the first blockchain token associated with the full-chain asset to be transferred, and use the obtained first blockchain token as the full-chain token to be airdropped;

[0163] The full-chain token writing unit 136 is used to write the full-chain token to be airdropped into the cross-chain asset transfer event when generating a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction.

[0164] The full-chain assets to be transferred belong to part or all of the full-chain assets determined on the first blockchain for cross-chain transfer;

[0165] The full-chain asset acquisition module 11 also includes:

[0166] A determination request acquisition unit 111 is configured to acquire a full-chain asset determination request for a full-chain asset determination transaction, invoke a target full-chain business contract on the first blockchain based on the full-chain asset determination request, and determine the number of determined assets involved in the full-chain asset determination transaction as the number of assets to be determined;

[0167] The asset identifier generation unit 112 is configured to call the full-chain contract protocol in the target full-chain business contract, obtain the identifier prefix associated with the first blockchain, and generate a to-be-determined full-chain asset identifier corresponding to the to-be-determined asset quantity based on the identifier prefix associated with the first blockchain and the asset identifier template configured in the full-chain contract protocol; the to-be-determined full-chain asset identifier includes the identifier prefix associated with the first blockchain;

[0168] The full-chain asset determination unit 113 is used to call the asset determination contract in the target full-chain business contract, determine the full-chain asset corresponding to the full-chain asset identifier to be determined on the first blockchain, and use the determined full-chain asset as the full-chain asset determined on the first blockchain for cross-chain transfer.

[0169] Among them, the contract address determination module 12 also includes:

[0170] The lock request acquisition unit 123 is configured to acquire a contract lock request sent by the second business object for a target remote full-chain business contract deployed on the second blockchain; the second business object is a business object on the second blockchain corresponding to the target remote full-chain business contract; the contract lock request is generated by the second business object after remotely locking the contract address corresponding to the target remote full-chain business contract in the target remote full-chain business contract deployed on the second blockchain;

[0171] The address acquisition unit 124 is used to obtain the target remote contract address corresponding to the target remote full-chain business contract to be locked on the second blockchain from the contract locking request;

[0172] The remote address locking unit 125 is used to determine the remote contract address locking method for remotely locking the target remote contract address in the target full-chain business contract through the remote contract address locking mechanism associated with the target full-chain business contract, call the remote contract address locking method to remotely lock the target remote contract address corresponding to the target remote full-chain business contract, and configure the address state of the target remote contract address after the remote address is locked to the address locked state in the target full-chain business contract; the target remote contract address in the address locked state is used to suspend receiving the full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer.

[0173] Wherein, when the contract status of the target remote full-chain business contract is adjusted from the contract update status to the contract update completion status, the target remote full-chain business contract in the contract update completion status is the updated target remote full-chain business contract; the contract address of the updated target remote full-chain business contract is the updated target remote contract address;

[0174] The contract address determination module 12 also includes:

[0175] The binding request acquisition unit 126 is configured to acquire a first contract binding request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain; the first contract binding request is generated by the second business object after performing remote address binding on the target contract address in the updated target remote full-chain business contract deployed on the second blockchain;

[0176] The address acquisition unit 124 is further configured to acquire, from the first contract binding request, an updated target remote contract address corresponding to the updated target remote full-chain business contract to be bound on the second blockchain;

[0177] The remote address binding unit 127 is used to call the remote address setting interface through the full-chain contract protocol in the target full-chain business contract, and set the updated target remote contract address in the remote contract address bound to the target full-chain business contract.

[0178] Among them, the contract address determination module 12 also includes:

[0179] The unlock request acquisition unit 128 is configured to acquire a first contract unlock request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain; the first contract unlock request is generated by the second business object after remotely unlocking the target contract address in the updated target remote full-chain business contract deployed on the second blockchain;

[0180] The address acquisition unit 124 is further configured to acquire, from the first contract unlocking request, an updated target remote contract address corresponding to the updated target remote full-chain business contract to be unlocked on the second blockchain;

[0181] The remote address unlocking unit 129 is used to determine the remote contract address unlocking method for remotely unlocking the updated target remote contract address in the target full-chain business contract through the remote contract address unlocking mechanism associated with the target full-chain business contract, call the remote contract address unlocking method to remotely unlock the updated target remote contract address corresponding to the updated target remote full-chain business contract, and configure the address state of the updated target remote contract address after the remote address is unlocked to the address unlocked state in the target full-chain business contract; the updated target remote contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer.

[0182] Among them, the contract address determination module 12 also includes:

[0183] The information verification unit 1210 is configured to, when determining that the remote contract address bound to the target full-chain business contract is updated, use the updated target remote contract address in the remote contract address bound to the target full-chain business contract as the updated remote contract address;

[0184] The information verification unit 1210 is further used to call the key information disclosure interface through the full-chain contract protocol in the target full-chain business contract to obtain the node port information associated with the updated remote contract address;

[0185] The information verification unit 1210 is also used to perform security verification on the node port information associated with the updated remote contract address through the information management and verification service in the off-chain full-chain cross-chain service.

[0186] The transfer event generating module 13 is specifically configured to:

[0187] The cross-chain asset transfer event associated with the target full-chain business contract generated within the target period is read through the off-chain cross-chain service device; the off-chain cross-chain service device is used to verify the cross-chain asset transfer event through the cross-chain event verification and forwarding service in the off-chain full-chain cross-chain service when reading the cross-chain asset transfer event associated with the target full-chain business contract, and forward the cross-chain asset transfer event after the event verification with the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event.

[0188] The specific implementation of the full-chain asset acquisition module 11, the contract address determination module 12, and the transfer event generation module 13 can be found in the relevant descriptions of the above embodiments and will not be further elaborated here. It should be understood that the description of the beneficial effects obtained by adopting the same method will not be repeated here.

[0189] Further, please refer to Figure 12, which is a structural diagram of a multi-blockchain-based data processing device provided in an embodiment of the present application. As shown in Figure 12, the multi-blockchain-based data processing device 2 can be applied to a computer device. It should be understood that the multi-blockchain-based data processing device 2 can be a computer-readable instruction running in a computer device, for example, the multi-blockchain-based data processing device 2 can be an application software; it can be understood that the multi-blockchain-based data processing device 2 can be used to execute the corresponding steps in the method provided in an embodiment of the present application. As shown in Figure 12, the multi-blockchain-based data processing device 2 may include: a reconstructed transaction acquisition module 21, a mapped asset generation module 22;

[0190] The reconstruction transaction acquisition module 21 is used to obtain a cross-chain asset reconstruction transaction, which corresponds to a cross-chain asset transfer event. The cross-chain asset transfer event is sent by the first blockchain node in the first blockchain network through the off-chain cross-chain service device; the cross-chain asset transfer event is an event corresponding to a cross-chain asset transfer transaction generated by the first blockchain node based on the target remote contract address bound to the target full-chain business contract and the full-chain asset to be transferred; the target remote contract address is obtained by the first blockchain node through the full-chain contract agreement in the target full-chain business contract; the full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node obtains the full-chain asset transfer request sent by the first business object for the business transaction and determines that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request; the target full-chain business contract is a full-chain business contract integrated with the full-chain contract agreement on the first blockchain; the remote full-chain business contract corresponding to the target remote contract address is a full-chain business contract integrated with the full-chain contract agreement on the second blockchain;

[0191] The mapping asset generation module 22 is used to determine the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and call the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; the asset data information of the full-chain mapping asset is consistent with the asset data information of the target full-chain asset.

[0192] The cross-chain asset reconstruction transaction carries the full-chain token to be airdropped; the full-chain token to be airdropped is the first blockchain token obtained by the first blockchain node through the full-chain token airdrop contract on the first blockchain for the full-chain assets to be transferred;

[0193] The mapping asset generation module 22 is further configured to:

[0194] The full-chain token airdrop contract on the second blockchain is called through the target remote full-chain business contract to determine the second blockchain airdrop token corresponding to the full-chain token to be airdropped, and the second blockchain airdrop token is allocated to the business object corresponding to the full-chain mapped asset; the second blockchain airdrop token is used to support the business object corresponding to the full-chain mapped asset to perform business operations on the full-chain mapped asset on the second blockchain.

[0195] The reconstructed transaction acquisition module 21 further includes:

[0196] The contract update unit 211 is configured to obtain a contract update request sent by the second business object for the target remote full-chain business contract, perform contract update processing on the target remote full-chain business contract based on the contract update request, and set the contract state of the target remote full-chain business contract to the contract update state; the second business object is the business object corresponding to the target remote full-chain business contract on the second blockchain;

[0197] The contract address acquisition unit 212 is configured to acquire the target contract address corresponding to the target full-chain business contract to be locked on the first blockchain when detecting that the target remote full-chain business contract is in the contract update state;

[0198] The address locking unit 213 is used to determine the remote contract address locking method for remotely locking the target contract address in the target remote full-chain business contract through the remote contract address locking mechanism associated with the target remote full-chain business contract, call the remote contract address locking method to remotely lock the target contract address, and configure the address state of the target contract address after the remote address is locked to the address locked state in the target remote full-chain business contract; the target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

[0199] The reconstructed transaction acquisition module 21 further includes:

[0200] The locking request sending unit 214 is used to generate a contract locking request for the target remote full-chain business contract deployed on the second blockchain, and send the contract locking request to the first blockchain node, so that the first blockchain node remotely locks the target remote contract address of the target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

[0201] The reconstructed transaction acquisition module 21 further includes:

[0202] The contract updating unit 211 is further configured to, when detecting that the contract status of the target remote full-chain business contract is adjusted from the contract updating status to the contract updating completed status, use the target remote full-chain business contract in the contract updating completed status as the updated target remote full-chain business contract;

[0203] The contract address acquisition unit 212 is further configured to acquire a target contract address corresponding to the target full-chain business contract to be locked on the first blockchain;

[0204] The address locking unit 213 is also used to determine the remote contract address locking method for remotely locking the target contract address in the updated target remote full-chain business contract through the remote contract address locking mechanism associated with the updated target remote full-chain business contract, call the remote contract address locking method to remotely lock the target contract address, and configure the address state of the target contract address after the remote address is locked to the address locked state in the updated target remote full-chain business contract; the target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

[0205] The reconstructed transaction acquisition module 21 further includes:

[0206] The binding request obtaining unit 214 is configured to obtain a second contract binding request sent by the second business object for the updated target remote full-chain business contract, and obtain a target contract address corresponding to the target full-chain business contract to be bound on the first blockchain from the second contract binding request;

[0207] The contract address binding unit 215 is used to call the remote address setting interface through the full-chain contract protocol in the target remote full-chain business contract, and set the target contract address to the remote contract address bound to the updated target remote full-chain business contract.

[0208] The reconstructed transaction acquisition module 21 further includes:

[0209] The binding request sending unit 216 is used to generate a first contract binding request sent by the second business object to the updated target remote full-chain business contract deployed on the second blockchain, and send the first contract binding request to the first blockchain node, so that the first blockchain node performs remote address binding on the updated target remote contract address corresponding to the updated target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

[0210] The reconstructed transaction acquisition module 21 further includes:

[0211] The unlocking address obtaining unit 217 is configured to obtain a second contract unlocking request sent by the second business object for the updated target remote full-chain business contract, and obtain the target contract address corresponding to the target full-chain business contract to be unlocked on the first blockchain from the second contract unlocking request;

[0212] The contract address unlocking unit 218 is used to determine the remote contract address unlocking method for remotely unlocking the target contract address in the updated target remote full-chain business contract through the remote contract address unlocking mechanism associated with the updated target remote full-chain business contract, call the remote contract address unlocking method to remotely unlock the target contract address corresponding to the target full-chain business contract, and configure the address status of the target contract address after the remote address is unlocked to the address unlocked state in the updated target remote full-chain business contract; the target contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

[0213] The reconstructed transaction acquisition module 21 further includes:

[0214] The unlock request sending unit 219 is used to generate a first contract unlock request sent by the second business object to the updated target remote full-chain business contract deployed on the second blockchain, and send the first contract unlock request to the first blockchain node, so that the first blockchain node can remotely unlock the updated target remote contract address corresponding to the updated target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

[0215] The specific implementation of the reconstructed transaction acquisition module 21 and the mapped asset generation module 22 can be found in the relevant descriptions of the above embodiments and will not be further elaborated here. It should be understood that the description of the beneficial effects obtained by adopting the same method will not be repeated.

[0216] Further, please refer to Figure 13, which is a structural diagram of a computer device provided in an embodiment of the present application. As shown in Figure 13, the computer device 1300 can be an object terminal or a server, and will not be limited here. For ease of understanding, this application takes the computer device as an object terminal as an example. The computer device 1300 may include: a processor 1301, a network interface 1304 and a memory 1305. In addition, the computer device 1300 may also include: an object interface 1303, and at least one communication bus 1302. Among them, the communication bus 1302 is used to realize the connection and communication between these components. Among them, the object interface 1303 may also include a standard wired interface and a wireless interface. The network interface 1304 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1305 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk storage. The memory 1305 may also be at least one storage device located away from the aforementioned processor 1301. As shown in FIG. 13 , the memory 1305 , which is a computer-readable storage medium, may include an operating system, a network communication module, an object interface module, and a device control application program.

[0217] The network interface 1304 in the computer device 1300 can also provide network data interaction functions. In the computer device 1300 shown in Figure 13, the network interface 1304 can provide network data interaction functions; the object interface 1303 is mainly used to provide an input interface for business objects; and the processor 1301 can be used to call the device control application stored in the memory 1305 to execute the description of the multi-blockchain-based data processing method in the embodiment corresponding to Figure 3 or Figure 4 above. It can also execute the description of the multi-blockchain-based data processing device 1 in the embodiment corresponding to Figure 13 above, which will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated here.

[0218] In one possible implementation, the memory 1305 is used to store program instructions. The processor 1301 may call the program instructions to perform the following steps:

[0219] Obtaining a full-chain asset transfer request sent by the first business object for a business transaction. When determining that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request, calling the target full-chain business contract on the first blockchain and using the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred; the cross-chain asset transfer transaction is used to instruct the transfer of the full-chain asset to be transferred from the first blockchain to the second blockchain.

[0220] Call the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract; the full-chain contract protocol is determined based on the full-chain contract protocol interface provided by the full-chain business parent contract on the first blockchain; the target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol;

[0221] When a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred, the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is sent to the second blockchain node in the second blockchain network through the off-chain cross-chain service device, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred.

[0222] Among them, the cross-chain asset transfer transaction carries the second blockchain identifier of the second blockchain;

[0223] When the processor 1301 is used to call the full-chain contract protocol in the target full-chain business contract and determine the target remote contract address bound to the target full-chain business contract, it is specifically used to:

[0224] Call the full-chain contract protocol in the target full-chain business contract to obtain the remote contract address bound to the target full-chain business contract; the remote contract address bound to the target full-chain business contract includes the contract address corresponding to the full-chain business contract integrated with the full-chain contract protocol on the reference business chain; the reference business chain is a blockchain other than the first blockchain in the multiple blockchains; the reference business chain includes the second blockchain;

[0225] Among the remote contract addresses bound to the target full-chain business contract, the remote contract address associated with the second blockchain identifier is determined as the target remote contract address.

[0226] The processor 1301, when used to generate a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction based on the target remote contract address and the full-chain assets to be transferred, is specifically used to:

[0227] Call the target full-chain business contract to switch the asset status of the full-chain assets to be transferred from the first state to the second state; the second state is the asset locked state;

[0228] When the asset status of the full-chain asset to be transferred is the second state, a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred.

[0229] The processor 1301, when used to generate a cross-chain asset transfer event corresponding to a cross-chain asset transfer transaction based on the target remote contract address and the full-chain assets to be transferred, is specifically used to:

[0230] Obtaining a first blockchain identifier for the first blockchain; the first blockchain identifier is a blockchain identifier configured for the first blockchain through the full-chain unified registration service in the off-chain full-chain cross-chain service;

[0231] Based on the first blockchain identifier, calling the full-chain event identifier generation protocol in the full-chain service contract to generate an event identifier associated with the first blockchain identifier;

[0232] Based on the event identifier, the target remote contract address, and the full-chain assets to be transferred, a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated.

[0233] Among them, the cross-chain asset transfer event carries the asset identification of the full-chain asset to be transferred, and the asset identification of the full-chain asset to be transferred is generated based on the identification prefix associated with the first blockchain and the asset identification template configured in the full-chain contract agreement; the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is constructed by the off-chain cross-chain service device based on the identification prefix and the asset identification template to verify the asset identification of the full-chain asset to be transferred carried by the cross-chain asset transfer event, and the identification verification is successful.

[0234] Before generating a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction, the processor 1301 is further configured to:

[0235] Call the full-chain token airdrop contract on the first blockchain through the target full-chain business contract to obtain the first blockchain token associated with the full-chain asset to be transferred, and use the obtained first blockchain token as the full-chain token to be airdropped;

[0236] When generating a cross-chain token transfer event corresponding to a cross-chain token transfer transaction, the full-chain token to be airdropped will be written into the cross-chain token transfer event.

[0237] The full-chain assets to be transferred belong to part or all of the full-chain assets determined on the first blockchain for cross-chain transfer;

[0238] The processor 1301 is further configured to:

[0239] Obtain a full-chain asset determination request for a full-chain asset determination transaction, invoke a target full-chain business contract on the first blockchain based on the full-chain asset determination request, and determine the number of determined assets involved in the full-chain asset determination transaction as the number of assets to be determined;

[0240] Invoke the full-chain contract protocol in the target full-chain business contract, obtain the identification prefix associated with the first blockchain, and generate a to-be-determined full-chain asset identifier corresponding to the to-be-determined asset quantity based on the identification prefix associated with the first blockchain and the asset identifier template configured in the full-chain contract protocol; the to-be-determined full-chain asset identifier includes the identification prefix associated with the first blockchain;

[0241] The asset determination contract in the target full-chain business contract is called to determine the full-chain asset corresponding to the full-chain asset identifier to be determined on the first blockchain, and the determined full-chain asset is used as the full-chain asset determined on the first blockchain for cross-chain transfer.

[0242] When the contract state of the target remote full-chain business contract is in the contract update state, the processor 1301 is further configured to:

[0243] Obtaining a contract lock request sent by a second business object for a target remote full-chain business contract deployed on the second blockchain; the second business object is a business object on the second blockchain corresponding to the target remote full-chain business contract; the contract lock request is generated by the second business object after remotely locking the contract address corresponding to the target remote full-chain business contract in the target remote full-chain business contract deployed on the second blockchain;

[0244] Obtain the target remote contract address corresponding to the target remote full-chain business contract to be locked on the second blockchain from the contract locking request;

[0245] Through the remote contract address locking mechanism associated with the target full-chain business contract, the remote contract address locking method for remotely locking the target remote contract address is determined in the target full-chain business contract, and the remote contract address locking method is called to remotely lock the target remote contract address corresponding to the target remote full-chain business contract, and the address state of the target remote contract address after the remote address is locked is configured as an address locked state in the target full-chain business contract; the target remote contract address in the address locked state is used to suspend receiving the full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer.

[0246] Wherein, when the contract status of the target remote full-chain business contract is adjusted from the contract update status to the contract update completion status, the target remote full-chain business contract in the contract update completion status is the updated target remote full-chain business contract; the contract address of the updated target remote full-chain business contract is the updated target remote contract address;

[0247] The processor 1301 is further configured to:

[0248] Obtaining a first contract binding request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain; the first contract binding request is generated by the second business object after performing remote address binding on the target contract address in the updated target remote full-chain business contract deployed on the second blockchain;

[0249] Obtaining the updated target remote contract address corresponding to the updated target remote full-chain business contract to be bound on the second blockchain from the first contract binding request;

[0250] Call the remote address setting interface through the full-chain contract protocol in the target full-chain business contract, and set the updated target remote contract address to the remote contract address bound to the target full-chain business contract.

[0251] The processor 1301 is further configured to:

[0252] Obtaining a first contract unlock request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain; the first contract unlock request is generated by the second business object after remotely unlocking the target contract address in the updated target remote full-chain business contract deployed on the second blockchain;

[0253] Obtaining the updated target remote contract address corresponding to the updated target remote full-chain business contract to be unlocked on the second blockchain from the first contract unlock request;

[0254] Through the remote contract address unlocking mechanism associated with the target full-chain business contract, the remote contract address unlocking method for remotely unlocking the updated target remote contract address is determined in the target full-chain business contract, and the remote contract address unlocking method is called to remotely unlock the updated target remote contract address corresponding to the updated target remote full-chain business contract, and the address status of the updated target remote contract address after the remote address is unlocked is configured as an address unlocked state in the target full-chain business contract; the updated target remote contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer.

[0255] The processor 1301 is further configured to:

[0256] When it is determined that the remote contract address bound to the target full-chain business contract has been updated, the updated target remote contract address in the remote contract address bound to the target full-chain business contract will be used as the updated remote contract address;

[0257] Call the key information disclosure interface through the full-chain contract protocol in the target full-chain business contract to obtain the node port information associated with the updated remote contract address;

[0258] The node port information associated with the updated remote contract address is securely verified through the information management and verification service in the off-chain full-chain cross-chain service.

[0259] The processor 1301 is further configured to:

[0260] The cross-chain asset transfer event associated with the target full-chain business contract generated within the target period is read through the off-chain cross-chain service device; the off-chain cross-chain service device is used to verify the cross-chain asset transfer event through the cross-chain event verification and forwarding service in the off-chain full-chain cross-chain service when reading the cross-chain asset transfer event associated with the target full-chain business contract, and forward the cross-chain asset transfer event after the event verification with the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event.

[0261] In one possible implementation, the memory 1305 is used to store program instructions. The processor 1301 may call the program instructions to perform the following steps:

[0262] Obtain a cross-chain asset reconstruction transaction, the cross-chain asset reconstruction transaction corresponds to a cross-chain asset transfer event, the cross-chain asset transfer event is sent by the first blockchain node in the first blockchain network through the off-chain cross-chain service device; the cross-chain asset transfer event is an event corresponding to the cross-chain asset transfer transaction generated by the first blockchain node based on the target remote contract address bound to the target full-chain business contract and the full-chain asset to be transferred; the target remote contract address is obtained by the first blockchain node through the full-chain contract agreement in the target full-chain business contract; the full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node obtains the full-chain asset transfer request sent by the first business object for the business transaction and determines that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request; the target full-chain business contract is a full-chain business contract on the first blockchain that is integrated with the full-chain contract agreement; the remote full-chain business contract corresponding to the target remote contract address is a full-chain business contract on the second blockchain that is integrated with the full-chain contract agreement;

[0263] Based on the cross-chain asset reconstruction transaction, the target remote full-chain business contract corresponding to the target remote contract address is determined on the second blockchain, and the target remote full-chain business contract is called to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain; the asset data information of the full-chain mapping asset is consistent with the asset data information of the target full-chain asset.

[0264] The cross-chain asset reconstruction transaction carries the full-chain token to be airdropped; the full-chain token to be airdropped is the first blockchain token obtained by the first blockchain node through the full-chain token airdrop contract on the first blockchain for the full-chain assets to be transferred;

[0265] When calling the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, the processor 1301 is further configured to:

[0266] The full-chain token airdrop contract on the second blockchain is called through the target remote full-chain business contract to determine the second blockchain airdrop token corresponding to the full-chain token to be airdropped, and the second blockchain airdrop token is allocated to the business object corresponding to the full-chain mapped asset; the second blockchain airdrop token is used to support the business object corresponding to the full-chain mapped asset to perform business operations on the full-chain mapped asset on the second blockchain.

[0267] The processor 1301 is further configured to:

[0268] Obtain a contract update request sent by the second business object for the target remote full-chain business contract, perform contract update processing on the target remote full-chain business contract based on the contract update request, and set the contract status of the target remote full-chain business contract to the contract update status; the second business object is the business object corresponding to the target remote full-chain business contract on the second blockchain;

[0269] When it is detected that the target remote full-chain business contract is in the contract update state, obtain the target contract address corresponding to the target full-chain business contract to be locked on the first blockchain;

[0270] Through the remote contract address locking mechanism associated with the target remote full-chain business contract, the remote contract address locking method for remotely locking the target contract address is determined in the target remote full-chain business contract, the remote contract address locking method is called to remotely lock the target contract address, and the address state of the target contract address after the remote address is locked is configured as the address locked state in the target remote full-chain business contract; the target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

[0271] The processor 1301 is further configured to:

[0272] Generate a contract lock request for the target remote full-chain business contract deployed on the second blockchain, and send the contract lock request to the first blockchain node, so that the first blockchain node remotely locks the target remote contract address of the target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

[0273] The processor 1301 is further configured to:

[0274] When it is detected that the contract status of the target remote full-chain business contract is adjusted from the contract update status to the contract update completion status, the target remote full-chain business contract in the contract update completion status is used as the updated target remote full-chain business contract;

[0275] Obtain the target contract address corresponding to the target full-chain business contract to be locked on the first blockchain;

[0276] Through the remote contract address locking mechanism associated with the updated target remote full-chain business contract, the remote contract address locking method for remotely locking the target contract address is determined in the updated target remote full-chain business contract, the remote contract address locking method is called to remotely lock the target contract address, and the address state of the target contract address after the remote address is locked is configured as the address locked state in the updated target remote full-chain business contract; the target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

[0277] Among them, the contract address corresponding to the updated target remote full-chain business contract is the updated target remote contract address;

[0278] The processor 1301 is further configured to:

[0279] Obtain a second contract binding request sent by the second business object for the updated target remote full-chain business contract, and obtain the target contract address corresponding to the target full-chain business contract to be bound on the first blockchain from the second contract binding request;

[0280] The remote address setting interface is called through the full-chain contract protocol in the target remote full-chain business contract, and the target contract address is set to the remote contract address bound to the updated target remote full-chain business contract.

[0281] The processor 1301 is further configured to:

[0282] Generate a first contract binding request sent by the second business object to the updated target remote full-chain business contract deployed on the second blockchain, and send the first contract binding request to the first blockchain node, so that the first blockchain node performs remote address binding on the updated target remote contract address corresponding to the updated target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

[0283] The processor 1301 is further configured to:

[0284] Obtain a second contract unlock request sent by the second business object for the updated target remote full-chain business contract, and obtain the target contract address corresponding to the target full-chain business contract to be unlocked on the first blockchain from the second contract unlock request;

[0285] Through the remote contract address unlocking mechanism associated with the updated target remote full-chain business contract, the remote contract address unlocking method for remotely unlocking the target contract address is determined in the updated target remote full-chain business contract, and the remote contract address unlocking method is called to remotely unlock the target contract address corresponding to the target full-chain business contract, and the address status of the target contract address after the remote address is unlocked is configured as an address unlocked state in the updated target remote full-chain business contract; the target contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

[0286] The processor 1301 is further configured to:

[0287] Generate a first contract unlock request sent by the second business object to the updated target remote full-chain business contract deployed on the second blockchain, and send the first contract unlock request to the first blockchain node, so that the first blockchain node remotely unlocks the updated target remote contract address corresponding to the updated target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

[0288] In specific implementations, the device, processor 1301, memory 1305, etc. described in the embodiments of this application can execute the implementation methods described in the above method embodiments, and can also execute the implementation methods described in the embodiments of this application, which will not be repeated here.

[0289] In addition, it should be noted that the embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores computer-readable instructions executed by the multi-blockchain-based data processing device 1 and the multi-blockchain-based data processing device 2 mentioned above, and the computer-readable instructions include computer-readable instructions. When the processor executes the computer-readable instructions, it can perform the description of the multi-blockchain-based data processing method in the embodiments corresponding to Figures 4, 6, and 8 above. Therefore, they will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiments involved in this application, please refer to the description of the method embodiments of this application. As an example, the computer-readable instructions can be deployed and executed on a computing device, or on multiple computing devices located in a single location, or on multiple computing devices distributed at multiple locations and interconnected by a communication network. Multiple computing devices distributed at multiple locations and interconnected by a communication network can constitute a blockchain system.

[0290] Further, please refer to Figure 14, which is a schematic diagram of a multi-blockchain-based data processing system provided in an embodiment of the present application. The multi-blockchain-based data processing system 3 may include a first blockchain node 3a and a second blockchain node 3b. The first blockchain node 3a may be a blockchain node in the first blockchain network described in the above embodiment. For example, the first blockchain node 3a may be any blockchain node in the first blockchain network 200 shown in Figure 1 above, and will not be further described here. The second blockchain node 3b may be a blockchain node in the second blockchain network described in the above embodiment. For example, the second blockchain node 3b may be any blockchain node in the second blockchain network 300 shown in Figure 1 above, and will not be further described here. Furthermore, the description of the beneficial effects of using the same method will not be repeated here.

[0291] In addition, it should be noted that the embodiments of the present application also provide a computer program product or computer program, which may include computer-readable instructions, which may be stored in a computer-readable storage medium. The processor of the computer device reads the computer-readable instructions from the computer-readable storage medium and executes the computer-readable instructions, causing the computer device to perform the description of the multi-blockchain data processing method described in the embodiments corresponding to Figures 4, 6, and 8 above. Therefore, these descriptions will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated. For technical details not disclosed in the computer program product or computer program embodiments involved in this application, please refer to the description of the method embodiments of this application.

[0292] It should be noted that for the aforementioned various method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0293] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0294] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0295] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware via computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium. When executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0296] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

[0297] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0298] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A data processing method based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the first blockchain corresponds to a first blockchain network, and the second blockchain corresponds to a second blockchain network, wherein the first blockchain network is independent of the second blockchain network, and the method is performed by a computer device that maintains a first blockchain node in the first blockchain network, and includes: Obtaining a full-chain asset transfer request sent by the first business object for a business transaction, and when determining that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request, calling the target full-chain business contract on the first blockchain, and using the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred, wherein the cross-chain asset transfer transaction is used to indicate that the full-chain asset to be transferred is transferred from the first blockchain to the second blockchain; Call the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract, wherein the full-chain contract protocol is determined based on the full-chain contract protocol interface provided by the full-chain business parent contract on the first blockchain, and the target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and When a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred, the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is sent to the second blockchain node in the second blockchain network through the off-chain cross-chain service device, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, and the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred.

2. According to the method of claim 1, the cross-chain asset transfer transaction carries the second blockchain identifier of the second blockchain; The calling of the full-chain contract protocol in the target full-chain business contract to determine the target remote contract address bound to the target full-chain business contract includes: Calling the full-chain contract protocol in the target full-chain business contract to obtain the remote contract address bound to the target full-chain business contract, wherein the remote contract address bound to the target full-chain business contract includes the contract address corresponding to the full-chain business contract integrated with the full-chain contract protocol on the reference business chain, wherein the reference business chain is a blockchain other than the first blockchain in the multiple blockchains, and the reference business chain includes the second blockchain; Among the remote contract addresses bound to the target full-chain business contract, the remote contract address associated with the second blockchain identifier is determined as the target remote contract address.

3. The method according to claim 1 or 2, wherein generating a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction based on the target remote contract address and the full-chain asset to be transferred comprises: Obtaining a first blockchain identifier of the first blockchain, where the first blockchain identifier is a blockchain identifier configured for the first blockchain through a full-chain unified registration service in an off-chain full-chain cross-chain service; Based on the first blockchain identifier, calling the full-chain event identifier generation protocol in the full-chain service contract to generate an event identifier associated with the first blockchain identifier; Based on the event identifier, the target remote contract address and the full-chain asset to be transferred, a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated.

4. According to the method described in any one of claims 1 to 3, the cross-chain asset transfer event carries the asset identification of the full-chain asset to be transferred, and the asset identification of the full-chain asset to be transferred is generated based on the identification prefix associated with the first blockchain and the asset identification template configured in the full-chain contract protocol. The cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event is constructed by the off-chain cross-chain service device based on the identification prefix and the asset identification template to verify the asset identification of the full-chain asset to be transferred carried by the cross-chain asset transfer event, and the identification verification is successful.

5. According to the method according to any one of claims 1 to 4, before generating the cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction, the method further includes: Calling the full-chain token airdrop contract on the first blockchain through the target full-chain business contract, obtaining the first blockchain token associated with the full-chain asset to be transferred, and using the obtained first blockchain token as the full-chain token to be airdropped; When generating the cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction, the full-chain token to be airdropped is written into the cross-chain asset transfer event.

6. According to the method according to any one of claims 1 to 5, when the contract status of the target remote full-chain business contract is in the contract update status, the method further comprises: Obtaining a contract lock request sent by a second business object for the target remote full-chain business contract deployed on the second blockchain, where the second business object is a business object corresponding to the target remote full-chain business contract on the second blockchain, and the contract lock request is generated by the second business object after remotely locking the contract address corresponding to the target full-chain business contract in the target remote full-chain business contract deployed on the second blockchain; Obtaining the target remote contract address corresponding to the target remote full-chain business contract to be locked on the second blockchain from the contract locking request; Through the remote contract address locking mechanism associated with the target full-chain business contract, a remote contract address locking method for remotely locking the target remote contract address is determined in the target full-chain business contract, and the remote contract address locking method is called to remotely lock the target remote contract address corresponding to the target remote full-chain business contract, and the address state of the target remote contract address after the remote address is locked is configured as an address locked state in the target full-chain business contract. The target remote contract address in the address locked state is used to suspend receiving the full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer.

7. According to the method of claim 6, when the contract status of the target remote full-chain business contract is adjusted from the contract update status to the contract update completion status, the target remote full-chain business contract in the contract update completion status is the updated target remote full-chain business contract, and the contract address of the updated target remote full-chain business contract is the updated target remote contract address; The method further comprises: Obtaining a first contract binding request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain, wherein the first contract binding request is generated by the second business object after performing remote address binding on the target contract address in the updated target remote full-chain business contract deployed on the second blockchain; Obtaining the updated target remote contract address corresponding to the updated target remote full-chain business contract to be bound on the second blockchain from the first contract binding request; The remote address setting interface is called through the full-chain contract protocol in the target full-chain business contract, and the updated target remote contract address is set in the remote contract address bound to the target full-chain business contract.

8. The method according to claim 7, further comprising: Obtaining a first contract unlocking request sent by the second business object for the updated target remote full-chain business contract deployed on the second blockchain, wherein the first contract unlocking request is generated by the second business object after remote address unlocking of the target contract address in the updated target remote full-chain business contract deployed on the second blockchain; Obtaining the updated target remote contract address corresponding to the updated target remote full-chain business contract to be unlocked on the second blockchain from the first contract unlock request; Through the remote contract address unlocking mechanism associated with the target full-chain business contract, a remote contract address unlocking method for remotely unlocking the updated target remote contract address is determined in the target full-chain business contract, and the remote contract address unlocking method is called to unlock the updated target remote full-chain business contract corresponding to the updated target remote contract address. The updated target remote contract address is remotely unlocked, and the address state of the updated target remote contract address after the remote address is unlocked is configured as an address unlocked state in the target full-chain business contract. The updated target remote contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the first business object through the target full-chain business contract for cross-chain transfer.

9. A data processing method based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the first blockchain corresponds to a first blockchain network, and the second blockchain corresponds to a second blockchain network, wherein the second blockchain network is independent of the first blockchain network, and the method is performed by a computer device that maintains a second blockchain node in the second blockchain network, comprising: Obtain a cross-chain asset reconstruction transaction, the cross-chain asset reconstruction transaction corresponds to a cross-chain asset transfer event, the cross-chain asset transfer event is sent by the first blockchain node in the first blockchain network through the off-chain cross-chain service device, the cross-chain asset transfer event is an event corresponding to a cross-chain asset transfer transaction generated by the first blockchain node based on the target remote contract address bound to the target full-chain business contract and the full-chain asset to be transferred, the target remote contract address is obtained by the first blockchain node through the full-chain contract protocol in the target full-chain business contract, the full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node obtains the full-chain asset transfer request sent by the first business object for the business transaction and determines that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request, the target full-chain business contract is a full-chain business contract on the first blockchain that integrates the full-chain contract protocol, and the remote full-chain business contract corresponding to the target remote contract address is a full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and Based on the cross-chain asset reconstruction transaction, the target remote full-chain business contract corresponding to the target remote contract address is determined on the second blockchain, and the target remote full-chain business contract is called to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, and the asset data information of the full-chain mapping asset is consistent with the asset data information of the target full-chain asset.

10. According to the method of claim 9, the cross-chain asset reconstruction transaction carries the full-chain token to be airdropped, and the full-chain token to be airdropped is the first blockchain token obtained by the first blockchain node through the full-chain token airdrop contract on the first blockchain for the full-chain asset to be transferred; When calling the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, the method further includes: The full-chain token airdrop contract on the second blockchain is called through the target remote full-chain business contract to determine the second blockchain airdrop token corresponding to the full-chain token to be airdropped, and the second blockchain airdrop token is allocated to the business object corresponding to the full-chain mapped asset. The second blockchain airdrop token is used to support the business object corresponding to the full-chain mapped asset to perform business operations on the full-chain mapped asset on the second blockchain.

11. The method according to claim 9 or 10, further comprising: Obtain a contract update request sent by the second business object for the target remote full-chain business contract, perform contract update processing on the target remote full-chain business contract based on the contract update request, and set the contract state of the target remote full-chain business contract to the contract update state, where the second business object is a business object corresponding to the target remote full-chain business contract on the second blockchain; When it is detected that the target remote full-chain business contract is in the contract update state, obtaining the target contract address corresponding to the target full-chain business contract to be locked on the first blockchain; Through the remote contract address locking mechanism associated with the target remote full-chain business contract, a remote contract address locking method for remotely locking the target contract address is determined in the target remote full-chain business contract, the remote contract address locking method is called to remotely lock the target contract address, and the address state of the target contract address after the remote address is locked is configured as an address locked state in the target remote full-chain business contract. The target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

12. The method according to claim 11, further comprising: Generate a contract lock request for the target remote full-chain business contract deployed on the second blockchain, and send the contract lock request to the first blockchain node, so that the first blockchain node remotely locks the target remote contract address of the target remote full-chain business contract in the target full-chain business contract deployed on the first blockchain.

13. The method according to claim 11 or 12, further comprising: When it is detected that the contract state of the target remote full-chain business contract is adjusted from the contract update state to the contract update completion state, the target remote full-chain business contract in the contract update completion state is used as the updated target remote full-chain business contract; Obtaining a target contract address corresponding to the target full-chain business contract to be locked on the first blockchain; Through the remote contract address locking mechanism associated with the updated target remote full-chain business contract, the remote contract address locking method for remotely locking the target contract address is determined in the updated target remote full-chain business contract, the remote contract address locking method is called to remotely lock the target contract address, and the address state of the target contract address after the remote address is locked is configured as an address locked state in the updated target remote full-chain business contract. The target contract address in the address locked state is used to suspend receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

14. According to the method of claim 13, the contract address corresponding to the updated target remote full-chain business contract is the updated target remote contract address, and the method further comprises: Obtain a second contract binding request sent by the second business object for the updated target remote full-chain business contract, and obtain the target contract address corresponding to the target full-chain business contract to be bound on the first blockchain from the second contract binding request; The remote address setting interface is called through the full-chain contract protocol in the target remote full-chain business contract, and the target contract address is set in the remote contract address bound to the updated target remote full-chain business contract.

15. The method according to claim 14, further comprising: Obtaining a second contract unlocking request sent by the second business object for the updated target remote full-chain business contract, and obtaining the target contract address corresponding to the target full-chain business contract to be unlocked on the first blockchain from the second contract unlocking request; Through the remote contract address unlocking mechanism associated with the updated target remote full-chain business contract, the remote contract address unlocking method for remotely unlocking the target contract address is determined in the updated target remote full-chain business contract, and the remote contract address unlocking method is called to remotely unlock the target contract address corresponding to the target full-chain business contract, and the address state of the target contract address after the remote address is unlocked is configured as an address unlocked state in the updated target remote full-chain business contract. The target contract address in the address unlocked state is used to restart receiving the full-chain assets sent by the updated target remote full-chain business contract for cross-chain transfer.

16. A data processing device based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the blockchain network corresponding to the first blockchain is a first blockchain network, and the blockchain network corresponding to the second blockchain is a second blockchain network, wherein the first blockchain network is independent of the second blockchain network, and wherein the device runs on a first blockchain node in the first blockchain network, and wherein the device comprises: A full-chain asset acquisition module, used to acquire a full-chain asset transfer request sent by the first business object for a business transaction, and when it is determined based on the full-chain asset transfer request that the business transaction is a cross-chain asset transfer transaction, call the target full-chain business contract on the first blockchain, and use the full-chain asset associated with the cross-chain asset transfer transaction as the full-chain asset to be transferred, and the cross-chain asset transfer transaction is used to indicate that the full-chain asset to be transferred is transferred from the first blockchain to the second blockchain; A contract address determination module, used to call the full-chain contract protocol in the target full-chain business contract, determine the target remote contract address bound to the target full-chain business contract, the full-chain contract protocol is determined based on the full-chain contract protocol interface provided by the full-chain business parent contract on the first blockchain, and the target remote full-chain business contract corresponding to the target remote contract address is the full-chain business contract on the second blockchain that integrates the full-chain contract protocol; and A transfer event generation module is used to, when a cross-chain asset transfer event corresponding to the cross-chain asset transfer transaction is generated based on the target remote contract address and the full-chain asset to be transferred, send the cross-chain asset reconstruction transaction corresponding to the cross-chain asset transfer event to the second blockchain node in the second blockchain network through an off-chain cross-chain service device, so that the second blockchain node determines the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain based on the cross-chain asset reconstruction transaction, and calls the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, and the asset data information of the full-chain mapping asset is consistent with the asset data information of the full-chain resource to be transferred.

17. A data processing device based on multiple blockchains, wherein the multiple blockchains include a first blockchain and a second blockchain, wherein the blockchain network corresponding to the first blockchain is a first blockchain network, and the blockchain network corresponding to the second blockchain is a second blockchain network, and the second blockchain network is independent of the first blockchain network, and the device runs on a second blockchain node in the second blockchain network, comprising: a reconstruction transaction acquisition module, used to obtain a cross-chain asset reconstruction transaction, wherein the cross-chain asset reconstruction transaction corresponds to a cross-chain asset transfer event, which is sent by the first blockchain node in the first blockchain network through an off-chain cross-chain service device, and the cross-chain asset transfer event is an event corresponding to a cross-chain asset transfer transaction generated by the first blockchain node based on the target remote contract address bound to the target full-chain business contract and the full-chain asset to be transferred, wherein the target remote contract address is obtained by the first blockchain node through the full-chain contract protocol in the target full-chain business contract, and the full-chain asset to be transferred is the full-chain asset associated with the cross-chain asset transfer transaction determined by calling the target full-chain business contract when the first blockchain node obtains the full-chain asset transfer request sent by the first business object for the business transaction and determines that the business transaction is a cross-chain asset transfer transaction based on the full-chain asset transfer request, wherein the target full-chain business contract is a full-chain business contract on the first blockchain that is integrated with the full-chain contract protocol, and the remote full-chain business contract corresponding to the target remote contract address is a full-chain business contract on the second blockchain that is integrated with the full-chain contract protocol; and A mapping asset generation module is used to reconstruct the transaction based on the cross-chain assets, determine the target remote full-chain business contract corresponding to the target remote contract address on the second blockchain, and call the target remote full-chain business contract to generate a full-chain mapping asset corresponding to the full-chain asset to be transferred on the second blockchain, and the asset data information of the full-chain mapping asset is consistent with the asset data information of the target full-chain asset.

18. A computer device comprising a memory and a processor, wherein the memory stores computer-readable instructions, and the processor is configured to execute the computer-readable instructions to perform the method according to any one of claims 1 to 15.

19. A computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the method according to any one of claims 1 to 15 is implemented.

20. A computer program product, comprising computer readable instructions, which, when executed by a processor, implement the method according to any one of claims 1 to 15.

Citation Information

Patent Citations

  • Block chain multistage intelligent contract-oriented data migration method

    CN107145521A

  • Hash time locking method and system based on cloud cross-chain transfer protocol

    CN113269545A

  • SGX-based notary cross-chain data security protection system and method

    CN114647871A

  • Cross-chain resource transfer method and device, medium and electronic equipment

    CN115115360A

  • Relay chain-based cross-chain asset transaction method, system and equipment

    CN115601168A