Block chain resource transfer processing method, related device and medium

Abstract

According to one aspect of the invention, the invention provides a block chain resource transfer processing method, a related device and a medium. The block chain resource transfer processing method comprises the following steps: in response to a target resource packet deployment request of a first object, deploying a target resource packet in an overall contract on a block chain; receiving a binding request of a plurality of target resources to be bound; calling a resource affiliation transfer function in a sub-contract on the block chain, so that a second affiliation party of the to-be-bound target resource on an application platform corresponding to the sub-contract is transferred to an address of an overall contract, and determining the to-be-bound target resource as a bound target resource; and in response to the target resource affiliation transfer request of the second object, the first affiliation party of the target resource corresponding to the bound target resource is transferred to the second object, so that the resource transfer and scheduling efficiency and the inter-application platform interoperability are improved. The embodiment of the invention can be applied to various fields of block chains, structured information processing, security technologies and the like.

Description

Technical Field

[0001] The present disclosure relates to the field of blockchain, and in particular to a blockchain resource transfer processing method, related devices and media. Background Art

[0002] At present, blockchain networks are often used for resource scheduling and transfer. With the development of blockchain, the same resource can be scheduled and transferred in multiple application platforms (such as game platforms). For example, armor in a game can be used in game A, game B, game C, etc. at the same time, can be obtained in game A, game B, game C, etc., and transferred to other objects in game A, game B, game C, etc. In practice, there is often a need to collectively transfer resources collected on different application platforms. For example, armor collected separately in game A, game B, and game C is transferred to other objects as a collection. At this time, due to the limitations of the existing technology, the resources in the resource collection need to be transferred and scheduled separately on the application platform where they are obtained, the transfer and scheduling efficiency is low, and the interoperability across application platforms is low. Summary of the invention

[0003] The disclosed embodiments provide a blockchain resource transfer processing method, related devices and media, which can improve the transfer and scheduling efficiency of resources and improve the interoperability across application platforms.

[0004] According to one aspect of the present disclosure, a blockchain resource transfer processing method is provided, which is used for a blockchain node, wherein the blockchain node is connected to multiple application platforms, and multiple sub-contracts corresponding to the multiple application platforms and an overall contract for the multiple application platforms are maintained on the blockchain, and the blockchain resource transfer processing method includes:

[0005] In response to a target resource package deployment request of a first object, deploy the target resource package in the overall contract on the blockchain, where a first owner of the target resource package is the first object;

[0006] Receiving binding requests of multiple target resources to be bound, wherein the multiple target resources to be bound are registered as the first objects by second owners on the multiple application platforms;

[0007] Calling the resource ownership transfer function in the sub-contract on the blockchain, so that the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as a bound target resource;

[0008] In response to a target resource ownership transfer request of a second object, the first owner of the bound target resource corresponding to the target resource is transferred to the second object.

[0009] According to one aspect of the present disclosure, a blockchain resource transfer processing device is provided, wherein the blockchain resource transfer processing device is located in a blockchain node, wherein the blockchain node is connected to multiple application platforms, and multiple sub-contracts corresponding to the multiple application platforms and an overall contract for the multiple application platforms are maintained on the blockchain, including:

[0010] a resource deployment unit, configured to deploy the target resource package in the overall contract on the blockchain in response to a target resource package deployment request of the first object, wherein the first owner of the target resource package is the first object;

[0011] A first receiving unit is configured to receive binding requests of multiple target resources to be bound, wherein the multiple target resources to be bound are registered as the first objects by second owners on the multiple application platforms;

[0012] A resource binding unit, configured to call a resource ownership transfer function in the sub-contract on the blockchain, so that the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as a bound target resource;

[0013] The first transfer execution unit is configured to transfer the first owner of the bound target resource corresponding to the target resource to the second object in response to a target resource ownership transfer request of the second object.

[0014] Optionally, the resource deployment unit is specifically used to:

[0015] In response to the target resource bundle deployment request of the first object, assigning a target resource bundle identifier to the target resource bundle;

[0016] Receiving an initial target resource list of the target resource package;

[0017] Recording the mapping relationship between the target resource package identifier and the initial target resource list into a first variable;

[0018] The target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain.

[0019] Optionally, the blockchain resource transfer processing device further includes:

[0020] A first acquiring unit, configured to acquire the target resource package identifier targeted by the binding request;

[0021] A first search unit, configured to search the first variable based on the target resource package identifier to obtain the initial target resource list;

[0022] The first determining unit is configured to determine whether a plurality of the target resources to be bound fall into the initial target resource list.

[0023] Optionally, the initial target resource list includes, for each of the initial target resources, the first sub-contract address corresponding to the application platform where the initial target resource is registered, the initial target resource identifier, and the number of registered initial target resources on the application platform; the binding request includes, for each of the target resources to be bound, the second sub-contract address corresponding to the application platform where the target resource to be bound is registered, the target resource identifier to be bound, and the number to be bound;

[0024] The first determining unit is specifically configured to:

[0025] If the first sub-contract address of one of the initial target resources in the initial target resource list is equal to the second sub-contract address of the target resource to be bound, and the initial target resource identifier is equal to the target resource identifier to be bound of the target resource to be bound, then the initial target resource is determined as the target resource to be examined;

[0026] Based on the registered number of the target resources to be examined and the to-be-bound number of the target resources to be bound, it is determined that the target resources to be bound fall into the initial target resource list.

[0027] Optionally, the first determining unit is specifically configured to:

[0028] Acquire a second variable, where the second variable indicates the bound number of the registered number of the initial target resource;

[0029] If the sum of the second variable and the number to be bound is not greater than the registered number, it is determined that the target resource to be bound falls into the initial target resource list, and the number to be bound is increased on the second variable.

[0030] Optionally, the blockchain resource transfer processing device further includes:

[0031] A second determining unit, configured to determine that the first sub-contract address corresponding to the initial target resource is of a first type, wherein the first type indicates that the initial target resource cannot be copied;

[0032] The first verification unit is used to verify that the registration number of the initial target resource is 1.

[0033] Optionally, the resource binding unit is specifically used to:

[0034] If the second sub-contract address of the target resource to be bound is of the first type, and the first type indicates that the initial target resource cannot be copied, then the second owner of the target resource to be bound is transferred to the address of the overall contract;

[0035] If the second sub-contract address of the target resource to be bound is of the second type, and the second type indicates that the initial target resource is replicable, the second attribution party of the target resource to be bound with the number to be bound in the target resource to be bound is transferred to the address of the overall contract.

[0036] Optionally, the blockchain resource transfer processing device further includes:

[0037] A second obtaining unit, configured to obtain a first issuer of the binding request;

[0038] A third determining unit is configured to determine that the first sender is the first object.

[0039] Optionally, the blockchain resource transfer processing device further includes:

[0040] A second receiving unit, configured to receive an unbinding request for a plurality of to-be-unbound target resources among the plurality of bound target resources;

[0041] The second transfer execution unit is used to call the resource ownership transfer function in the sub-contract on the blockchain, so that the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract is transferred to the first object.

[0042] Optionally, the blockchain resource transfer processing device further includes:

[0043] A third acquisition unit, configured to acquire the target resource package identifier targeted by the unbinding request;

[0044] A first search unit, configured to search the first variable based on the target resource package identifier to obtain the initial target resource list;

[0045] The fourth determining unit is used to determine whether a plurality of the to-be-unbound target resources fall into the initial target resource list.

[0046] Optionally, the initial target resource list includes, for each of the initial target resources, the first sub-contract address corresponding to the application platform where the initial target resource is registered, and the initial target resource identifier; the unbinding request includes, for each of the target resources to be unbound, the third sub-contract address corresponding to the application platform where the target resource to be unbound is registered, and the target resource identifier to be unbound;

[0047] The fourth determining unit is specifically configured to:

[0048] If the first sub-contract address of one of the initial target resources in the initial target resource list is equal to the third sub-contract address of the target resource to be unbound, and the initial target resource identifier is equal to the target resource identifier to be unbound of the target resource to be unbound, it is determined that the target resource to be unbound falls into the initial target resource list.

[0049] Optionally, the unbinding request further includes the number of resources to be unbound for each target resource to be unbound;

[0050] The blockchain resource transfer processing device also includes:

[0051] a fourth acquisition unit, configured to acquire a second variable, where the second variable indicates the bound number of the initial target resource;

[0052] A fifth determining unit, configured to determine that the number to be unbound is not greater than the second variable;

[0053] A resource unbinding unit is used to call the resource ownership transfer function in the sub-contract on the blockchain, so that the target resource to be unbound is transferred from the second owner on the application platform corresponding to the sub-contract to the first object. The blockchain resource transfer processing method also includes: subtracting the number to be unbound from the second variable.

[0054] Optionally, the unbinding request further includes the number of resources to be unbound for each target resource to be unbound;

[0055] The blockchain resource transfer processing device also includes:

[0056] an attribution party address determination unit, configured to, if the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, call the obtain attribution party function in the sub-contract on the blockchain to determine that the second attribution party of the target resource to be unbound on the application platform corresponding to the sub-contract is the address of the overall contract;

[0057] The unit for determining the number of attributable parties is used to call the obtain attributable party function in the sub-contract on the blockchain if the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, so as to determine that the number of target resources whose second attributable party is the address of the overall contract on the application platform corresponding to the sub-contract is not less than the number to be unbound.

[0058] Optionally, the blockchain resource transfer processing device further includes:

[0059] A fifth obtaining unit, configured to obtain a second sender of the unbinding request;

[0060] A sixth determining unit is used to determine that the second sender is the first object.

[0061] Optionally, the resource unbinding unit is specifically used to:

[0062] If the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, then the second owner of the target resource to be unbound is transferred to the first object;

[0063] If the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, the second belonging party of the target resource to be unbound of the number to be unbound in the bound target resources is transferred to the first object.

[0064] Optionally, the blockchain resource transfer processing device further includes:

[0065] An authorization function calling unit, used to call the authorization functions in the plurality of sub-contracts;

[0066] An authorization function execution unit is used to execute the authorization function so that the sub-contract is authorized to the overall contract, so that the address of the overall contract can serve as the second attribution party registered on the application platform corresponding to the sub-contract.

[0067] Optionally, the blockchain resource transfer processing device further includes:

[0068] A third receiving unit, configured to receive a target resource package viewing request of the second object, wherein the target resource package viewing request has the target resource package identifier;

[0069] A second searching unit, configured to search the first variable based on the target resource package identifier to obtain the initial target resource list;

[0070] A list sending unit is used to send the initial target resource list to the second object.

[0071] According to one aspect of the present disclosure, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the blockchain resource transfer processing method as described above is implemented.

[0072] According to one aspect of the present disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the blockchain resource transfer processing method as described above is implemented.

[0073] According to one aspect of the present disclosure, a computer program product is provided, which includes a computer program, and the computer program is read and executed by a processor of a computer device, so that the computer device executes the blockchain resource transfer processing method as described above.

[0074] The disclosed embodiment is aimed at multiple application platforms that need to enhance interoperability, and multiple sub-contracts corresponding to multiple application platforms and overall contracts for multiple application platforms are maintained on the blockchain. The owner of the resource on the application platform is registered as the first object to which the resource belongs on the sub-contract corresponding to the application platform. In order to facilitate the collective transfer and scheduling of resources, the first object collects the resources collected on different application platforms into a target resource package, deploys the target resource package in the overall contract on the blockchain, and its first owner is set to the first object. If it is expected that part or all of the target resource package will be collectively scheduled or transferred, the sub-contract on the blockchain is called so that the second owner of the target resource to be bound in the sub-contract to be collectively scheduled or transferred is uniformly transferred to the address of the overall contract, so that the target resource to be bound can be determined as the bound target resource bound to the overall contract. Under normal circumstances, the owner of the target resource can be determined from the second owner in the sub-contract, but if the second owner becomes the address of the overall contract, it is necessary to find the first owner of the target resource in the overall contract according to the address of the overall contract to determine. Since the second party of the bound target resources has been changed to the address of the overall contract, once the attribution transfer request of the target resource package is received, the first party of the bound target resources corresponding to the target resource package is changed to the sender of the transfer request to achieve unified transfer and scheduling of the target resources without making tedious changes on each application platform respectively, thereby improving the efficiency of resource transfer and scheduling, as well as interoperability across application platforms.

[0075] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or understood by practicing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] The accompanying drawings are used to provide further understanding of the technical solution of the present disclosure and constitute a part of the specification. Together with the embodiments of the present disclosure, they are used to explain the technical solution of the present disclosure and do not constitute a limitation on the technical solution of the present disclosure.

[0077] Figure 1 It is a schematic diagram of the system architecture of a blockchain node connection application platform to which an embodiment of the present disclosure is applied;

[0078] Figure 2A-2G It is a schematic diagram of a type of business scenario of a blockchain resource transfer processing method according to an embodiment of the present disclosure;

[0079] Figure 3 is a flowchart of a blockchain resource transfer processing method according to an embodiment of the present disclosure;

[0080] Figure 4 yes Figure 3 A specific implementation flow chart of step 310;

[0081] Figure 5 is a flowchart of steps further included after step 320 in another embodiment of the present disclosure;

[0082] Figure 6 yes Figure 5 A specific implementation flow chart of step 520;

[0083] Figure 7 yes Figure 6 A specific implementation diagram of determining that the target resource to be bound falls into the initial target resource list;

[0084] Figure 8 yes Figure 6 Another specific implementation flow chart of step 620;

[0085] Fig. 9 yes Figure 8 A specific implementation diagram of determining that the target resource to be bound falls into the initial resource list based on the second variable;

[0086] Fig.10 yes Figure 3 A specific implementation flow chart of step 330;

[0087] Figures 11A-11C Shows Fig.10 A specific implementation diagram of binding the target resource based on the type of the second sub-contract address;

[0088] Fig.12 is a flowchart of steps further included after step 330 in another embodiment of the present disclosure;

[0089] Fig.13 is a flowchart of steps further included after step 1210 in another embodiment of the present disclosure;

[0090] Fig.14 is a flowchart of steps further included after step 1330 in another embodiment of the present disclosure;

[0091] Fig.15 Shows Fig.14 A specific implementation diagram of unbinding a target resource from a bound target resource based on a second variable;

[0092] Fig.16 is a flowchart of steps further included after step 1330 in another embodiment of the present disclosure;

[0093] Fig.17 yes Fig.14 A specific implementation flow chart of step 1430;

[0094] Fig.18 is a flowchart of steps further included before step 340 in another embodiment of the present disclosure;

[0095] Fig.19 is a module diagram of a blockchain resource transfer processing device according to an embodiment of the present disclosure;

[0096] Fig. 20 According to the embodiment of the present disclosure Figure 3 The terminal structure diagram of the blockchain resource transfer processing method shown;

[0097] Fig.21 According to the embodiment of the present disclosure Figure 3 The server structure diagram of the blockchain resource transfer processing method shown. DETAILED DESCRIPTION

[0098] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.

[0099] It should be noted that in various specific implementations of the present disclosure, when it comes to the need to perform relevant processing based on data related to the characteristics of the target object such as the target object attribute information or attribute information set, the permission or consent of the target object will be obtained first, and the collection, use and processing of these data will comply with relevant laws, regulations and standards. In addition, when the embodiment of the present disclosure needs to obtain the attribute information of the target object, the separate permission or separate consent of the target object will be obtained through a pop-up window or jump to a confirmation page. After clearly obtaining the separate permission or separate consent of the target object, the necessary target object-related data for the normal operation of the embodiment of the present disclosure will be obtained.

[0100] Before further describing the embodiments of the present disclosure in detail, the nouns and terms involved in the embodiments of the present disclosure are described. The nouns and terms involved in the embodiments of the present disclosure are subject to the following interpretations:

[0101] Blockchain: Blockchain is a new application model of computer technologies such as distributed data storage, consensus mechanism, and encryption algorithm. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of transaction information, which is used to verify the validity of its information (anti-counterfeiting) and associate with the previous block. Currently, many applications have begun to use blockchain networks because the decentralized nature of blockchain networks has the following advantages: strong fault tolerance, not easy to be attacked, and data cannot be tampered with. This makes objects trust applications that deploy blockchains, and the activities of objects outside the chain on the blockchain are increasing. More and more transactions need to be processed on the chain.

[0102] Peer-to-peer network: a point-to-point network. Peer-to-peer network is based on a specific type of network protocol. There is no need for a central node to maintain the network status between network nodes. Instead, each node maintains the node status of the entire network or the connection status of its adjacent nodes through broadcast interaction with adjacent nodes.

[0103] Blockchain node: A blockchain node usually refers to a computer in a blockchain network. It can also be said that any computer connected to a blockchain network is called a node. Generally speaking, a blockchain node has three characteristics: first, it has storage space, which can store block data in devices such as mobile hard disks and computers; second, it is connected to the network, and all devices with storage space must be connected to the network; third, to participate in the blockchain, it is necessary to run the corresponding blockchain program on the storage space and execute transactions on the chain through a visual terminal.

[0104] Virtual resources: Virtual resources are a term that is opposite to real resources. They were born mainly with the birth of the Internet. With the popularization of the Internet, people's demand for obtaining information on the Internet has greatly increased. Therefore, the amount of information circulating on the Internet has also increased. These information resources edited by databases and programs are what we often call virtual resources. It should be noted that on the application platform, some data protocol standards can be used to perform specific data processing on virtual resources, making these virtual resources unique and irreplaceable. It should be understood that in different business scenarios, the types of non-homogeneous virtual resources can also be diverse. For example, non-homogeneous virtual resources can be virtual paintings, non-homogeneous virtual resources can also be virtual equipment, and non-homogeneous virtual resources can also be other types of virtual resources.

[0105] Business contract: is a piece of code written on the blockchain. Once the terms of the contract are triggered in the blockchain at a certain time, the code will be automatically executed. Business contracts are computer protocols designed to disseminate, verify or execute transactions in an information-based manner. Business contracts are in digital form, and digital form means that business contracts have to be written in computer-readable code. Once the parties to a business contract reach an agreement, the rights and obligations established by the business contract are executed by a computer or computer network through the code on the blockchain.

[0106] Currently, blockchain networks are often used for resource scheduling and transfer. With the development of blockchain, the same resource can be scheduled and transferred in multiple application platforms (such as game platforms). For example, armor in a game can be used in game A, game B, game C, etc. at the same time, can be obtained in game A, game B, game C, etc., and transferred to other objects in game A, game B, game C, etc.

[0107] In practice, there is often a need to collectively transfer resources collected on different application platforms. For example, the armor collected in Game A, Game B, and Game C are transferred to other objects as a collection. It should be pointed out that the data protocol standards followed by different application platforms may be different. The armor in the game is a non-homogeneous virtual equipment. Even if it is the same armor, the data form stored on different application platforms will be different. At this time, due to the limitations of the existing technology, the resources in the resource collection need to be transferred and scheduled separately on the application platform where they are obtained, and the resources in the resource collection cannot be transferred and scheduled as a whole. As a result, in practice, the efficiency of resource transfer and scheduling will be low, and the interoperability across application platforms will be low.

[0108] System architecture and scenario description of the application of the embodiments of the present disclosure

[0109] See also Figure 1 The blockchain resource transfer processing network shown includes:

[0110] Application platform A, application platform B, application platform C, and application platform D are four types of application platforms. The application platform of the disclosed embodiment refers to a network platform that carries blockchain applications. It should be emphasized that on the application platform, specific data processing can be performed on virtual resources through some data protocol standards, making these virtual resources unique and irreplaceable. It should be understood that in different business scenarios, the types of non-homogeneous virtual resources can also be diverse. For example, non-homogeneous virtual resources can be virtual paintings, non-homogeneous virtual resources can also be virtual equipment, and non-homogeneous virtual resources can also be other types of virtual resources.

[0111] Blockchain node A, blockchain node B, blockchain node C, and blockchain node D are all nodes of the blockchain. Blockchain nodes refer to computers in the blockchain network, and any computer connected to the blockchain network is called a node. Generally speaking, blockchain nodes have three characteristics: first, they have storage space, which can store block data in devices such as mobile hard disks and computers; second, they are connected to the network, and all devices with storage space must be connected to the network; third, to participate in the blockchain, it is necessary to run the corresponding blockchain program on the storage space and execute transactions on the chain through the visual terminal. It should be pointed out that blockchain node A, blockchain node B, blockchain node C, and blockchain node D maintain multiple sub-contracts corresponding to multiple application platforms on the blockchain, and overall contracts for multiple application platforms. Figure 1 In the business scenario shown, sub-contract A corresponding to application platform A, sub-contract B corresponding to application platform B, sub-contract C corresponding to application platform C, and sub-contract D corresponding to application platform D are stored on different blocks of the same blockchain, and the overall contracts of application platforms A, B, C, and D are different from the sub-contracts and are stored on another blockchain. It should be understood that Figure 1 The blockchain resource transfer processing network of one embodiment of the present disclosure is shown. The storage of contracts on the blockchain is not limited to Figure 1 As shown, multiple sub-contracts corresponding to multiple application platforms are not necessarily stored on the same blockchain, and sub-contracts and overall contracts are not necessarily stored on different blockchains.

[0112] The blockchain server refers to a server that distributes the data to be uploaded to the corresponding blockchain nodes and controls each blockchain node to maintain the blockchain. It should be understood that the blockchain node is connected to the application platform through the blockchain server.

[0113] The embodiments of the present disclosure can be applied in various scenarios, such as Figure 2A-2G The scenario of transferring the virtual resources of application platform A and application platform B as a whole is shown. It should be noted that sub-contract A is a business contract for storing virtual resources in application platform A, and sub-contract B is a business contract for storing virtual resources in application platform B. In order to transfer the virtual resources on application platform A and application platform B as a whole from the first object to the second object, the present disclosure provides Figure 2A-2G The embodiment shown.

[0114] Reference Figure 2AIn order to facilitate the collective transfer and scheduling of resources, the first object issues a target resource package deployment request to the blockchain node, aiming to aggregate the resources collected on different application platforms into a target resource package, deploy the target resource package in the overall contract on the blockchain, and set its first owner to the first object. It should be noted that the target resource package deployment request may include a target resource package identifier and a target resource list; wherein the target resource package identifier is used to distinguish different target resource packages, and the target resource list is used to record the resource storage status of the first object on different application platforms. Figure 2A In the example, the target resource package corresponding to the target resource package is identified as 1, which indicates that the identification number of the currently deployed target resource package is 1, and the target resource list corresponding to target resource package No. 1 is List M, which records the resource storage status of each resource belonging to the first object in the target resource package on different application platforms. It should be pointed out that the target resource identifier is used to distinguish different target resources of the first object in the target resource package, the first sub-contract address indicates the storage address of the target resource, and the number of target resources indicates the number of target resources stored in the first contract address. In List M: the target resource corresponding to the target resource identifier B1 stores C1 resources at the first sub-contract address A1, the target resource corresponding to the target resource identifier B2 stores C2 resources at the first sub-contract address A2, the target resource corresponding to the target resource identifier B3 stores C3 resources at the first sub-contract address A3, and the target resource corresponding to the target resource identifier B4 stores C4 resources at the first sub-contract address A4.

[0115] Reference Figure 2B , shows the contract fragment in the overall contract after the deployment of target resource package No. 1. It should be pointed out that after the first object issues a target resource package deployment request for target resource package No. 1 to the blockchain node, the deployed target resource package will be stored in the overall contract. Since the target resource corresponding to the target resource identifier B1, the target resource corresponding to the target resource identifier B2, the target resource corresponding to the target resource identifier B3, and the target resource corresponding to the target resource identifier B4 are all deployed by the first object, the above target resources are all registered as the first object in the first owner of the overall contract.

[0116] Reference Figure 2C, showing the contract fragment of sub-contract A of application platform A bound before the overall contract, and the contract fragment of sub-contract B of application platform B bound before the overall contract. It should be noted that when sub-contract A of application platform A is bound before the overall contract, the contract fragment of sub-contract A records the second sub-contract address D1, target resource identifier E1 and target resource number F1 of sub-contract A, and records that the second owner of the target resource corresponding to the target resource identifier E1 in sub-contract A is the first object; it should be noted that when sub-contract B of application platform B is bound before the overall contract, the contract fragment of sub-contract B records the second sub-contract address D2, target resource identifier E2 and target resource number F2 of sub-contract B, and records that the second owner of the target resource corresponding to the target resource identifier E2 in sub-contract B is the first object. It can be clearly seen that for the target resource corresponding to the target resource identifier E1, the first object has a target resource number F1 on the application platform A, and these target resources are stored in the second sub-contract address D1; ​​for the target resource corresponding to the target resource identifier E2, the first object has a target resource number F2 on the application platform B, and these target resources are stored in the second sub-contract address D2.

[0117] Reference Figure 2D If it is desired to collectively schedule or transfer part or all of the target resource package, the first object needs to issue a binding request for multiple target resources to be bound, and call the sub-contract on the blockchain, so that the target resources to be bound that are to be collectively scheduled or transferred are uniformly transferred to the address of the overall contract by the second owner in the sub-contract. In this way, the target resources to be bound can be determined as the bound target resources bound to the overall contract. Figure 2D In the binding request, the target resources to be bound include the target resources corresponding to the target resource identifier E1 and the target resources corresponding to the target resource identifier E2; wherein, the target resources corresponding to the target resource identifier E1 are collected in the target resource package No. 1 and stored in the second contract address D1, and the number stored is the number of target resources F1; the target resources corresponding to the target resource identifier E2 are collected in the target resource package No. 1 and stored in the second contract address D2, and the number stored is the number of target resources F2.

[0118] Reference Figure 2E ,exist Figure 2D After the binding request in is issued, the sub-contract on the blockchain is called, so that the second owner of the target resources to be bound to be collectively scheduled or transferred in the sub-contract is uniformly transferred to the address of the overall contract, so as to determine the target resources to be bound as bound target resources. Figure 2CIt can be clearly seen that the target resource corresponding to the target resource identifier E1 is stored in the sub-contract A, and the number of target resources to be bound is the number of target resources F1 stored in the sub-contract A; the target resource corresponding to the target resource identifier E2 is stored in the sub-contract B, and the number of target resources to be bound is the number of target resources F2 stored in the sub-contract B. Figure 2E It shows that after the binding request is issued, the second owner of the target resource to be bound in the sub-contract is uniformly transferred to the address of the overall contract, that is, for the target resource corresponding to the target resource identifier E1 in sub-contract A, its second owner is transferred from the first object to the address of the overall contract; and, for the target resource corresponding to the target resource identifier E2 in sub-contract B, its second owner is transferred from the first object to the address of the overall contract.

[0119] Reference Figure 2F , when calling the sub-contract on the blockchain, the second owner of the target resources to be bound that are to be collectively scheduled or transferred in the sub-contract is uniformly transferred to the address of the overall contract, so as to determine the target resources to be bound as bound target resources. In order to collectively schedule or transfer the bound target resources, the first object needs to issue an ownership transfer request for the target resource package for the bound target resources, aiming to transfer the first owner of the target resource corresponding to the bound target resource to the second object. It should be noted that the "resources to be transferred" field in the resource transfer request is filled with the previously determined bound target resources, that is, the target resources corresponding to the target resource identifier E1 and the target resources corresponding to the target resource identifier E2. In addition, the "transfer target object" field in the resource transfer request is filled with the second object, aiming to collectively schedule or transfer the bound target resources to the second object.

[0120] Reference Figure 2GAfter the first object issues a request for transferring the ownership of the target resource package, in the contract fragment of the overall contract, the first owner of the target resource corresponding to the bound target resource is transferred to the second object. It needs to be clarified according to the contract fragment of the overall contract that the bound target resources corresponding to the target resource identifier E1 are collected in the target resource package No. 1. It can be determined from the list M of the target resource package No. 1 that the target resource identifier E1 corresponding to the bound target resource is equal to the target resource identifier B1, the second sub-contract address D1 of the bound target resource is equal to the first sub-contract address A1, and the number of bound target resources F1 corresponding to the bound target resource is equal to the number of resources C1. Therefore, the first owner of the target resource corresponding to the target resource identifier B1 in the overall contract needs to be transferred to the second object; similarly, the bound target resources corresponding to the target resource identifier E2 are collected in the target resource package No. 1. It can be determined from the list M of the target resource package No. 1 that the target resource identifier E2 corresponding to the bound target resource is equal to the target resource identifier B2, the second sub-contract address D2 of the bound target resource is equal to the first sub-contract address A2, and the number of bound target resources F2 corresponding to the bound target resource is equal to the number of resources C2. Therefore, the first owner of the target resource corresponding to the target resource identifier B2 in the overall contract needs to be transferred to the second object. Under normal circumstances, the target resource's owner can be determined from the second owner in the sub-contract, but if the second owner becomes the address of the overall contract, the target resource's owner must be determined by searching the first owner of the target resource in the overall contract based on the address of the overall contract. Since the second owners of the bound target resources have all been changed to the address of the overall contract, once the target resource package's ownership transfer request is received, the first owners of the bound target resources corresponding to the target resource package are all changed to the sender of the transfer request to achieve unified transfer and scheduling of the target resources, without having to make cumbersome changes on each application platform, thereby improving the efficiency of resource transfer and scheduling, as well as interoperability across application platforms.

[0121] It should be emphasized that the embodiments of the present disclosure can be applied in a variety of scenarios. Figures 2A to 2G One type of business scenario in the embodiment of the present disclosure is shown. The business scenarios to which the blockchain resource transfer processing method in the embodiment of the present disclosure can be applied may include, but are not limited to, the specific embodiments listed above.

[0122] General description of the disclosed embodiments

[0123] Reference Figure 3 According to an embodiment of the present disclosure, a blockchain resource transfer processing method is applied to a blockchain node, where the blockchain node connects multiple application platforms and maintains multiple sub-contracts corresponding to the multiple application platforms and an overall contract for the multiple application platforms on the blockchain. The blockchain resource transfer processing method may include, but is not limited to, the following steps 310 to 340.

[0124] Step 310, in response to the target resource package deployment request of the first object, deploy the target resource package in the overall contract on the blockchain, and the first owner of the target resource package is the first object;

[0125] Step 320, receiving binding requests of multiple target resources to be bound, wherein the multiple target resources to be bound are registered as first objects by second owners on multiple application platforms;

[0126] Step 330, calling the resource ownership transfer function in the sub-contract on the blockchain, so that the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as a bound target resource;

[0127] Step 340: In response to the target resource ownership transfer request of the second object, the first owner of the target resource corresponding to the bound target resource is transferred to the second object.

[0128] Steps 310 to 340 are described in detail below.

[0129] In step 310, in response to the target resource package deployment request of the first object, the target resource package is deployed in the overall contract on the blockchain, and the first owner of the target resource package is the first object. It should be noted that the target resource package deployment request is intended to aggregate the resources collected on different application platforms into a target resource package and deploy it in the overall contract. Its purpose is to integrate the resources belonging to the first object on different application platforms so as to facilitate the collective transfer and scheduling of the collected resources. Therefore, in response to the target resource package deployment request of the first object, the target resource package needs to be deployed in the overall contract on the blockchain, and the first owner of the target resource package is determined to be the first object. It should be pointed out that in the process of aggregating the resources collected on different application platforms into a target resource package, the first owner will be configured for each target resource. When the target resource is uploaded by the first object, the first owner of the target resource can be registered as the first object; when the target resource is scheduled or transferred from the first object to the second object, the first owner of the target resource can be changed from the first object to the second object.

[0130] According to some embodiments provided by the present disclosure, before step 320, the blockchain resource transfer processing method may further include, but is not limited to, the following steps:

[0131] Call authorization functions in multiple sub-contracts;

[0132] Execute the authorization function so that the sub-contract is authorized to the overall contract, so that the address of the overall contract can act as the second party registered on the application platform corresponding to the sub-contract.

[0133] It should be noted that the authorization functions in multiple sub-contracts are called and the authorization functions are executed so that the sub-contracts are authorized to the overall contract, so that the address of the overall contract can serve as the second attribution party registered on the application platform corresponding to the sub-contract. The purpose is to authorize the overall contract through the authorization function in the sub-contract so that the overall contract has the right to call the resource attribution transfer function in the sub-contract on the blockchain in subsequent steps, so that the address of the overall contract can serve as the second attribution party registered on the application platform corresponding to the sub-contract. In this way, adding an authorization barrier helps to improve the security of the disclosed blockchain resource transfer processing method, and the address of the overall contract can serve as the second attribution party registered on the application platform corresponding to the sub-contract, which helps to help the target resources be more flexibly scheduled and circulated.

[0134] In step 320, a binding request for multiple target resources to be bound is received, wherein the multiple target resources to be bound are registered as first objects on the second ownership party on multiple application platforms. It should be noted that in order to be able to perform overall scheduling or transfer of resources of multiple application platforms, the target resources to be bound of the multiple application platforms need to be bound first. It should be pointed out that the overall scheduling or transfer of resources is initiated by the first object, and the first object can control the resources belonging to him. Therefore, the target resources to be bound that need to be scheduled or transferred as a whole are registered as first objects on the second ownership party on multiple application platforms.

[0135] In step 330, the resource ownership transfer function in the sub-contract on the blockchain is called, so that the second owner of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as the bound target resource. It should be noted that the sub-contract is configured with a resource ownership transfer function for adjusting the resource ownership on the sub-contract. Therefore, in order to bind the target resources to be bound of multiple application platforms, it is necessary to call the resource ownership transfer function in the sub-contract on the blockchain, so that the second owner of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract. In this way, the second owner of the target resource to be bound needs to be specifically determined in the overall contract through the address of the overall contract, so as to determine the target resource to be bound as the bound target resource. On this basis, by operating the overall contract, it is possible to change the second owner of the bound resources on different application platforms at one time, and complete the scheduling and transfer of the bound resources.

[0136] In step 340, in response to the target resource attribution transfer request of the second object, the first attribution party of the target resource corresponding to the bound target resource is transferred to the second object. It should be emphasized that in the process of collecting resources collected on different application platforms into a target resource package, a first attribution party will be configured for each target resource. When the target resource is uploaded by the first object, the first attribution party of the target resource can be registered as the first object; when the target resource is scheduled or transferred from the first object to the second object, the first attribution party of the target resource can be changed from the first object to the second object. Therefore, after calling the resource attribution transfer function in the sub-contract on the blockchain, the second attribution party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as the bound target resource, in order to transfer the bound target resource, the first attribution party configured for the bound target resource needs to be transferred to the second object in the target resource package. In this way, the bound resources on different application platforms can be linked to the first attribution party of the overall contract according to the address of the overall contract in their second attribution party, so that the attribution of the bound resources on different application platforms is transferred to the second object, realizing the unified transfer and scheduling of target resources.

[0137] The disclosed embodiment shown by steps 310 to 340 maintains multiple sub-contracts corresponding to multiple application platforms and a general contract for multiple application platforms on the blockchain for multiple application platforms that need to enhance interoperability. The owner of the resource on the application platform is registered as the first object to which the resource belongs on the sub-contract corresponding to the application platform. In order to facilitate the collective transfer and scheduling of resources, the first object collects the resources collected on different application platforms into a target resource package, deploys the target resource package in the overall contract on the blockchain, and its first owner is set to the first object. If it is expected that part or all of the target resource package will be collectively scheduled or transferred, the sub-contract on the blockchain is called so that the second owner of the target resource to be bound in the sub-contract to be collectively scheduled or transferred is uniformly transferred to the address of the overall contract, so that the target resource to be bound can be determined as the bound target resource bound to the overall contract. Under normal circumstances, the owner of the target resource can be determined from the second owner in the sub-contract, but if the second owner becomes the address of the overall contract, it is necessary to find the first owner of the target resource in the overall contract according to the address of the overall contract to determine. Since the second party of the bound target resources has been changed to the address of the overall contract, once the attribution transfer request of the target resource package is received, the first party of the bound target resources corresponding to the target resource package is changed to the sender of the transfer request to achieve unified transfer and scheduling of the target resources without making tedious changes on each application platform respectively, thereby improving the efficiency of resource transfer and scheduling, as well as interoperability across application platforms.

[0138] Since steps 320 and 340 of the embodiment of the present disclosure have been described in detail above, step 310, steps that may be included before step 330, step 330, and steps that may be included after step 330 will be described in detail below.

[0139] Detailed description of step 310

[0140] Reference Figure 4 In some embodiments of the present disclosure, step 310 may include, but is not limited to, the following steps 410 to 440.

[0141] Step 410, in response to the target resource package deployment request of the first object, assigning a target resource package identifier to the target resource package;

[0142] Step 420, receiving an initial target resource list of the target resource package;

[0143] Step 430, recording the mapping relationship between the target resource package identifier and the initial target resource list into the first variable;

[0144] Step 440, recording the target resource package identifier, the initial target resource list, and the first variable into the overall contract on the blockchain.

[0145] Steps 410 to 440 are described in detail below.

[0146] In step 410, in response to the target resource package deployment request of the first object, a target resource package identifier is assigned to the target resource package. It should be emphasized that the target resource package deployment request is intended to aggregate the resources collected on different application platforms into a target resource package and deploy it in the overall contract. Its purpose is to integrate the resources belonging to the first object on different application platforms to facilitate the collective transfer and scheduling of the collected resources. In order to distinguish different target resource packages, it is necessary to assign a target resource package identifier to the target resource package. It should be understood that there are various types of target resource package identifiers, which can be an identification number of the target resource package or an identification string of the target resource package.

[0147] In step 420, the initial target resource list of the target resource package is received. It should be noted that the target resource list is used to record the resource storage status of the first object on different application platforms, and the initial target resource list is the target resource list initially formed after the resources collected on different application platforms are aggregated into target resource packages. It should be clear that the initial target resource list is the initial target resource list, which records the number of target resources initially registered by the first object on different application platforms, that is, the number of registered target resources.

[0148] In some more specific embodiments, for a certain target resource, the target resource list may record the target resource identifier that matches the target resource, the first sub-contract address of the target resource, and the number of resources corresponding to the target resource. The target resource identifier is used to distinguish different target resources in the target resource package, the first sub-contract address is the storage address of the target resource, and the number of resources is the number of resources stored in the first sub-contract address of the target resource. It should be understood that the target resource list may record a variety of contents, which may include, but not be limited to, the specific embodiments listed above.

[0149] In some more specific embodiments, after step 420, the blockchain resource transfer processing method may also include, but is not limited to: determining that the first sub-contract address corresponding to the initial target resource is of the first type, and the first type indicates that the initial target resource cannot be copied; verifying that the registration number of the initial target resource is 1. It should be noted that the sub-contract address may include the first type, wherein the first type indicates that the initial target resource cannot be copied. Therefore, in order to ensure that the registration number of the initial target resource matches the first type, it is necessary to verify that the registration number of the initial target resource is 1. In this way, before receiving the binding request of multiple target resources to be bound at 320, it can be determined that the registration number of the initial target resource matches the first type, and then the unqualified initial target resource list can be screened out, reducing the occurrence of invalid resource binding processes, which helps to improve the accuracy and efficiency of resource binding.

[0150] In step 430 to step 440, the mapping relationship between the target resource package identifier and the initial target resource list is recorded in the first variable, and the target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain. It should be noted that after receiving the initial target resource list of the target resource package, the mapping relationship between the target resource package identifier and the initial target resource list needs to be recorded in the first variable. On this basis, since the first variable records the mapping relationship between the target resource package identifier and the initial target resource list, recording the target resource package identifier, the initial target resource list, and the first variable in the overall contract on the blockchain can facilitate the subsequent scheduling and transfer of target resources in the target resource package.

[0151] Through steps 410 to 440 of the embodiment of the present disclosure, the specific steps of deploying the target resource package in the overall contract on the blockchain are described. Since in the process of deploying the target resource package in the overall contract on the blockchain, the target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain, this can facilitate the subsequent scheduling and transfer of target resources in the target resource package.

[0152] The steps that may be included before step 330 in the embodiment of the present disclosure

[0153] Reference Figure 5 After receiving the binding requests of multiple target resources to be bound in step 320, and before calling the resource ownership transfer function in the sub-contract on the blockchain in 330, the blockchain resource transfer processing method may also include, but is not limited to, the following steps 510 to 530.

[0154] Step 510, obtaining the target resource package identifier for the binding request;

[0155] Step 520, based on the target resource package identifier, search for the first variable to obtain an initial target resource list;

[0156] Step 530: Determine whether a plurality of target resources to be bound fall into the initial target resource list.

[0157] Steps 510 to 530 are described in detail below.

[0158] In step 510, the target resource bundle identifier of the binding request is obtained. It should be noted that the binding request of the target resource to be bound is configured with the target resource bundle identifier to which the resource to be bound belongs. Based on this, it is necessary to obtain the target resource bundle identifier of the binding request in order to determine the search index for searching the corresponding initial target resource list.

[0159] In some more specific embodiments, before obtaining the target resource package identifier for the binding request, the blockchain resource transfer processing method may also include: obtaining the first issuer of the binding request; determining that the first issuer is the first object. Since the object that issues the binding request may not be the same object as the object that deploys the target resource package, when it is clear that the target resource package is deployed by the first object, the first issuer of the binding request can be obtained, and then the first issuer can be determined to be the first object, and subsequent steps can be performed after the determination. In this way, the security of the disclosed blockchain resource transfer processing method can be further improved.

[0160] In step 520, based on the target resource package identifier, the first variable is searched to obtain the initial target resource list. It should be noted that, in the process of deploying the target resource package, the target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain, and the first variable records the mapping relationship between the target resource package identifier and the initial target resource list. Therefore, based on the target resource package identifier, the first variable is searched on the overall contract to obtain the initial target resource list that matches the target resource package identifier.

[0161] In step 530, it is determined that multiple target resources to be bound fall into the initial target resource list. After searching the first variable based on the target resource package identifier and obtaining the initial target resource list, it can be clearly seen that multiple target resources to be bound can be found in the initial target resource list of the target resource package in the overall contract. It should be emphasized that the resources collected by the first object on different application platforms are compiled into target resource packages and deployed in the overall contract. On this basis, multiple target resources to be bound that need to be bound fall into the initial target resource list, which means that these target resources to be bound that need to be bound can be found in the target resource package deployed by the overall contract.

[0162] In the embodiment of the present disclosure shown in steps 510 to 530, before calling the resource ownership transfer function in the sub-contract on the blockchain, it is first clarified that multiple target resources to be bound fall into the initial target resource list to ensure that the target resources to be bound can be found in the overall contract. On this basis, the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is subsequently transferred to the address of the overall contract, which will help improve the accuracy and efficiency of resource binding.

[0163] In some more specific embodiments, if there is a situation where the target resource to be bound does not fall into the initial target resource list, corresponding error information can be generated according to this situation and fed back to the first object.

[0164] Reference Figure 6 The initial target resource list includes, for each initial target resource: the first sub-contract address corresponding to the application platform where the initial target resource is registered, the initial target resource identifier, and the number of initial target resources registered on the application platform; the binding request includes, for each target resource to be bound, the second sub-contract address corresponding to the application platform where the target resource to be bound is registered, the identifier of the target resource to be bound, and the number to be bound. It should be noted that the number to be bound refers to the number of target resources to be bound. Step 530 may include, but is not limited to, the following steps 610 to 620.

[0165] Step 610, if the first sub-contract address of an initial target resource in the initial target resource list is equal to the second sub-contract address of the target resource to be bound, and the initial target resource identifier is equal to the target resource to be bound identifier of the target resource to be bound, then the initial target resource is determined as the target resource to be examined;

[0166] Step 620: Based on the registered number of the target resources to be inspected and the number of the target resources to be bound, it is determined whether the target resources to be bound fall into the initial target resource list.

[0167] Steps 610 to 620 are described in detail below.

[0168] It should be emphasized that the resources collected by the first object on different application platforms are aggregated into a target resource package and deployed in the overall contract. On this basis, multiple target resources to be bound fall into the initial target resource list, which means that these target resources to be bound can be found in the target resource package deployed by the overall contract.

[0169] In step 610, if the first sub-contract address of an initial target resource in the initial target resource list is equal to the second sub-contract address of the target resource to be bound, and the initial target resource identifier is equal to the target resource identifier to be bound of the target resource to be bound, then the initial target resource is determined as the target resource to be investigated. It should be pointed out that the initial target resource list records the first sub-contract address and the initial target resource identifier corresponding to the application platform where the initial target resource is registered for each initial target resource; the binding request records the second sub-contract address and the target resource identifier to be bound corresponding to the application platform where the target resource to be bound is registered for each target resource to be bound. Therefore, if the first sub-contract address of an initial target resource in the initial target resource list is equal to the second sub-contract address of the target resource to be bound, and the initial target resource identifier is equal to the target resource identifier to be bound of the target resource to be bound, it means that there is a target resource to be bound that falls into the initial target resource list, so the initial target resource can be determined as the target resource to be investigated.

[0170] In step 620, based on the registered number of the target resources to be investigated and the number of target resources to be bound, it is determined that the target resources to be bound fall into the initial target resource list. It should be noted that the initial target resource list records the number of registrations of the initial target resource on the application platform for each initial target resource; the binding request includes the number of target resources to be bound for each target resource to be bound. Therefore, after determining the registered number of the target resources to be investigated and the number of target resources to be bound, it can be further determined that the target resources to be bound fall into the initial target resource list.

[0171] In some more specific embodiments, the registered number of the target resources to be investigated is greater than or equal to the number of target resources to be bound, so it can be determined that all the target resources to be bound fall into the initial target resource list. In other more specific embodiments, the registered number of the target resources to be investigated is less than the number of target resources to be bound, so it can be determined that part of the target resources to be bound falls into the initial target resource list.

[0172] It should be understood that there are various embodiments for determining whether the target resources to be bound fall into the initial target resource list based on the registered number of target resources to be examined and the number of target resources to be bound. The embodiments may include, but are not limited to, the specific embodiments listed above.

[0173] The embodiment of the present disclosure shown in step 610 to step 620 can determine whether the target resource to be bound falls into the initial target resource list based on the first sub-contract address, the initial target resource identifier, the number of initial target resources registered on the application platform, and the second sub-contract address, the target resource identifier to be bound, and the number to be bound corresponding to the application platform where the target resource to be bound is registered. This helps to improve the accuracy and efficiency of resource binding.

[0174] Reference Figure 7 , Figure 7 An exemplary embodiment for determining whether the target resource to be bound falls into the initial target resource list is shown. The target resource to be bound targeted by the binding request includes: the second sub-contract address D1 corresponding to the application platform where the target resource to be bound is registered, the target resource identifier E1 (virtual equipment A), and the number to be bound F1 (60); the second sub-contract address D2 corresponding to the application platform where the target resource to be bound is registered, the target resource identifier E2 (virtual equipment B), and the number to be bound F2 (30). It should be noted that since the target resource package identifier corresponding to the binding request is 1, the first variable is searched based on the target resource package identifier No. 1 to obtain the initial target resource list of target resource package No. 1.

[0175] It should be clear that the first sub-contract address A1 of an initial target resource in the initial target resource list is equal to the second sub-contract address D1 of the target resource to be bound, and the initial target resource identifier B1 (virtual equipment A) is equal to the target resource identifier E1 (virtual equipment A) of the target resource to be bound, therefore, the corresponding initial target resource can be determined as the target resource to be examined. Based on the number of target resources to be bound corresponding to the target resource identifier E1 (virtual equipment A): the number of resource registrations F1 (60), and based on the number of target resources to be examined corresponding to the target resource identifier B1 (virtual equipment A): the number of resource registrations C1 (100), it can be determined that the target resource corresponding to the target resource identifier E1 (virtual equipment A) falls into the initial target resource list of the target resource package No. 1. Similarly, the first sub-contract address A2 of an initial target resource in the initial target resource list is equal to the second sub-contract address D1 of the target resource to be bound, and the initial target resource identifier B2 (virtual equipment B) is equal to the target resource identifier E2 (virtual equipment B) of the target resource to be bound, therefore, the corresponding initial target resource can be determined as the target resource to be examined. Based on the number of target resources to be bound corresponding to the target resource identifier E2 (virtual equipment B): the number of resource registrations F2 (30), and based on the number of target resources to be examined corresponding to the target resource identifier B2 (virtual equipment B): the number of resource registrations C2 (50), it can be determined that the target resource corresponding to the target resource identifier E2 (virtual equipment B) falls into the initial target resource list of target resource package No. 1.

[0176] It should be understood that Figure 7 One embodiment of determining whether the target resource to be bound falls into the initial target resource list is shown. Determining whether the target resource to be bound falls into the initial target resource list may include multiple embodiments, which are not limited to the above examples.

[0177] Reference Figure 8 , step 620 may include, but is not limited to, the following steps 810 to 820.

[0178] Step 810, obtaining a second variable, the second variable indicating the bound number in the registered number of the initial target resource;

[0179] Step 820: If the sum of the second variable and the number to be bound is not greater than the registered number, determine that the target resource to be bound falls into the initial target resource list, and increase the number to be bound to the second variable.

[0180] Steps 810 to 820 are described in detail below.

[0181] In step 810 to step 820, a second variable is obtained, and the second variable indicates the number of bound resources in the registered number of the initial target resource. If the sum of the second variable and the number to be bound is not greater than the registered number, it is determined that the target resource to be bound falls into the initial target resource list, and the number to be bound is increased on the second variable. It should be noted that the second variable indicates the number of bound resources in the registered number of the initial target resource. It should be clarified that the number of bound resources here refers to the number of bound resources before the current round of binding of the target resource. Therefore, after obtaining the second variable, it can be determined whether the sum of the bound number and the number to be bound is greater than the registered number based on the number of bound resources and the number to be bound of the initial target resource. If the sum of the second variable and the number to be bound is not greater than the registered number, it means that the number of resources that have not been bound in the registered number can support multiple binding requests for the number to be bound. At this time, it can be determined that the target resource to be bound falls into the initial target resource list, and the number to be bound is increased on the second variable. It should be clarified that increasing the number to be bound on the second variable specifically refers to increasing the number to be bound in the number of bound resources of the second variable to update the number of bound resources in the registered number.

[0182] In this way, through the embodiment of the present disclosure shown in steps 810 to 820, in the process of determining whether the target resources to be bound fall into the initial target resource list, it can be determined in advance that the number of unbound target resources is greater than the number of target resources to be bound, thereby reducing the occurrence of invalid resource binding processes and helping to improve the accuracy and efficiency of resource binding.

[0183] Reference Fig. 9 , showing an embodiment of determining whether the target resource to be bound falls into the initial target resource list. Fig. 9In the process, it is necessary to determine whether a "virtual armor" falls into the initial target resource list. For this purpose, the second variable is obtained. Since the number of registrations corresponding to the "virtual armor" in the initial target resource is 100, the number of bound in the registration number is 45, and the corresponding number of bound in the registration number is 5, the second variable indicates that the number of bound in the registration number is 45. On this basis, since the number of "virtual armor" to be bound is 35, the number of bound in the registration number is 45, the number of bound in the registration number is 35, and the number of registered is 100, where the sum of the number of bound in the registration number is 80, which is less than the number of registered number 100, it can be determined that the target resource to be bound falls into the initial target resource list. In this way, in the process of determining that the target resource to be bound falls into the initial target resource list, it can be determined in advance that the number of unbound target resources is greater than the number of target resources to be bound, reducing the occurrence of invalid resource binding processes, which helps to improve the accuracy and efficiency of resource binding. In addition, the number to be bound is increased on the second variable, specifically, the number to be bound 35 is added to the bound number 45 of the second variable, and the bound number of the second variable is updated to 80, so as to update the bound number of "virtual armor" indicated in the second variable.

[0184] Detailed description of step 330

[0185] Reference Fig.10 , step 330 may include, but is not limited to, the following steps 1010 to 1020.

[0186] Step 1010: if the second sub-contract address of the target resource to be bound is of the first type, and the first type indicates that the initial target resource cannot be copied, the second attribution party of the target resource to be bound is transferred to the address of the overall contract;

[0187] Step 1020: If the second sub-contract address of the target resource to be bound is of the second type, and the second type indicates that the initial target resource is replicable, the second attribution party of the target resource to be bound of the number to be bound in the target resource to be bound is transferred to the address of the overall contract.

[0188] Steps 1010 to 1020 are described in detail below.

[0189] It should be emphasized that the application platform of the embodiment of the present disclosure refers to the network platform that carries the blockchain application, and the sub-contract refers to the business contract that stores virtual resources in the application platform. It should be pointed out that on the application platform, some data protocol standards can be used to perform specific data processing on virtual resources, so that these virtual resources have uniqueness and irreplaceability. Based on different data protocol standards, the types of specific data processing for virtual resources are also different. Therefore, based on the differences in the data protocol standards followed by different sub-contracts, the sub-contract address can be either the first type or the second type. Among them, the first type of initial target resource is not replicable, and the second type indicates that the initial target resource is replicable.

[0190] In step 1010, if the second sub-contract address of the target resource to be bound is of the first type, and the first type indicates that the initial target resource cannot be copied, the second attribution party of the target resource to be bound is transferred to the address of the overall contract. It should be noted that the first type indicates that the initial target resource cannot be copied, which means that the initial target resource of the first type is limited to 1 or 0. In this case, this initial target resource is used as the target resource to be bound, and then the second attribution party of the target resource to be bound is transferred to the address of the overall contract, so as to complete the binding of the target resource.

[0191] In step 1020, if the second sub-contract address of the target resource to be bound is of the second type, and the second type indicates that the initial target resource is replicable, the second attribution party of the target resource to be bound of the number to be bound in the target resource to be bound is transferred to the address of the overall contract. It should be noted that the first type indicates that the initial target resource is not replicable, which means that the initial target resource of the first type is not limited to 1. In this case, it is necessary to determine the number of target resources to be bound from the initial target resource. In this way, the second attribution party of the number of target resources to be bound is transferred to the address of the overall contract to complete the binding of the target resource.

[0192] Through the embodiment of the present disclosure shown in step 1010 to step 1020, the second attribution party of the target resource to be bound in the target resource to be bound can be transferred to the address of the overall contract according to the type of the second sub-contract address. In this way, the differences in data protocol standards between different application platforms can be flexibly dealt with. Even if some of the multiple application platforms storing virtual resources are of the first type and some are of the second type, and the virtual resources stored on these different platforms are difficult to integrate, the embodiment of the present disclosure shown in step 1010 to step 1020 can be targeted to transfer the second attribution party of the target resource to be bound in the target resource to be bound according to the type of the second sub-contract address to the address of the overall contract, bind the sub-contract to the overall contract, and link the second attribution party of the sub-contract to the first attribution party of the overall contract, so that the operation of one-time complete resource scheduling or transfer can be realized by subsequently changing the first attribution party of the overall contract. In this way, there is no need to make cumbersome changes on each application platform, which improves the efficiency of resource transfer and scheduling, as well as the interoperability across application platforms.

[0193] Reference Fig.11A Before binding the target resource, the first type of virtual equipment A is stored in the sub-contract A corresponding to the second sub-contract address A. Since the initial target resource of the first type cannot be copied, the number of target resources to be bound corresponding to the virtual equipment A can only be 1. It should be noted that the second owner of the virtual equipment A is registered as the first object in the sub-contract A; the second sub-contract address A of the target resource virtual equipment A to be bound is of the first type, and the first type indicates that the virtual equipment A cannot be copied, so the second owner of the virtual equipment A can be transferred to the address of the overall contract;

[0194] Reference Fig. 11B In the sub-contract B corresponding to the second sub-contract address B, the second type of virtual equipment B is stored. Since the second type of initial target resource can be copied, the number of target resources to be bound corresponding to the virtual equipment B is not limited to 1. Fig. 11B In the embodiment of , the number of target resources to be bound corresponding to virtual equipment B is 55. It should be noted that the second ownership parties of the 55 virtual equipment B are all registered as the first object in the sub-contract B; the second sub-contract address of the target resource virtual equipment B to be bound is of the second type, and the second type indicates that the virtual equipment B is replicable, so the second ownership parties of the 55 virtual equipment B in the target resource to be bound can all be transferred to the address of the overall contract;

[0195] Reference Fig. 11CAccording to some more specific embodiments, the sub-contract B corresponding to the second sub-contract address B stores the second type of virtual equipment B. Since the second type of initial target resource can be copied, the number of target resources to be bound corresponding to the virtual equipment B is not limited to 1. Fig. 11B In the embodiment of the present invention, the number of target resources to be bound corresponding to the virtual equipment B is 155. It should be noted that if the second sub-contract address of the target resource to be bound is of the second type, the second type indicates that the initial target resource can be copied, but the number of target resources to be bound in the target resource to be bound 155 is greater than the number of registered resources in the initial target resource list 100, then a corresponding error message can be generated according to this situation and fed back to the first object.

[0196] The steps that may be included after step 330 in the embodiment of the present disclosure

[0197] Reference Fig.12 After step 330, the blockchain resource transfer processing method disclosed in the present invention may also include, but is not limited to, the following steps 1210 to 1220.

[0198] Step 1210, receiving an unbinding request for multiple to-be-unbound target resources among multiple bound target resources;

[0199] Step 1220, calling the resource ownership transfer function in the sub-contract on the blockchain, so that the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract is transferred to the first object.

[0200] Steps 1210 to 1220 are described in detail below.

[0201] It should be noted that in some embodiments, the resource ownership transfer function in the sub-contract on the blockchain is called to transfer the target resource to be bound to the second ownership party on the application platform corresponding to the sub-contract to the address of the overall contract, so that the target resource to be bound is determined as a bound target resource. In the process, there may be binding errors and the need to adjust the binding scheme. In this regard, steps 1210 to 1230 provide some embodiments, and after a batch of target resources are bound, some or all of the target resources can be unbound, so as to improve the flexibility of resource scheduling or transfer.

[0202] In step 1210 to step 1220, an unbinding request for multiple target resources to be unbound among multiple bound target resources is received, and a resource ownership transfer function in a sub-contract on the blockchain is called to transfer the target resource to be unbound from the second owner on the application platform corresponding to the sub-contract to the first object. It should be emphasized that a resource ownership transfer function is configured in the sub-contract to adjust the resource ownership on the sub-contract. It should be pointed out that when a binding error occurs, the binding scheme needs to be adjusted, etc., it is necessary to unbind part or all of the multiple bound target resources. Therefore, it is first necessary to receive an unbinding request for multiple target resources to be unbound among multiple bound target resources, and on this basis, call the resource ownership transfer function in the sub-contract on the blockchain to transfer the target resource to be unbound from the second owner on the application platform corresponding to the sub-contract back to the first object. In this way, it is possible to unbind part or all of the multiple bound target resources, thereby improving the flexibility of resource scheduling or transfer.

[0203] Reference Fig.13 Before step 1220, the blockchain resource transfer processing method disclosed in the present invention may also include, but is not limited to, the following steps 1310 to 1330.

[0204] Step 1310, obtaining the target resource package identifier of the unbinding request;

[0205] Step 1320, based on the target resource package identifier, search for the first variable to obtain an initial target resource list;

[0206] Step 1330: Determine whether a plurality of target resources to be unbound fall into the initial target resource list.

[0207] Steps 1310 to 1330 are described in detail below.

[0208] In step 1310, the target resource package identifier of the unbinding request is obtained. It should be noted that the unbinding request of the target resource to be unbound is configured with the target resource package identifier to which the resource to be unbound belongs. Based on this, it is necessary to obtain the target resource package identifier of the unbinding request in order to determine the search index for searching the corresponding initial target resource list.

[0209] In some more specific embodiments, before obtaining the target resource package identifier for the unbinding request, the blockchain resource transfer processing method may also include: obtaining the second issuer of the unbinding request; determining that the second issuer is the first object. Since the object that issues the unbinding request may not be the same object as the object that issues the binding request and the object that deploys the target resource package, when it is clear that the target resource package is deployed by the first object, the second issuer of the unbinding request can be obtained, and then the second issuer can be determined to be the first object, and subsequent steps can be performed after the determination. In this way, the security of the disclosed blockchain resource transfer processing method can be further improved.

[0210] In step 1320, based on the target resource package identifier, the first variable is searched to obtain the initial target resource list. It should be noted that, in the process of deploying the target resource package, the target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain, and the first variable records the mapping relationship between the target resource package identifier and the initial target resource list. Therefore, based on the target resource package identifier, the first variable is searched on the overall contract to obtain the initial target resource list that matches the target resource package identifier.

[0211] In step 1330, it is determined that multiple target resources to be unbound fall into the initial target resource list. After searching the first variable based on the target resource package identifier and obtaining the initial target resource list, it can be clearly seen that multiple target resources to be unbound can be found in the initial target resource list of the target resource package in the overall contract. It should be emphasized that the resources collected by the first object on different application platforms are compiled into target resource packages and deployed in the overall contract. On this basis, multiple target resources to be unbound that need to be unbound fall into the initial target resource list, which means that these target resources to be unbound that need to be unbound can be found in the target resource package deployed by the overall contract.

[0212] In the embodiment of the present disclosure shown in step 1310 to step 1330, before calling the resource ownership transfer function in the sub-contract on the blockchain, it is first clarified that multiple target resources to be unbound fall into the initial target resource list to ensure that the target resources to be unbound can be found in the overall contract. On this basis, the second ownership party of the target resource to be unbound on the application platform corresponding to the sub-contract is subsequently transferred back to the first object, which will help improve the accuracy and efficiency of resource unbinding.

[0213] In some more specific embodiments, if there is a situation where the target resource to be unbound does not fall into the initial target resource list, corresponding error information can be generated according to this situation and fed back to the first object.

[0214] In some exemplary embodiments, the initial target resource list includes, for each initial target resource, a first sub-contract address corresponding to the application platform where the initial target resource is registered, and an initial target resource identifier; and the unbinding request includes, for each target resource to be unbound, a third sub-contract address corresponding to the application platform where the target resource to be unbound is registered, and an identifier of the target resource to be unbound. Step 130 may include, but is not limited to:

[0215] If the first sub-contract address of an initial target resource in the initial target resource list is equal to the third sub-contract address of the target resource to be unbound, and the initial target resource identifier is equal to the target resource identifier to be unbound of the target resource to be unbound, then it is determined that the target resource to be unbound falls into the initial target resource list.

[0216] It should be emphasized that the resources collected by the first object on different application platforms are aggregated into a target resource package and deployed in the overall contract. On this basis, multiple target resources to be unbound that need to be unbound fall into the initial target resource list, which means that these target resources to be unbound that need to be unbound can be found in the target resource package deployed by the overall contract.

[0217] It should be pointed out that, for each initial target resource in the initial target resource list, the first sub-contract address corresponding to the application platform where the initial target resource is registered and the initial target resource identifier are recorded; for each target resource to be unbound, the unbinding request records the third sub-contract address corresponding to the application platform where the target resource to be unbound is registered and the target resource identifier to be unbound. Therefore, if the first sub-contract address of an initial target resource in the initial target resource list is equal to the third sub-contract address of the target resource to be unbound, and the initial target resource identifier is equal to the target resource identifier to be unbound of the target resource to be unbound, it means that there is a target resource to be unbound that falls into the initial target resource list, so the initial target resource can be determined as the target resource to be examined. Determining that the target resource to be unbound falls into the initial target resource list in the above manner helps to improve the accuracy and efficiency of resource unbinding.

[0218] Reference Fig.14 The unbinding request may also include the number of resources to be unbound for each target resource to be unbound. After step 1330, the blockchain resource transfer processing method may also include, but is not limited to, the following.

[0219] Step 1410, obtaining a second variable, where the second variable indicates the bound number of the initial target resource;

[0220] Step 1420, determining that the number to be unbound is not greater than a second variable;

[0221] After 1220, the blockchain resource transfer processing method may further include:

[0222] Step 1430, subtract the number of to-be-unbound from the second variable.

[0223] Steps 1410 to 1430 are described in detail below.

[0224] In step 1410 to step 1420, a second variable is obtained, and the second variable indicates the bound number of the initial target resources. It is determined that the number to be unbound is not greater than the second variable. It should be noted that the second variable indicates the bound number in the registered number of the initial target resources. It should be clear that the bound number here refers to the bound number before the target resources are unbound in this round. Therefore, after obtaining the second variable, it can be determined whether the number to be unbound is not greater than the second variable, that is, the bound number before the target resources are unbound in this round, based on the bound number of the target resources and the number to be unbound. If the number to be unbound is not greater than the second variable, it means that the bound number can support the unbinding request of all or part of the target resources. At this time, it can be determined that the target resources to be unbound fall into the list of initial target resources.

[0225] Step 1430, subtract the number of unbound resources from the second variable. It should be noted that after calling the resource ownership transfer function in the sub-contract on the blockchain, so that the target resource to be unbound is transferred from the second ownership party on the application platform corresponding to the sub-contract to the first object, it can be clearly seen that the number of bound target resources needs to be changed, so the number of unbound resources is subtracted from the second variable to complete the response to the unbinding request.

[0226] In this way, through the embodiment of the present disclosure shown in steps 1410 to 1430, before calling the resource ownership transfer function in the sub-contract on the blockchain to unbind the target resources, it can be determined in advance that the number of target resources to be unbound is greater than the number of bound target resources, thereby reducing the occurrence of invalid resource unbinding processes and helping to improve the accuracy and efficiency of resource unbinding.

[0227] Reference Fig.15 , shows an embodiment of unbinding the target resource after determining that the target resource to be unbound falls into the initial target resource list. Fig.15In the example, 80 pieces of "virtual armor" that have been bound need to be unbound, and 20 pieces of "virtual armor" need to be unbound. To this end, the second variable needs to be obtained first, where the second variable indicates the number of bound initial target resources 80; then it is determined that the number to be unbound 20 is less than the second variable 80; further, the resource ownership transfer function in the sub-contract on the blockchain is called to transfer the target resource to be unbound from the second ownership party on the application platform corresponding to the sub-contract to the first object; further, the number to be unbound 20 is subtracted from the second variable 80. In this way, before calling the resource ownership transfer function in the sub-contract on the blockchain to unbind the target resource, it can be determined in advance that the number of target resources to be unbound is greater than the number of bound target resources, reducing the occurrence of invalid resource unbinding processes, which helps to improve the accuracy and efficiency of resource unbinding.

[0228] Reference Fig.16 The unbinding request may also include the number of resources to be unbound for each target resource to be unbound. After step 1330, the blockchain resource transfer processing method may also include, but is not limited to, the following steps 1610 to 1620.

[0229] Step 1610: If the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, then call the get-owner function in the sub-contract on the blockchain to determine that the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract is the address of the overall contract;

[0230] Step 1620, if the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, then the get-owner function in the sub-contract on the blockchain is called to determine that the number of target resources whose second owner is the address of the overall contract on the application platform corresponding to the sub-contract is not less than the number to be unbound.

[0231] Steps 1610 to 1620 are described in detail below.

[0232] It should be emphasized that the application platform of the embodiment of the present disclosure refers to the network platform that carries the blockchain application, and the sub-contract refers to the business contract that stores virtual resources in the application platform. It should be pointed out that on the application platform, some data protocol standards can be used to perform specific data processing on virtual resources, so that these virtual resources have uniqueness and irreplaceability. Based on different data protocol standards, the types of specific data processing for virtual resources are also different. Therefore, based on the differences in the data protocol standards followed by different sub-contracts, the sub-contract address can be either the first type or the second type. Among them, the first type of initial target resource is not replicable, and the second type indicates that the initial target resource is replicable.

[0233] In step 1610, if the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, then the Get Attribution Party function in the sub-contract on the blockchain is called to determine that the second attribution party of the target resource to be unbound on the application platform corresponding to the sub-contract is the address of the overall contract. It should be noted that the first type indicates that the initial target resource cannot be copied, which means that the bound target resources of the first type are limited to 1 or 0. In this case, the Get Attribution Party function in the sub-contract on the blockchain can be called to determine that the second attribution party of the target resource to be unbound on the application platform corresponding to the sub-contract is the address of the overall contract. Further, the second attribution party of the target resource to be unbound is transferred back to the first object to complete the unbinding of the target resource.

[0234] In step 1620, if the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, then the Get Attribution Party function in the sub-contract on the blockchain is called to determine that the number of target resources whose second attribution party is the address of the overall contract on the application platform corresponding to the sub-contract is not less than the number to be unbound. It should be noted that the first type indicates that the initial target resource is not replicable, which means that the bound target resources of the first type are not limited to 1. In this case, it is necessary to call the Get Attribution Party function in the sub-contract on the blockchain to determine that the number of target resources whose second attribution party is the address of the overall contract on the application platform corresponding to the sub-contract is not less than the number to be unbound. Further, the second attribution party of the number of target resources to be unbound is transferred back to the first object to complete the unbinding of the target resource.

[0235] Through the embodiment of the present disclosure shown in steps 1610 to 1620, the second belonging party of the target resource to be unbound and the number of target resources to be unbound in the target resource to be unbound can be transferred to the first object according to the type of the third sub-contract address. In this way, the differences in data protocol standards between different application platforms can be flexibly dealt with. Even if some of the multiple application platforms storing virtual resources are of the first type and some are of the second type, and the virtual resources stored on these different platforms are difficult to integrate, the embodiment of the present disclosure shown in steps 1610 to 1620 can be targeted to transfer the second belonging party of the target resource to be unbound and the number of target resources to be unbound in the target resource to be unbound back to the first object according to the type of the third sub-contract address, and the unbinding of target resources on different application platforms can be achieved at one time. In this way, there is no need to make cumbersome changes on each application platform separately, which improves the efficiency of resource transfer and scheduling, as well as the interoperability across application platforms.

[0236] Reference Fig.17Step 1430 transfers the target resource to be unbound from the second owner on the application platform corresponding to the sub-contract to the first object, which may include, but is not limited to, the following steps 1710 to 1720.

[0237] Step 1710: if the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, the second owner of the target resource to be unbound is transferred to the first object;

[0238] Step 1720: If the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, the second owner of the target resource to be unbound of the bound target resource is transferred to the first object.

[0239] Steps 1710 to 1720 are described in detail below.

[0240] In step 1710, if the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, the second owner of the target resource to be unbound is transferred to the first object. It should be noted that the first type indicates that the initial target resource cannot be copied, which means that the initial target resource of the first type is limited to 1 or 0. When it is determined that the third sub-contract address of the target resource to be unbound is of the first type, the second owner of the target resource to be unbound is transferred to the address of the overall contract, and the target resource can be unbound.

[0241] In step 1720, if the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, the second attribution party of the target resource to be unbound of the number to be unbound among the unbound target resources is transferred to the first object. It should be noted that the first type indicates that the initial target resource is not replicable, which means that the initial target resource of the first type is not limited to 1. When it is determined that the third sub-contract address of the target resource to be unbound is of the second type, the second attribution party of the target resource to be unbound of the number to be unbound among the unbound target resources is transferred to the first object.

[0242] In this way, through the embodiment of the present disclosure shown in steps 1710 to 1720, the second owner of the number of target resources to be unbound can be transferred from the address of the overall contract back to the first object to complete the unbinding of the target resources, reflecting the flexibility of the overall scheduling or transfer of target resource information.

[0243] Reference Fig.18 Before step 340, the blockchain resource transfer processing method may also include, but is not limited to, the following steps 1810 to 1820.

[0244] Step 1810, receiving a target resource package viewing request of a second object, the target resource package viewing request having a target resource package identifier;

[0245] Step 1820, based on the target resource package identifier, search for the first variable to obtain an initial target resource list;

[0246] Step 1830: Send the initial target resource list to the second object.

[0247] Steps 1810 to 1830 are described in detail below.

[0248] It should be noted that, before the first owner of the bound target resource corresponding to the target resource is transferred to the second object in response to the target resource ownership transfer request of the second object, the second object may need to confirm the resource ownership corresponding to the target resource ownership transfer request. In this regard, the embodiment of the present disclosure provides the implementation shown in steps 1810 to 1830 to achieve this effect.

[0249] In step 1810, a target resource package viewing request of the second object is received, and the target resource package viewing request has a target resource package identifier. It should be noted that the target resource package viewing request is configured with the target resource package identifier to which the resource to be viewed belongs, based on which it is necessary to obtain the target resource package identifier targeted by the viewing request, in order to determine a search index for searching the corresponding initial target resource list.

[0250] In some more specific embodiments, before obtaining the target resource package identifier for the viewing request, the blockchain resource transfer processing method may also include: obtaining the third issuer of the viewing request; determining that the third issuer is the second object. Since the object that issues the viewing request may not be the same object as the target object of the target resource package flow, when it is clear that the second object is the target object of the resource flow, the third issuer of the viewing request can be obtained, and then the third issuer can be determined to be the second object, and subsequent steps can be performed after the determination. In this way, the security of the disclosed blockchain resource transfer processing method can be further improved.

[0251] In step 1820, based on the target resource package identifier, the first variable is searched to obtain the initial target resource list. It should be noted that, in the process of deploying the target resource package, the target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain, and the first variable records the mapping relationship between the target resource package identifier and the initial target resource list. Therefore, based on the target resource package identifier, the first variable is searched on the overall contract to obtain the initial target resource list that matches the target resource package identifier.

[0252] Step 1830, sending the initial target resource list to the second object. After searching the first variable based on the target resource package identifier and obtaining the initial target resource list, it can be clearly seen that multiple target resources to be viewed can be found in the initial target resource list of the target resource package in the overall contract, which means that the resources that the second object needs to view are collected into a target resource package by the first object and deployed in the overall contract. On this basis, the multiple target resources to be viewed that need to be viewed fall into the initial target resource list, so the initial target resource list can be sent to the second object for it to confirm the resource ownership corresponding to the target resource ownership transfer request. In this way, the security of the disclosed blockchain resource transfer processing method can be further improved.

[0253] Device description of the present embodiment

[0254] According to one aspect of the present disclosure, a blockchain resource transfer processing device 1900 is provided, and the blockchain resource transfer processing device 1900 is located in a blockchain node, and the blockchain node is connected to multiple application platforms, and multiple branch contracts corresponding to the multiple application platforms and a general contract for the multiple application platforms are maintained on the blockchain. The blockchain resource transfer processing device 1900 includes:

[0255] A resource deployment unit 1910 is configured to deploy the target resource package in the overall contract on the blockchain in response to a target resource package deployment request of the first object, wherein the first owner of the target resource package is the first object;

[0256] The first receiving unit 1920 is configured to receive binding requests of multiple target resources to be bound, wherein the multiple target resources to be bound are registered as first objects by second owners on multiple application platforms;

[0257] The resource binding unit 1930 is used to call the resource ownership transfer function in the sub-contract on the blockchain, so that the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as a bound target resource;

[0258] The first transfer execution unit 1940 is configured to transfer the first owner of the target resource corresponding to the bound target resource to the second object in response to the target resource ownership transfer request of the second object.

[0259] Optionally, the resource deployment unit 1910 is specifically configured to:

[0260] In response to the target resource bundle deployment request of the first object, assigning a target resource bundle identifier to the target resource bundle;

[0261] Receive an initial target resource list of the target resource package;

[0262] Record the mapping relationship between the target resource package identifier and the initial target resource list into the first variable;

[0263] The target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain.

[0264] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0265] A first acquisition unit (not shown), configured to acquire a target resource package identifier for a binding request;

[0266] A first search unit (not shown), configured to search for a first variable based on a target resource package identifier to obtain an initial target resource list;

[0267] The first determining unit (not shown) is configured to determine whether a plurality of to-be-bound target resources fall into the initial target resource list.

[0268] Optionally, the initial target resource list includes, for each initial target resource, a first sub-contract address corresponding to the application platform where the initial target resource is registered, an initial target resource identifier, and the number of registered initial target resources on the application platform; the binding request includes, for each target resource to be bound, a second sub-contract address corresponding to the application platform where the target resource to be bound is registered, an identifier of the target resource to be bound, and the number of target resources to be bound;

[0269] The first determining unit is specifically configured to:

[0270] If the first sub-contract address of an initial target resource in the initial target resource list is equal to the second sub-contract address of the target resource to be bound, and the initial target resource identifier is equal to the target resource to be bound identifier of the target resource to be bound, then the initial target resource is determined as the target resource to be examined;

[0271] Based on the registered number of the target resources to be inspected and the to-be-bound number of the target resources to be bound, it is determined that the target resources to be bound fall into the initial target resource list.

[0272] Optionally, the first determining unit is specifically configured to:

[0273] Obtain a second variable, where the second variable indicates the number of bound resources in the number of registered resources of the initial target resource;

[0274] If the sum of the second variable and the number to be bound is not greater than the registered number, it is determined that the target resource to be bound falls into the initial target resource list, and the number to be bound is increased on the second variable.

[0275] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0276] A second determining unit (not shown), configured to determine that the first sub-contract address corresponding to the initial target resource is of a first type, where the first type indicates that the initial target resource cannot be copied;

[0277] The first verification unit (not shown) is used to verify that the registration number of the initial target resource is 1.

[0278] Optionally, the resource binding unit 1930 is specifically configured to:

[0279] If the second sub-contract address of the target resource to be bound is of the first type, and the first type indicates that the initial target resource cannot be copied, the second owner of the target resource to be bound is transferred to the address of the overall contract;

[0280] If the second sub-contract address of the target resource to be bound is of the second type, and the second type indicates that the initial target resource is replicable, the second attribution party of the target resource to be bound with the number of target resources to be bound in the target resource to be bound is transferred to the address of the overall contract.

[0281] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0282] A second obtaining unit (not shown), configured to obtain a first issuer of the binding request;

[0283] The third determining unit (not shown) is configured to determine that the first sender is the first object.

[0284] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0285] A second receiving unit (not shown), configured to receive an unbinding request for a plurality of to-be-unbound target resources among a plurality of bound target resources;

[0286] The second transfer execution unit (not shown) is used to call the resource ownership transfer function in the sub-contract on the blockchain, so that the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract is transferred to the first object.

[0287] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0288] A third acquisition unit (not shown), configured to acquire an identifier of a target resource package for which an unbinding request is made;

[0289] A first search unit (not shown), configured to search for a first variable based on a target resource package identifier to obtain an initial target resource list;

[0290] The fourth determining unit (not shown) is configured to determine whether a plurality of to-be-unbound target resources fall into the initial target resource list.

[0291] Optionally, the initial target resource list includes, for each initial target resource, a first sub-contract address corresponding to the application platform where the initial target resource is registered, and an initial target resource identifier; and the unbinding request includes, for each target resource to be unbound, a third sub-contract address corresponding to the application platform where the target resource to be unbound is registered, and an identifier of the target resource to be unbound;

[0292] The fourth determining unit (not shown) is specifically configured to:

[0293] If the first sub-contract address of an initial target resource in the initial target resource list is equal to the third sub-contract address of the target resource to be unbound, and the initial target resource identifier is equal to the target resource identifier to be unbound of the target resource to be unbound, then it is determined that the target resource to be unbound falls into the initial target resource list.

[0294] Optionally, the unbinding request further includes the number of resources to be unbound for each target resource to be unbound;

[0295] The blockchain resource transfer processing device 1900 further includes:

[0296] a fourth acquisition unit (not shown), configured to acquire a second variable, where the second variable indicates the bound number of the initial target resource;

[0297] a fifth determining unit (not shown), configured to determine that the number to be unbound is not greater than a second variable;

[0298] The resource unbinding unit (not shown) is used to call the resource ownership transfer function in the sub-contract on the blockchain, so that the target resource to be unbound is transferred from the second owner on the application platform corresponding to the sub-contract to the first object. The blockchain resource transfer processing method also includes: subtracting the number to be unbound from the second variable.

[0299] Optionally, the unbinding request further includes the number of resources to be unbound for each target resource to be unbound;

[0300] The blockchain resource transfer processing device 1900 further includes:

[0301] The attribution party address determination unit (not shown) is used to call the attribution party acquisition function in the sub-contract on the blockchain to determine that the second attribution party of the target resource to be unbound on the application platform corresponding to the sub-contract is the address of the overall contract if the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied;

[0302] The unit for determining the number of attributable parties (not shown) is used to call the obtain attributable party function in the sub-contract on the blockchain if the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, so as to determine that the number of target resources whose second attributable party is the address of the overall contract on the application platform corresponding to the sub-contract is not less than the number to be unbound.

[0303] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0304] a fifth obtaining unit (not shown), configured to obtain a second sender of the unbinding request;

[0305] The sixth determining unit (not shown) is configured to determine that the second sender is the first object.

[0306] Optionally, the resource unbinding unit (not shown) is specifically used for:

[0307] If the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, the second owner of the target resource to be unbound is transferred to the first object;

[0308] If the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, the second owner of the target resource to be unbound of the number of bound target resources to be unbound is transferred to the first object.

[0309] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0310] An authorization function calling unit (not shown), used to call authorization functions in multiple sub-contracts;

[0311] The authorization function execution unit (not shown) is used to execute the authorization function so that the sub-contract is authorized to the overall contract, so that the address of the overall contract can serve as the second attribution party registered on the application platform corresponding to the sub-contract.

[0312] Optionally, the blockchain resource transfer processing device 1900 further includes:

[0313] A third receiving unit (not shown), configured to receive a target resource package viewing request of a second object, wherein the target resource package viewing request has a target resource package identifier;

[0314] A second search unit (not shown), configured to search the first variable based on the target resource package identifier to obtain an initial target resource list;

[0315] The list sending unit (not shown) is used to send the initial target resource list to the second object.

[0316] Reference Fig. 20, Fig. 20 The structural block diagram of the terminal part of the blockchain resource transfer processing method for implementing the embodiment of the present disclosure includes: a radio frequency (RF) circuit 2010, a memory 2015, an input unit 2030, a display unit 2040, a sensor 2050, an audio circuit 2060, a wireless fidelity (WiFi) module 2070, a processor 2080, and a power supply 2090. Those skilled in the art can understand that Fig. 20 The terminal structure shown does not constitute a limitation on the mobile phone or computer, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0317] The RF circuit 2010 can be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information from the base station, it is sent to the processor 2080 for processing; in addition, the designed uplink data is sent to the base station.

[0318] The memory 2015 may be used to store software programs and modules. The processor 2080 executes various functional applications and data processing of the target terminal by running the software programs and modules stored in the memory 2015 .

[0319] The input unit 2030 may be used to receive input digital or character information and generate key signal input related to the setting and function control of the target terminal. Specifically, the input unit 2030 may include a touch panel 2031 and other input devices 2032.

[0320] The display unit 2040 may be used to display input information or provided information and various menus of the target terminal. The display unit 2040 may include a display panel 2041.

[0321] The audio circuit 2060 , the speaker 2061 , and the microphone 2062 may provide an audio interface.

[0322] In this embodiment, the processor 2080 included in the terminal can execute the blockchain resource transfer processing method of the previous embodiment.

[0323] The terminals of the embodiments of the present disclosure include but are not limited to mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, aircraft, etc. The embodiments of the present disclosure can be applied to various fields, including but not limited to alliance chains, structured information processing, security technology, data security, data storage, information technology, etc.

[0324] Fig.21A block diagram of the structure of a portion of a server for implementing the blockchain resource transfer processing method of an embodiment of the present disclosure. The server may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPUs) 2122 (e.g., one or more processors) and memory 2132, and one or more storage media 2130 (e.g., one or more mass storage devices) storing application programs 2142 or data 2144. Among them, the memory 2132 and the storage medium 2130 may be short-term storage or permanent storage. The program stored in the storage medium 2130 may include one or more modules (not shown in the figure), each of which may include a series of instruction operations on the server. Furthermore, the central processor 2122 may be configured to communicate with the storage medium 2130 and execute a series of instruction operations in the storage medium 2130 on the server.

[0325] The server may also include one or more power supplies 2126, one or more wired or wireless network interfaces 2150, one or more input and output interfaces 2158, and / or one or more operating systems 2141, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

[0326] The central processor 2122 in the server can be used to execute the blockchain resource transfer processing method of the embodiment of the present disclosure.

[0327] The embodiments of the present disclosure also provide a computer-readable storage medium, which is used to store program code, and the program code is used to execute the blockchain resource transfer processing method of each of the aforementioned embodiments.

[0328] The present disclosure also provides a computer program product, which includes a computer program. A processor of a computer device reads and executes the computer program, so that the computer device executes the above-mentioned blockchain resource transfer processing method.

[0329] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present disclosure described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "comprises" and "comprising" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0330] It should be understood that in the present disclosure, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0331] It should be understood that in the description of the embodiments of the present disclosure, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to not include the number, and above, below, within, etc. are understood to include the number.

[0332] In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

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

[0334] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0335] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present disclosure. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

[0336] It should also be understood that the various implementations provided in the embodiments of the present disclosure can be combined arbitrarily to achieve different technical effects.

[0337] The above is a specific description of the implementation methods of the present disclosure, but the present disclosure is not limited to the above implementation methods. Technical personnel familiar with the art can also make various equivalent modifications or substitutions without violating the spirit of the present disclosure. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present disclosure.

Claims

1. A blockchain resource transfer processing method, characterized in that: For a blockchain node, the blockchain node is connected to multiple application platforms, and multiple sub-contracts corresponding to the multiple application platforms and a general contract for the multiple application platforms are maintained on the blockchain. The blockchain resource transfer processing method includes: In response to a target resource package deployment request of a first object, deploy the target resource package in the overall contract on the blockchain, where a first owner of the target resource package is the first object; Receiving binding requests of multiple target resources to be bound, wherein the multiple target resources to be bound are registered as the first objects by second owners on the multiple application platforms; Calling the resource ownership transfer function in the sub-contract on the blockchain, so that the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as a bound target resource; In response to a target resource ownership transfer request of a second object, the first owner of the bound target resource corresponding to the target resource is transferred to the second object.

2. The blockchain resource transfer processing method according to claim 1 is characterized in that: The step of deploying the target resource package in the overall contract on the blockchain in response to the target resource package deployment request of the first object includes: In response to the target resource bundle deployment request of the first object, assigning a target resource bundle identifier to the target resource bundle; Receiving an initial target resource list of the target resource package; Recording the mapping relationship between the target resource package identifier and the initial target resource list into a first variable; The target resource package identifier, the initial target resource list, and the first variable are recorded in the overall contract on the blockchain.

3. The blockchain resource transfer processing method according to claim 2 is characterized in that: Before calling the resource ownership transfer function in the sub-contract on the blockchain, the blockchain resource transfer processing method further includes: Obtaining the target resource bundle identifier for the binding request; Based on the target resource package identifier, searching the first variable to obtain the initial target resource list; It is determined that a plurality of the target resources to be bound fall into the initial target resource list.

4. The blockchain resource transfer processing method according to claim 3 is characterized in that: The initial target resource list includes, for each of the initial target resources, the first sub-contract address corresponding to the application platform where the initial target resource is registered, the initial target resource identifier, and the number of registered initial target resources on the application platform; the binding request includes, for each of the target resources to be bound, the second sub-contract address corresponding to the application platform where the target resource to be bound is registered, the target resource identifier to be bound, and the number to be bound; The determining that the plurality of target resources to be bound fall into the initial target resource list includes: If the first sub-contract address of one of the initial target resources in the initial target resource list is equal to the second sub-contract address of the target resource to be bound, and the initial target resource identifier is equal to the target resource identifier to be bound of the target resource to be bound, then the initial target resource is determined as the target resource to be examined; Based on the registered number of the target resources to be examined and the to-be-bound number of the target resources to be bound, it is determined that the target resources to be bound fall into the initial target resource list.

5. The blockchain resource transfer processing method according to claim 4 is characterized in that: The determining, based on the registered number of the target resources to be inspected and the to-be-bound number of the target resources to be bound, that the target resources to be bound fall into the initial target resource list includes: Acquire a second variable, where the second variable indicates the bound number of the registered number of the initial target resource; If the sum of the second variable and the number to be bound is not greater than the registered number, it is determined that the target resource to be bound falls into the initial target resource list, and the number to be bound is increased on the second variable.

6. The blockchain resource transfer processing method according to claim 4 is characterized in that: After receiving the initial target resource list of the target resource package, the blockchain resource transfer processing method further includes: Determining that the first sub-contract address corresponding to the initial target resource is of a first type, where the first type indicates that the initial target resource cannot be copied; Verify that the registration number of the initial target resource is 1.

7. The blockchain resource transfer processing method according to claim 4 is characterized in that: The step of transferring the second owner of the target resource to be bound on the application platform corresponding to the sub-contract to the address of the overall contract includes: If the second sub-contract address of the target resource to be bound is of the first type, and the first type indicates that the initial target resource cannot be copied, then the second owner of the target resource to be bound is transferred to the address of the overall contract; If the second sub-contract address of the target resource to be bound is of the second type, and the second type indicates that the initial target resource is replicable, the second attribution party of the target resource to be bound with the number to be bound in the target resource to be bound is transferred to the address of the overall contract.

8. The blockchain resource transfer processing method according to claim 3 is characterized in that: Before obtaining the target resource package identifier for the binding request, the blockchain resource transfer processing method further includes: Obtaining the first issuer of the binding request; It is determined that the first issuer is the first object.

9. The blockchain resource transfer processing method according to claim 2 is characterized in that: After calling the resource ownership transfer function in the sub-contract on the blockchain, the blockchain resource transfer processing method further includes: receiving an unbinding request for a plurality of to-be-unbound target resources among the plurality of bound target resources; The resource ownership transfer function in the sub-contract on the blockchain is called to transfer the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract to the first object.

10. The blockchain resource transfer processing method according to claim 9 is characterized in that: Before calling the resource ownership transfer function in the sub-contract on the blockchain to transfer the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract to the first object, the blockchain resource transfer processing method further includes: Obtaining the target resource package identifier for the unbinding request; Based on the target resource package identifier, searching the first variable to obtain the initial target resource list; It is determined that a plurality of the to-be-unbound target resources fall into the initial target resource list.

11. The blockchain resource transfer processing method according to claim 10 is characterized in that: The initial target resource list includes, for each of the initial target resources, the first sub-contract address corresponding to the application platform where the initial target resource is registered, and the initial target resource identifier; the unbinding request includes, for each of the target resources to be unbound, the third sub-contract address corresponding to the application platform where the target resource to be unbound is registered, and the target resource identifier to be unbound; The determining that the plurality of target resources to be unbound fall into the initial target resource list includes: If the first sub-contract address of one of the initial target resources in the initial target resource list is equal to the third sub-contract address of the target resource to be unbound, and the initial target resource identifier is equal to the target resource identifier to be unbound of the target resource to be unbound, it is determined that the target resource to be unbound falls into the initial target resource list.

12. The blockchain resource transfer processing method according to claim 10, characterized in that: The unbinding request further includes, for each target resource to be unbound, a number of resources to be unbound; After determining that a plurality of the target resources to be unbound fall into the initial target resource list, the blockchain resource transfer processing method further includes: Acquire a second variable, where the second variable indicates the bound number of the initial target resource; Determining that the number to be unbound is not greater than the second variable; After calling the resource ownership transfer function in the sub-contract on the blockchain to transfer the target resource to be unbound from the second owner on the application platform corresponding to the sub-contract to the first object, the blockchain resource transfer processing method also includes: subtracting the number to be unbound from the second variable.

13. The blockchain resource transfer processing method according to claim 10 is characterized in that: The unbinding request further includes, for each target resource to be unbound, a number of resources to be unbound; After determining that a plurality of the target resources to be unbound fall into the initial target resource list, the blockchain resource transfer processing method further includes: If the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, then calling the get-owner function in the sub-contract on the blockchain to determine that the second owner of the target resource to be unbound on the application platform corresponding to the sub-contract is the address of the overall contract; If the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, the obtain-attribution-party function in the sub-contract on the blockchain is called to determine that the number of target resources whose second attribution party is the address of the overall contract on the application platform corresponding to the sub-contract is not less than the number to be unbound.

14. The blockchain resource transfer processing method according to claim 10 is characterized in that: Before obtaining the target resource package identifier for the unbinding request, the blockchain resource transfer processing method further includes: Obtaining a second sender of the unbinding request; It is determined that the second issuer is the first object.

15. The blockchain resource transfer processing method according to claim 9 is characterized in that: The step of transferring the target resource to be unbound to the first object from the second owner on the application platform corresponding to the sub-contract includes: If the third sub-contract address of the target resource to be unbound is of the first type, and the first type indicates that the initial target resource cannot be copied, then the second owner of the target resource to be unbound is transferred to the first object; If the third sub-contract address of the target resource to be unbound is of the second type, and the second type indicates that the initial target resource is replicable, the second belonging party of the target resource to be unbound of the number to be unbound in the bound target resources is transferred to the first object.

16. The blockchain resource transfer processing method according to claim 2 is characterized in that: In response to the target resource ownership transfer request of the second object, before transferring the first ownership party of the bound target resource corresponding to the target resource to the second object, the blockchain resource transfer processing method further includes: receiving a target resource bundle viewing request of the second object, wherein the target resource bundle viewing request has the target resource bundle identifier; Based on the target resource package identifier, searching the first variable to obtain the initial target resource list; The initial target resource list is sent to the second object.

17. A blockchain resource transfer processing device, characterized in that: The blockchain resource transfer processing device is located at a target consensus node among multiple consensus nodes of the alliance chain consensus network, and the blockchain resource transfer processing device includes: a resource deployment unit, configured to deploy the target resource package in the overall contract on the blockchain in response to a target resource package deployment request of the first object, wherein the first owner of the target resource package is the first object; A first receiving unit is configured to receive binding requests of multiple target resources to be bound, wherein the multiple target resources to be bound are registered as the first objects by second owners on the multiple application platforms; A resource binding unit, configured to call a resource ownership transfer function in the sub-contract on the blockchain, so that the second ownership party of the target resource to be bound on the application platform corresponding to the sub-contract is transferred to the address of the overall contract, so as to determine the target resource to be bound as a bound target resource; The first transfer execution unit is configured to transfer the first owner of the bound target resource corresponding to the target resource to the second object in response to a target resource ownership transfer request of the second object.

18. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, it implements the blockchain resource transfer processing method according to any one of claims 1 to 16.

19. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the blockchain resource transfer processing method according to any one of claims 1 to 16 is implemented.

20. A computer program product, comprising a computer program, wherein the computer program is read and executed by a processor of a computer device, so that the computer device executes the blockchain resource transfer processing method according to any one of claims 1 to 16.

Images