Data processing method and device, equipment and medium

Different types of digital assets are linked through asset registration contracts and proxy contracts on the blockchain, solving the problem of difficulty in managing multiple independent digital assets, realizing the integration of unified management and transaction records, and improving management efficiency and display effect.

CN119090646APending Publication Date: 2024-12-06TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310657756.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-06-05
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing technology is difficult to effectively manage transaction records between multiple independent digital assets, resulting in increased difficulty in unified management.

Method used

Through asset registration contracts and proxy contracts on the blockchain, different types of digital assets are associated, permission verification and synchronous transfer are realized, and associated transaction records are generated.

Benefits of technology

It realizes unified management of multiple digital assets, reduces the confusion of transaction records on the blockchain, and improves the display effect and traceability of digital asset transaction records.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119090646A_ABST
    Figure CN119090646A_ABST
Patent Text Reader

Abstract

The invention discloses a data processing method and apparatus, a device and a medium. The method comprises the steps of obtaining a first asset transfer request initiated by a first business object for a first type of assets; the proxy contract bound with the first type of assets is used for carrying out asset association on the second type of assets and the first type of assets; based on the first asset transfer request, an asset registration contract and a proxy contract are called to perform permission verification on the first business object, and if an obtained first permission verification result indicates that the first business object has transfer permission for the first type of assets and the second type of assets, the first type of assets are transferred. If yes, when the first type of assets are transferred to the second business object through the asset registration contract, the second type of assets are synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of assets and the second type of assets is generated. By adopting the method and the device, different digital assets can be subjected to asset association so as to realize unified management of a plurality of digital assets.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data processing method, device, equipment and medium. Background Art

[0002] At present, with the emergence of technologies such as blockchain, it provides important opportunities for the development of digital assets. Existing digital assets are unique and independent. When transferring multiple independent digital assets, a large number of transaction records will be generated, and the transaction records for each digital asset exist separately, which increases the difficulty of unified management of multiple digital assets involved in these transaction records. Summary of the invention

[0003] The embodiments of the present application provide a data processing method, apparatus, device and medium, which can achieve unified management of multiple digital assets by associating different digital assets.

[0004] On the one hand, an embodiment of the present application provides a data processing method, including:

[0005] A first asset transfer request initiated by a first business object for a first type of asset held by the first business object is obtained after asset registration through an asset registration contract on a blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of asset on the blockchain; the proxy contract is used to associate a second type of asset held by the first business object with the first type of asset; the second type of asset is different from the first type of asset;

[0006] Based on the first asset transfer request, the asset registration contract and the proxy contract are called to perform permission verification on the first business object to obtain a first permission verification result;

[0007] If the first permission verification result indicates that the first business object has the transfer authority for the first type of assets and the second type of assets, then when the first type of assets are transferred to the second business object through the asset registration contract, the second type of assets will be synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of assets and the second type of assets will be generated.

[0008] An embodiment of the present application provides a data processing device, including:

[0009] The first acquisition module is used to acquire a first asset transfer request initiated by the first business object for the first type of assets held; the first type of assets are obtained after asset registration through the asset registration contract on the blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of assets on the blockchain; the proxy contract is used to associate the second type of assets held by the first business object with the first type of assets; the second type of assets are different from the first type of assets;

[0010] The authority verification module is used to call the asset registration contract and the proxy contract to perform authority verification on the first business object based on the first asset transfer request, and obtain a first authority verification result;

[0011] The first transfer module is used to synchronously transfer the second type of assets to the second business object when the first type of assets are transferred to the second business object through the asset registration contract if the first permission verification result indicates that the first business object has the transfer authority for the first type of assets and the second type of assets, and generate a synchronous transfer transaction record associated with the first type of assets and the second type of assets.

[0012] The device further comprises:

[0013] An asset registration module, used to obtain an asset registration request initiated by the first business object, call an asset registration contract on the blockchain based on the asset registration request, and register the first digital asset held by the first business object as a first type of asset;

[0014] A contract deployment module, used to deploy a proxy contract for managing the first type of assets on the blockchain through an asset registration contract, and bind the first type of assets to the proxy contract;

[0015] The asset association module is used to, when obtaining an asset association request initiated by the first business object for the first type of asset, call the proxy contract based on the asset association request, associate the second digital asset held by the first business object that is different from the first digital asset with the first type of asset, and obtain the second type of asset associated with the first type of asset.

[0016] The asset registration request carries the asset registration data submitted by the first business object for the first digital asset held and the first signature information of the first business object; the first signature information is obtained by signing the asset registration data with the private key information of the first business object; the first signature information carries the public key information corresponding to the private key information;

[0017] The asset registration module includes:

[0018] A first signature verification unit is used to obtain first signature information from the asset registration request, perform signature verification on the first signature information using public key information carried in the first signature information, and obtain a first signature verification result;

[0019] The asset registration unit is used to call the asset registration contract on the blockchain based on the asset registration data carried in the asset registration request when the first signature verification result indicates that the signature verification is successful, and register the first digital asset as a first type of asset.

[0020] The asset registration data includes a first asset identifier corresponding to a first digital asset that is an asset of the first type;

[0021] The contract deployment module includes:

[0022] A contract deployment unit, configured to deploy a proxy contract for managing the first type of assets on the blockchain through an asset registration contract, and configure the contract holding object address of the proxy contract as a first account address of the first business object; the first account address is determined by the public key information of the first business object;

[0023] The contract binding unit is used to obtain the first asset identifier from the asset registration data, and establish a binding relationship between the first asset identifier and the proxy contract account corresponding to the proxy contract through the asset registration contract; the binding relationship is used to indicate that the first type of asset is managed by the proxy contract account.

[0024] The asset association request carries the associated asset data submitted by the first business object for the first type of asset and the second signature information of the first business object; the associated asset data is determined by the second digital asset held by the first business object and different from the first digital asset; the second signature information is obtained by signing the associated asset data with the private key information of the first business object; the second signature information carries the public key information corresponding to the private key information;

[0025] The asset association module includes:

[0026] The second signature verification unit is used to obtain the second signature information from the asset association request, perform signature verification on the second signature information using the public key information carried by the second signature information, and obtain a second signature verification result;

[0027] A request forwarding unit, configured to call the asset registration contract, obtain the proxy contract address of the proxy contract, and forward the asset association request to the proxy contract according to the proxy contract address when the second signature verification result indicates that the signature verification is successful;

[0028] The asset association unit is used to call the proxy contract based on the associated asset data carried in the asset association request, associate the second digital asset with the first type of asset, and obtain the second type of asset associated with the first type of asset.

[0029] The request forwarding unit includes:

[0030] The first authentication subunit is used to perform permission verification on the first business object through the asset registration contract to obtain a second permission verification result;

[0031] The request forwarding subunit is used to obtain the proxy contract address of the proxy contract when the second permission verification result indicates that the first business object holds the first type of assets, and forward the asset association request to the proxy contract according to the proxy contract address.

[0032] Among them, the first authentication subunit is specifically used to obtain the first asset holding object address corresponding to the first type of asset through the asset registration contract, and compare the first asset holding object address with the first account address of the first business object; the first account address is determined by the public key information of the first business object; if the first asset holding object address is the same as the first account address, it is determined that the first business object holds the first type of asset; the result when the first business object holds the first type of asset is used as the second authority verification result.

[0033] The associated asset data includes a second asset identifier corresponding to the second digital asset; the proxy contract includes an asset association function;

[0034] Asset-related units include:

[0035] The second authentication subunit is used to perform permission verification on the first business object through the proxy contract when the second asset identifier is obtained from the associated asset data carried in the asset association request, so as to obtain a third permission verification result;

[0036] The asset association subunit is used to establish an association relationship between the second asset identifier and the first asset identifier corresponding to the first digital asset as the first type of asset through the asset association function in the proxy contract when the third permission verification result indicates that the first business object holds the second digital asset corresponding to the second asset identifier; the association relationship is used to indicate that when the second digital asset is used as a second type of asset associated with the first type of asset, both the first type of asset and the second type of asset belong to the proxy contract account corresponding to the proxy contract.

[0037] Among them, the second authentication subunit is specifically used to obtain the second asset holding object address corresponding to the second digital asset corresponding to the second asset identifier through the proxy contract, and compare the second asset holding object address with the first account address of the first business object; if the second asset holding object address is the same as the first account address, it is determined that the first business object holds the second digital asset; and the result when the first business object holds the second digital asset is used as the third authority verification result.

[0038] Among them, the permission verification module includes:

[0039] A first authentication unit is used to call the asset registration contract to obtain the first asset holding object address corresponding to the first type of asset based on the first asset transfer request, compare the first asset holding object address with the first account address of the first business object, and determine that the first business object has the transfer authority for the first type of asset when the first asset holding object address is the same as the first account address, and forward the first asset transfer request to the proxy contract;

[0040] A second authentication unit is used to call the proxy contract to find an asset identifier associated with the first asset identifier of the first type of asset based on the first asset transfer request, use the found asset identifier as the target asset identifier, compare the target asset identifier with the second asset identifier of the second type of asset, and determine that the first business object has transfer authority for the second type of asset when the target asset identifier and the second asset identifier are the same;

[0041] The result determination unit is used to use the result when the first business object has the transfer authority for the first type of assets and the second type of assets as the first authority verification result.

[0042] Wherein, the first transfer module includes:

[0043] A synchronous transfer unit, used to change the holding authority of the first type of assets and synchronously transfer the second type of assets to the second business object when the first type of assets are transferred to the second business object through the asset registration contract;

[0044] A record generation unit is used to generate a first transaction record corresponding to a first type of asset and a second transaction record corresponding to a second type of asset, and use the first transaction record and the second transaction record as synchronous transfer transaction records associated with the first type of asset and the second type of asset; the second transaction record is associated with the first transaction record.

[0045] Among them, the synchronous transfer unit is specifically used to change the asset holding object of the first type of asset from the first business object to the second business object through the asset registration contract, and change the contract holding object address of the proxy contract from the first account address of the first business object to the second account address of the second business object.

[0046] The second type of assets include digital assets to be transferred; and the device further includes:

[0047] A second acquisition module, used to acquire a second asset transfer request initiated by the first business object for the digital asset to be transferred;

[0048] A first forwarding module is used to call the asset registration contract based on the second asset transfer request, obtain the proxy contract address of the proxy contract, and forward the second asset transfer request to the proxy contract according to the proxy contract address;

[0049] The second transfer module is used to unbind the digital assets to be transferred and the first type of assets based on the second asset transfer request, transfer the unbound digital assets to be transferred to the second business object, and generate a third transaction record corresponding to the digital assets to be transferred when it is determined through the proxy contract that the first business object has the transfer authority for the digital assets to be transferred.

[0050] Wherein, the second transfer module includes:

[0051] A third authentication unit is used to call the asset transfer function in the proxy contract based on the second asset transfer request, perform authority verification on the first business object, and obtain a fourth authority verification result;

[0052] The unbinding and transferring unit is used to determine that the first business object has the transfer authority for the digital assets to be transferred when the fourth authority verification result indicates that the first business object holds the digital assets to be transferred, unbind the digital assets to be transferred and the first type of assets, and transfer the unbound digital assets to be transferred to the second business object.

[0053] The second type of assets include digital assets to be unbound; and the device further includes:

[0054] A third acquisition module is used to obtain an asset unbinding request initiated by the first business object for the digital asset to be unbound;

[0055] The second forwarding module is used to call the asset registration contract based on the asset unbinding request, obtain the proxy contract address of the proxy contract, and forward the asset unbinding request to the proxy contract according to the proxy contract address;

[0056] The asset unbinding module is used to unbind the digital asset to be unbound and the first type of asset based on the asset unbinding request when it is determined through the proxy contract that the first business object holds the digital asset to be unbound.

[0057] An embodiment of the present application provides a computer device, including: a processor and a memory;

[0058] The processor is connected to the memory, wherein the memory is used to store a computer program. When the computer program is executed by the processor, the computer device executes the method provided in the embodiment of the present application.

[0059] On the one hand, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. The computer program is suitable for being loaded and executed by a processor so that a computer device having the processor executes the method provided by the embodiment of the present application.

[0060] In one aspect, the present application provides a computer program product or a computer program, which includes a computer instruction stored in a computer-readable storage medium. A processor of a computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the method provided in the present application.

[0061] In an embodiment of the present application, a consensus node in a blockchain network may obtain a first asset transfer request initiated by a first business object for a first type of asset held by the first business object; wherein the first type of asset here is obtained after asset registration through an asset registration contract on the blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of asset on the blockchain; and the proxy contract may be used to associate a second type of asset held by the first business object with the first type of asset; the second type of asset is different from the first type of asset; further, the consensus node in the blockchain network may call the asset registration contract and the proxy contract to perform authority verification on the first business object based on the first asset transfer request, and obtain a first authority verification result; it can be understood that if the first authority verification result indicates that the first business object has the transfer authority for the first type of asset and the second type of asset, then when the first type of asset is transferred to the second business object through the asset registration contract, the second type of asset is synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of asset and the second type of asset is generated. It can be seen that the embodiment of the present application provides a digital asset management method, which can associate the first type of assets with the second type of assets through the proxy contract after registering the first type of assets through the asset registration contract, so that different digital assets have correlation, and then the associated digital assets (such as the first type of assets and the second type of assets) can be synchronously transferred to the second business object, that is, a unified asset transfer is completed, so that unified management of multiple digital assets can be achieved. At the same time, when the associated first type of assets and second type of assets are transferred, there will also be a correlation between the transaction records corresponding to the first type of assets and the transaction records corresponding to the second type of assets. The synchronous transfer transaction records obtained by integrating these associated transaction records can reduce the complexity of the transaction records on the blockchain, and can improve the display effect and traceability of digital asset transaction records. BRIEF DESCRIPTION OF THE DRAWINGS

[0062] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0063] Figure 1 This is a schematic diagram of the structure of a blockchain network provided in an embodiment of the present application;

[0064] Figure 2a This is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0065] Figure 2bThis is a schematic diagram of a data processing scenario provided by an embodiment of the present application;

[0066] Figure 3 It is a flowchart of a data processing method provided in an embodiment of the present application;

[0067] Figure 4 It is a schematic diagram of the relationship between an asset and a proxy contract account provided in an embodiment of the present application;

[0068] Figure 5 This is a schematic diagram of a scenario of a main asset transfer provided by an embodiment of the present application;

[0069] Figure 6 It is a flowchart of a data processing method provided in an embodiment of the present application;

[0070] Figure 7 This is a flowchart of an asset registration provided by an embodiment of the present application;

[0071] Figure 8 It is a flowchart of an asset association provided by an embodiment of the present application;

[0072] Fig. 9 This is a schematic diagram of a scenario of ancillary asset transfer provided in an embodiment of the present application;

[0073] Fig.10 This is a schematic diagram of a scenario of unbinding an affiliated asset provided in an embodiment of the present application;

[0074] Fig.11 is a structural schematic diagram of a data processing device provided in an embodiment of the present application;

[0075] Fig.12 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0077] See also Figure 1 , Figure 1It is a schematic diagram of the structure of a blockchain network provided in an embodiment of the present application. It can be understood that blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism and encryption algorithm. It is mainly used to organize data in chronological order and encrypt it into a ledger to make it impossible to be tampered with or forged. At the same time, it can verify, store and update data. Blockchain is essentially a decentralized database in which each node stores an identical blockchain. Figure 1 The blockchain network 100 shown can be applied to a blockchain system (such as a blockchain electronic bill system). A blockchain system refers to a system for sharing data between blockchain nodes. The blockchain network 100 can be deployed with multiple blockchain nodes (referred to as nodes for short). The number of blockchain nodes deployed in the blockchain network 100 is not limited. For example, Figure 1 As shown, the blockchain network 100 may specifically include nodes 100a, 100b, 100c, 100d, ..., 100m. It is understandable that the blockchain node may be a server connected to the blockchain network or a terminal connected to the blockchain network. The specific form of the blockchain node is not limited here, and each blockchain node may include a hardware layer, an intermediate layer, an operating system layer, and an application layer.

[0078] It should be noted that the blockchain network in the embodiments of the present application can be a layered structure or a single-layer structure, and the specific structure of the blockchain network is not limited here.

[0079] For example, optionally, for a blockchain network with a hierarchical structure, Figure 1 The blockchain network 100 shown can be further divided into a business network (i.e., a witness network) and a core consensus network, and the business network and the core consensus network are independent of each other. In particular, both the business network and the core consensus network can deploy multiple nodes, and there is no limit on the number of nodes deployed in the two networks. For example, the business network may include Figure 1 As shown in nodes 100a, 100b and 100c, the core consensus network may include Figure 1Node 100d, node 100e, ..., node 100m are shown. Among them, the node in the business network can be called a business node, which is mainly used to execute transaction business to obtain transaction data associated with the transaction business and synchronize the data in a timely manner. It can be understood that the business node here does not need to participate in the bookkeeping consensus, but can obtain block header data and partially authorized visible block data from the core consensus network through identity authentication. Among them, the business node can be a full node (Full Node) containing a complete blockchain database, or a lightweight node (Lightweight Node) that stores part of the data in the blockchain database. This type of node can complete transaction verification through "Simplified Payment Verification (SPV)", so it can also be called SPV node, and the type of business node will not be limited here. Similarly, the node in the core consensus network can be called a consensus node (i.e., a bookkeeping node), and the consensus node can run a blockchain consensus protocol. Among them, the consensus node can be a full node containing a complete blockchain database. The consensus node can participate in the verification and broadcasting of transaction data and block information, and can discover and maintain connections with other nodes. In addition, optionally, the business network and the core consensus network can be isolated through a routing network (i.e., a routing proxy layer). For example, the peer-to-peer (P2P) network can be layered through the routing nodes in the routing network to form a layered structure such as "business network-core consensus network", thereby improving the confidentiality and security of data on the blockchain. Among them, the number of routing nodes in the routing network can be one or more, which is not limited here.

[0080] It is understandable that the above-mentioned business network and core consensus network can be in different network environments. For example, in some embodiments, the business node can be deployed in the business network in the public network, and the consensus node running the blockchain consensus protocol can be deployed in the private core consensus network, and the two can interact through the routing boundary. In this case, since the core consensus network is in a relatively secure private cloud, its mutual access has a consensus mechanism to ensure security, and there is no need to add additional identity management and network control; while the business node is in the public network and may be accessed by other uncertain network terminals, so the behavior of the business node and other possible nodes accessing the core consensus network needs to be strictly controlled. Optionally, in some other embodiments, the business node and the consensus node can also directly transmit data without going through the routing node, which is not limited here.

[0081] For another example, optionally, for a blockchain network with a single-layer structure, Figure 1 The blockchain network 100 shown may include consensus nodes and ordinary nodes. Consensus nodes participate in consensus, while ordinary nodes do not participate in consensus but can help propagate blocks and voting messages, as well as synchronize states with each other. For example, Figure 1 Nodes 100a, 100b, and 100c are used as common nodes, and the remaining nodes are used as consensus nodes. There is no limit on the number of consensus nodes and the number of common nodes.

[0082] In the above blockchain system, the consensus node may be responsible for the consensus in the network (such as the core consensus network) where the corresponding blockchain is located. For example, under the hierarchical structure of the blockchain network, for the core consensus network, the specific process of writing the transaction data in the core consensus network into the corresponding blockchain ledger (for example, a distributed database) may be that the user client sends the transaction data to a certain business node, and then the transaction data is passed between the business nodes in the business network in the above blockchain network in a relay manner until the consensus node in the corresponding core consensus network in the above blockchain network (for example, the consensus node 100m in the blockchain network 100) receives the transaction data. At this time, the consensus node (for example, the consensus node 100m in the blockchain network 100) then packages the transaction data into a block so that it can be subsequently reached through consensus with other consensus nodes, so that after the consensus is passed, the consensus-passed block can be written into the distributed database of the core consensus network where it is located.

[0083] Optionally, it is understandable that the embodiment of the present application can also write the block carrying the transaction data and multiple other blocks associated with the block into a distributed database in parallel through the storage layer of its own core consensus network after the consensus is passed. This can fundamentally break through the limitations of the blockchain structure of the blockchain, and thus effectively improve the storage efficiency of data storage.

[0084] It is understandable that a smart contract can be deployed in the above blockchain system. The smart contract can be understood as a code that can be understood and executed by each node (such as a consensus node) of the blockchain system, and can execute any logic and obtain results. A smart contract is a computer protocol that digitally promotes, verifies or executes the negotiation or performance of a contract. It is a piece of code written on the blockchain. Once an event triggers the terms in the contract, the code is automatically executed, that is, it is executed when the conditions are met without human manipulation. Smart contracts can be used to automate the execution of agreements so that all participants can determine the results immediately without the involvement of any middleman or the waste of time. For example, an entity object (such as a user requesting to execute a transaction) can call a smart contract that has been deployed on the blockchain by initiating a transaction request through the client on the terminal it holds.

[0085] Specifically, under the hierarchical structure of the blockchain network, the business node in the business network can send the transaction business request to the consensus node in the corresponding core consensus network (for example, Figure 1 The node 100m shown in the figure is used to authenticate the identity of the user who sent the transaction service request, and when the identity authentication is successful, the transaction service request sent by the user is allowed to be sent to other consensus nodes in the corresponding core consensus network (for example, Figure 1 Node 100g shown) to call these consensus nodes (e.g., Figure 1 The smart contracts running in the nodes 100m and 100g shown execute the transaction requested by the user.

[0086] It should be understood that a blockchain system may include one or more smart contracts, which can be distinguished by contract identifiers (such as identification numbers (Identity document, ID) or names, and may also include contract addresses or contract function names (also called contract method names)). The transaction service request initiated by the client may also carry the identification number or name of the smart contract to specify the smart contract that the blockchain needs to run.

[0087] It is understandable that in order to achieve unified management of digital assets (which can be referred to as assets), the embodiment of the present application provides a novel digital asset management method, using smart contracts, providing one or more interfaces that are mutually related between digital assets, and providing a unified management interface for these digital assets, so that multiple digital assets can be managed in a unified manner, which may involve asset registration, asset association, asset transfer, and asset unbinding. Among them, the digital assets in the embodiment of the present application can be used to represent unique, irreplaceable items, including but not limited to game resources (such as props, equipment, skins, etc. in electronic games), digital artworks, digital collections (such as digital music / video collections), various virtual assets or real assets (such as stocks, funds, securities, membership cards, shopping cards, etc.). Digital assets are created based on blockchain technology, and each digital asset can have its unique identifier (such as the ID of a digital asset, which can be generated by the generation rules specified in the blockchain protocol standard) and metadata, which can include ownership, author, creation time and other detailed information, so each digital asset is unique and cannot be replaced or exchanged.

[0088] Among them, to facilitate subsequent understanding and explanation, the embodiments of the present application may collectively refer to entity objects (such as individual users, corporate users, institutions, etc.) that send transaction business requests to the blockchain network for digital assets held as business objects. Further, in the asset transfer scenario, for ease of distinction, the business object that initiates the asset transfer (for example, user 1) may be referred to as the first business object, and correspondingly, the business object that receives the assets transferred by the first business object (for example, user 2) may be referred to as the second business object. It can be understood that the embodiments of the present application do not limit the types and quantities of digital assets held by the first business object and the second business object. Similarly, the terminal associated with the first business object may be referred to as the first terminal, and the terminal associated with the second business object may be referred to as the second terminal.

[0089] The method provided in the embodiment of the present application can be executed by a consensus node in a blockchain network (for example, the consensus node 100m in the above-mentioned blockchain network 100). Specifically, the consensus node in the blockchain network can obtain a first asset transfer request initiated by a first business object for a first type of asset held; wherein the first type of asset here is obtained after asset registration through an asset registration contract deployed on the blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of asset on the blockchain; the proxy contract can be used to associate a second type of asset held by the first business object with the first type of asset; the second type of asset is different from the first type of asset; further, the consensus node in the blockchain network can call the asset registration contract and the proxy contract to perform permission verification on the first business object based on the first asset transfer request to obtain a first permission verification result; it can be understood that if the first permission verification result indicates that the first business object has the transfer authority for the first type of asset and the second type of asset, then when the first type of asset is transferred to the second business object through the asset registration contract, the second type of asset is synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of asset and the second type of asset is generated.

[0090] It can be understood that the first type of asset in the embodiment of the present application can be understood as the main asset, which is determined after the asset registration of a certain digital asset (such as asset A1) held by the first business object; the second type of asset can be understood as an ancillary asset bound (or associated) to the main asset, where the ancillary asset is determined after the digital asset (such as asset A2, asset A3, etc.) held by the first business object that is different from the main asset is associated with the main asset. Among them, a business object can be registered with one or more main assets at the same time, a main asset can be bound to one or more ancillary assets, and an ancillary asset can only be bound to one main asset. The embodiment of the present application does not limit the number of main assets held by a business object and the number of ancillary assets bound to these main assets. In this way, it can be understood that if the main asset and the ancillary asset are in a bound state, when the main asset is transferred, the associated ancillary assets will be transferred along with the transfer of the main asset, thereby realizing the batch transfer of assets.

[0091] It can be seen from this that, after registering the first type of asset through the asset registration contract, the embodiment of the present application can associate the first type of asset with the second type of asset through the proxy contract, so that different digital assets have relevance, and then the associated digital assets (such as the first type of asset and the second type of asset) can be transferred to the second business object synchronously, that is, a unified asset transfer is completed, so that unified management of multiple digital assets can be achieved. In other words, the embodiment of the present application can associate multiple digital assets through a general smart contract specification interface (such as an asset registration contract interface) for unified management. At the same time, when the associated first type of asset and the second type of asset are transferred, there will also be relevance between the transaction records corresponding to the first type of asset and the transaction records corresponding to the second type of asset. The synchronous transfer transaction records obtained by integrating these associated transaction records can reduce the complexity of the transaction records on the blockchain, and can improve the display effect and traceability of the digital asset transaction records.

[0092] For further understanding, please refer to Figure 2a-2b , Figure 2a-2b Schematic diagram of a data processing scenario provided by an embodiment of the present application. Figure 2a The user A shown is the first business object mentioned above. Figure 2bUser B shown is the second business object mentioned above, wherein user A may hold multiple digital assets, and the number of digital assets held by user A is not limited here. For example, the multiple digital assets held by user A may specifically include asset 1, asset 2, asset 3, ..., asset N; and user B may hold one or more digital assets, or may not hold any digital assets, which is not limited in this embodiment of the present application. It can be understood that the terminal 20A used by user A is the first terminal mentioned above, and user A can send the corresponding transaction business request to the blockchain network through the client 21a running on the terminal 20A. In addition, Figure 2a The consensus node 20B shown can be any consensus node in the blockchain network.

[0093] like Figure 2a As shown, in order to support the correlation between digital assets on the blockchain and realize the unified management of digital assets, a digital asset (e.g., asset 1) held by user A can be registered as a first type of asset (i.e., the main asset) through an asset registration contract (e.g., asset registration contract 21c) pre-deployed on the blockchain corresponding to the blockchain network where the consensus node 20B is located, and then a corresponding proxy contract (e.g., proxy contract 21d) can be deployed on the above blockchain for the first type of asset (e.g., asset 1) through the asset registration contract (e.g., asset registration contract 21c), and the proxy contract (e.g., proxy contract 21d) is bound to the first type of asset (e.g., asset 1) to record the main asset (e.g., asset 1) managed by the proxy contract account corresponding to the proxy contract (e.g., proxy contract 21d). It can be understood that the first type of asset and the proxy contract (or proxy contract account) are bound one-to-one. Furthermore, through the above-mentioned proxy contract (for example, proxy contract 21d), any one or more digital assets among the digital assets held by user A except the first type of assets (for example, asset 1) can be associated with the first type of assets. For example, asset 2, asset 3, ..., and asset N held by user A can be associated with the above-mentioned asset 1, so that asset 2, asset 3, ..., and asset N can be used as second type assets (i.e., subsidiary assets) associated with the first type of assets (for example, asset 1). In this way, the associated first type of assets (for example, asset 1) and second type of assets (for example, asset 2, asset 3, ..., asset N) can be managed uniformly later.

[0094] Further, assuming that user A wishes to transfer the associated first type assets and second type assets to user B, user A can send a first asset transfer request (e.g., asset transfer request 21b) to the consensus node 20B in the blockchain network for the first type assets (e.g., asset 1) held by the user through the client 21a running on the terminal 20A. After receiving the asset transfer request 21b, the consensus node 20B can call the asset registration contract (e.g., asset registration contract 21c) and the proxy contract (e.g., proxy contract 21d) on the blockchain based on the asset transfer request 21b to perform authority verification on user A (i.e., verify whether user A has the transfer authority for the first type assets and the second type assets), thereby obtaining a first authority verification result (e.g., authority verification result 21e).

[0095] It is understandable that if Figure 2b As shown, if the above-mentioned first authority verification result (for example, authority verification result 21e) indicates that user A has the transfer authority for the first type of assets (for example, asset 1) and the second type of assets (for example, asset 2, asset 3, ..., asset N), then the consensus node 20B will transfer the first type of assets (for example, asset 1) to user B through the above-mentioned asset registration contract (for example, asset registration contract 21c), and will also transfer the second type of assets (for example, asset 2, asset 3, ..., asset N) to user B simultaneously, that is, the above-mentioned assets 1 to asset N are transferred to user B in batches, thereby realizing the unified management of assets 1 to asset N.

[0096] In addition, if Figure 2bAs shown, after the asset transfer is successful, the consensus node 20B will also generate transaction records corresponding to the first type of asset (for example, transaction record T1 corresponding to asset 1) and transaction records corresponding to the second type of asset (for example, transaction record T2 corresponding to asset 2, transaction record T3 corresponding to asset 3, ..., transaction record TN corresponding to asset N), each transaction record can display the transaction information of the corresponding digital asset, for example, transaction record T1 displays the transaction history of asset 1 transferred from user A to user B, and asset 2 is transferred to user B as an affiliated asset of asset 1, so transaction record T2 also displays the transaction history of asset 2 transferred from user A to user B, and transaction records T3 to transaction records TN are the same. It can be seen that, due to the association between the first type of asset and the second type of asset, the transaction record corresponding to the first type of asset (i.e., the transaction record corresponding to the main asset) can be regarded as the overall transaction record (i.e., unified transaction information) of all associated digital assets, and the overall transaction record is displayed to the user; the user can quickly obtain the transaction record of the second type of asset bound to it through the transaction record of the first type of asset, and the advantage of doing so is to facilitate the display and tracing of the transaction history of multiple digital assets. In an embodiment of the present application, the transaction records corresponding to the first type of assets (for example, transaction record T1) and the transaction records corresponding to the second type of assets (for example, transaction record T2, transaction record T3, ..., transaction record TN) can also be integrated into synchronous transfer transaction records. Compared with independent transaction records, the embodiment of the present application improves the correlation between transaction records. Therefore, after these transaction records are associated and stored, the complexity of the transaction records on the blockchain can be reduced, and the display effect and traceability of digital asset transaction records can be effectively improved.

[0097] It is understandable that when user B holds multiple digital assets, he can also perform operations similar to those performed by user A above, such as asset registration, asset association, and asset transfer, so as to better unify the management of the multiple digital assets he holds. The specific implementation process will not be repeated here.

[0098] It should be noted that, in the embodiment of the present application, a prompt interface or pop-up window may be displayed when performing asset registration, asset association, asset transfer or asset unbinding. The prompt interface or pop-up window is used to prompt the business object that it is currently collecting account addresses, asset registration data, associated asset data, asset transfer information, asset unbinding information, signature information and other data. Only after the business object issues a confirmation operation on the prompt interface or pop-up window, the relevant steps of data acquisition are started, otherwise the process ends.

[0099] In addition, it can be understood that in the specific implementation of the present application, account addresses, asset registration data, associated asset data, asset transfer information, asset unbinding information, signature information and other data related to business objects such as users, enterprises and institutions may be involved. When the above embodiments of the present application are applied to specific products or technologies, it is necessary to obtain the permission or consent of business objects such as users, enterprises and institutions, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0100] Among them, based on the first asset transfer request obtained, the consensus node calls the asset registration contract and the proxy contract to verify the authority of the first business object, and when the first business object has the transfer authority for the first type of assets and the second type of assets, the first type of assets and the associated second type of assets are synchronously transferred to the second business object through the asset registration contract, and the specific implementation method of generating the synchronous transfer transaction record associated with the first type of assets and the second type of assets can be found in the following Figure 3-Figure 10 The corresponding embodiment.

[0101] For further information, see Figure 3 , Figure 3 is a flow chart of a data processing method provided in an embodiment of the present application. Figure 3 As shown, the method can be executed by a consensus node in the blockchain network. For example, the consensus node can be the above Figure 1 Any consensus node (e.g., node 100m) in the blockchain network 100 shown. The method may specifically include the following steps S101-S103:

[0102] Step S101, obtaining a first asset transfer request initiated by a first business object for a first type of asset held;

[0103] It is understandable that different digital assets are independent of each other. In order to make different digital assets have associations, and the associated digital assets can complete a unified transfer, and have associated transaction records, the embodiment of the present application provides a business object with an interface for the association between multiple digital assets through an asset registration contract, and provides a unified management interface for these associated digital assets. Among them, the asset registration contract is a smart contract pre-deployed on the blockchain corresponding to the blockchain network, which can be used for asset registration and provides an interface for business objects to configure assets (that is, business objects can interact with the asset registration contract).

[0104] Based on this, before transferring multiple digital assets in a unified manner, it is necessary to establish the association relationship between these digital assets. Among them, the first type of assets are obtained after asset registration through the asset registration contract on the blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of assets on the blockchain; the proxy contract is used to associate the second type of assets held by the first business object with the first type of assets; the second type of assets are different from the first type of assets. In other words, the first type of assets (i.e., the main assets) can be registered through the asset registration contract first, and then a proxy contract can be deployed for the first type of assets through the asset registration contract, and the first type of assets can be bound to the proxy contract, and then the first type of assets can be associated with the second type of assets (i.e., the subsidiary assets) through the proxy contract, thereby establishing the association between the first type of assets and the second type of assets, reducing the difficulty of unified asset management.

[0105] Specifically, the consensus node can obtain an asset registration request initiated by the first business object, and the asset registration request can be sent to the consensus node by the first terminal corresponding to the first business object; further, the asset registration contract on the blockchain can be called based on the asset registration request to register the first digital asset held by the first business object as a first type of asset (i.e., the main asset); and then, an agent contract for managing the first type of assets can be deployed on the blockchain through the asset registration contract, and the first type of assets can be bound to the agent contract; further, when the consensus node obtains an asset association request initiated by the first business object for the first type of assets, the agent contract can be called based on the asset association request to associate a second digital asset held by the first business object that is different from the first digital asset with the first type of asset to obtain a second type of asset (i.e., an affiliated asset) associated with the first type of asset.

[0106] The first business object may hold multiple digital assets, and the first digital asset may be any digital asset among the multiple digital assets held by the first business object (for example, the above Figure 2a The first digital asset is not limited to the specific type of the first digital asset. Accordingly, the second digital asset may include any one or more digital assets different from the first digital asset among the multiple digital assets held by the first business object (for example, the above Figure 2aThe specific type and quantity of the second digital asset are not limited here. It should be noted that a business object can register one or more first-type assets (i.e., main assets) through an asset registration contract, and each first-type asset will be bound to a corresponding proxy contract (i.e., one proxy contract is only bound to one first-type asset), and is also bound to the proxy contract account corresponding to the proxy contract; and a first-type asset can be bound to multiple second-type assets (i.e., subsidiary assets), but the second-type assets bound to different first-type assets are different (i.e., one second-type asset can only be bound to one first-type asset), therefore, the bound first-type assets (i.e., main assets) and their associated second-type assets (i.e., subsidiary assets) can be uniformly managed through different proxy contract accounts. It can be understood that after the association between the first-type assets and the second-type assets is established through the above process, when the first-type assets are transferred, the second-type assets associated with the first-type assets can be transferred synchronously, thereby realizing the unified transfer of multiple associated digital assets (i.e., batch transfer), which is conducive to improving the unified management capabilities and transfer efficiency of multiple digital assets.

[0107] The asset registration request carries the asset registration data submitted by the first business object for the first digital asset held and the first signature information of the first business object; the first signature information is obtained by the first terminal signing the asset registration data through the private key information of the first business object; the first signature information carries the public key information corresponding to the private key information; optionally, since the public key information of the first business object belongs to private content, the first signature information may also carry the public key address generated by the public key information, and the signature may be subsequently verified through the public key address; the private key information and public key information of the first business object may be configured by the object key management tool (i.e., the blockchain key management tool) associated with the first business object, and the public key information may be generated by the private key information; the asset registration data here may include the asset identifier of the first digital asset (which may be called the first asset identifier) ​​and some metadata that need to be registered, such as the ownership of the first digital asset (i.e., the address of the holding object of the first digital asset), the creation time, etc., and may also include other information required for asset registration, and the specific content of the asset registration data is not limited here. Based on this, after obtaining the asset registration request, the consensus node can first verify the legitimacy of the asset registration request, and when the legitimacy verification passes, the asset registration request is added to the transaction pool to be packaged into a block chain. Specifically, the consensus node can obtain the first signature information from the asset registration request, and can verify the signature of the first signature information through the public key information (or public key address) carried by the first signature information to obtain the first signature verification result; further, when the first signature verification result indicates that the signature verification is successful, the consensus node can call the asset registration contract on the blockchain based on the asset registration data carried by the asset registration request, and register the first digital asset as a first type of asset, that is, record the above-mentioned asset registration data (such as the asset identification, ownership and other information of the first digital asset) in the asset registration contract, so that the first digital asset can be registered as a first type of asset in the asset registration contract. It can be understood that in addition to signature verification, legitimacy verification can also include other content, which will not be expanded here.

[0108] When the consensus node obtains the first signature information, it can use an asymmetric encryption algorithm (such as an ECDSA signature algorithm) to verify the signature. Specifically, the first signature information can be signed and verified by the public key information (or public key address) carried by the first signature information to obtain the summary information of the original asset registration data (which can be called the first summary information, such as summary information H1); at the same time, the asset registration data carried in the asset registration request can be hashed using the same hash algorithm as the first terminal, so as to obtain the summary information of the asset registration data (which can be called the second summary information, such as summary information H2); further, the consensus node can use the signature verification to obtain the summary information of the asset registration data. The first summary information (such as summary information H1) is compared with the second summary information (such as summary information H2) obtained by hash operation. If the first summary information is the same as the second summary information, it can be understood that the first signature information verification is successful, the asset registration request is a legal request, and the consensus node can write the asset registration request into the blockchain; if the first summary information is different from the second summary information, it can be understood that the first signature information verification failed, the asset registration request is an illegal request, and the consensus node can return corresponding prompt information (which can be called first prompt information) to the first terminal, and the first prompt information can be used to indicate that the first signature information verification failed (that is, the asset registration request is an illegal request).

[0109] Among them, the above-mentioned asset registration data includes the first asset identifier (i.e., the ID of the first digital asset) corresponding to the first digital asset as the first type of asset; then the specific process of deploying the proxy contract for the first type of asset and binding the two can be: the consensus node deploys the proxy contract for managing the first type of asset on the blockchain through the asset registration contract, and configures the contract holding object address of the proxy contract as the first account address of the first business object; wherein the first account address is determined by the public key information of the first business object; further, the consensus node can obtain the first asset identifier from the asset registration data, and establish a binding relationship between the first asset identifier and the proxy contract account corresponding to the proxy contract through the asset registration contract (i.e., establish a binding relationship between the first type of asset and the proxy contract account); the binding relationship can be used to indicate that the first type of asset is managed by the proxy contract account. In other words, the asset registration contract will record the binding relationship between the first type of asset and the proxy contract (account) so as to clarify that the proxy contract account has the ability to manage the first type of asset, thereby maintaining effective management of the first type of asset.

[0110] Optionally, after completing the asset registration, the consensus node may return a registration success notification message to the first terminal to notify the first business object that the asset registration is successful.

[0111] Among them, the proxy contract account (referred to as the proxy account) is an independent contract account, which is generated when registering the first type of asset and is bound to the first type of asset one-to-one, which is equivalent to providing a proxy service for the first type of asset, and all transfer transactions related to the first type of asset can be completed through the proxy service. In other words, it can be understood that the first business object authorizes the asset management capability to the proxy contract account, so that the proxy contract account can manage the main asset it is bound to (for example, transfer the main asset). At this time, the proxy contract account is the agent of the first business object, so that the assets in the proxy contract account can be managed in a unified manner.

[0112] For easier understanding, please also refer to Figure 4 , Figure 4 This is a schematic diagram of the relationship between an asset and a proxy contract account provided in an embodiment of the present application. Figure 4 As shown, user 1 is the first business object mentioned above. User 1 can register a main asset M (i.e., the first type of asset) held by the user through the external interface provided by the asset registration contract. Then, the asset registration contract can bind the main asset M to the proxy contract account corresponding to the proxy contract deployed for the main asset M one-to-one. After the binding is successful, the proxy contract account can manage the main asset M on behalf of user 1. It can be understood that the smart contract managed by the proxy contract account (i.e., the proxy contract) can support the following functions: (1) asset association; (2) asset association release (i.e., asset unbinding); (3) asset call (i.e., asset transfer). Among them, asset association refers to binding the subsidiary asset and the main asset, asset association release refers to releasing the association between the subsidiary asset and the main asset, and asset call refers to configuring and using the subsidiary asset. Based on this, the embodiment of the present application can use an independent account (i.e., the proxy contract account) to manage assets to support the association between digital assets.

[0113] Among them, the first business object can send an asset association request for the first type of asset to the consensus node through the first terminal, and the asset association request carries the associated asset data submitted by the first business object for the first type of asset and the second signature information of the first business object; the associated asset data is determined by the second digital asset held by the first business object that is different from the first digital asset, and the associated asset data may include the asset identifier of the first digital asset as the first type of asset (i.e., the first asset identifier) ​​and the asset identifier of the second digital asset (which may be called the second asset identifier), and may also include other information required for asset association. The specific content of the associated asset data is not limited here; the second signature information is obtained by signing the associated asset data with the private key information of the first business object; the second signature information carries the public key information corresponding to the private key information (or the public key address determined by the public key information). Based on this, after obtaining the asset association request, the consensus node can first verify the legitimacy of the asset association request, and when the legitimacy verification passes, the asset association request is added to the transaction pool to be packaged into a block chain. Specifically, the consensus node can obtain the second signature information from the asset association request, and can verify the second signature information through the public key information (or public key address) carried by the second signature information to obtain the second signature verification result; further, when the second signature verification result indicates that the signature verification is successful, the consensus node can call the asset registration contract, obtain the proxy contract address of the proxy contract, and forward the asset association request to the proxy contract according to the proxy contract address; wherein, the proxy contract address refers to the contract address of the proxy contract deployed on the blockchain, which is determined when the asset registration contract deploys the proxy contract, and the asset registration contract will record the proxy contract address. Further, the consensus node can call the proxy contract based on the associated asset data carried by the asset association request, associate the second digital asset with the first type of asset, and thus obtain the second type of asset associated with the first type of asset. In this way, digital assets can be bound to each other, improving the correlation between digital assets, thereby improving the ability to uniformly manage multiple digital assets. For example, see above Figure 4 ,like Figure 4 As shown, after registering the main asset M, user 1 can bind multiple digital assets held as subsidiary assets associated with the main asset M (i.e., second-type assets, such as subsidiary asset a, subsidiary asset b, ..., subsidiary asset x, subsidiary asset y). Subsequently, the proxy contract account bound to the main asset M can uniformly manage the main asset M and subsidiary assets a, subsidiary asset b, ..., subsidiary asset x, and subsidiary asset y, thereby improving asset management efficiency.

[0114] When the consensus node obtains the second signature information, it can also use an asymmetric encryption algorithm (such as the ECDSA signature algorithm) to verify the signature. Specifically, the second signature information can be signed and verified by the public key information (or public key address) carried by the second signature information to obtain the summary information of the original associated asset data (which can be called the third summary information, such as summary information H3); at the same time, the associated asset data carried in the asset association request can be hashed using the same hash algorithm as the first terminal, so as to obtain the summary information of the associated asset data (which can be called the fourth summary information, such as summary information H4); further, the consensus node can use the signature verification to obtain the summary information of the associated asset data. The third summary information (such as summary information H3) is compared with the fourth summary information (such as summary information H4) obtained by performing the hash operation. If the third summary information is the same as the fourth summary information, it can be understood that the second signature information verification is successful, and the asset association request is a legal request. The consensus node can write the asset association request into the blockchain; if the third summary information is different from the fourth summary information, it can be understood that the second signature information verification failed, and the asset association request is an illegal request. The consensus node can return corresponding prompt information (which can be called second prompt information) to the first terminal, and the second prompt information can be used to indicate that the second signature information verification failed (that is, the asset association request is an illegal request).

[0115] It can be understood that when the asset association is completed, the above-mentioned second type of assets (i.e., subsidiary assets) will be transferred to the proxy contract account. Since the first type of assets (i.e., main assets) do not have account attributes and cannot own other assets, by establishing a corresponding proxy contract account, the first type of assets can have the ability of an account and own other assets (i.e., associated subsidiary assets). When the first type of assets are transferred, the associated second type of assets can also be transferred synchronously, which improves the efficiency of asset transfer and thus realizes efficient management of digital assets.

[0116] Among them, it can be understood that the first business object mainly interacts with the asset registration contract, and does not directly call the proxy contract. Therefore, in the above-mentioned asset association scenario, the asset registration contract will forward the asset association request to the proxy contract for processing, which is equivalent to the asset registration contract having a forwarding function; similarly, in the subsequent asset transfer and asset unbinding scenarios, the asset registration contract will also forward the relevant requests to the proxy contract. It can be seen that the embodiment of the present application can provide a unified standardized interface to the outside through the asset registration contract, and then the asset registration contract calls the corresponding proxy contract to handle different businesses, which reduces the difficulty of business operations and improves the ability to manage assets.

[0117] It can be understood that before forwarding the asset association request to the proxy contract, the first business object needs to be authenticated through the asset registration contract. Only when it is confirmed that the holder of the first type of asset (also referred to as the holding object) is the first business object, the asset association request can be forwarded to the proxy contract. Specifically, the consensus node can first verify the authority of the first business object through the asset registration contract to obtain a second authority verification result; further, when the second authority verification result indicates that the first business object holds the first type of asset, the consensus node can obtain the proxy contract address of the proxy contract, and then forward the asset association request to the proxy contract according to the proxy contract address.

[0118] The specific process of the consensus node verifying the authority of the first business object through the asset registration contract can be: obtaining the first asset holding object address corresponding to the first type of asset through the asset registration contract, and the first asset holding object address refers to the account address of the holder of the first type of asset. For example, Figure 4 The holder of the main asset M shown is user 1, then the asset holding object address of the main asset M is the account address of user 1; then the first asset holding object address can be compared with the first account address of the first business object; wherein the first account address is determined by the public key information of the first business object, and can be used to identify the first business object on the blockchain; optionally, if the first asset holding object address is the same as the first account address, it can be determined that the first business object holds the first type of asset; at this time, the result when the first business object holds the first type of asset can be used as the second permission verification result. Conversely, optionally, if the first asset holding object address is not the same as the first account address, it can be determined that the first business object does not hold the first type of asset, and asset association can no longer be performed at this time. The consensus node can return an association failure notification message to the first terminal to prompt the first business object asset association failure.

[0119] It can be understood that before the asset association is performed, the first business object needs to be authenticated through the proxy contract, and the subsequent asset association operation can only be performed when the holder of the second digital asset is confirmed to be the first business object. Among them, the above-mentioned associated asset data includes the second asset identifier corresponding to the second digital asset (i.e., the ID of the second digital asset); the proxy contract includes an asset association function; then the specific process of the consensus node calling the proxy contract to associate the second digital asset with the first type of asset can be: when the second asset identifier is obtained from the associated asset data carried by the asset association request, the consensus node can verify the authority of the first business object through the proxy contract to obtain a third authority verification result; further, when the third authority verification result indicates that the first business object holds the second digital asset corresponding to the second asset identifier, the consensus node can establish an association relationship between the second asset identifier and the first asset identifier corresponding to the first digital asset as the first type of asset (i.e., establish an association relationship between the second type of asset and the first type of asset) through the asset association function in the proxy contract; the association relationship can be used to indicate that when the second digital asset is used as a second type of asset associated with the first type of asset, both the first type of asset and the second type of asset belong to the proxy contract account corresponding to the proxy contract. It can be seen that since the correlation between the first type of assets and the second type of assets is established, the first type of assets and the second type of assets will be managed by the proxy contract account, thereby achieving unified and efficient management of multiple digital assets.

[0120] Optionally, after completing the asset association, the consensus node may return an association success notification message to the first terminal to notify the first business object that the asset association is successful.

[0121] The specific process of the consensus node verifying the authority of the first business object through the proxy contract can be: obtaining the second asset holding object address corresponding to the second digital asset corresponding to the second asset identifier through the proxy contract, and the second asset holding object address refers to the account address of the holder of the second digital asset. For example, Figure 4 The holder of the subsidiary asset a shown is user 1, then the asset holding object address of the subsidiary asset a is the account address of user 1; then the second asset holding object address can be compared with the first account address of the first business object; optionally, if the second asset holding object address is the same as the first account address, it can be determined that the first business object holds the second digital asset; at this time, the result when the first business object holds the second digital asset can be used as the third permission verification result. Conversely, optionally, if the second asset holding object address is not the same as the first account address, it can be determined that the first business object does not hold the second digital asset, and asset association can no longer be performed at this time. The consensus node can return an association failure notification message to the first terminal to prompt the first business object asset association failure.

[0122] It can be understood that after completing the asset registration and asset association through the above steps, the association relationship between the first type of assets and the second type of assets is established, and then these associated digital assets can be managed in a unified manner (such as asset transfer).

[0123] Among them, the consensus node can obtain the first asset transfer request initiated by the first business object for the first type of assets held, and the first asset transfer request can be sent by the first business object to the consensus node through the first terminal. Further, the consensus node can verify the legitimacy of the first asset transfer request, and write the first asset transfer request into the blockchain when the legitimacy verification passes. Among them, the first asset transfer request carries the first asset transfer information submitted by the first business object for the first type of assets and the third signature information of the first business object; wherein the first asset transfer information may include the asset identifier of the first type of assets (i.e., the first asset identifier), the account address of the asset receiving object (i.e., the second account address of the second business object) and other information required for asset transfer, and the specific content of the first asset transfer information is not limited here. The third signature information is obtained by signing the first asset transfer information with the private key information of the first business object; the third signature information carries the public key information corresponding to the private key information (or the public key address determined by the public key information). Based on this, after obtaining the first asset transfer request, the consensus node can first obtain the third signature information from the first asset transfer request, and can perform signature verification on the third signature information through the public key information (or public key address) carried by the third signature information to obtain the third signature verification result; further, when the third signature verification result indicates that the signature verification is successful, it is determined that the first asset transfer request is a legitimate request, and the first asset transfer request is written into the blockchain.

[0124] Among them, the specific process of verifying the signature of the third signature information through the public key information carried by the third signature information can be referred to the process of verifying the signature of the first signature information or the second signature information above, and will not be repeated here.

[0125] Optionally, if the third signature verification result indicates that the signature verification failed, it can be determined that the first asset transfer request is an illegal request, and the consensus node can return corresponding prompt information (which may be referred to as third prompt information) to the first terminal. The third prompt information can be used to indicate that the third signature information verification failed (that is, the first asset transfer request is an illegal request).

[0126] Step S102: Based on the first asset transfer request, the asset registration contract and the proxy contract are called to perform permission verification on the first business object to obtain a first permission verification result;

[0127] It is understandable that after the consensus node receives the first asset transfer request, it is also necessary to authenticate the first business object through the asset registration contract and the proxy contract (i.e., verify the authority of the first business object) before executing the asset transfer. When it is confirmed that the holder of the first type of asset is the first business object and the second type of asset is associated with the first type of asset, the first business object is considered to have the transfer authority for the first type of asset and the second type of asset, and then the first type of asset and the second type of asset can be transferred to other business objects (such as the second business object) to ensure asset security.

[0128] The specific process of the consensus node calling the asset registration contract and the proxy contract to verify the authority of the first business object can be: based on the first asset transfer request, calling the asset registration contract to obtain the first asset holding object address corresponding to the first type of asset (such as the above Figure 2a The asset holding object address of asset 1 shown in the figure) and then the first asset holding object address and the first account address of the first business object (such as the above Figure 2a If the address of the first asset holding object is the same as the first account address, it can be determined that the holder of the first type of asset is the first business object, and the first business object has the transfer authority for the first type of asset. For example, in the above Figure 2a In the corresponding embodiment, the asset registration contract 21c compares the asset holding object address of asset 1 with the account address of user A, and can determine that user A has the transfer authority for asset 1; then the proxy contract address of the proxy contract can be obtained through the asset registration contract, and the first asset transfer request can be forwarded to the proxy contract according to the proxy contract address. For example, in the above Figure 2a In the corresponding embodiment, the asset transfer request 21b can be forwarded to the proxy contract 21d; further, the consensus node can call the proxy contract to find an asset identifier that has an association relationship with the first asset identifier of the first type of asset based on the first asset transfer request, and use the found asset identifier as the target asset identifier (such as the above Figure 2a The target asset identifier can be associated with the second type of asset (such as the asset identifiers of asset 2 to asset N shown above). Figure 2a By comparing the second asset identifiers of the target asset 2 to the asset N shown in FIG. 1 , it can be understood that when the target asset identifier and the second asset identifier are the same, it can be determined that the second type of asset is associated with the first type of asset, and the first business object has the transfer authority for the second type of asset; for example, in the above Figure 2aIn the corresponding embodiment, through the proxy contract 21d, authentication can be performed to determine that assets 2 to N are associated with asset 1, so that it can be determined that user A has the transfer authority for assets 2 to N. Finally, the result when the first business object has the transfer authority for the first type of assets and the second type of assets can be used as the first authority verification result.

[0129] It can be seen that by verifying whether the current user (i.e., the first business object) has ownership of the relevant assets, it can be determined whether the user has the transfer authority for these assets. Only the real holder of the assets can operate the assets in the proxy contract account, thereby ensuring the security of the assets. In the embodiment of the present application, the bound digital assets can be regarded as a whole. For the main asset in this whole, it is only necessary to care about who its holder (also known as the owner) is, and for the remaining subsidiary assets, it is only necessary to care about whether they are bound to the main asset, so as to reflect the correlation and integrity between multiple digital assets. In this way, when the main asset is transferred, it can also be known that the subsidiary assets will be transferred synchronously with the main asset, and at the same time, the efficiency of asset transfer can be improved and the difficulty of asset management can be reduced.

[0130] Step S103, if the first permission verification result indicates that the first business object has the transfer authority for the first type of assets and the second type of assets, then when the first type of assets are transferred to the second business object through the asset registration contract, the second type of assets are synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of assets and the second type of assets is generated.

[0131] It can be understood that if the first permission verification result indicates that the first business object has the transfer authority for the first type of assets and the second type of assets, the consensus node can call the asset registration contract to transfer the first type of assets and the second type of assets to the second business object, realize the main asset transfer (i.e., batch transfer), and at the same time generate synchronous transfer transaction records associated with the first type of assets and the second type of assets.

[0132] Specifically, when the consensus node transfers the first type of asset to the second business object through the asset registration contract, it can change the holding authority of the first type of asset and simultaneously transfer the second type of asset to the second business object; in addition, it can also generate the first transaction record corresponding to the first type of asset (for example, the above Figure 2b The transaction record T1 shown in FIG. 1 and the second transaction record corresponding to the second type of asset (for example, the transaction record T2 shown in FIG. 1 ) Figure 2bThe transaction records T2, T3, ..., TN shown in the figure can be used as synchronous transfer transaction records associated with the first type of assets and the second type of assets; wherein each transaction record here can be used to record the asset identifier (i.e., the ID of the digital asset), the asset transfer object (contract parameter from, i.e., the first business object), and the asset receiving object (contract parameter to, i.e., the second business object) of the digital asset involved, so as to facilitate the intuitive display of the transaction information of the digital asset; and the second transaction record is associated with the first transaction record. It can be understood that the synchronous transfer transaction record here can integrate the associated transaction records (i.e., the first transaction record and the second transaction record). In the batch transfer scenario, after the first type of assets and the second type of assets are regarded as a whole, only the first transaction record corresponding to the first type of assets can be displayed (for example, the above Figure 2b The transaction record T1 shown is taken as a whole transaction record, which is more concise and efficient in display effect and can reduce the complexity of transaction records on the blockchain; in addition, based on the correlation between the first type of assets and the second type of assets (or the correlation between the first transaction record and the second transaction record), it is helpful to trace back to the second transaction record corresponding to the second type of assets, thereby effectively improving the display effect and traceability of digital asset transaction records.

[0133] In addition, it should be noted that when executing asset association, the second type of assets are transferred to the proxy contract account through the proxy contract. Therefore, corresponding transaction records will also be generated for the second type of assets, which can be called associated transfer transaction records. The associated transfer transaction records can be used to record the transaction information of the second type of assets transferred from the account of the first business object to the proxy contract account, thereby reflecting the relationship between the second type of assets and the proxy contract account, and to a certain extent, it also helps to trace the transaction history of multiple digital assets.

[0134] Optionally, after completing the asset transfer, the consensus node may return a first transfer success notification message to the first terminal to notify the first business object that the transfer of the first type of assets and the second type of assets is successful.

[0135] Among them, the specific process of the consensus node changing the holding authority for the first type of asset can be: through the asset registration contract, the asset holding object of the first type of asset is changed from the first business object to the second business object (that is, the ownership of the first type of asset is modified), and the contract holding object address of the proxy contract is changed from the first account address of the first business object to the second account address of the second business object (that is, changing the holder of the proxy contract is equivalent to modifying the external address of the proxy contract, but the proxy contract address remains unchanged). It can be understood that the proxy contract can be configured with two addresses, one is the contract holding object address (that is, the account address corresponding to the holder of the proxy contract), which is an external address that can be changed manually; the other is the proxy contract address, which is generated when the proxy contract is deployed, determined by the proxy contract itself, and usually does not change. The proxy contract address and the contract holding object address can be understood as a one-to-one mapping relationship. As the main asset is transferred between different business objects, this mapping relationship will also change dynamically.

[0136] For easier understanding, please also refer to Figure 5 , Figure 5 Schematic diagram of a scenario of a primary asset transfer provided by an embodiment of the present application. Figure 5 As shown, combined with the above Figure 4 In the corresponding embodiment, after user 1 (i.e., the first business object) transfers the asset, user 2 (i.e., the second business object) obtains the ownership of the main asset M (i.e., the first type of asset), and the binding relationship between the main asset M and the proxy contract account remains unchanged. At the same time, the association relationship between the subsidiary assets a, subsidiary assets b, ..., subsidiary assets x, subsidiary assets y (i.e., the second type of assets) and the main asset M has not changed, which is equivalent to that these subsidiary assets have not been transferred and are still under the proxy contract account. Therefore, the batch transfer method of multiple digital assets provided in the embodiment of the present application is a lightweight operation. In other words, the embodiment of the present application can support the synchronous transfer of multiple digital assets through lightweight operations without the need to transfer each digital asset one by one, thereby effectively improving the efficiency of asset transfer and reducing the difficulty of asset management.

[0137] As can be seen from the above, the embodiment of the present application proposes a method for unified management of multiple digital assets for the first time. After registering the first type of assets through the asset registration contract, the first type of assets and the second type of assets can be associated through the proxy contract to make the different digital assets have associations, and then the associated digital assets (such as the first type of assets and the second type of assets) can be synchronously transferred to the second business object, that is, the unified asset transfer is completed, so that the unified management of multiple digital assets can be achieved, and the efficiency of asset transfer can be improved. At the same time, when the associated first type of assets and second type of assets are transferred, there will also be an association between the transaction records corresponding to the first type of assets and the transaction records corresponding to the second type of assets. The synchronous transfer transaction records obtained by integrating these associated transaction records can reduce the complexity of the transaction records on the blockchain, and can improve the display effect and traceability of digital asset transaction records.

[0138] For further information, see Figure 6 , Figure 6 is a flow chart of a data processing method provided in an embodiment of the present application. Figure 6 As shown, the method can be executed by a consensus node in the blockchain network. For example, the consensus node can be the above Figure 1 Any consensus node (e.g., node 100m) in the blockchain network 100 shown. The method may specifically include the following steps:

[0139] Step S201, when an asset registration request initiated by the first business object is obtained, the asset registration contract on the blockchain is called based on the asset registration request, the first type of asset is registered, and the first type of asset is bound to the proxy contract deployed by the asset registration contract;

[0140] For easier understanding, please also refer to Figure 7 , Figure 7 This is a flow chart of an asset registration process provided by an embodiment of the present application. Figure 7 As shown in the figure, asset registration refers to registering a digital asset as the main asset, which mainly includes the following steps:

[0141] Step S2011: the first business object (such as the above Figure 4 The user 1) initiates an asset registration request (also referred to as a registration request) through the first terminal. After receiving the asset registration request, the consensus node calls the asset registration contract deployed on the blockchain to register the main asset (i.e. the first type of asset, such as the above Figure 4 The main asset M) shown is registered;

[0142] Step S2012: The consensus node deploys a proxy contract for the main asset through the asset registration contract, and configures the contract holding object address of the proxy contract to the account address of the first business object (i.e. the first account address mentioned above, such as the above Figure 4 The account address of User 1 shown);

[0143] Step S2013: The consensus node sends the asset identifier of the primary asset (i.e., the first asset identifier, such as Figure 4 The ID of the main asset M shown in the figure is bound to the proxy contract in the above step S2012 to record the main asset managed by the proxy contract account corresponding to the proxy contract (such as the above Figure 4 The main asset M shown);

[0144] Step S2014, completing the main asset registration. Optionally, the consensus node can notify the first business object of the success of the main asset registration through the asset registration contract.

[0145] The specific implementation of step S201 can be found in the above Figure 3 The relevant description in step S101 of the corresponding embodiment will not be repeated here.

[0146] Step S202: when an asset association request initiated by the first business object for the first type of asset is obtained, the proxy contract is called based on the asset association request to associate the second type of asset held by the first business object with the first type of asset;

[0147] For easier understanding, please also refer to Figure 8 , Figure 8 This is a flowchart of an asset association provided by an embodiment of the present application. Figure 8 As shown, asset association refers to associating any one or more subsidiary assets with the main asset, which mainly includes the following steps:

[0148] Step S2021, the first business object (such as the above Figure 4 The user 1) initiates a request for a primary asset (i.e., the first type of asset, such as the above) through a first terminal. Figure 4 The consensus node receives the asset association request (also called the associated subsidiary asset request) of the main asset M shown in the figure, and calls the asset registration contract;

[0149] Step S2022, the consensus node obtains the proxy contract address of the proxy contract created when the main asset is registered through the asset registration contract;

[0150] Step S2023, the asset registration contract calls the asset association function of the proxy contract (i.e., the asset association function) according to the proxy contract address in step S2022, and associates the attached assets (i.e., the second type of assets, such as Figure 4 The subsidiary assets a, subsidiary assets b, ..., subsidiary assets x, subsidiary assets y) shown in the figure are related to the main assets (such as the above Figure 4 The main asset M) shown is associated;

[0151] Step S2024, completing the association of the subsidiary assets. Optionally, the consensus node may notify the asset registration contract of the successful association of the subsidiary assets through the proxy contract;

[0152] Step S2025, optionally, after completing the association of the subsidiary assets, the consensus node may notify the first business object of the successful association of the subsidiary assets through the asset registration contract.

[0153] The specific implementation of step S202 can be found in the above Figure 3 The relevant description in step S101 of the corresponding embodiment will not be repeated here.

[0154] Step S203, when a first asset transfer request initiated by the first business object for the first type of assets held is obtained, based on the first asset transfer request, the asset registration contract and the proxy contract are called to perform permission verification on the first business object to obtain a first permission verification result;

[0155] It is understandable that the asset transfer in the embodiments of the present application is divided into two situations: (1) transfer of main assets; (2) transfer of subsidiary assets. The transfer of main assets is a batch transfer, and the subsidiary assets will be transferred along with the transfer of the main assets; the transfer of subsidiary assets is to transfer only the corresponding subsidiary assets.

[0156] It can be understood that in the main asset transfer scenario, the first business object (such as the above Figure 5 The user 1) can initiate a transaction for the first type of asset (i.e., the main asset) held by the first terminal. Figure 5 After receiving the first asset transfer request, the consensus node can call the asset registration contract and the proxy contract to perform permission verification on the first business object to obtain the first permission verification result. The specific process can be found in the above Figure 3 The relevant descriptions in step S101 and step S102 of the corresponding embodiment will not be repeated here.

[0157] Step S204: if the first permission verification result indicates that the first business object has the transfer permission for the first type of assets and the second type of assets, when the first type of assets are transferred to the second business object through the asset registration contract, the second type of assets are synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of assets and the second type of assets is generated;

[0158] It can be understood that the first permission verification result indicates the first business object (such as the above Figure 5 The user 1 shown in the figure has a first type of asset (such as the above Figure 5 The main asset M shown above) and the second type of asset (i.e., the subsidiary asset, such as Figure 5 When the consensus node has the transfer permission for the subsidiary asset a, subsidiary asset b, ..., subsidiary asset x, subsidiary asset y shown in the figure, the consensus node can call the asset registration contract to transfer the first type of asset and the second type of asset to the second business object (such as the above Figure 5 The user 2 shown in the figure) generates a synchronous transfer transaction record associated with the first type of asset and the second type of asset. At the same time, through the asset registration contract, the asset holding object of the first type of asset is changed from the first business object to the second business object, and the contract holding object address of the proxy contract is changed from the first account address of the first business object to the second account address of the second business object, thereby completing the transfer of the main asset. The specific process can be found in the above Figure 3 The relevant description in step S103 of the corresponding embodiment will not be repeated here.

[0159] Step S205: when a second asset transfer request initiated by the first business object for the digital asset to be transferred in the second type of assets is obtained, the asset registration contract and the proxy contract are called based on the second asset transfer request. When it is determined through the proxy contract that the first business object has the transfer authority for the digital asset to be transferred, the digital asset to be transferred and the first type of asset are unbound, the unbound digital asset to be transferred is transferred to the second business object, and a third transaction record corresponding to the digital asset to be transferred is generated;

[0160] For easier understanding, please also refer to Fig. 9 , Fig. 9 Schematic diagram of a scenario of subsidiary asset transfer provided by an embodiment of the present application. Figure 4 The corresponding embodiments are as follows: Fig. 9 As shown, in the attached asset transfer scenario, it is assumed that the second type of assets includes the digital assets to be transferred, and the digital assets to be transferred can be any digital assets in the second type of assets, for example, Fig. 9 The subsidiary asset x shown; when the first business object (such as Fig. 9The user 1) shown in the figure wishes to transfer the digital asset to be transferred (such as the subsidiary asset x) to the second business object (such as Fig. 9 When the user 2 shown in the figure is in the first terminal, the first business object can initiate a second asset transfer request for the digital asset to be transferred (such as the subsidiary asset x) through the first terminal. When the consensus node obtains the second asset transfer request, it can verify the legitimacy of the second asset transfer request, and write the second asset transfer request into the blockchain when the legitimacy verification passes. Among them, the second asset transfer request carries the second asset transfer information submitted by the first business object for the digital asset to be transferred and the fourth signature information of the first business object; wherein, the second asset transfer information may include the asset identification of the digital asset to be transferred, the account address of the asset receiving object (i.e., the second account address of the second business object) and other information required for the asset transfer, and the specific content of the second asset transfer information is not limited here. The fourth signature information is obtained by signing the second asset transfer information with the private key information of the first business object; the fourth signature information carries the public key information corresponding to the private key information (or the public key address determined by the public key information). Based on this, after obtaining the second asset transfer request, the consensus node can first obtain the fourth signature information from the second asset transfer request, and can perform signature verification on the fourth signature information through the public key information (or public key address) carried by the fourth signature information to obtain the fourth signature verification result; further, when the fourth signature verification result indicates that the signature verification is successful, it is determined that the second asset transfer request is a legitimate request, and the second asset transfer request is written into the blockchain.

[0161] The specific process of verifying the signature of the fourth signature information by using the public key information carried by the fourth signature information can be found in the above Figure 3 The process of performing signature verification on the first signature information or the second signature information in step S101 of the corresponding embodiment will not be described in detail here.

[0162] Optionally, if the fourth signature verification result indicates that the signature verification failed, it can be determined that the second asset transfer request is an illegal request, and the consensus node can return corresponding prompt information (which may be referred to as fourth prompt information) to the first terminal. The fourth prompt information can be used to indicate that the fourth signature information verification failed (that is, the second asset transfer request is an illegal request).

[0163] It is understandable that after the consensus node receives the second asset transfer request, it is also necessary to authenticate the first business object before executing the asset transfer. Only when it is confirmed that the first business object has the transfer authority for the digital assets to be transferred can the digital assets to be transferred be transferred to other business objects (such as the second business object), thereby ensuring the security of the assets.

[0164] The consensus node may call the asset registration contract based on the second asset transfer request to obtain the proxy contract address of the proxy contract, and may forward the second asset transfer request to the proxy contract according to the proxy contract address. Optionally, the consensus node may call the asset registration contract based on the second asset transfer request to obtain the first asset holding object address corresponding to the first type of asset (e.g. Fig. 9 The asset holding object address of the main asset M shown in FIG. 1 ) is then associated with the first asset holding object address and the first account address of the first business object (for example, Fig. 9 1) is compared with the account address of user 1 shown in FIG. 1. When the first asset holding object address is the same as the first account address, it can be determined that the holder of the first type of asset is the first business object. For example, Fig. 9 As shown, by comparing the asset holding object address of the main asset M and the account address of user 1 through the asset registration contract, it can be determined that user 1 holds the main asset M; then the proxy contract address of the proxy contract can be obtained through the asset registration contract, and the second asset transfer request can be forwarded to the proxy contract according to the proxy contract address.

[0165] Furthermore, the consensus node may transfer the digital asset to be transferred (for example, Fig. 9 The subsidiary assets x) and the first type of assets (such as Fig. 9 The main asset M) shown in the figure is untied, and then the untied digital asset to be transferred can be transferred to the second business object, and a third transaction record corresponding to the digital asset to be transferred is generated at the same time. The third transaction record can be an independent transaction record, but because the association relationship between the digital asset to be transferred and the first type of asset has been established, it is also helpful to trace the transaction history of the digital asset. For example, Fig. 9 As shown, after authenticating user 1 through the proxy contract and confirming that user 1 has the transfer authority for the subsidiary asset x, the subsidiary asset x can be untied from the main asset M, and the untied asset x can be transferred to user 2. In addition, a transaction record corresponding to asset x can also be generated.

[0166] It can be understood that after the second business object receives the above-mentioned digital assets to be transferred, it can call the asset registration contract to register the digital assets to be transferred as new main assets, or, if the second business object has already registered a main asset, it can bind the digital assets to be transferred as a subsidiary asset of the existing main asset through the proxy contract corresponding to the existing main asset, or it can directly put it into its own account without binding.

[0167] Among them, the consensus node can call the asset transfer function (i.e., asset transfer function) in the proxy contract based on the second asset transfer request, perform permission verification on the first business object, and obtain the fourth permission verification result. Specifically, the consensus node can obtain the asset holding object address corresponding to the digital asset to be transferred (such as the asset holding object address corresponding to the subsidiary asset x) through the proxy contract, and compare the asset holding object address corresponding to the digital asset to be transferred with the first account address of the first business object; optionally, if the two addresses are the same, it can be determined that the first business object holds the digital asset to be transferred, and the result when the first business object holds the digital asset to be transferred can be used as the fourth permission verification result; conversely, optionally, if the two addresses are not the same, it can be determined that the first business object does not hold the digital asset to be transferred, and the first business object does not have the transfer authority for the digital asset to be transferred, and the asset transfer cannot be performed. In addition, other authentication methods can be set to verify user permissions to ensure asset security, such as setting multiple authentication thresholds, which are not limited here.

[0168] Furthermore, when the fourth authority verification result indicates that the first business object holds the digital assets to be transferred, it can be determined that the first business object has the transfer authority for the digital assets to be transferred, and the digital assets to be transferred and the first type of assets can be untied. After the unbinding, the digital assets to be transferred and the first type of assets no longer have an association relationship, so the untied digital assets to be transferred can be transferred to the second business object alone.

[0169] Optionally, after completing the asset transfer, the consensus node may return a second transfer success notification message to the first terminal to notify the first business object that the digital asset to be transferred is successfully transferred.

[0170] As can be seen from the above, in addition to supporting the batch transfer of multiple associated digital assets, the embodiments of the present application can also support the individual transfer of digital assets. Therefore, the method provided by the embodiments of the present application can be applied to a variety of asset management scenarios. When multiple digital assets need to be managed in a unified manner, these digital assets can be associated and bound; and when one or more digital assets need to be managed separately, they do not need to be bound to the main asset, and can be managed by conventional means. It can be seen that the embodiments of the present application expand the way of asset management and can meet a variety of business needs.

[0171] Step S206, when an asset unbinding request initiated by the first business object for the digital asset to be unbound in the second type of assets is obtained, the asset registration contract and the proxy contract are called based on the asset unbinding request. When it is determined through the proxy contract that the first business object holds the digital asset to be unbound, the digital asset to be unbound and the first type of assets are unbound.

[0172] It can be understood that the purposes of unbinding the subsidiary assets are as follows: 1) to be able to be registered as the main asset; 2) to unbind the asset and not be controlled by the main asset; 3) to rebind the new main asset. Based on this, the main asset owner can initiate an asset unbinding request through the proxy contract account, wait for the smart contract to execute successfully, and unbind the asset.

[0173] For easier understanding, please also refer to Fig.10 , Fig.10 This is a schematic diagram of a scenario of unbinding an affiliated asset provided by an embodiment of the present application. Figure 4 The corresponding embodiments are as follows: Fig.10 As shown, in the scenario of unbinding the attached assets, it is assumed that the second type of assets includes the digital assets to be unbound, and the digital assets to be unbound can be any digital asset in the second type of assets, for example, Fig.10 The subsidiary asset y shown; when the first business object (such as Fig.10 The user 1) shown in the figure wishes to unbind the digital asset to be untied from the first type of asset (e.g. Fig.10 When the consensus node obtains the asset unbinding request, it can verify the legitimacy of the asset unbinding request, and write the asset unbinding request into the blockchain when the legitimacy verification passes. Among them, the asset unbinding request carries the asset unbinding information submitted by the first business object for the digital asset to be unbound and the fifth signature information of the first business object; wherein, the asset unbinding information may include the asset identifier of the digital asset to be unbound, the asset identifier of the first type of asset (i.e., the first asset identifier mentioned above) and other information required for asset unbinding, and the specific content of the asset unbinding information is not limited here. The fifth signature information is obtained by signing the asset unbinding information with the private key information of the first business object; the fifth signature information carries the public key information corresponding to the private key information (or the public key address determined by the public key information). Based on this, after obtaining the asset unbinding request, the consensus node can first obtain the fifth signature information from the asset unbinding request, and can perform signature verification on the fifth signature information through the public key information (or public key address) carried by the fifth signature information to obtain the fifth signature verification result; further, when the fifth signature verification result indicates that the signature verification is successful, it is determined that the asset unbinding request is a legitimate request, and the asset unbinding request is written into the blockchain.

[0174] For the specific process of verifying the signature of the fifth signature information using the public key information carried by the fifth signature information, please refer to the above Figure 3 The process of performing signature verification on the first signature information or the second signature information in step S101 of the corresponding embodiment will not be described in detail here.

[0175] Optionally, if the fifth signature verification result indicates that the signature verification failed, it can be determined that the asset unbinding request is an illegal request, and the consensus node can return corresponding prompt information (which may be referred to as the fifth prompt information) to the first terminal. The fifth prompt information can be used to indicate that the fifth signature information verification failed (that is, the asset unbinding request is an illegal request).

[0176] It is understandable that after the consensus node receives the asset unbinding request, it is also necessary to authenticate the first business object before executing the asset unbinding. Only when it is confirmed that the first business object holds the first type of asset and the digital asset to be unbound is associated with the first type of asset, can the binding between the digital asset to be unbound and the first type of asset be released.

[0177] Among them, the consensus node can call the asset registration contract based on the asset unbinding request, obtain the proxy contract address of the proxy contract, and forward the asset unbinding request to the proxy contract according to the proxy contract address. Among them, optionally, the consensus node can call the asset registration contract based on the asset unbinding request to obtain the first asset holding object address corresponding to the first type of asset (for example Fig.10 The asset holding object address of the main asset M shown in FIG. 1 ) is then associated with the first asset holding object address and the first account address of the first business object (for example, Fig.10 1) is compared with the account address of user 1 shown in FIG. 1. When the first asset holding object address is the same as the first account address, it can be determined that the holder of the first type of asset is the first business object. For example, Fig.10 As shown, by comparing the asset holding object address of the main asset M and the account address of user 1 through the asset registration contract, it can be determined that user 1 holds the main asset M; then the proxy contract address of the proxy contract can be obtained through the asset registration contract, and the asset unbinding request can be forwarded to the proxy contract according to the proxy contract address.

[0178] Furthermore, the consensus node can, based on the asset unbinding request, unbind the digital asset to be untied (for example, Fig.10 The subsidiary assets y) and the first type of assets (such as Fig.10 The main asset M shown in the figure is used to unbind the asset (specifically, the asset unbinding function in the proxy contract can be used to unbind the asset). The proxy contract can be used to determine whether the digital asset to be unbound is associated with the first type of asset. If the two are associated, it can be determined that the first business object holds the digital asset to be unbound. The specific process can be found in the above Figure 3 In step S102 of the corresponding embodiment, the description of determining whether the second type of asset is associated with the first type of asset will not be repeated here.

[0179] For example, Fig.10As shown, when it is determined through the proxy contract that user 1 holds the subsidiary asset y, the subsidiary asset y and the main asset M are untied. The untied asset y no longer belongs to the proxy contract account, but is transferred back to user 1's own account. Therefore, asset y is no longer managed by the proxy contract account, nor is it controlled by the main asset M. Subsequently, user 1 can choose to register the asset y as the main asset and bind it with other subsidiary assets; or, it can also bind asset y with other main assets (such as the main asset P) and manage it together with the main asset P; or, it can also transfer the asset y separately to other business objects (such as the above-mentioned user 2).

[0180] It can be seen that the embodiment of the present application also supports the unbinding of any affiliated assets, and does not limit the processing method of the unbound assets. Therefore, the flexibility of the asset management method can be improved, so that it is suitable for various asset management scenarios and can meet various business needs.

[0181] As can be seen from the above, the embodiment of the present application proposes a method for unified management of multiple digital assets for the first time. After registering the first type of assets through the asset registration contract, the first type of assets and the second type of assets can be associated through the proxy contract to make different digital assets have relevance, and then the associated digital assets (such as the first type of assets and the second type of assets) can be synchronously transferred to the second business object, that is, the unified asset transfer is completed, so that the unified management of multiple digital assets can be achieved, and the efficiency of asset transfer can be improved. At the same time, when the associated first type of assets and second type of assets are transferred, there will also be a correlation between the transaction records corresponding to the first type of assets and the transaction records corresponding to the second type of assets. The synchronous transfer transaction records obtained by integrating these associated transaction records can reduce the complexity of the transaction records on the blockchain, and can improve the display effect and traceability of the digital asset transaction records. In addition, the embodiment of the present application can also support the separate transfer of digital assets and the unbinding of affiliated assets, thereby improving the flexibility of the asset management method.

[0182] See also Fig.11 , is a schematic diagram of the structure of a data processing device provided in an embodiment of the present application. Fig.11 As shown, the data processing device 1 can be a computer program (including program code) running on a blockchain node (for example, the aforementioned consensus node 20B). For example, the data processing device 1 can be an application software. It can be understood that the device can be used to execute the corresponding steps in the data processing method provided in the embodiment of the present application. Fig.11As shown, the data processing device 1 may include: a first acquisition module 101, an authority verification module 102, a first transfer module 103, an asset registration module 104, a contract deployment module 105, an asset association module 106, a second acquisition module 107, a first forwarding module 108, a second transfer module 109, a third acquisition module 110, a second forwarding module 111, and an asset unbinding module 112;

[0183] The first acquisition module 101 is used to acquire a first asset transfer request initiated by a first business object for a first type of asset held; the first type of asset is obtained after asset registration through an asset registration contract on a blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of asset on the blockchain; the proxy contract is used to associate a second type of asset held by the first business object with the first type of asset; the second type of asset is different from the first type of asset;

[0184] The authority verification module 102 is used to call the asset registration contract and the proxy contract to perform authority verification on the first business object based on the first asset transfer request, and obtain a first authority verification result;

[0185] The authority verification module 102 may include: a first authentication unit 1021, a second authentication unit 1022, and a result determination unit 1023;

[0186] The first authentication unit 1021 is used to call the asset registration contract to obtain the first asset holding object address corresponding to the first type of asset based on the first asset transfer request, compare the first asset holding object address with the first account address of the first business object, and determine that the first business object has the transfer authority for the first type of asset when the first asset holding object address and the first account address are the same, and forward the first asset transfer request to the proxy contract;

[0187] The second authentication unit 1022 is used to call the proxy contract to find an asset identifier associated with the first asset identifier of the first type of asset based on the first asset transfer request, use the found asset identifier as the target asset identifier, compare the target asset identifier with the second asset identifier of the second type of asset, and determine that the first business object has the transfer authority for the second type of asset when the target asset identifier and the second asset identifier are the same;

[0188] The result determination unit 1023 is configured to use the result when the first business object has the transfer authority for the first type of assets and the second type of assets as the first authority verification result.

[0189] The specific implementation of the first authentication unit 1021, the second authentication unit 1022, and the result determination unit 1023 can be found in the above Figure 3The description of step S102 in the corresponding embodiment will not be repeated here.

[0190] A first transfer module 103 is configured to, if the first permission verification result indicates that the first business object has the transfer permission for the first type of assets and the second type of assets, transfer the second type of assets to the second business object synchronously when the first type of assets are transferred to the second business object through the asset registration contract, and generate a synchronous transfer transaction record associated with the first type of assets and the second type of assets;

[0191] The first transfer module 103 may include: a synchronous transfer unit 1031 and a record generation unit 1032;

[0192] The synchronous transfer unit 1031 is used to change the holding authority of the first type of assets and synchronously transfer the second type of assets to the second business object when the first type of assets are transferred to the second business object through the asset registration contract;

[0193] The record generation unit 1032 is used to generate a first transaction record corresponding to the first type of asset and a second transaction record corresponding to the second type of asset, and use the first transaction record and the second transaction record as synchronous transfer transaction records associated with the first type of asset and the second type of asset; the second transaction record is associated with the first transaction record.

[0194] The specific implementation of the synchronization transfer unit 1031 and the record generation unit 1032 can be found in the above Figure 3 The description of step S103 in the corresponding embodiment will not be repeated here.

[0195] The asset registration module 104 is used to obtain an asset registration request initiated by the first business object, call the asset registration contract on the blockchain based on the asset registration request, and register the first digital asset held by the first business object as a first type of asset;

[0196] The asset registration request carries the asset registration data submitted by the first business object for the first digital asset held and the first signature information of the first business object; the first signature information is obtained by signing the asset registration data with the private key information of the first business object; the first signature information carries the public key information corresponding to the private key information;

[0197] The asset registration module 104 may include: a first signature verification unit 1041, an asset registration unit 1042;

[0198] The first signature verification unit 1041 is used to obtain the first signature information from the asset registration request, perform signature verification on the first signature information using the public key information carried in the first signature information, and obtain a first signature verification result;

[0199] The asset registration unit 1042 is used to call the asset registration contract on the blockchain based on the asset registration data carried in the asset registration request when the first signature verification result indicates that the signature verification is successful, and register the first digital asset as a first type of asset.

[0200] The specific implementation of the first signature verification unit 1041 and the asset registration unit 1042 can be found in the above Figure 3 The description of step S101 in the corresponding embodiment, or can refer to the above Figure 6 The description of step S201 in the corresponding embodiment will not be repeated here.

[0201] The contract deployment module 105 is used to deploy a proxy contract for managing the first type of assets on the blockchain through the asset registration contract, and bind the first type of assets to the proxy contract;

[0202] The asset registration data includes a first asset identifier corresponding to a first digital asset that is an asset of the first type;

[0203] The contract deployment module 105 may include: a contract deployment unit 1051 and a contract binding unit 1052;

[0204] The contract deployment unit 1051 is used to deploy a proxy contract for managing the first type of assets on the blockchain through the asset registration contract, and configure the contract holding object address of the proxy contract to be the first account address of the first business object; the first account address is determined by the public key information of the first business object;

[0205] The contract binding unit 1052 is used to obtain the first asset identifier from the asset registration data, and establish a binding relationship between the first asset identifier and the proxy contract account corresponding to the proxy contract through the asset registration contract; the binding relationship is used to indicate that the first type of asset is managed by the proxy contract account.

[0206] The specific implementation of the contract deployment unit 1051 and the contract binding unit 1052 can be found in the above Figure 3 The description of step S101 in the corresponding embodiment, or can refer to the above Figure 6 The description of step S201 in the corresponding embodiment will not be repeated here.

[0207] The asset association module 106 is used to, when obtaining an asset association request initiated by the first business object for the first type of asset, call the proxy contract based on the asset association request, associate the second digital asset held by the first business object and different from the first digital asset with the first type of asset, and obtain the second type of asset associated with the first type of asset;

[0208] The asset association request carries the associated asset data submitted by the first business object for the first type of asset and the second signature information of the first business object; the associated asset data is determined by the second digital asset held by the first business object and different from the first digital asset; the second signature information is obtained by signing the associated asset data with the private key information of the first business object; the second signature information carries the public key information corresponding to the private key information;

[0209] The asset association module 106 may include: a second signature verification unit 1061, a request forwarding unit 1062, and an asset association unit 1063;

[0210] The second signature verification unit 1061 is used to obtain the second signature information from the asset association request, and perform signature verification on the second signature information using the public key information carried in the second signature information to obtain a second signature verification result;

[0211] The request forwarding unit 1062 is used to call the asset registration contract, obtain the proxy contract address of the proxy contract, and forward the asset association request to the proxy contract according to the proxy contract address when the second signature verification result indicates that the signature verification is successful;

[0212] The request forwarding unit 1062 may include: a first authentication subunit 10621, a request forwarding subunit 10622;

[0213] The first authentication subunit 10621 is used to perform authority verification on the first business object through the asset registration contract to obtain a second authority verification result;

[0214] Among them, the first authentication subunit 10621 is specifically used to obtain the first asset holding object address corresponding to the first type of asset through the asset registration contract, and compare the first asset holding object address with the first account address of the first business object; the first account address is determined by the public key information of the first business object; if the first asset holding object address is the same as the first account address, it is determined that the first business object holds the first type of asset; the result when the first business object holds the first type of asset is used as the second authority verification result.

[0215] The request forwarding subunit 10622 is used to obtain the proxy contract address of the proxy contract when the second permission verification result indicates that the first business object holds the first type of assets, and forward the asset association request to the proxy contract according to the proxy contract address.

[0216] The specific implementation of the first authentication subunit 10621 and the request forwarding subunit 10622 can be found in the above Figure 3 The description of step S101 in the corresponding embodiment, or can refer to the above Figure 6 The description of step S202 in the corresponding embodiment will not be repeated here.

[0217] The asset association unit 1063 is used to call the proxy contract based on the associated asset data carried in the asset association request, associate the second digital asset with the first type of asset, and obtain the second type of asset associated with the first type of asset.

[0218] The associated asset data includes a second asset identifier corresponding to the second digital asset; the proxy contract includes an asset association function;

[0219] The asset association unit 1063 may include: a second authentication subunit 10631, an asset association subunit 10632;

[0220] The second authentication subunit 10631 is used to perform permission verification on the first business object through the proxy contract when the second asset identifier is obtained from the associated asset data carried in the asset association request, so as to obtain a third permission verification result;

[0221] Among them, the second authentication subunit 10631 is specifically used to obtain the second asset holding object address corresponding to the second digital asset corresponding to the second asset identifier through the proxy contract, and compare the second asset holding object address with the first account address of the first business object; if the second asset holding object address is the same as the first account address, it is determined that the first business object holds the second digital asset; and the result when the first business object holds the second digital asset is used as the third authority verification result.

[0222] The asset association subunit 10632 is used to establish an association relationship between the second asset identifier and the first asset identifier corresponding to the first digital asset as the first type of asset through the asset association function in the proxy contract when the third permission verification result indicates that the first business object holds the second digital asset corresponding to the second asset identifier; the association relationship is used to indicate that when the second digital asset is used as a second type of asset associated with the first type of asset, both the first type of asset and the second type of asset belong to the proxy contract account corresponding to the proxy contract.

[0223] The specific implementation of the second authentication subunit 10631 and the asset association subunit 10632 can be found in the above Figure 3 The description of step S101 in the corresponding embodiment, or can refer to the above Figure 6 The description of step S202 in the corresponding embodiment will not be repeated here.

[0224] The specific implementation of the second signature verification unit 1061, the request forwarding unit 1062, and the asset association unit 1063 can be found in the above Figure 3The description of step S101 in the corresponding embodiment, or can refer to the above Figure 6 The description of step S202 in the corresponding embodiment will not be repeated here.

[0225] Among them, the synchronous transfer unit is specifically used to change the asset holding object of the first type of asset from the first business object to the second business object through the asset registration contract, and change the contract holding object address of the proxy contract from the first account address of the first business object to the second account address of the second business object.

[0226] The second type of assets include digital assets to be transferred; and the device further includes:

[0227] The second acquisition module 107 is used to acquire a second asset transfer request initiated by the first business object for the digital asset to be transferred;

[0228] The first forwarding module 108 is used to call the asset registration contract based on the second asset transfer request, obtain the proxy contract address of the proxy contract, and forward the second asset transfer request to the proxy contract according to the proxy contract address;

[0229] The second transfer module 109 is used to unbind the digital asset to be transferred from the first type of asset based on the second asset transfer request, transfer the unbound digital asset to be transferred to the second business object, and generate a third transaction record corresponding to the digital asset to be transferred when it is determined through the proxy contract that the first business object has the transfer authority for the digital asset to be transferred;

[0230] The second transfer module 109 may include: a third authentication unit 1091, and an unbinding transfer unit 1092;

[0231] The third authentication unit 1091 is used to call the asset transfer function in the proxy contract based on the second asset transfer request, perform authority verification on the first business object, and obtain a fourth authority verification result;

[0232] The unbinding and transferring unit 1092 is used to determine that the first business object has the transfer authority for the digital assets to be transferred when the fourth authority verification result indicates that the first business object holds the digital assets to be transferred, unbind the digital assets to be transferred and the first type of assets, and transfer the unbound digital assets to be transferred to the second business object.

[0233] The specific implementation of the third authentication unit 1091 and the unbinding transfer unit 1092 can be found in the above Figure 6 The description of step S205 in the corresponding embodiment will not be repeated here.

[0234] The second type of assets include digital assets to be unbound; and the device further includes:

[0235] The third acquisition module 110 is used to obtain an asset unbinding request initiated by the first business object for the digital asset to be unbound;

[0236] The second forwarding module 111 is used to call the asset registration contract based on the asset unbinding request, obtain the proxy contract address of the proxy contract, and forward the asset unbinding request to the proxy contract according to the proxy contract address;

[0237] The asset unbinding module 112 is used to unbind the digital asset to be unbound and the first type of asset based on the asset unbinding request when it is determined through the proxy contract that the first business object holds the digital asset to be unbound.

[0238] The specific implementation methods of the first acquisition module 101, the authority verification module 102, the first transfer module 103, the asset registration module 104, the contract deployment module 105, the asset association module 106, the second acquisition module 107, the first forwarding module 108, the second transfer module 109, the third acquisition module 110, the second forwarding module 111, and the asset unbinding module 112 can be found in the above Figure 3 The description of steps S101 to S103 in the corresponding embodiment, or can refer to the above Figure 6 The description of steps S201 to S206 in the corresponding embodiment will not be repeated here. It should be understood that the description of the beneficial effects obtained by adopting the same method will not be repeated here either.

[0239] See also Fig.12 , is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig.12 As shown, the computer device 1000 may include: a processor 1001, a network interface 1004 and a memory 1005. In addition, the above-mentioned computer device 1000 may also include: a user interface 1003, and at least one communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. Among them, the user interface 1003 may include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or it may be a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1005 may optionally also be at least one storage device located away from the aforementioned processor 1001. As Fig.12As shown, the memory 1005 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application program.

[0240] In such Fig.12 In the computer device 1000 shown in the figure, the network interface 1004 can provide a network communication function; the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 can be used to call the device control application stored in the memory 1005 to execute the above Figure 3 , Figure 6 The description of the data processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here.

[0241] In addition, it should be pointed out that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program executed by the data processing device 1 mentioned above, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the above-mentioned Figure 3 , Figure 6 The description of the data processing method in the corresponding embodiment will therefore not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, computer instructions may be deployed on a computing device for execution, or on multiple computing devices located at one location, or on multiple computing devices distributed at multiple locations and interconnected by a communication network. Multiple computing devices distributed at multiple locations and interconnected by a communication network can constitute a blockchain system.

[0242] The computer-readable storage medium may be the data processing device provided in any of the aforementioned embodiments or the internal storage unit of the computer device, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, a smart memory card (smart media card, SMC), a secure digital (secure digital, SD) card, a flash card (flash card), etc. equipped on the computer device. Further, the computer-readable storage medium may also include both the internal storage unit of the computer device and an external storage device. The computer-readable storage medium is used to store the computer program and other programs and data required by the computer device. The computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.

[0243] In addition, it should be noted that: the embodiment of the present application also provides a computer program product or a computer program, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the above Figure 3 , Figure 6 The description of the data processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of the same method will not be repeated. For technical details not disclosed in the computer program product or computer program embodiment involved in this application, please refer to the description of the method embodiment of this application.

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

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

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

[0247] The terms "first", "second", etc. in the description, claims, and drawings of the embodiments of the present application are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, device, product, or equipment that includes a series of steps or units is not limited to the listed steps or modules, but optionally includes steps or modules that are not listed, or optionally includes other step units inherent to these processes, methods, devices, products, or equipment.

[0248] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

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

Claims

1. A data processing method, characterized in that: include: Obtaining a first asset transfer request initiated by a first business object for a first type of asset held by the first business object; The first type of asset is obtained by registering the asset through an asset registration contract on the blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of asset on the blockchain; the proxy contract is used to associate the second type of asset held by the first business object with the first type of asset; the second type of asset is different from the first type of asset; Based on the first asset transfer request, calling the asset registration contract and the proxy contract to perform permission verification on the first business object to obtain a first permission verification result; If the first permission verification result indicates that the first business object has the transfer authority for the first type of assets and the second type of assets, then when the first type of assets are transferred to the second business object through the asset registration contract, the second type of assets are synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of assets and the second type of assets is generated.

2. The method according to claim 1, characterized in that: Also includes: Obtaining an asset registration request initiated by a first business object, calling an asset registration contract on the blockchain based on the asset registration request, and registering a first digital asset held by the first business object as a first type of asset; Deploying a proxy contract for managing the first type of assets on the blockchain through the asset registration contract, and binding the first type of assets to the proxy contract; When an asset association request initiated by the first business object for the first type of asset is obtained, the proxy contract is called based on the asset association request, and a second digital asset different from the first digital asset held by the first business object is associated with the first type of asset to obtain a second type of asset associated with the first type of asset.

3. The method according to claim 2, characterized in that The asset registration request carries the asset registration data submitted by the first business object for the first digital asset held by the first business object and the first signature information of the first business object; the first signature information is obtained by signing the asset registration data with the private key information of the first business object; The first signature information carries the public key information corresponding to the private key information; The calling of the asset registration contract on the blockchain based on the asset registration request to register the first digital asset held by the first business object as a first type of asset includes: Acquire the first signature information from the asset registration request, perform signature verification on the first signature information using the public key information carried by the first signature information, and obtain a first signature verification result; When the first signature verification result indicates that the signature verification is successful, based on the asset registration data carried by the asset registration request, the asset registration contract on the blockchain is called to register the first digital asset as a first type of asset.

4. The method according to claim 3, characterized in that The asset registration data includes a first asset identifier corresponding to the first digital asset as the first type of asset; The step of deploying a proxy contract for managing the first type of assets on the blockchain through the asset registration contract and binding the first type of assets to the proxy contract includes: Deploying a proxy contract for managing the first type of assets on the blockchain through the asset registration contract, and configuring the contract holding object address of the proxy contract to be the first account address of the first business object; the first account address is determined by the public key information of the first business object; The first asset identifier is obtained from the asset registration data, and a binding relationship between the first asset identifier and the proxy contract account corresponding to the proxy contract is established through the asset registration contract; the binding relationship is used to indicate that the first type of asset is managed by the proxy contract account.

5. The method according to claim 2, characterized in that: The asset association request carries the associated asset data submitted by the first business object for the first type of asset and the second signature information of the first business object; the associated asset data is determined by a second digital asset held by the first business object and different from the first digital asset; the second signature information is obtained by signing the associated asset data with the private key information of the first business object; the second signature information carries the public key information corresponding to the private key information; The calling of the proxy contract based on the asset association request, associating a second digital asset held by the first business object and different from the first digital asset with the first type of asset, to obtain a second type of asset associated with the first type of asset, includes: Acquire the second signature information from the asset association request, perform signature verification on the second signature information using the public key information carried by the second signature information, and obtain a second signature verification result; When the second signature verification result indicates that the signature verification is successful, calling the asset registration contract, obtaining the proxy contract address of the proxy contract, and forwarding the asset association request to the proxy contract according to the proxy contract address; Based on the associated asset data carried in the asset association request, the proxy contract is called to associate the second digital asset with the first type of asset to obtain a second type of asset associated with the first type of asset.

6. The method according to claim 5, characterized in that The calling of the asset registration contract, obtaining the proxy contract address of the proxy contract, and forwarding the asset association request to the proxy contract according to the proxy contract address, includes: Performing authority verification on the first business object through the asset registration contract to obtain a second authority verification result; When the second permission verification result indicates that the first business object holds the first type of asset, the proxy contract address of the proxy contract is obtained, and the asset association request is forwarded to the proxy contract according to the proxy contract address.

7. The method according to claim 6, characterized in that The performing authority verification on the first business object through the asset registration contract to obtain a second authority verification result includes: Obtaining the first asset holding object address corresponding to the first type of asset through the asset registration contract, and comparing the first asset holding object address with the first account address of the first business object; the first account address is determined by the public key information of the first business object; If the first asset holding object address is the same as the first account address, it is determined that the first business object holds the first type of asset; The result when the first business object holds the first type of assets is used as the second authority verification result.

8. The method according to claim 5, characterized in that The associated asset data includes a second asset identifier corresponding to the second digital asset; the proxy contract includes an asset association function; The calling of the proxy contract based on the associated asset data carried in the asset association request to associate the second digital asset with the first type of asset includes: When the second asset identifier is obtained from the associated asset data carried in the asset association request, performing permission verification on the first business object through the proxy contract to obtain a third permission verification result; When the third permission verification result indicates that the first business object holds the second digital asset corresponding to the second asset identifier, an association relationship between the second asset identifier and the first asset identifier corresponding to the first digital asset as the first type of asset is established through the asset association function in the proxy contract; the association relationship is used to indicate that when the second digital asset is used as a second type of asset associated with the first type of asset, both the first type of asset and the second type of asset belong to the proxy contract account corresponding to the proxy contract.

9. The method according to claim 8, characterized in that The performing permission verification on the first business object through the proxy contract to obtain a third permission verification result includes: Obtaining, through the proxy contract, the second asset holding object address corresponding to the second digital asset corresponding to the second asset identifier, and comparing the second asset holding object address with the first account address of the first business object; If the second asset holding object address is the same as the first account address, it is determined that the first business object holds the second digital asset; The result when the first business object holds the second digital asset is used as the third authority verification result.

10. The method according to claim 1, characterized in that The method of calling the asset registration contract and the proxy contract to perform permission verification on the first business object based on the first asset transfer request to obtain a first permission verification result includes: Based on the first asset transfer request, the asset registration contract is called to obtain the first asset holding object address corresponding to the first type of asset, and the first asset holding object address is compared with the first account address of the first business object. When the first asset holding object address is the same as the first account address, it is determined that the first business object has the transfer authority for the first type of asset, and the first asset transfer request is forwarded to the proxy contract; Based on the first asset transfer request, the proxy contract is called to search for an asset identifier associated with the first asset identifier of the first type of asset, the found asset identifier is used as a target asset identifier, the target asset identifier is compared with the second asset identifier of the second type of asset, and when the target asset identifier is the same as the second asset identifier, it is determined that the first business object has transfer authority for the second type of asset; The result when the first business object has the transfer authority for the first type of assets and the second type of assets is used as the first authority verification result.

11. The method according to claim 1, characterized in that: When the first type of asset is transferred to the second business object through the asset registration contract, the second type of asset is synchronously transferred to the second business object, and a synchronous transfer transaction record associated with the first type of asset and the second type of asset is generated, including: When the first type of assets are transferred to the second business object through the asset registration contract, the holding authority of the first type of assets is changed, and the second type of assets are transferred to the second business object simultaneously; Generate a first transaction record corresponding to the first type of asset and a second transaction record corresponding to the second type of asset, and use the first transaction record and the second transaction record as synchronous transfer transaction records associated with the first type of asset and the second type of asset; the second transaction record is associated with the first transaction record.

12. The method according to claim 11, characterized in that The changing of holding authority for the first type of assets includes: Through the asset registration contract, the asset holding object of the first type of asset is changed from the first business object to the second business object, and the contract holding object address of the proxy contract is changed from the first account address of the first business object to the second account address of the second business object.

13. The method according to claim 2, characterized in that The second type of assets includes digital assets to be transferred; and the method further includes: Acquire a second asset transfer request initiated by the first business object for the digital asset to be transferred; Based on the second asset transfer request, calling the asset registration contract, obtaining the proxy contract address of the proxy contract, and forwarding the second asset transfer request to the proxy contract according to the proxy contract address; Based on the second asset transfer request, when it is determined through the proxy contract that the first business object has the transfer authority for the digital asset to be transferred, the digital asset to be transferred and the first type of asset are unbound, the unbound digital asset to be transferred is transferred to the second business object, and a third transaction record corresponding to the digital asset to be transferred is generated.

14. The method according to claim 13, characterized in that The method of unbinding the digital asset to be transferred from the first type of asset based on the second asset transfer request and transferring the unbound digital asset to be transferred to the second business object when it is determined through the proxy contract that the first business object has the transfer authority for the digital asset to be transferred, includes: Based on the second asset transfer request, calling the asset transfer function in the proxy contract, performing permission verification on the first business object, and obtaining a fourth permission verification result; When the fourth authority verification result indicates that the first business object holds the digital asset to be transferred, it is determined that the first business object has the transfer authority for the digital asset to be transferred, the digital asset to be transferred and the first type of asset are unbound, and the unbound digital asset to be transferred is transferred to the second business object.

15. The method according to claim 2, characterized in that The second type of assets includes digital assets to be untied; and the method further includes: Obtaining an asset unbinding request initiated by the first business object for the digital asset to be unbound; Based on the asset unbinding request, call the asset registration contract, obtain the proxy contract address of the proxy contract, and forward the asset unbinding request to the proxy contract according to the proxy contract address; Based on the asset unbinding request, when it is determined through the proxy contract that the first business object holds the digital asset to be unbound, the digital asset to be unbound and the first type of asset are unbound.

16. A data processing device, characterized in that: include: A first acquisition module, used to acquire a first asset transfer request initiated by a first business object for a first type of asset held; The first type of asset is obtained by registering the asset through an asset registration contract on the blockchain; the asset registration contract is used to deploy a proxy contract bound to the first type of asset on the blockchain; the proxy contract is used to associate the second type of asset held by the first business object with the first type of asset; the second type of asset is different from the first type of asset; an authority verification module, configured to call the asset registration contract and the proxy contract to perform authority verification on the first business object based on the first asset transfer request, and obtain a first authority verification result; The first transfer module is used to synchronously transfer the second type of assets to the second business object when the first type of assets is transferred to the second business object through the asset registration contract, and generate a synchronous transfer transaction record associated with the first type of assets and the second type of assets if the first permission verification result indicates that the first business object has the transfer authority for the first type of assets and the second type of assets.

17. A computer device, characterized in that: include: Processor and memory; The processor is connected to the memory, wherein the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method according to any one of claims 1 to 15.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 15.

19. A computer program product, characterized in that The computer program product comprises computer instructions, which are stored in a computer-readable storage medium. The computer instructions are suitable for being read and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 15.