CN116226277A - NFT resource transfer method and block chain link point - Google Patents

Abstract

An NFT resource transfer method and blockchain node, the method comprising: receiving a first transaction, wherein the first transaction is used for transferring the NFT resources of a first account to a second account, and account information corresponding to the first account stored in a blockchain comprises resource identifiers of the NFT resources; and deleting the resource identifier of the NFT resource in the account information corresponding to the first account according to the first transaction, and adding the resource identifier of the NFT resource in the account information corresponding to the second account stored in the blockchain.

Description

A NFT resource transfer method and blockchain nodes

technical field

The embodiment of this description belongs to the technical field of blockchain, and in particular relates to a NFT resource transfer method and blockchain nodes.

Background technique

Blockchain is a new application model of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. In the blockchain system, the data blocks are combined into a chained data structure in a sequentially connected manner in chronological order, and a non-tamperable and unforgeable distributed ledger is cryptographically guaranteed. Due to the characteristics of decentralization, non-tamperable information, and autonomy, the blockchain has also received more and more attention and application.

In the blockchain, digital resources can be generated based on Non-Fungible Tokens (NFT) technology, which are usually irreplaceable, limited, and indivisible. Different blockchains can use different NFT protocol standards to generate digital resources. The current mainstream protocol standards include ERC721, ERC1155, and ERC998. Among them, ERC721 is the most commonly used NFT protocol standard. Under the ERC721 standard, each digital resource generated has a unique identifier, and different digital resources are irreplaceable with each other. In the above protocol standards, the attribution account of NFT resources is usually recorded in the contract state.

Contents of the invention

The purpose of the present invention is to provide a solution for transferring NFT resources, which improves the transfer efficiency of NFT resources.

The first aspect of this specification provides a method for transferring NFT resources, which is executed by blockchain nodes, including:

Receive a first transaction, the first transaction is used to transfer the NFT resources of the first account to the second account, and the account information corresponding to the first account stored in the blockchain includes the resources of the NFT resources logo;

According to the first transaction, delete the resource identifier of the NFT resource in the account information corresponding to the first account, and add the NFT in the account information corresponding to the second account stored in the blockchain The resource ID of the resource.

In one embodiment, the account information corresponding to the first account includes the account address of the first NFT account associated with the first account, and the deletion of the NFT resource in the account information corresponding to the first account The resource identification includes: deleting the resource identification of the NFT resource in the account information of the first NFT account according to the account address of the first NFT account.

In one embodiment, the account information corresponding to the second account includes the account address of the second NFT account associated with the second account, and the first transaction includes the account address of the first NFT account and the account address of the first NFT account. The account address of the second NFT account.

In one embodiment, the method further includes: receiving a signature of the first transaction generated based on the private key of the first account, and verifying the signature based on the public key of the first account.

In one embodiment, the method further includes: obtaining the state root hash value of the state tree corresponding to the block to which the first transaction belongs, and the account information corresponding to the first account is corresponding to the second account Update the state root hash value of the state tree in the account information of the state tree.

In one embodiment, the method also includes:

receiving a second transaction sent by the first account for minting the NFT resource;

According to the second transaction, a resource identifier of the NFT resource is generated, and the resource identifier of the NFT resource is added to the account information corresponding to the first account.

In one embodiment, the method also includes:

receiving a third transaction, the third transaction is used to query the NFT resources owned by the first account;

According to the third transaction, the resource identifier of the NFT resource owned by the first account is obtained from the account information corresponding to the first account, and a query result is returned according to the resource identifier of the NFT resource owned by the first account.

The second aspect of this specification provides a blockchain node, including:

A receiving unit, configured to receive a first transaction, the first transaction is used to transfer the NFT resources of the first account to the second account, and the account information corresponding to the first account stored in the blockchain includes the The resource identifier of the NFT resource;

A transfer unit, configured to delete the resource identifier of the NFT resource in the account information corresponding to the first account according to the first transaction, and delete the account information corresponding to the second account stored in the blockchain Add the resource identifier of the NFT resource in .

A third aspect of the present specification provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed in a computer, the computer is instructed to execute the method described in the first aspect.

A fourth aspect of the specification provides a computing device, including a memory and a processor, where executable codes are stored in the memory, and when the processor executes the executable codes, the method described in the first aspect is implemented.

In the embodiment of this specification, a new account model is proposed. The external account contains NFT resource information, so that the NFT resource can be transferred directly between external accounts, which effectively reduces the interaction between contracts and reduces the The cost of the transaction improves the query efficiency of NFT resources.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of this specification, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments recorded in this specification. , for those skilled in the art, other drawings can also be obtained according to these drawings without paying creative labor.

Fig. 1 shows a blockchain architecture diagram in an embodiment;

Fig. 2 is a flow chart of the NFT resource transfer method in the embodiment of this specification;

FIG. 3 is a schematic diagram of account information of an account in an embodiment of this specification;

FIG. 4 is a flowchart of a method for querying NFT resources corresponding to an account in an embodiment of this specification;

Fig. 5 is an architecture diagram of a block chain node in the embodiment of this specification.

Detailed ways

In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below in conjunction with the drawings in the embodiments of this specification. Obviously, the described The embodiments are only some of the embodiments in this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of this specification.

Fig. 1 shows a block chain architecture diagram in an embodiment. In the blockchain architecture diagram shown in FIG. 1 , the blockchain includes, for example, 6 nodes from node 1 to node 6 . The connection between the nodes schematically represents a P2P (Peer to Peer, point-to-point) connection. These nodes can store a full amount of books, that is, store the status of all blocks and all accounts. Wherein, each node in the blockchain can generate the same state in the blockchain by executing the same transaction, and each node in the blockchain can store the same state database. It can be understood that although it is shown in FIG. 1 that the block chain includes 6 nodes, this embodiment of the specification is not limited thereto, but may include other numbers of nodes. Specifically, the nodes included in the blockchain can meet Byzantine Fault Tolerance (BFT) requirements. The Byzantine fault tolerance requirement can be understood as that there may be Byzantine nodes inside the blockchain, but the blockchain does not reflect Byzantine behavior externally. Generally, some Byzantine fault-tolerant algorithms require the number of nodes to be greater than 3f+1, where f is the number of Byzantine nodes, such as the practical Byzantine fault-tolerant algorithm PBFT (Practical Byzantine Fault Tolerance).

A transaction in the blockchain field may refer to a unit of tasks performed and recorded in the blockchain. A transaction usually includes a sending field (From), a receiving field (To) and a data field (Data). Among them, when the transaction is a transfer transaction, the From field indicates the account address that initiated the transaction (that is, initiates a transfer task to another account), the To field indicates the account address that received the transaction (that is, received the transfer), and the Data field Include the transfer amount. In the case of a transaction calling a smart contract in the blockchain, the From field indicates the account address that initiated the transaction, the To field indicates the account address of the contract called by the transaction, and the Data field includes the function name in the calling contract, and the Data such as the incoming parameters of the function are used to obtain the code of the function from the blockchain and execute the code of the function when the transaction is executed.

The function of smart contracts can be provided in the blockchain. Smart contracts on the blockchain are contracts that can be triggered by transactions on the blockchain system. Smart contracts can be defined in the form of code. Invoking a smart contract in the blockchain is to initiate a transaction pointing to the address of the smart contract, so that each node in the blockchain runs the smart contract code in a distributed manner. It should be noted that in addition to creating smart contracts by users, smart contracts can also be set by the system in the genesis block. This type of contract is generally called a genesis contract. Generally, some blockchain data structures, parameters, attributes and methods can be set in the genesis contract. In addition, accounts with system administrator privileges can create system-level contracts or modify system-level contracts (referred to as system contracts). Wherein, the system contract can be used to add data structures of different business data in the blockchain.

In the scenario of deploying a contract, for example, Bob sends a transaction containing information about creating a smart contract (that is, deploying a contract) to the blockchain shown in Figure 1, and the data field of the transaction includes the code of the contract to be created ( Such as bytecode or machine code), the to field of the transaction is empty to indicate that the transaction is used to deploy the contract. After the nodes reach an agreement through the consensus mechanism, determine the contract address "0x6f8ae93...", each node adds the contract account corresponding to the contract address of the smart contract in the state database, allocates the state storage corresponding to the contract account, and The contract code is saved in the state storage of the contract, so the contract is created successfully.

In the scenario of calling the contract, for example, Bob sends a transaction for calling the smart contract to the blockchain shown in Figure 1, the from field of the transaction is the address of the account of the transaction initiator (ie Bob), "0x6f8ae93..." in the to field represents the address of the called smart contract, and the data field of the transaction includes the method and parameters of calling the smart contract. After consensus is reached on the transaction in the blockchain, each node in the blockchain can respectively execute the transaction, thereby respectively executing the contract, and updating the state database based on the execution of the contract.

Smart contracts deployed in the blockchain can include NFT smart contracts, and NFT smart contracts can be codes on the blockchain that can realize NFT functions. For example, NFT functions may include minting functions, transfer functions, query functions, and so on. Here, the minting function can be used to create NFT resources in the blockchain, specifically, the resource identification and attributes of the NFT resources are recorded in the contract state of the NFT smart contract in the blockchain. The transfer function can be used to transfer NFT resources from the current owner to another user. The query function can be used to query the attribute information of NFT resources.

In related technologies, NFT resources are processed based on the ERC1155 protocol. The ERC1155 protocol supports multiple types of certificates. The NFT contract based on the ERC1155 protocol can transfer multiple resources in one call. In this related technology, in the NFT contract The attribution account of the NFT resource is stored in the contract state. When other accounts want to check whether a specific account owns the NFT resource, they need to call the NFT contract to check whether the attribution account of the NFT resource is the specific account. When resources are transferred to other accounts, it is necessary to transfer NFT resources by calling the NFT contract. This query or transfer method is inefficient and reduces the transaction execution efficiency of the blockchain system.

The embodiment of this specification provides a transfer scheme of NFT resources. By including the information of the NFT resources owned by the external account in the account information corresponding to the external account, it can be determined whether the external account owns NFT resources by querying the information corresponding to the external account , and can directly transfer NFT resources between external accounts, effectively improving the processing efficiency of NFT resources.

Fig. 2 is a flow chart of the NFT resource transfer method in the embodiment of this specification, which can be executed by any node in the blockchain, including the following steps S201 and S203.

First, in step S201, the blockchain node receives transaction Tx1, which is used to transfer the NFT resource of account Account1 to account Account2.

Assuming that account Account1 is the account of user A, user A can mint NFT resources by sending a transaction calling a smart contract to the blockchain, and the sending account of the transaction is Account1. After receiving the transaction, the nodes in the blockchain execute the transaction, generate the resource identifier (for example, tokenID1) of the newly minted NFT resource, and add this to the account information corresponding to the account Account1 based on the account mode in the embodiment of this specification. The resource identifier of the newly minted NFT resource to indicate that Account1 owns the NFT resource.

FIG. 3 is a schematic diagram of account information of an account (for example, Account1) in the embodiment of this specification. Among them, the account information shown in Figure 3 is stored in the state database stored in each node in the blockchain, and the state database includes the account status of each account (including external accounts and contract accounts) in the blockchain. These accounts The account state of is stored in the form of a state tree. As shown in FIG. 3 , Account1 is an external account, that is, the user's account. Include NFT resource information in the status information of Account1.

In one embodiment, the NFT resource information shown in FIG. 3 includes information about NFT resources owned by the account Account1 indicated by the dotted line, for example, resource identifiers (such as tokenId1 ) of one or more NFT resources. Corresponding to this embodiment, the transaction Tx1 may be an NFT resource transfer transaction, where the from field in the transaction Tx1 is account Account1, the to field is account Account2, and the data field includes, for example, resource identifiers of one or more NFT resources to be transferred (for example tokenId) to transfer NFT resources from Account1 to Account2. The transaction Tx1 may also include indication information for indicating that the tokenId is the resource identifier of the NFT resource. For example, the transaction Tx1 can be sent by the user equipment corresponding to the account Account1 to any node in the blockchain, so that the transaction Tx1 can be broadcast on the blockchain, so that each node in the blockchain can receive the transaction, and the user equipment At the same time, the signature of the transaction Tx1 will be sent to any node in the blockchain. The signature can be generated by signing the transaction body of the transaction Tx1 with the private key of the account Account1.

In another embodiment, the NFT resource information is, for example, the account address of the NFT account corresponding to the account Account1, such as nft_address1. Meanwhile, state data corresponding to the address nft_address1 is stored in the state database, wherein the state data corresponding to the address nft_address1 includes, for example, table information corresponding to NFT resource information indicated by a dotted line in FIG. 3 . Similarly, the account information of the account Account2 may include the account address nft_address2 of the NFT account corresponding to the account Account2.

Corresponding to this embodiment, the from field in the transaction Tx1 is account Account1, the to field is account Account2, and the data field includes, for example, the resource identifier (such as tokenId) of the NFT resource, which is used to transfer the NFT resource from the NFT account of Account1 To the NFT account of account Account2. In one embodiment, the transaction Tx1 may also include the account address nft_address1 of the NFT account of Account1 and the account address nft_address2 of the NFT account of Account2, to indicate the transfer of the NFT resource from the NFT account nft_address1 of Account1 to Account2 NFT account nft_address2.

In one embodiment, as shown in FIG. 3 , the account information of the account Account1 may also include a state root hash value corresponding to the current state information of the account Account1, so as to verify the account information corresponding to the account Account1, The account information corresponding to the account Account1 includes the table content corresponding to the NFT resource information.

In step S203, the blockchain node deletes the resource identifier of the NFT resource in the account information corresponding to Account1 according to the transaction Tx1, and adds the resource identifier of the NFT resource in the account information corresponding to Account2.

After each node in the blockchain receives the transaction Tx1, it can use the public key of the account Account1 to verify the signature of the transaction Tx1. After the verification is passed, a consensus on the transaction Tx1 can be carried out. Each node in the blockchain executes the transaction Tx1 after the consensus on the transaction Tx1 is passed, and obtains the execution result of the transaction Tx1. The execution result of the transaction Tx1 is used to instruct to delete the resource identifier of the NFT resource in the account information corresponding to the account Account1, and to add the resource identifier of the NFT resource in the account information corresponding to the account Account2. Afterwards, the blockchain node can update the state database according to the execution result of the transaction Tx1, that is, delete the resource identifier of the NFT resource in the account information corresponding to Account1, and add the resource identifier of the NFT resource in the account information corresponding to Account2.

Specifically, in the case where the account information of Account1 includes a list of NFT resource identifiers, assuming that the resource identifier of the NFT resource to be transferred is tonkeID1, the blockchain node can directly assign the resource identifier tokenID1 in the NFT resource identifier list of Account1 Delete, add the resource identifier tokenID1 in the NFT resource identifier list of account Account2, so as to transfer the NFT resource corresponding to toneID1 from Account1 to Account2.

In the case where the account information of account Account1 includes the account address nft_address1 of its associated NFT account, and the account information of account Account2 includes the account address nft_address2 of its associated NFT account, the blockchain node can read the address through address nft_address1 The corresponding NFT resource identifier list, delete the NFT resource identifier tokenID1 in the NFT resource identifier list, read the NFT resource identifier list corresponding to the address through the address nft_address2, and add the NFT resource identifier tokenID1 in the NFT resource identifier list to realize the The NFT resource corresponding to tonkeID1 is transferred from account Account1 to account Account2.

In the embodiment of this specification, a new account model is proposed. The external account contains NFT resource information, so that the NFT resource can be transferred directly between external accounts, which effectively reduces the interaction between contracts and reduces the the cost of the transaction.

Fig. 4 is a flowchart of a method for querying an NFT resource corresponding to an account in an embodiment of this specification. This method is executed by any node in the blockchain.

As shown in Figure 4, first in step S401, the blockchain node receives transaction Tx2, which is used to query the NFT resources owned by account Account1.

Assuming that account Account1 is the account of user A, and account Account2 is the account of user B, user B can first inquire whether user B owns the NFT resource before purchasing the NFT resource owned by user A. User B can send transaction Tx2 to any node in the blockchain (for example, node 1). The sending account of transaction Tx2 is account Account2, and the receiving account can be the account corresponding to node 1.

In one embodiment, the transaction Tx2 may include the account Account1 and indication information, and the indication information is used to indicate the query of all NFT resources owned by the account Account1.

In another embodiment, the transaction Tx2 may include the account Account1 and the resource identifier (for example, tokenID1) of the NFT resource to be queried, so as to query whether the account Account1 owns a specific NFT resource (tokenID1).

In step S405, the blockchain node obtains the identifier of the NFT resource owned by the account Account1 from the account information corresponding to the account Account1 according to the transaction Tx2, and returns the query result according to the identifier of the NFT resource owned by the account Account1.

After node 1 receives transaction Tx2 and determines that transaction Tx2 is a query transaction, it can directly obtain the query result and return it to user B's device without broadcasting transaction Tx2 to the blockchain. Specifically, node 1 may query the account information corresponding to account Account1 from the state database. The account information includes, for example, a resource list of NFT resources owned by Account1 as shown in FIG. 3 . In the case that transaction Tx2 is used to query all NFT resources owned by account Account1, node 1 can return the resource list of NFT resources owned by Account1 to user B's device. In the case that transaction Tx2 is used to query whether Account1 owns the NFT resource corresponding to tokenID1, node 1 can determine whether tokenID1 is included in the resource list according to the resource list of the NFT resource owned by Account1, and if so, return it to user B’s device The NFT resource corresponding to tokenID1 owned by Account1, otherwise, the NFT resource corresponding to tokenID1 not owned by Account1 is returned to user B's device.

In the embodiment of this specification, when other accounts want to query the information of NFT resources owned by a specific account, they can directly obtain the account information corresponding to the specific account based on the address of the specific account, and obtain the NFT resources owned by the specific account from the account information. The information of NFT resources does not need to call the NFT contract to query the attribution account of NFT resources, which improves the query efficiency of NFT resources.

Fig. 5 is an architecture diagram of a block chain node in the embodiment of this specification, the block chain node is used to execute the method shown in Fig. 2 or Fig. 4, and the block chain node includes:

The receiving unit 51 is configured to receive a first transaction, the first transaction is used to transfer the NFT resource of the first account to the second account, and the account information corresponding to the first account stored in the blockchain includes A resource identifier of the NFT resource;

The transfer unit 52 is configured to delete the resource identifier of the NFT resource in the account information corresponding to the first account according to the first transaction, and the account corresponding to the second account stored in the blockchain The resource identifier of the NFT resource is added to the information.

In one embodiment, the account information corresponding to the first account includes an account address of a first NFT account associated with the first account, and the transfer unit 52 is specifically configured to: according to the account address of the first NFT account Address, delete the resource identifier of the NFT resource in the account information of the first NFT account.

In one embodiment, the account information corresponding to the second account includes the account address of the second NFT account associated with the second account, and the first transaction includes the account address of the first NFT account and the account address of the first NFT account. The account address of the second NFT account.

In one embodiment, the receiving unit 51 is further configured to: receive the signature of the first transaction generated based on the private key of the first account, and perform the signature on the signature based on the public key of the first account. verify.

In one embodiment, the blockchain node further includes: an acquisition unit, configured to acquire the state root hash value of the state tree corresponding to the block to which the first transaction belongs, and the account corresponding to the first account The state root hash value of the state tree is updated respectively in the information and the account information corresponding to the second account.

In one embodiment, the receiving unit 51 is further configured to: receive a second transaction, the second transaction is sent by the first account, and is used to mint the NFT resource;

The blockchain node further includes: a generating unit, configured to generate a resource identifier of the NFT resource according to the second transaction, and add the resource identifier of the NFT resource to the account information corresponding to the first account.

In one embodiment, the receiving unit is further configured to receive a third transaction, and the third transaction is used to query the NFT resources owned by the first account;

The acquiring unit is further configured to, according to the third transaction, acquire the resource identifier of the NFT resource owned by the first account from the account information corresponding to the first account, and according to the NFT resource owned by the first account The resource ID for returns query results.

The embodiment of this specification also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed in a computer, the computer is made to execute the methods shown in FIG. 2 and FIG. 4 .

The embodiment of this specification also provides a block chain node, including a memory and a processor, the memory stores executable code, and when the processor executes the executable code, the implementation is shown in Figure 2 and Figure 4 Methods.

In the 1990s, the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, and switches) or improvements in software (improvement in method flow). However, with the development of technology, the improvement of many current method flows can be regarded as the direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (Programmable Logic Device, PLD) (such as a Field Programmable Gate Array (Field Programmable Gate Array, FPGA)) is such an integrated circuit, and its logic function is determined by programming the device by a user. It is programmed by the designer to "integrate" a digital system on a PLD, instead of asking a chip manufacturer to design and make a dedicated integrated circuit chip. Moreover, nowadays, instead of making integrated circuit chips by hand, this kind of programming is mostly realized by "logic compiler (logic compiler)" software, which is similar to the software compiler used when writing programs. The original code of the computer must also be written in a specific programming language, which is called a hardware description language (Hardware Description Language, HDL), and there is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., currently the most commonly used is VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that only a little logical programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit for realizing the logic method flow.

The controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers, and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that, in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a server system. Of course, the present application does not exclude that with the development of future computer technology, the computer that realizes the functions of the above embodiments can be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant , media players, navigation devices, email devices, game consoles, tablet computers, wearable devices, or any combination of these devices.

Although one or more embodiments of the present specification provide the operation steps of the method described in the embodiment or the flowchart, more or fewer operation steps may be included based on conventional or non-inventive means. The sequence of steps enumerated in the embodiments is only one of the execution sequences of many steps, and does not represent the only execution sequence. When an actual device or terminal product is executed, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (such as a parallel processor or multi-thread processing environment, or even a distributed data processing environment). The term "comprising", "comprising" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, product, or apparatus comprising a set of elements includes not only those elements, but also other elements not expressly listed elements, or also elements inherent in such a process, method, product, or apparatus. Without further limitations, it is not excluded that there are additional identical or equivalent elements in a process, method, product or device comprising said elements. For example, if the words first, second, etc. are used, they are used to indicate names and do not indicate any specific order.

For the convenience of description, when describing the above devices, functions are divided into various modules and described separately. Of course, when implementing one or more of the present specification, the functions of each module can be realized in the same or more software and/or hardware, and the modules that realize the same function can also be realized by a combination of multiple submodules or subunits, etc. . The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated. to another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram. These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors, input/output interfaces, network interfaces, and memory. Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape disk storage, graphene storage or other magnetic storage devices or any other non-transmission medium that can be used to store information that can be accessed by computing devices. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

Those skilled in the art should understand that one or more embodiments of this specification may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description may employ a computer program embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. The form of the product.

One or more embodiments of this specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present description may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment. In the description of this specification, descriptions referring to the terms "one embodiment", "some embodiments", "example", "specific examples", or "some examples" mean that specific features described in connection with the embodiment or example , structures, materials or features are included in at least one embodiment or example of this specification. In this specification, the schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the described specific features, structures, materials or characteristics may be combined in any suitable manner in any one or more embodiments or examples. In addition, those skilled in the art can combine and combine different embodiments or examples and features of different embodiments or examples described in this specification without conflicting with each other.

The above description is only an example of one or more embodiments of this specification, and is not intended to limit one or more embodiments of this specification. For those skilled in the art, various modifications and changes may occur in one or more embodiments of this description. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in the scope of the claims.

Claims (10)

1. A NFT resource transfer method, executed by blockchain nodes, including: Receive a first transaction, the first transaction is used to transfer the NFT resources of the first account to the second account, and the account information corresponding to the first account stored in the blockchain includes the resources of the NFT resources logo; According to the first transaction, delete the resource identifier of the NFT resource in the account information corresponding to the first account, and add the NFT in the account information corresponding to the second account stored in the blockchain The resource ID of the resource. 2. The method according to claim 1, wherein the account information corresponding to the first account includes the account address of the first NFT account associated with the first account, and the account information corresponding to the first account is deleted The resource identification of the NFT resource includes: deleting the resource identification of the NFT resource in the account information of the first NFT account according to the account address of the first NFT account. 3. The method according to claim 2, wherein the account information corresponding to the second account includes the account address of the second NFT account associated with the second account, and the first transaction includes the first NFT The account address of the account and the account address of the second NFT account. 4. The method according to claim 1 or 2, further comprising: obtaining the hash value of the state root of the state tree corresponding to the block to which the first transaction belongs, the account information corresponding to the first account and the The state root hash value of the state tree is updated in the account information corresponding to the two accounts. 5. The method of claim 1 or 2, further comprising: receiving a second transaction sent by the first account for minting the NFT resource; According to the second transaction, a resource identifier of the NFT resource is generated, and the resource identifier of the NFT resource is added to the account information corresponding to the first account. 6. The method of claim 1 or 2, further comprising: receiving a third transaction, the third transaction is used to query the NFT resources owned by the first account; According to the third transaction, the resource identifier of the NFT resource owned by the first account is obtained from the account information corresponding to the first account, and a query result is returned according to the resource identifier of the NFT resource owned by the first account. 7. A blockchain node, comprising: A receiving unit, configured to receive a first transaction, the first transaction is used to transfer the NFT resources of the first account to the second account, and the account information corresponding to the first account stored in the blockchain includes the The resource identifier of the NFT resource; A transfer unit, configured to delete the resource identifier of the NFT resource in the account information corresponding to the first account according to the first transaction, and delete the account information corresponding to the second account stored in the blockchain Add the resource identifier of the NFT resource in . 8. The blockchain node according to claim 7, the account information corresponding to the first account includes the account address of the first NFT account associated with the first account, and the transfer unit is specifically configured to: according to the The account address of the first NFT account, and the resource identifier of the NFT resource is deleted in the account information of the first NFT account. 9. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed in a computer, it causes the computer to execute the method according to any one of claims 1-6. 10. A block chain node, comprising a memory and a processor, wherein executable code is stored in the memory, and when the processor executes the executable code, the method described in any one of claims 1-6 is realized. method.

Images