Blockchain transaction execution method and device, electronic equipment and storage medium

Abstract

The application provides a transaction execution method and device of a blockchain, electronic equipment and a storage medium, and relates to the technical field of blockchains. By deploying a corresponding representative contract for an asset, when the attribute of the asset is changed, the attribute change request of the asset is initiated through the corresponding representative contract of the asset, and the identifier of the creator of the to-be-traded asset is modified by using the information of the representative contract of the target asset, thereby establishing the ownership association relationship between the to-be-traded asset and the target asset. The to-be-traded asset is the attribute of the target asset, and the representative contract of the target asset indirectly owns the to-be-traded asset, thereby realizing the change of the attribute of the target asset, fusing different assets, breaking the problem that each asset exists independently in the conventional asset representation mode, and expanding the asset representation capability in some complex scenarios.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and more specifically, to a blockchain transaction execution method, apparatus, electronic device, and storage medium. Background Technology

[0002] Non-fungible tokens (NFTs) under the Ethereum ERC721 protocol are trusted digital rights certificates with unique characteristics in the blockchain network. They are data objects with multi-dimensional and complex attributes that can be recorded and processed on the blockchain. They are used to correspond to virtual items on the Internet (such as pictures, videos, music, etc.) and can also be used to associate with physical objects in real life (such as cars, houses, etc.). Any NFT object is unique and cannot be copied in the blockchain system.

[0003] Currently, NFTs in the standard ERC721 protocol can only be represented by a tokenId. An NFT uniquely represents an object under the ERC721 protocol and cannot be integrated with other NFT objects under the same protocol, resulting in poor NFT representation capabilities in complex scenarios. Summary of the Invention

[0004] The purpose of this application is to address the shortcomings of the prior art by providing a blockchain transaction execution method, apparatus, electronic device, and storage medium to effectively expand the representation capabilities of NFTs.

[0005] To achieve the above objectives, the technical solutions adopted in the embodiments of this application are as follows:

[0006] In a first aspect, embodiments of this application provide a blockchain transaction execution method, including:

[0007] Receive a user's request to change the asset attributes of a representative contract initiated through the representative contract corresponding to the target asset. The request to change the asset attributes includes: the identifier of the asset to be traded, the identifier of the target asset, and the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset.

[0008] Verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset;

[0009] If the verification is successful, the identifier of the creator of the asset to be traded will be changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset, so as to change the attributes of the target asset.

[0010] Secondly, embodiments of this application also provide a blockchain transaction execution device, including: a receiving module, a verification module, and an execution module;

[0011] The receiving module is used to receive an asset attribute change request initiated by a user through a representative contract corresponding to the target asset. The asset attribute change request includes: the identifier of the asset to be traded, the identifier of the target asset, and the identifier of the target asset and the identifier of the creator of the target asset are recorded in the representative contract corresponding to the target asset.

[0012] The verification module is used to verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset.

[0013] The execution module is configured to, if the verification passes, change the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, so as to change the attributes of the target asset.

[0014] Thirdly, embodiments of this application provide an electronic device, including: a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the blockchain transaction execution method provided in the first aspect.

[0015] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, performs the steps of the blockchain transaction execution method provided in the first aspect.

[0016] The beneficial effects of this application are:

[0017] This application provides a blockchain transaction execution method, apparatus, electronic device, and storage medium. The method deploys a corresponding representative contract for each asset. When asset attributes are changed, an asset attribute change request is initiated through the corresponding representative contract. The identifier of the asset creator recorded in the representative contract can be used to verify the identity of the initiator of the asset attribute change request, ensuring the security of asset transactions. By executing the asset attribute change request, the identifier of the creator of the asset to be traded is modified using information from the representative contract corresponding to the target asset. This establishes an ownership association between the asset to be traded and the target asset. The asset to be traded becomes an attribute of the target asset, and the representative contract of the target asset indirectly owns the asset to be traded, thus realizing the change of the target asset's attributes. This method can integrate different assets, breaking the problem of each asset existing independently in conventional asset representation methods and expanding the asset representation capabilities in complex scenarios. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 1 ;

[0020] Figure 2 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 2 ;

[0021] Figure 3 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 3 ;

[0022] Figure 4 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 4 ;

[0023] Figure 5 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 5 ;

[0024] Figure 6 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 6 ;

[0025] Figure 7A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 7 ;

[0026] Figure 8 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 8 ;

[0027] Figure 9 A schematic diagram of a blockchain transaction execution device provided in an embodiment of this application;

[0028] Figure 10 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0030] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0031] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0032] Figure 1 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 1 This method can be applied to blockchain nodes. A blockchain node can be deployed on a single server, or multiple blockchain nodes can be deployed on the same server. The execution entity of this method can be the server, such as... Figure 1As shown, the method may include:

[0033] S101. Receive the asset attribute change request initiated by the user through the representative contract corresponding to the target asset. The asset attribute change request includes: the identifier of the asset to be traded, the identifier of the target asset, the identifier of the target asset recorded in the representative contract corresponding to the target asset, and the identifier of the creator of the target asset.

[0034] First, let's explain the assets here. Assets can refer to any virtual or real object, such as a picture, a song, or a house, all of which are considered as independent assets. In this embodiment, assets can be equivalent to NFTs, and an asset is an NFT.

[0035] The asset creator can refer to the owner of the asset. For example, if Zhang San owns a picture and initiates the minting of that picture in the blockchain, then an asset representing that picture will be generated in the blockchain, and Zhang San, as the minter of that asset, becomes the creator of that asset.

[0036] Typically, each asset has a unique tokenID stored in the blockchain, referred to as the asset identifier below. Similar to ID card information, the asset identifier can be used to accurately locate the asset to be traded.

[0037] In this method, for each asset, a representative contract is deployed for the asset when the asset is created. The representative contract for the asset records the hierarchical relationship between the asset creator, the asset, and the asset's representative contract. At the same time, the representative contract also records some relevant rules for asset transactions.

[0038] Optionally, when an asset creator initiates a request to change the asset's attributes, the request can be made through a representative contract deployed for the asset. The representative contract acts as a bridge between the asset creator and the asset, enabling the asset transaction to be executed according to some rules in the representative contract, thus providing security for the asset transaction.

[0039] Optionally, users can initiate an asset attribute change request to a blockchain node through the representative contract corresponding to the target asset. The asset attribute change request includes the identifier of the asset to be traded and the identifier of the target asset. Here, the target asset can refer to an asset created by the user, and the asset to be traded can refer to an asset that the user wants to buy from other users. In other words, the asset attribute change request can realize the transformation of the asset to be traded into the attribute of the target asset.

[0040] In some embodiments, the correspondence between the asset identifier, the asset creator identifier, and the address of the representative contract corresponding to the asset can be recorded in the representative contract corresponding to the asset. Of course, the correspondence between the asset identifier, the asset creator identifier, and the address of the representative contract corresponding to the asset can also be recorded in a standard protocol contract similar to ERC721. In particular, for assets that have not deployed a representative contract, the correspondence between the asset identifier and the asset creator identifier is recorded in the standard protocol contract.

[0041] S102. Verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset.

[0042] As explained above, each asset can be deployed with a corresponding representative contract. For the target asset, the representative contract corresponding to the target asset can record the identifier of the creator of the target asset. The identity of the user who initiated the asset attribute change request can be verified based on the identifier of the creator of the target asset.

[0043] When executing an asset attribute change request, only the asset creator has the authority to initiate the request through the representative contract corresponding to the asset. This request can be used to transfer the asset to be traded to the target asset, so that the asset to be traded exists as an attribute of the target asset.

[0044] In this embodiment, by recording the identifier of the asset creator in the representative contract to verify the identity of the user who initiates the asset attribute change request, it can be ensured that only the creator of the target asset can operate on the target asset, thereby ensuring the security of asset transactions and preventing malicious theft of assets.

[0045] S103. If the verification is successful, the identifier of the creator of the asset to be traded will be changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset, so as to change the attributes of the target asset.

[0046] Optionally, when the user's identifier is the same as the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset, it can be proven that the user who initiates the asset attribute change request is the creator of the target asset and has the authority to initiate the asset attribute change request. Then, based on the identifier of the asset to be traded in the asset attribute change request and the representative contract corresponding to the target asset, the identifier of the creator of the asset to be traded can be changed, so as to establish the ownership relationship between the asset to be traded and the target asset through the representative contract corresponding to the target asset, thereby realizing the change of the attribute of the target asset.

[0047] In summary, the blockchain transaction execution method provided in this embodiment deploys corresponding representative contracts for assets. When asset attributes are changed, an asset attribute change request is initiated through the corresponding representative contract. The identifier of the asset creator recorded in the representative contract can be used to verify the identity of the initiator of the asset attribute change request, ensuring the security of asset transactions. By executing the asset attribute change request, the identifier of the creator of the asset to be traded is modified using the information of the representative contract corresponding to the target asset. This establishes an ownership association between the asset to be traded and the target asset. The asset to be traded becomes an attribute of the target asset, and the representative contract of the target asset indirectly owns the asset to be traded. This achieves the change of the target asset's attributes and allows for the fusion of different assets, breaking the problem of each asset existing independently in conventional asset representation methods and expanding the asset representation capabilities in complex scenarios.

[0048] Figure 2 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 2 In step S101, before receiving the asset attribute change request initiated by the user through the representative contract corresponding to the target asset, the following may be included:

[0049] S201. Receive an asset creation request initiated by the asset creator. The asset creation request includes information about the asset to be created.

[0050] This embodiment describes the deployment of the representative contract corresponding to the asset. The asset creator here can be any user. When a user wants to record an item they own on the blockchain, they can create an asset to represent that item. The user, as the asset creator, then initiates an asset creation request to the blockchain node. The request includes information about the asset to be created. This information can refer to the content of the item. For example, if the item is an image, the information about the asset to be created would be a detailed description of the image, including its color, content, and other details.

[0051] S202. Generate an asset identifier based on the information of the asset to be created.

[0052] Optionally, based on the information of the asset to be created, an asset identifier can be generated. Here, the asset identifier refers to the tokenID mentioned above, which is used to uniquely identify the asset and distinguish it from any other asset.

[0053] S203. Assign a target address to the asset, record the correspondence between the asset's identifier, the asset creator's identifier, and the target address in the target address, generate a representative contract corresponding to the asset, and use the address of the representative contract as the owner of the asset and the asset creator as the owner of the representative contract, with the address of the representative contract being the target address.

[0054] Assigning a target address to an asset here refers to deploying a representative contract for the asset. The assigned target address is the address of the representative contract. By assigning a target address, a representative contract is deployed to the asset, and the address of the representative contract is the target address.

[0055] The representative contract can also record various correspondences, including the fact that the address of the representative contract can be the owner of the asset, while the asset creator can be the owner of the representative contract, so that the asset creator can operate on the asset through the representative contract.

[0056] Figure 3 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 3 Optionally, in step S103, changing the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset may include:

[0057] S301. Based on the identifier of the asset to be traded, query and obtain the identifier of the creator of the asset to be traded.

[0058] Optionally, the identifier of the creator of the asset to be traded can be obtained from the contract by querying the correspondence between the asset identifier and the asset creator recorded in the contract. Here, the contract can be the representative contract corresponding to the asset to be traded or a standard protocol contract.

[0059] S302. Based on the representative contract corresponding to the target asset, change the identifier of the creator of the asset to be traded to the address of the representative contract corresponding to the target asset.

[0060] Optionally, the identifier of the creator of the asset to be traded recorded in the contract can be replaced with the address of the representative contract corresponding to the target asset. The identifier of the creator of the asset to be traded can be a wallet account or account address, which can be replaced with the address of the representative contract corresponding to the target asset.

[0061] As explained above, the creator of an asset is the owner of the corresponding representative contract, and the corresponding representative contract is the owner of the asset. Therefore, it can be considered that the representative contract is the direct owner of the asset, and the creator of the asset is the indirect owner of the asset.

[0062] By replacing the creator's identifier of the asset to be traded with the address of the representative contract corresponding to the target asset, the address of the representative contract corresponding to the target asset indirectly owns the asset to be traded, while the representative contract corresponding to the target asset also directly owns the target asset. Thus, the target asset acquires the asset to be traded, and the asset to be traded becomes an attribute of the target asset.

[0063] By deploying representative contracts on assets, the representative contract can represent the corresponding asset, and other assets indirectly owned by the representative contract can be added to the asset's attributes as attributes of the asset corresponding to the representative contract.

[0064] For example, if the target asset is a suit of armor and the asset to be traded is a sword, after executing the asset attribute change request as described above, the representative contract corresponding to the armor indirectly acquires the sword, that is, a sword is added to the armor. In this way, the sword can be used as an attribute of the armor, and two independent assets can be merged and represented, expanding the representation capabilities of assets.

[0065] Figure 4 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 4 ;like Figure 4 As shown, the method of this application may further include:

[0066] S401. Receive an asset query request. The asset query request includes: the identifier of the asset to be queried.

[0067] In some embodiments, an asset query request can be initiated to query any additional assets owned by any asset. The asset query request may include: the identifier of the asset to be queried.

[0068] S402. Based on the asset query request, query and output the additional assets owned by the asset to be queried.

[0069] By using an asset query request, you can query the additional assets that any asset possesses. For example, when the asset to be queried is the target asset mentioned above, then the attribute of the asset to be traded as the target asset is the additional assets that the target asset possesses. However, for the asset to be queried that exists independently without any additional assets, the output additional asset information can be empty.

[0070] Figure 5 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 5 ;like Figure 5 As shown, in step S402 above, querying and outputting the additional assets owned by the asset to be queried based on the asset query request may include:

[0071] S501. Based on the identifier of the asset to be queried, determine the address of the representative contract corresponding to the asset to be queried.

[0072] The address of the representative contract corresponding to the asset to be queried can be determined by matching the asset identifier recorded in the contract with the corresponding representative contract.

[0073] S502. Based on the identifier of the creator of each asset, identify the assets whose representative contract address contained in the creator's identifier matches the representative contract address of the asset to be queried as the additional assets owned by the asset to be queried, and output the additional assets.

[0074] By traversing through all assets in the blockchain, and based on the identifier of each asset's creator, assets whose creator identifier matches the address of the representative contract corresponding to the asset being queried can be identified as additional assets owned by the asset being queried.

[0075] Since the creator's identifier of asset 1 is replaced with the address of the representative contract corresponding to asset 2 when asset 1 is changed to asset 2, the creator's identifier of each asset can be queried. When the creator's identifier of an asset is the address of the representative contract corresponding to the asset to be queried, it can be determined that the asset is an additional asset owned by the asset to be queried.

[0076] Figure 6 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 6 Optionally, the address of the representative contract corresponding to the target asset also records a lock mark.

[0077] In step S103, changing the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset may include:

[0078] S601. Query the lock marker in the representative contract corresponding to the target asset.

[0079] In some embodiments, a lock flag may also be set in the representative contract. When executing an asset attribute change request through the representative contract, the current lock flag status in the representative contract can be queried first. By setting the lock flag, the security of executing the request can be guaranteed.

[0080] S602. When the lock is in the open state, the identifier of the creator of the asset to be traded is changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset.

[0081] Optionally, after the user's identity is verified, when the query lock is marked as open, the identity of the creator of the asset to be traded can be changed according to the identity of the asset to be traded and the representative contract corresponding to the target asset.

[0082] Figure 7A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 7 Optionally, in step S601, before querying the lock token in the representative contract corresponding to the target asset, the following may be included:

[0083] S701: Receive lock tag modification signature information sent by the user.

[0084] Optionally, the aforementioned lock marker can only be modified by the creator of the target asset. When the creator of the target asset wants to modify the lock marker, they also need to obtain authorization information output by the blockchain node. Modification of the lock marker is only permitted with authorization, thus ensuring the asset security of the target asset creator. When modifying the lock marker, the user can send lock marker modification signature information to the blockchain node.

[0085] S702. Obtain the current signature information of the lock token.

[0086] The current signature information of the lock tag mentioned here refers to the signature information of the lock tag at the current moment stored in the blockchain node. In order to ensure the real-time nature of the lock tag and prevent the signature information from being reused by users, each lock tag is given a temporary parameter. The temporary parameter will change every time the lock tag is modified, so that the current signature information is dynamically updated in real time.

[0087] S703. If the lock flag's modified signature information matches the current signature information, then the authorization information is output to the user. The current signature information is generated based on the current temporary parameters corresponding to the lock flag.

[0088] When the lock token modification signature information sent by the user matches the current signature information, the user is granted authorization, and the authorization information is output, allowing the user to modify the lock token in the contract.

[0089] S704. In response to the lock marker change information entered by the user based on the authorization information, modify the lock marker in the representative contract corresponding to the target asset.

[0090] Optionally, the lock marker may include two states: open and closed. If the current lock marker is in the open state and the user wants to change it to the closed state, the user can enter lock marker update information to change the lock marker from the open state to the closed state, thereby responding to the user's input information and completing the modification of the lock marker state.

[0091] Of course, there are many specific authorization methods, not limited to the above implementation methods.

[0092] Figure 8 A flowchart illustrating the blockchain transaction execution method provided in this application embodiment. Figure 8 Optionally, the method of this application may also include:

[0093] S801. Receive an asset creator change request initiated by a user through the representative contract corresponding to the target asset. The asset creator change request includes: the identifier of the target user corresponding to the target asset.

[0094] The above embodiments illustrate asset change transactions, which involve changing the owner of an asset, that is, changing the address of the contract representing the asset.

[0095] In this embodiment, the asset creator change request is a change to the asset creator, and the asset creator change request includes the identifier of the target user corresponding to the target asset.

[0096] S802. Verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset.

[0097] Similar to step S102, when executing the asset creator change request, the user's identity must also be verified, which will not be elaborated here.

[0098] S803. If the verification is successful, execute the asset creator change request based on the target user's identifier to change the asset creator of the target asset to the target user.

[0099] Once the verification is successful, the asset creator change request can be executed, thereby changing the asset creator's identifier of the target asset to the target user's identifier. In other words, the right to operate the asset is transferred to someone else. Subsequent operations on the target asset will be performed by the target user, who has the authority to operate it. When the target user performs an operation, the request is initiated through the representative contract corresponding to the asset created by the target user.

[0100] In addition, similar to the above method, after verification, it is also necessary to query the status of the lock marker in the contract. When the lock marker is in the open state, the asset creator change request is executed.

[0101] In summary, the blockchain transaction execution method provided in this embodiment deploys corresponding representative contracts for assets. When asset attributes are changed, an asset attribute change request is initiated through the corresponding representative contract. This allows for identity verification of the initiator of the asset attribute change request using the asset creator's identifier recorded in the representative contract, ensuring the security of asset transactions. By executing the asset attribute change request, the identifier of the creator of the asset to be traded is modified using the information from the representative contract corresponding to the target asset. This establishes an ownership association between the asset to be traded and the target asset. The asset to be traded becomes an attribute of the target asset, and the representative contract of the target asset indirectly owns the asset to be traded. This achieves the change of the target asset's attributes and allows for the fusion of different assets, breaking the problem of each asset existing independently in conventional asset representation methods and expanding the asset representation capabilities in complex scenarios.

[0102] The following describes the apparatus, device, and storage medium used to execute the blockchain transaction execution method provided in this application. The specific implementation process and technical effects are described above and will not be repeated below.

[0103] Figure 9 This diagram illustrates a blockchain transaction execution device provided in an embodiment of this application. The functions implemented by this blockchain transaction execution device correspond to the steps executed by the aforementioned method. This device can be understood as the aforementioned server, or the server's processor, or it can be understood as a component independent of the aforementioned server or processor, but under the control of the server, that implements the functions of this application, such as... Figure 9 As shown, the device may include: a receiving module 610, a verification module 620, and an execution module 630;

[0104] The receiving module 610 is used to receive the asset attribute change request initiated by the user through the representative contract corresponding to the target asset. The asset attribute change request includes: the identifier of the asset to be traded, the identifier of the target asset, the identifier of the target asset recorded in the representative contract corresponding to the target asset, and the identifier of the creator of the target asset.

[0105] The verification module 620 is used to verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset.

[0106] The execution module 630 is used to change the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, so as to change the attributes of the target asset.

[0107] Optionally, the apparatus further includes: a generation module;

[0108] The receiving module 610 is also used to receive an asset creation request initiated by the asset creator, the asset creation request including: information about the asset to be created;

[0109] The generation module is used to generate an asset identifier based on the information of the asset to be created;

[0110] The generation module is used to assign target addresses to assets, record the correspondence between the asset's identifier, the asset creator's identifier, and the target address into the target address, generate a representative contract corresponding to the asset, and set the address of the representative contract as the owner of the asset and the asset creator as the owner of the representative contract, with the address of the representative contract being the target address.

[0111] Optionally, the execution module 630 is specifically used to query and obtain the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded;

[0112] Based on the representative contract corresponding to the target asset, change the identifier of the creator of the asset to be traded to the address of the representative contract corresponding to the target asset.

[0113] Optionally, the device may further include: an output module;

[0114] The receiving module 610 is also used to receive an asset query request, which includes: the identifier of the asset to be queried;

[0115] The output module is used to query and output the additional assets owned by the asset to be queried, based on the asset query request.

[0116] Optionally, the output module is specifically used to determine the address of the representative contract corresponding to the asset to be queried based on the identifier of the asset to be queried;

[0117] Based on the identifier of each asset's creator, the assets whose representative contract address contained in the creator's identifier matches the representative contract address of the asset to be queried are identified as the additional assets owned by the asset to be queried, and the additional assets are output.

[0118] Optionally, the address of the representative contract corresponding to the target asset also records a lock marker;

[0119] Execution module 630 is specifically used to query the lock marker in the representative contract corresponding to the target asset;

[0120] When the lock is in the open state, the identity of the creator of the asset to be traded is changed according to the identity of the asset to be traded and the representative contract corresponding to the target asset.

[0121] Optionally, the device further includes: an acquisition module, an output module, and a modification module;

[0122] The receiving module 610 is also used to receive lock mark modification signature information sent by the user;

[0123] The acquisition module is also used to acquire the current signature information of the lock token;

[0124] The output module is used to output authorization information to the user if the modified signature information of the lock flag matches the current signature information. The current signature information is generated based on the current temporary parameters corresponding to the lock flag.

[0125] The modification module is used to respond to the lock mark change information input by the user based on the authorization information and modify the lock mark in the representative contract corresponding to the target asset.

[0126] Optionally, the receiving module 610 is further configured to receive an asset creator change request initiated by a user through a representative contract corresponding to the target asset. The asset creator change request includes: the identifier of the target user corresponding to the target asset.

[0127] The verification module 620 is also used to verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset;

[0128] The execution module 630 is also configured to, if the verification passes, execute an asset creator change request based on the target user's identifier to change the asset creator of the target asset to the target user.

[0129] The above-described device is used to execute the method provided in the foregoing embodiments, and its implementation principle and technical effect are similar, so they will not be described again here.

[0130] By deploying corresponding representative contracts for each asset, the receiving module receives asset attribute change requests initiated by users through the corresponding representative contracts during asset transactions. The verification module can then use the asset creator's identifier recorded in the representative contract to authenticate the initiator of the asset attribute change request, ensuring the security of asset transactions. By executing the asset attribute change request and modifying the creator's identifier of the asset to be traded using information from the representative contract corresponding to the target asset, an ownership association is established between the asset to be traded and the target asset. The asset to be traded becomes an attribute of the target asset, and the representative contract of the target asset indirectly owns the asset to be traded, thus realizing the change of the target asset's attributes. This allows for the fusion of different assets, breaking the problem of each asset existing independently in conventional asset representation methods and expanding the asset representation capabilities in complex scenarios.

[0131] These modules can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when a module is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these modules can be integrated together as a system-on-a-chip (SOC).

[0132] The modules described above can be connected or communicate with each other via wired or wireless connections. Wired connections can include metal cables, optical fibers, hybrid cables, or any combination thereof. Wireless connections can include connections via LAN, WAN, Bluetooth, ZigBee, or NFC, or any combination thereof. Two or more modules can be combined into a single module, and any module can be divided into two or more units. Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here.

[0133] Figure 10 A schematic diagram of an electronic device provided in this application embodiment includes: a processor 801, a storage medium 802, and a bus 803. The storage medium 802 stores machine-readable instructions executable by the processor 801. When the electronic device runs a blockchain transaction execution method as described in the embodiment, the processor 801 communicates with the storage medium 802 via the bus 803. The processor 801 executes the machine-readable instructions to perform the following steps:

[0134] Receive asset attribute change requests initiated by users through the representative contract corresponding to the target asset. The asset attribute change request includes: the identifier of the asset to be traded, the identifier of the target asset, the identifier of the target asset recorded in the representative contract corresponding to the target asset, and the identifier of the creator of the target asset.

[0135] Verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset;

[0136] If the verification is successful, the identifier of the creator of the asset to be traded will be changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset, so as to change the attributes of the target asset.

[0137] In a feasible implementation, before executing the process of receiving the asset attribute change request initiated by the user through the representative contract corresponding to the target asset, the processor 801 is specifically used to: receive the asset creation request initiated by the asset creator, the asset creation request including: information of the asset to be created;

[0138] Generate an asset identifier based on the information of the asset to be created;

[0139] Assign a target address to the asset, record the correspondence between the asset's identifier, the asset creator's identifier, and the target address in the target address, generate a representative contract corresponding to the asset, and set the address of the representative contract as the owner of the asset, the asset creator as the owner of the representative contract, and the address of the representative contract as the target address.

[0140] In one feasible implementation, when the processor 801 executes the change of the creator's identifier of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, it is specifically used to: query and obtain the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded.

[0141] Based on the representative contract corresponding to the target asset, change the identifier of the creator of the asset to be traded to the address of the representative contract corresponding to the target asset.

[0142] In one feasible implementation, the processor 801 is also configured to perform: receiving an asset query request, the asset query request including: the identifier of the asset to be queried;

[0143] Based on the asset query request, query and output the additional assets owned by the asset to be queried.

[0144] In one feasible implementation, when the processor 801 executes the query and output of the additional assets owned by the asset to be queried according to the asset query request, it is specifically used to: determine the address of the representative contract corresponding to the asset to be queried based on the identifier of the asset to be queried;

[0145] Based on the identifier of each asset's creator, the assets whose representative contract address contained in the creator's identifier matches the representative contract address of the asset to be queried are identified as the additional assets owned by the asset to be queried, and the additional assets are output.

[0146] In one feasible implementation, the address of the representative contract corresponding to the target asset also records a lock marker; when the processor 801 executes the change of the creator's identifier of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, it is specifically used to: query the lock marker in the representative contract corresponding to the target asset.

[0147] When the lock is in the open state, the identity of the creator of the asset to be traded is changed according to the identity of the asset to be traded and the representative contract corresponding to the target asset.

[0148] In one feasible implementation, before executing the query on the lock token in the representative contract corresponding to the target asset, the processor 801 is specifically used to: receive lock token modification signature information sent by the user;

[0149] Get the current signature information of the lock token;

[0150] If the lock flag modifies the signature information and matches the current signature information, then the authorization information is output to the user. The current signature information is generated based on the current temporary parameters corresponding to the lock flag.

[0151] In response to the lock marker change information entered by the user based on the authorization information, modify the lock marker in the representative contract corresponding to the target asset.

[0152] In one feasible implementation, the processor 801 is also configured to: receive an asset creator change request initiated by a user through a representative contract corresponding to the target asset, wherein the asset creator change request includes: the identifier of the target user corresponding to the target asset;

[0153] Verify the user's identity information based on the identifier of the target asset creator recorded in the representative contract corresponding to the target asset;

[0154] If the verification is successful, an asset creator change request will be executed based on the target user's identifier to change the asset creator of the target asset to the target user.

[0155] In this way, the server deploys corresponding representative contracts for each asset. During asset transactions, an asset attribute change request is initiated through the corresponding representative contract. The identity of the asset creator recorded in the representative contract is used to verify the initiator of the asset attribute change request, ensuring the security of the asset transaction. By executing the asset attribute change request, the identity of the creator of the asset to be traded is modified using the information from the representative contract corresponding to the target asset. This establishes an ownership association between the asset to be traded and the target asset. The asset to be traded becomes an attribute of the target asset, and the representative contract of the target asset indirectly owns the asset to be traded. This achieves the change of the target asset's attributes, allowing for the fusion of different assets and breaking the problem of each asset existing independently in conventional asset representation methods. This expands the asset representation capabilities in complex scenarios.

[0156] The storage medium 802 stores program code, which, when executed by the processor 801, causes the processor 801 to perform various steps in the methods according to various exemplary embodiments of this application described in the "Exemplary Methods" section above.

[0157] The processor 801 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0158] Storage medium 802, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The storage medium can include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type storage medium, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage medium, magnetic disk, optical disk, etc. The storage medium is any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. In the embodiments of this application, storage medium 802 can also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0159] Optionally, embodiments of this application also provide a computer-readable storage medium storing a computer program, which is executed by a processor, and the processor performs the following steps:

[0160] Receive asset attribute change requests initiated by users through the representative contract corresponding to the target asset. The asset attribute change request includes: the identifier of the asset to be traded, the identifier of the target asset, the identifier of the target asset recorded in the representative contract corresponding to the target asset, and the identifier of the creator of the target asset.

[0161] Verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset;

[0162] If the verification is successful, the identifier of the creator of the asset to be traded will be changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset, so as to change the attributes of the target asset.

[0163] In a feasible implementation, before executing the process of receiving the asset attribute change request initiated by the user through the representative contract corresponding to the target asset, the processor 801 is specifically used to: receive the asset creation request initiated by the asset creator, the asset creation request including: information of the asset to be created;

[0164] Generate an asset identifier based on the information of the asset to be created;

[0165] Assign a target address to the asset, record the correspondence between the asset's identifier, the asset creator's identifier, and the target address in the target address, generate a representative contract corresponding to the asset, and set the address of the representative contract as the owner of the asset, the asset creator as the owner of the representative contract, and the address of the representative contract as the target address.

[0166] In one feasible implementation, when the processor 801 executes the change of the creator's identifier of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, it is specifically used to: query and obtain the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded.

[0167] Based on the representative contract corresponding to the target asset, change the identifier of the creator of the asset to be traded to the address of the representative contract corresponding to the target asset.

[0168] In one feasible implementation, the processor 801 is also configured to perform: receiving an asset query request, the asset query request including: the identifier of the asset to be queried;

[0169] Based on the asset query request, query and output the additional assets owned by the asset to be queried.

[0170] In one feasible implementation, when the processor 801 executes the query and output of the additional assets owned by the asset to be queried according to the asset query request, it is specifically used to: determine the address of the representative contract corresponding to the asset to be queried based on the identifier of the asset to be queried;

[0171] Based on the identifier of each asset's creator, the assets whose representative contract address contained in the creator's identifier matches the representative contract address of the asset to be queried are identified as the additional assets owned by the asset to be queried, and the additional assets are output.

[0172] In one feasible implementation, the address of the representative contract corresponding to the target asset also records a lock marker; when the processor 801 executes the change of the creator's identifier of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, it is specifically used to: query the lock marker in the representative contract corresponding to the target asset.

[0173] When the lock is in the open state, the identity of the creator of the asset to be traded is changed according to the identity of the asset to be traded and the representative contract corresponding to the target asset.

[0174] In one feasible implementation, before executing the query on the lock token in the representative contract corresponding to the target asset, the processor 801 is specifically used to: receive lock token modification signature information sent by the user;

[0175] Get the current signature information of the lock token;

[0176] If the lock flag modifies the signature information and matches the current signature information, then the authorization information is output to the user. The current signature information is generated based on the current temporary parameters corresponding to the lock flag.

[0177] In response to the lock marker change information entered by the user based on the authorization information, modify the lock marker in the representative contract corresponding to the target asset.

[0178] In one feasible implementation, the processor 801 is also configured to: receive an asset creator change request initiated by a user through a representative contract corresponding to the target asset, wherein the asset creator change request includes: the identifier of the target user corresponding to the target asset;

[0179] Verify the user's identity information based on the identifier of the target asset creator recorded in the representative contract corresponding to the target asset;

[0180] If the verification is successful, an asset creator change request will be executed based on the target user's identifier to change the asset creator of the target asset to the target user.

[0181] In this way, the server deploys corresponding representative contracts for each asset. During asset transactions, an asset attribute change request is initiated through the corresponding representative contract. The identity of the asset creator recorded in the representative contract is used to verify the initiator of the asset attribute change request, ensuring the security of the asset transaction. By executing the asset attribute change request, the identity of the creator of the asset to be traded is modified using the information from the representative contract corresponding to the target asset. This establishes an ownership association between the asset to be traded and the target asset. The asset to be traded becomes an attribute of the target asset, and the representative contract of the target asset indirectly owns the asset to be traded. This achieves the change of the target asset's attributes, allowing for the fusion of different assets and breaking the problem of each asset existing independently in conventional asset representation methods. This expands the asset representation capabilities in complex scenarios.

[0182] In this embodiment, the computer program, when run by the processor, can also execute other machine-readable instructions to perform other methods as described in the embodiments. For details on the specific execution steps and principles, please refer to the description of the embodiments, which will not be repeated here.

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

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

[0185] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units.

[0186] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A blockchain transaction execution method, characterized in that, include: Receive a user's request to change the asset attributes of a representative contract initiated through the representative contract corresponding to the target asset. The request to change the asset attributes includes: the identifier of the asset to be traded, the identifier of the target asset, and the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset. Verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset; If the verification is successful, the identifier of the creator of the asset to be traded will be changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset, thereby establishing the ownership relationship between the asset to be traded and the target asset, so as to change the attributes of the target asset. Before receiving the asset attribute change request initiated by the user through the representative contract corresponding to the target asset, the process includes: Receive an asset creation request initiated by an asset creator, wherein the asset creation request includes: information about the asset to be created; Based on the information of the asset to be created, generate the identifier of the asset; Assign a target address to the asset, record the correspondence between the asset's identifier, the asset creator's identifier, and the target address in the target address, generate a representative contract corresponding to the asset, and use the address of the representative contract as the owner of the asset and the asset creator as the owner of the representative contract. The address of the representative contract is the target address.

2. The method according to claim 1, characterized in that, The step of changing the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset includes: Based on the identifier of the asset to be traded, retrieve the identifier of the creator of the asset to be traded; Based on the representative contract corresponding to the target asset, the identifier of the creator of the asset to be traded is changed to the address of the representative contract corresponding to the target asset.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive an asset query request, wherein the asset query request includes: the identifier of the asset to be queried; Based on the asset query request, query and output the additional assets owned by the asset to be queried.

4. The method according to claim 3, characterized in that, The step of querying and outputting the additional assets owned by the asset to be queried based on the asset query request includes: Based on the identifier of the asset to be queried, determine the address of the representative contract corresponding to the asset to be queried; Based on the identifier of each asset's creator, assets whose representative contract addresses contained in the creator's identifier match the address of the representative contract corresponding to the asset to be queried are identified as additional assets owned by the asset to be queried, and the additional assets are output.

5. The method according to claim 1, characterized in that, The address of the representative contract corresponding to the target asset also records a lock mark; Based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, the identifier of the creator of the asset to be traded is changed, including: Query the lock marker in the representative contract corresponding to the target asset; When the lock is marked as open, the identifier of the creator of the asset to be traded is changed according to the identifier of the asset to be traded and the representative contract corresponding to the target asset.

6. The method according to claim 5, characterized in that, Before querying the lock marker in the representative contract corresponding to the target asset, the process includes: Receive lock markers sent by the user and modify the signature information; Obtain the current signature information of the lock token; If the lock mark modification signature information matches the current signature information, then authorization information is output to the user, and the current signature information is generated based on the current temporary parameter corresponding to the lock mark; In response to the lock marker change information input by the user based on the authorization information, the lock marker in the representative contract corresponding to the target asset is modified.

7. The method according to claim 1, characterized in that, The method further includes: Receive an asset creator change request initiated by a user through the representative contract corresponding to the target asset, wherein the asset creator change request includes: the identifier of the target user corresponding to the target asset; Verify the user's identity information based on the identifier of the target asset creator recorded in the representative contract corresponding to the target asset; If the verification is successful, the asset creator change request is executed based on the target user's identifier to change the asset creator of the target asset to the target user.

8. A blockchain transaction execution device, characterized in that, include: Receive module, verification module, execution module, generation module; The receiving module is used to receive an asset attribute change request initiated by a user through a representative contract corresponding to the target asset. The asset attribute change request includes: the identifier of the asset to be traded, the identifier of the target asset, and the identifier of the target asset and the identifier of the creator of the target asset are recorded in the representative contract corresponding to the target asset. The verification module is used to verify the user's identity information based on the identifier of the creator of the target asset recorded in the representative contract corresponding to the target asset. The execution module is configured to, if the verification passes, change the identifier of the creator of the asset to be traded based on the identifier of the asset to be traded and the representative contract corresponding to the target asset, thereby establishing the ownership relationship between the asset to be traded and the target asset, so as to change the attributes of the target asset. The receiving module is also used to receive an asset creation request initiated by the asset creator, the asset creation request including: information about the asset to be created; The generation module is used to generate an identifier for the asset based on the information of the asset to be created; assign a target address to the asset; record the correspondence between the asset identifier, the asset creator's identifier, and the target address in the target address; generate a representative contract corresponding to the asset; and set the address of the representative contract as the owner of the asset and the asset creator as the owner of the representative contract, with the address of the representative contract being the target address.

9. An electronic device, characterized in that, include: The device includes a processor, a storage medium, and a bus. The storage medium stores program instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the program instructions to perform the blockchain transaction execution method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, performs the blockchain transaction execution method as described in any one of claims 1 to 7.

Images