Method for processing non-fungible token, electronic apparatus, and recording medium

Abstract

To provide a method for processing a non-fungible token about a receipt, an electronic apparatus, and a recording medium.SOLUTION: A processor of an electronic apparatus connected to a computer network including a block chain network executes a smart contract for processing an NFT related to a receipt. The smart contract includes one or more instructions, and the one or more instructions cause the processor to: identify an issue request for a digital file related to a receipt related to purchase of a product and a non-fungible token (NFT) related to the receipt; issue the NFT related to the receipt as a response to the issue request; identify the evaluation information related to the product; and if a creator created the evaluation information related to the product is a purchaser who purchased the product, record evaluation information on a product in metadata of the NFT related to the receipt.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present disclosure relates to a technology for processing non-fungible tokens, and specifically, to a method for processing non-fungible tokens related to receipts, an electronic device, and a recording medium.

Background Art

[0002] Recently, in various industrial fields, digital assets based on blockchain technology have been used. Digital assets such as non-fungible tokens can be traded in a blockchain network and used to exchange value among token holders. Non-fungible tokens (NFTs) have been integrated with various services and used to create new business models.

[0003] On the other hand, with the development of Internet services such as social network services (SNS), purchasers who plan to purchase a specific product or service tend to check the purchase reviews of those who have purchased the product or service earlier than themselves and are more likely to make a purchase.

Summary of the Invention

Problems to be Solved by the Invention

[0004] According to an embodiment of the present disclosure, a technical problem is to guarantee the fact of purchasing a product or service by using an NFT related to a receipt for purchasing the product or service.

[0005] According to an embodiment of the present disclosure, a technical problem is to enable an actual purchaser who has purchased a product or service to record evaluation information (e.g., a review) in the metadata of an NFT related to a receipt for purchasing the product or service.

[0006] The technical problem to be achieved by this embodiment is not limited to the above technical problems, and other technical problems can be analogized from the following embodiments.

Means for Solving the Problem

[0007] A method for an electronic device according to an embodiment of the present disclosure to process a non-fungible token (NFT) may include a processor of the electronic device connected to a computer network including a blockchain network executing a smart contract for processing an NFT related to a receipt. A smart contract according to an embodiment includes one or more instructions, and the one or more instructions, when executed, cause the processor to identify a digital file related to a receipt for the purchase of a product and a request for issuance of an NFT related to the receipt, and as a response to the identified request for issuance, issue an NFT related to the receipt, identify evaluation information about the product, and if the creator who created the evaluation information about the product is the purchaser who purchased the product, record the evaluation information about the product in the metadata of the NFT related to the receipt.

[0008] The one or more instructions according to an embodiment may be further configured such that, when executed, the processor stores the digital file related to the receipt in a distributed file system and records an address where the digital file related to the receipt is stored on the distributed file system in one or more blocks on the blockchain network, thereby issuing an NFT related to the receipt.

[0009] The one or more instructions according to an embodiment may be further configured such that, when executed, the processor records a wallet address of a first account corresponding to a purchaser who purchased the product in the metadata of the NFT related to the receipt.

[0010] In one embodiment, the one or more instructions, when executed, cause the processor to confirm whether the creator who created the evaluation information regarding the product is the holder of the NFT associated with the receipt, and if the creator is the holder of the NFT associated with the receipt, the one or more instructions may be further configured to determine that the creator is the purchaser who purchased the product.

[0011] In one embodiment, the one or more instructions, when executed, cause the processor to identify the wallet address of the creator's account, and based on the wallet address of the creator's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network, confirm whether the creator is the holder of the NFT associated with the receipt.

[0012] In one embodiment, the one or more instructions, when executed, cause the processor to store the evaluation information regarding the product in a distributed file system in response to the creator being the purchaser who purchased the product, and record the address where the evaluation information regarding the product is stored on the distributed file system in the metadata of the NFT associated with the receipt.

[0013] In one embodiment, the one or more instructions, when executed, cause the processor not to record the evaluation information regarding the product in the metadata of the NFT associated with the receipt if the creator is not the purchaser who purchased the product.

[0014] In one embodiment, the one or more instructions, when executed, cause the processor to obtain identification information regarding the creator, and based on the identification information regarding the creator, further verify whether the creator is the purchaser who purchased the product.

[0015] The one or more instructions according to one embodiment, when executed, cause the processor to identify a change request that requests the processor to change the holder of the NFT related to the receipt from the first account to a second account, verify whether the second account is the account of a repurchaser who repurchased the product from the purchaser, and, in response to the second account being the account of the repurchaser, may be further configured to record the wallet address of the second account in the metadata of the NFT related to the receipt.

[0016] The one or more instructions according to one embodiment, when executed, cause the processor to identify a digital file related to an additional receipt related to a repurchase of the product and an issuance request for an NFT related to the additional receipt, issue the NFT related to the additional receipt in response to the issuance request for the NFT related to the additional receipt, and may be further configured to associate the NFT related to the receipt and the NFT related to the additional receipt with each other.

[0017] The one or more instructions according to one embodiment, when executed, may be further configured to cause the processor to record information about the NFT related to the receipt in the metadata of the NFT related to the additional receipt.

[0018] The one or more instructions according to one embodiment, when executed, may be further configured to cause the processor to synthesize the NFT related to the receipt and the NFT related to the additional receipt.

[0019] The metadata of the NFT related to the receipt according to one embodiment may include at least one of detailed information about the product, the evaluation information, the creator information that created the evaluation information, or the creation date and time information.

[0020] The evaluation information according to one embodiment may include at least one of the name of the product, identification information related to the product, an image, a video, or a review.

[0021] A method for an electronic device according to an embodiment of the present disclosure to process a non-fungible token (NFT) may include a processor connected to a computer network including a blockchain network executing a smart contract for processing an NFT related to a receipt. The smart contract according to one embodiment includes one or more instructions, and the one or more instructions identify a digital file related to a receipt related to the purchase of a service and a request for issuing an NFT related to the receipt, and in response to the identified request for issuing, issue an NFT related to the receipt, identify evaluation information related to the service, and verify whether the creator who created the evaluation information related to the service is the holder of the NFT related to the receipt, thereby verifying whether the creator who created the evaluation information related to the service is the purchaser who purchased the service. If the creator is the purchaser who purchased the service, record the evaluation information related to the service in the metadata of the NFT related to the receipt, and in response to recording the evaluation information related to the service, it may be set to provide compensation to the first account.

[0022] The metadata of the NFT related to the receipt according to one embodiment includes at least one of detailed information related to the service, evaluation information, creator information who created the evaluation information, or creation date and time information, and the evaluation information may include at least one of the name of the store that provided the service, the fee related to the service, an image, a video, or a review.

[0023] An electronic device according to an embodiment of the present disclosure can include a communication circuit that communicates with a computer network including a blockchain network; a memory in which a smart contract for processing an NFT related to a receipt is stored; and a processor. The processor according to one embodiment is configured to execute the smart contract including one or more instructions, and by executing the one or more instructions, the processor identifies a digital file related to a receipt regarding the purchase of a product and a request for issuing an NFT related to the receipt, and as a response to the identified request for issuing, issues an NFT related to the receipt, receives evaluation information regarding the product, and if the creator who created the evaluation information regarding the product is the purchaser who purchased the product, may be configured to record the evaluation information regarding the product in the metadata of the NFT related to the receipt.

[0024] Specific matters of other embodiments are included in the detailed description and the drawings.

Advantages of the Invention

[0025] According to an embodiment of the present disclosure, the fact of purchasing a product or service can be technically guaranteed by using an NFT related to a receipt regarding the purchase of the product or service. More specifically, it can be technically guaranteed whether a specific user has purchased a product or service.

[0026] According to an embodiment of the present disclosure, a purchaser who has purchased a product or service can record evaluation information (e.g., a review) in the metadata of an NFT related to a receipt regarding the purchase of the product or service. Through this, the fact that the evaluation information of the product or service is created by the actual purchaser can be technically guaranteed, and a person planning to purchase the product or service can trust the evaluation information of the actual purchaser prior to the purchase.

[0027] According to an embodiment of the present disclosure, in the secondary trading process of a product, the authenticity of the product can be technically guaranteed through the evaluation information or purchase history of the previous owner, and the value of the product can be preserved or enhanced.

[0028] The effects of the present invention are not limited to the aforementioned effects, and other effects not mentioned will be clearly understood by those skilled in the art from the description of the claims.

Brief Description of the Drawings

[0029]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0030] The terms used in the embodiments are, as much as possible, general terms that are currently widely used while taking into account the functions in the present disclosure. However, this may change depending on the intentions or precedents of those skilled in the art, the emergence of new technologies, etc. Also, in certain cases, there are terms arbitrarily selected by the applicant, and in such cases, the meaning will be described in detail in the corresponding explanatory part. Therefore, the terms used in the present disclosure should not be mere term names, but must be defined based on the meaning of the terms and the overall content of the present disclosure.

[0031] Throughout the specification, when a certain part states that an element "includes", this means that, unless otherwise stated to the contrary, it does not exclude other elements and may further include other elements. Also, terms such as "~ part" and "~ module" described in the specification mean units that process at least one function or operation, which can be embodied in hardware or software, or in a combination of hardware and software, and unlike the illustrated examples, cannot be clearly distinguished in specific operations.

[0032] The expression "at least one of a, b, and c" described throughout the specification can include "a alone", "b alone", "c alone", "a and b", "a and c", "b and c", or "all of a, b, and c".

[0033] The "terminal" or "user terminal" mentioned below can be embodied as a computer or a mobile terminal that can be connected to a server or other terminals through a network. Here, the computer may include, for example, a notebook computer, a desktop, a laptop, etc. equipped with a web browser, and the mobile terminal may include, for example, as a wireless communication device that guarantees portability and mobility, communication infrastructure terminals such as IMT (International Mobile Telecommunication), CDMA (Code Division Multiple Access), W-CDMA (W-Code Division Multiple Access), LTE (Long Term Evolution), and all kinds of handheld-based wireless communication devices such as smartphones and tablet PCs.

[0034] In the following description, terms such as "transmission", "communication", "sending", "receiving", and other terms with similar meanings for signals, messages, or information not only include the direct transmission of information, messages, or information from one component to another component, but also include transmission through other components. In particular, "transmitting" or "sending" a signal, message, or information as one component indicates the ultimate destination of that signal, message, or information, and does not mean the direct destination. This is the same for the "receiving" of signals, messages, or information. Also, in this specification, when two or more data or information are "related", it means that if one data (or information) is obtained, at least a part of other data (or information) can be obtained based on it.

[0035] Also, terms such as first, second, etc. can be used to describe various components, but the components should not be limited by these terms. These terms can be used for the purpose of distinguishing one component from another component.

[0036] For example, without departing from the scope of the claims of this specification, the first component may be named as the second component, and similarly the second component may be named as the first component.

[0037] Hereinafter, with reference to the accompanying drawings, embodiments of this specification will be described in detail so that those having ordinary knowledge in the technical field to which this specification pertains can easily implement them. However, this specification can be embodied in a plurality of different forms and is not limited to the embodiments described herein.

[0038] In describing the embodiments, technical content that is well known in the technical field to which the embodiments of the present disclosure pertain and is not directly related to the present disclosure will be omitted from the description. This is to avoid obscuring the gist of the present invention and to convey it more clearly by omitting unnecessary explanations.

[0039] For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not fully reflect the actual size. In each drawing, the same or corresponding components are given the same reference numerals.

[0040] The advantages and features of the embodiments of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and can be embodied in a variety of different forms. Merely, these embodiments are provided so that the present disclosure is complete and so that those having ordinary knowledge in the technical field to which the embodiments of the present disclosure pertain can fully know the scope of the technology. The present disclosure is only defined by the scope of the claims. The same reference numerals throughout the specification refer to the same components.

[0041] One will be able to understand that the combination of each block of the flowchart and the flowchart drawing can be performed by computer program instructions. Since these computer program instructions can be loaded onto the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions performed through the processor of the computer or other programmable data processing equipment will generate means for performing the functions described in the flowchart block(s). Since these computer program instructions can also be stored in a computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment in order to embody the functions in a specific manner, the instructions stored in the computer-usable or computer-readable memory can also produce a manufactured item that includes instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions can also be loaded onto a computer or other programmable data processing equipment, a series of operational steps are performed on the computer or other programmable data processing equipment to generate a process executed by the computer, and the instructions for operating the computer or other programmable data processing equipment can also provide steps for performing the functions described in the flowchart block(s).

[0042] Also, each block can represent a module, segment, or portion of code that contains one or more executable instructions for performing a specified logical function(s). Note that in some alternative execution forms, the functions mentioned in the block can occur out of order. For example, two blocks shown consecutively can actually be performed substantially simultaneously, or the blocks can sometimes be performed in reverse order depending on the functions involved.

[0043] In the present disclosure, tokens issued, utilized, or erased based on a blockchain network can comply with at least some of the standards set by the Ethereum request for comments (ERC). For example, alternative fungible tokens (FTs) can comply with ERC20. ERC20 includes a set of rules required for a token to have the characteristics of an FT. The rules included in ERC20 can include rules regarding functions such as token transfer between addresses, querying the total token supply, and querying the token balance of a specific address. For example, non-fungible tokens (NFTs) can comply with ERC721. ERC721 includes a set of rules required for a token to have the characteristics of an NFT. The rules included in ERC721 can include rules regarding functions such as querying the number of tokens owned by a specific address, querying the owner of a specific token, token transfer between addresses, and returning the addresses approved to transfer a specific token. As another example, tokens can comply with ERC1155, which is a standard that encompasses both FTs and NFTs. ERC1155 is a combined token standard that can generate both FTs and NFTs with a single smart contract. By storing multiple token types in a single smart contract, it is possible to reduce gas fees and enhance scalability compared to ERC721.

[0044] In the present disclosure, the term "smart contract" used herein can be a program or application that operates on a virtual machine executed by two or more nodes included in a blockchain network. A smart contract can be a computer protocol for establishing, verifying, and fulfilling a specific contract by itself. A smart contract can mean a program that automatically executes a contract if the contract conditions programmed based on blockchain technology are met. The virtual machine can include, for example, the Ethereum virtual machine (EVM), which is a distributed computing environment that executes and manages smart contracts while operating on the Ethereum blockchain. The EVM is a Turing machine for processing (e.g., distributing, executing) smart contracts and can process all forms of algorithms. The EVM can execute smart contracts according to the rules defined by Ethereum and, as a result, perform the task of updating the changed state. Smart contracts can be created to comply with certain conventions or protocols. For example, referring to ERC-721 or ERC-1155, etc., a smart contract can be created to include one or more functions corresponding to each protocol. However, various types of smart contracts can be created by including other functions not included in the exemplified protocols.

[0045] In the present disclosure, the term "wallet" used herein can be a tool for securely storing and managing a user's digital assets in electronic form. A wallet can store and manage information regarding cryptocurrencies and digital assets. Digital asset wallets can be classified into hot wallets and cold wallets. A hot wallet is a wallet connected to the Internet and is in a form that allows access to cryptocurrencies in an online environment. A hot wallet can generally be provided as a software wallet or an online service. A hot wallet can provide convenient and fast access to transmit cryptocurrencies and can process transactions quickly. A cold wallet can be a wallet that stores private keys in an offline environment not connected to the Internet. A cold wallet can generally be provided as a hardware wallet or a paper wallet. Since a cold wallet securely protects private keys and stores them in an offline state, it can provide a high level of security against hacking and malicious software attacks. A wallet address can be a kind of identifier for identifying a wallet. A user can send and receive digital assets using the wallet address.

[0046] In the present disclosure, transmitting a transaction to a blockchain network may include uploading specific data to the blockchain network, modifying or deleting data already uploaded on the blockchain network, or executing a smart contract distributed on the blockchain network. In the present disclosure, the transaction used can be a logical unit of work performed on the blockchain network. The transaction can include a transaction recorded on the blockchain network and / or a transaction not recorded on the blockchain network. For example, a transaction of an Ethereum blockchain network can include a transaction recorded on the blockchain network including the hash value of the transaction and a message (message, internal transaction) generated when executing the transaction in the EVM.

[0047] FIG. 1 is a diagram illustrating a system 10 for processing non-fungible tokens (NFTs) according to an embodiment of the present disclosure. The system 10 can include a server 110, a terminal 120, a blockchain network 140, and / or a computer network 130. The blockchain network 140 can include two or more nodes (e.g., node 141). Each of the server 110, the terminal 120, and the nodes of the blockchain network 140 can communicate with each other through the computer network 130. The computer network 130 is a digital telecommunications network and can mean a network that connects each distributed device to a predetermined communication network. The computer network 130 can be implemented by all types of wired or wireless networks such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, or Wibro (wireless broadband internet). The computer network 130 is a comprehensive data communication network that enables each device illustrated in FIG. 1 to communicate smoothly with each other and can include a wired internet network, a wireless internet network, and a mobile wireless communication network. In this drawing, an environment is illustrated in which the server 110 communicates with the terminal 120 and two or more nodes through the computer network 130, but this is merely an example, and the number of terminals 120 and the number of nodes can vary.

[0048] According to one embodiment, the server 110 can be a server that implements (operates) a platform (hereinafter, NFT management platform) for managing non-fungible tokens related to receipts. The NFT management platform can be understood as a platform for various management or processing related to NFTs, such as issuing NFTs, assisting in circulation, promotion, or transactions, or extinguishing them. The server 110 can perform various management or processing on the NFTs related to receipts. For example, the server 110 can manage the wallet addresses of each digital asset in which the user's NFTs are stored. In the present disclosure, an account can be a unique character string that proves the identity of a user or can identify the user in the NFT management platform. A user can access the NFT management platform with their own account to trade NFTs. When an account is granted to a user from the NFT management platform, one or more wallets can be issued per account for NFT trading. For example, through the NFT management platform, the NFTs included in the wallet corresponding to one account can be transmitted to the wallet corresponding to another account. In this specification, the operation of an NFT being transmitted from the wallet corresponding to one account to the wallet corresponding to another account can be understood as being the same or similar to the information regarding the owner of the NFT recorded in the metadata of the NFT, for example, the information regarding the owner's wallet address being changed from the first information to the second information. The server 110 can perform various operations generally required in the NFT management platform (e.g., communication between users). The server 110 can participate in the issuance and trading of NFTs by interacting with at least one of the nodes included in the blockchain network 140. The server 110 can be a single electronic device, but is not limited thereto, and may also refer to a group in which a plurality of electronic devices are electronically or physically connected.

[0049] Server 110 according to one embodiment may be implemented by one or more electronic devices (or computing devices). For example, all functions of server 110 may be implemented in a single electronic device. As another example, the first function of server 110 may be implemented in the first electronic device, and the second function may be implemented in the second electronic device. The electronic device may be a desktop computer, a laptop computer, an application server, a proxy server, a cloud server, and is not limited thereto, and may be various types of devices equipped with computing functions.

[0050] Terminal 120 according to one embodiment may be a terminal 120 of a user using the NFT management platform or a terminal 120 of an administrator managing the NFT management platform. The user can use various functions provided by the NFT management platform through terminal 120. The user can request the issuance of an NFT related to a receipt or communicate with other users through terminal 120. The user can use the NFT management platform using a dedicated application or a web browser installed on terminal 120. Terminal 120 may be, for example, any one of devices such as a desktop computer, a workstation, a laptop computer, a tablet computer, an audio player, a wearable device, or a smart phone, but is not limited to this example, and may be various types of electronic devices equipped with computing functions. In this drawing, the number of terminals 120 is illustrated as one, but is not limited thereto, and the number of terminals 120 may be two or more.

[0051] According to one embodiment, one node (e.g., node 141) included in the blockchain network 140 may mean an electronic device of one participant who participated in the blockchain network 140. The node may be one element that constitutes the blockchain network 140. The node can perform operations for maintaining the blockchain of the blockchain network 140. For example, any one node of the blockchain network 140 can generate a new block of the corresponding blockchain. The new block can be shared among other nodes of the blockchain network 140 through a distributed consensus process and connected to the next block of the blockchain. That is, the node can perform operations of generating, verifying, or propagating a transaction and the block in which the transaction is recorded. The node can be a full node, a light node, a master node, a mining node, a random node, a baking node, or a super node, etc., depending on the operations performed by the node. The node can issue tokens by interacting with the server 110. The issuance of tokens may mean a process in which the issuer generates a specific amount of tokens using a smart contract and stores the generated tokens in a specific wallet.

[0052] According to one embodiment, the node can be embodied as an electronic device (or computing device). For example, the aforementioned electronic device can be a desktop computer, a laptop computer, etc., but is not limited thereto, and can be various types of devices equipped with computing functions. The server 110, the terminal 120, and the node can be elements shown as functionally divided. Two or more components can be embodied in an integrated form in an actual physical environment. For example, the server 110 and the nodes included in the blockchain network 140 can be embodied in different logic forms within the same electronic device 200. For example, the server 110 may be embodied to operate as one node of the blockchain network 140, or the terminal 120 may be embodied to operate as one node of the blockchain network 140.

[0053] According to one embodiment, the blockchain network 140 can record, approve, or process transactions in blocks and may be capable of generating smart contracts. In the present disclosure, although one blockchain network 140 is illustrated, it is not limited thereto, and it may be composed of a main blockchain network and a side blockchain network. In the above case, the main blockchain network can place emphasis on security and decentralization, and the side blockchain network can focus on speed and reduction of transaction fees (e.g., gas fees).

[0054] According to one embodiment, each node of the blockchain network can record transactions related to operations such as the issuance, drop, and update of NFTs in the blockchain network 140. Each node can also read the transactions recorded and verified on the blockchain network 140 and maintain the currency of the corresponding information.

[0055] According to one embodiment, a smart contract for performing operations such as issuing NFTs and recording information in the metadata of NFTs can be distributed to the blockchain network 140. The smart contract can be a smart contract that processes NFTs related to receipts, and the smart contract can include one or more instructions. A processor of an electronic device connected to the computer network 130 including the blockchain network 140 can execute a smart contract that processes NFTs related to receipts. The one or more instructions can be configured to cause the processor of the electronic device to perform various operations determined at runtime.

[0056] FIG. 2 is a block diagram illustrating an electronic device 200 that can embody any one of the devices according to an embodiment of the present disclosure. According to the present disclosure, the electronic device 200 can be represented as a computing device, and the electronic device 200 and the computing device can be referred to interchangeably. Each of the aforementioned server 110, terminal 120, and nodes included in the blockchain network 140 can be embodied by the electronic device 200.

[0057] The electronic device 200 according to one embodiment can include a processor 210, a memory 220, and a communication circuit 230. At least one of the components included in the electronic device 200 can be omitted, or other components can be added to the electronic device 200. Additionally or alternatively, some components can be integrated and embodied, or embodied as a single or multiple entities. At least some of the components within the electronic device 200 can be integrated and embodied, or embodied as a single or multiple entities. At least some of the components within the electronic device 200 are connected to each other through a bus, GPIO (general purpose input / output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface) to exchange data and / or signals.

[0058] The processor 210 of the electronic device 200 according to one embodiment is configured to perform operations and data processing related to the control and / or communication of each component of the electronic device 200, and can be operatively connected to the components of the electronic device 200. The processor 210 can load instructions or data received from other components of the electronic device 200 into the memory 220, process the instructions or data stored in the memory 220, and store the result data. Unless otherwise specified, in the present disclosure, the processor 210 may mean a set of one or more processors 210.

[0059] The memory 220 of the electronic device 200 according to one embodiment can store various data used by at least one component (e.g., the processor 210). The memory 220 can store instructions for the operation of the processor 210. The program can be stored in the memory 220 as software and can include, for example, an operating system, middleware, or an application. Unless otherwise specified, in the present disclosure, the memory 220 may mean a set of one or more memories 220.

[0060] The communication circuit 230 of the electronic device 200 according to one embodiment can establish a wired or wireless communication channel with an external device (e.g., the terminal 120) and transmit and receive various data with the external device. The communication circuit 230 of the electronic device 200 can include at least one port for connecting to the external device with a wired cable for wired communication with the external device. The communication circuit 230 of the electronic device 200 can be configured to be connected to a cellular network (e.g., 3G, LTE, 5G, Wibro, or Wimax) including a cellular communication module. According to one embodiment, the communication circuit 230 of the electronic device 200 can transmit and receive data with an external device using short-range communication (e.g., Wi-Fi, Bluetooth, Bluetooth low energy (BLE), UWB), including but not limited to this.

[0061] According to an embodiment, the electronic device 200 may further include a display, an input device, or an output device. The display can display various screens under the control of the processor 210. The input device can receive data from outside the electronic device 200 (e.g., a user). The input device can include, for example, a mouse and a keyboard. The output device can output information in various ways under the control of the processor 210. The output device can include, for example, a speaker.

[0062] FIG. 3 is a conceptual diagram of a blockchain network 140 according to an embodiment of the present disclosure. In the present disclosure, a block may refer to a specific data type. In the present disclosure, a blockchain may refer to a data structure in which one or more blocks 142a, 142b, 142c are connected in a chain form. One or more blocks 142a, 142b, 142c included in the blockchain may be stored independently in one or more nodes included in the blockchain network 140, or may be stored distributively across a plurality of nodes. Each of the one or more blocks 142a, 142b, 142c may include a block hash, a block header, or a block body. The block hash is unique information that can identify a block and may be, for example, a character string represented by 256 bits. The block header may include, for example, software or protocol version information, the hash of a previous block related to the connection order of the blocks on the blockchain, a Merkle root, time information indicating the time when the block was generated, bits indicating the difficulty of calculation, and at least one of a nonce, which is an arbitrary value for creating the hash value of a block required in the process of adding a new block to the blockchain. The block body may include at least one transaction. A transaction is a set of data having a specific data structure and may be a unit of information stored in the block body. A transaction may include information related to the generation or transaction of tokens. A transaction may be, for example, information to the effect that a first node included in the blockchain network 140 transmits an NFT to a second node.

[0063] The blockchain can be managed by a blockchain network 140 including at least one node. Each of the at least one node included in the blockchain network 140 may be referred to as a participant in the blockchain network. The at least one node included in the blockchain network 140 may operate according to a hierarchical structure. The hierarchical structure defines, for example, the structure of data handled by the blockchain network 140, a data hierarchy for managing data, performs mining to verify the validity of blocks and generate blocks, a consensus hierarchy responsible for processing fees paid to miners in the mining process, a P2P network protocol, a hash function, an electronic signature, an encoding, and a sharing hierarchy for embodying or managing a shared repository, or may include at least one of an application hierarchy in which various applications are generated or processed.

[0064] At least one node included in the blockchain network 140 can share or store the transactions recorded on the blockchain. Also, at least one node included in the blockchain network 140 can perform verification work on the transactions transmitted to the blockchain network 140 through the consensus algorithm of the blockchain, and when the verification is completed, it can perform the function of recording the verified transactions in one block on the blockchain. There is no limitation on the type of consensus algorithm performed by the blockchain network 140, and all types of consensus algorithms that can be adopted and modified by those skilled in the art can be performed. For example, the consensus algorithm can include at least one of the PoW (proof of work) algorithm, PoS (proof of stake) algorithm, DPoS (delegated proof of stage) algorithm, PBFT (practical byzantine fault tolerance) algorithm, DBFT (delegated byzantine fault tolerance) algorithm, RBFT (redundant byzantine fault tolerance) algorithm, Sieve algorithm, Tendermint algorithm, Paxos algorithm, Raft algorithm, PoA (proof of authority) algorithm, or PoET (proof of elapsed time) algorithm, or an algorithm applying the aforementioned consensus algorithms.

[0065] Each of at least one node included in the blockchain network 140 can store a smart contract. Through this, at least one node included in the blockchain network 140 can share the same smart contract. Also, the smart contract can be recorded in one block on the blockchain managed by the blockchain network 140. A smart contract can be a specification or script written in a programming language such as, for example, Solidity, and a program or application that operates on a virtual machine executed by at least one node included in the blockchain network 140. A smart contract can include one or more instructions that cause a specific action to be executed when specific conditions are met. The specific conditions can include, for example, conditions where a specific type of token is input or data in a specific format is input. The specific action can include, for example, an action of transmitting a specific type of token to any node of the blockchain network 140.

[0066] A smart contract can be created to comply with certain conventions (or protocols). For example, a smart contract can be created to include one or more functions corresponding to each of the ERC-20 or ERC-721 protocols. However, by including other functions not included in the exemplified protocols (for example, one or more functions corresponding to ERC-1155) in the smart contract, various types of smart contracts can be created.

[0067] In the present disclosure, a token can be a token that can be used on a blockchain managed by a blockchain network 140 and can be an NFT. The NFT can mean a virtual token generated by a smart contract created with reference to certain conventions (e.g., ERC-721 or ERC-1155). By being recorded on a blockchain which is a distributed storage, the integrity of the NFT can be maintained. By generating the NFT to include a specific type of data, the existence of the specific type of data can be guaranteed. In the present disclosure, the object referred to as a token can be an NFT unless otherwise represented contextually.

[0068] In the present disclosure, information about an NFT can be a set of data including a plurality of data. Information about an NFT can include at least one of NFT identification information (NFT ID), information indicating a specific object, event identification information (event ID), an issue number related to the event, information for accessing a digital file connected to the content corresponding to the NFT (digital file URI (uniform resource identifier)), information for accessing the metadata of the NFT (metadata URI), or current owner information of the token (e.g., the wallet address of the holder currently holding the NFT), the holding period of the NFT, the transaction breakdown for the NFT, and the transaction price. Hereinafter, for the convenience of explanation, the present disclosure will be described assuming that the token-related information recorded on the blockchain network 140 includes a digital file URI, a metadata URI, the metadata of the content indicated by the digital file, or the metadata of the token itself, but the content of the present disclosure is not limited thereto.

[0069] The NFT identification information included in the information about the NFT is a unique value assigned to each NFT and can be a value for distinguishing a plurality of NFTs from each other. The NFT identification information can be, for example, a character string such as 0x789456.

[0070] In the present disclosure, an NFT may be related to a specific object (e.g., a receipt). The expression that an NFT is related to a specific object may be an expression indicating the relationship between the NFT and the specific object when the digital file connected to the NFT is the digital file of the specific object. The specific object can include, for example, a receipt for the purchase of a product, a receipt for the purchase of a service. The digital file related to the receipt can be, for example, an image or video of a receipt for the purchase of a product, an image or video of a receipt for the purchase of a service. Or, the digital file related to the receipt can be, for example, an electronic receipt issued by the purchase of a product or service.

[0071] The digital file URI included in the information about the NFT can be the address where the digital file is stored on a distributed file system or the hash value of the stored digital file. The distributed file system can be IPFS (interplanetary file system) that distributes and stores files on multiple devices. The digital file accessible through the digital file URI can be, for example, an image file, a video file, or an audio file. In the present disclosure, the digital file connected to the NFT is an expression referring to the digital file obtained through the digital file URI recorded in the NFT, and can have the same meaning as an expression such as the digital file owned by the NFT or the digital file related to the NFT, unless clearly used differently in the context.

[0072] The metadata URI included in the information about the NFT can be the hash value of the metadata where the metadata of the NFT is stored on a distributed file system. The metadata of the NFT can refer to a data set including various information about the NFT. The metadata can include, for example, at least one of the name of the NFT, the NFT ID, the name of the receipt related to the NFT, the generation time of the NFT, the current owner information of the NFT, the change history of the owner of the NFT, the event-related information corresponding to the NFT, or the digital file URI.

[0073] At least a part of the various information included in the information regarding the NFT may be stored in the memory 220 of the electronic device 200. Also, at least a part of the various information included in the information regarding the NFT may be recorded in one block managed by the blockchain network 140.

[0074] In the present disclosure, the NFT may be processed by a smart contract. In the present disclosure, the expression that the NFT is processed by a smart contract may comprehensively refer to various operations such as the NFT being issued (generated) by the smart contract, the NFT being transmitted from one user's address to another user's address, and the NFT being burned. The smart contract may include various types of functions.

[0075] The smart contract may be created to comply with certain rules (or protocols). For example, a smart contract created to comply with any first rule (e.g., ERC-20) may include a function to return the total supply of virtual currency tokens. A smart contract created to comply with the first rule may include a function to obtain the address on the blockchain of a specific node and return the quantity of virtual currency tokens held by the corresponding address. A smart contract created to comply with the first rule may include a function to obtain the quantity of any virtual currency tokens and the address on the blockchain of the node that receives the virtual currency tokens, and transmit the virtual currency tokens to the receiving node's address. A smart contract created to comply with the first rule may include a function to obtain the quantity of any virtual currency tokens, the address on the blockchain of the node that sends the virtual currency tokens, and the address on the blockchain of the node that receives the virtual currency tokens, and transmit the virtual currency tokens from the sending node's address to the receiving node's address. A smart contract created to comply with the first rule may include a function to return whether a withdrawal is allowed in order to limit the quantity of withdrawable virtual currency tokens. Also, a smart contract created to comply with the first rule may include a function to return the remaining withdrawable quantity.

[0076] A smart contract created to comply with any second convention (e.g., ERC - 721) can include a function (i.e., NFT generation function) that generates an NFT based on one or more pieces of information received from a specific node. For example, the NFT generation function can obtain the URI of a specific digital file received from a specific node and the address on the blockchain of any node, and generate a token corresponding to the URI of the corresponding digital file. When an NFT is generated (issued) by the NFT generation function, the holder information of the corresponding NFT can be determined by the address on the blockchain of any node input into the NFT generation function. The NFT generation function can additionally obtain one or more pieces of information included in the NFT metadata (e.g., the name of the NFT, attributes regarding the NFT) and generate the NFT. In the present disclosure, the expressions "issuance of NFT" or "generation of NFT" can be used interchangeably with the expression "minting of NFT". Also, a smart contract created to comply with the second convention can include a function that obtains the address on the blockchain of any node and returns the quantity of tokens held by the corresponding address. A smart contract created to comply with the second convention can include a function that obtains the NFT ID of any NFT and returns the holder information holding the corresponding NFT. A smart contract created to comply with the second convention can include a function that obtains the address on the blockchain of any node and the NFT ID of any NFT and allows the corresponding node to have the transmission right of the NFT having the corresponding NFT ID. A smart contract created to comply with the second convention can include a function that obtains the NFT ID of any NFT and returns the addresses on the blockchain of one or more nodes having the transmission right of the corresponding NFT.

[0077] The description regarding the smart contract created in accordance with the above-mentioned First Convention and Second Convention is merely for exemplarily explaining the functions included in the smart contract, and does not limit the present disclosure. The smart contract according to the present disclosure can include various types of smart contracts including at least one function related to NFT.

[0078] FIG. 4 is a flowchart of an electronic device 200 showing a process of processing an NFT related to a receipt for purchasing a product according to an embodiment of the present disclosure. A processor 210 of the electronic device 200 connected to a computer network 130 including a blockchain network 140 can execute a smart contract for processing the NFT related to the receipt. Each node included in the above-mentioned server 110, terminal 120, and blockchain network 140 can be implemented by the electronic device 200. The processor 210 of the electronic device 200 can transmit a transaction to the blockchain network 140 in order to process the NFT related to the receipt. In this case, a smart contract distributed to the blockchain network 140 through a virtual machine (e.g., EVM) can be executed. The smart contract can include one or more instructions. That is, the processor 210 of the electronic device 200 can perform one or more instructions included in the smart contract by executing the smart contract for processing the NFT related to the receipt through the virtual machine. When the one or more instructions are executed, the processor 210 of the electronic device 200 can be configured to perform specific operations corresponding to the one or more instructions. The flowchart illustrated in FIG. 4 is a drawing illustrating operations corresponding to one or more instructions included in the smart contract when the processor 210 of the electronic device 200 executes the smart contract through the virtual machine. That is, in FIG. 4, a series of operations performed by the processor 210 of the electronic device 200 can be performed through the virtual machine.

[0079] Referring to flowchart 400, in step 410, the processor 210 of the electronic device 200 according to one embodiment can identify a digital file related to a receipt for a purchase of a product and a request for issuing an NFT related to the receipt. That is, the smart contract can include instructions for identifying a digital file related to a receipt for a purchase of a product and a request for issuing an NFT related to the receipt. The processor 210 of the electronic device 200 can transmit a request for issuing an NFT related to the receipt together with a digital file related to the receipt for the purchase of the product to the blockchain network 140. The digital file related to the receipt for the purchase of the product may be, for example, an image of the obtained receipt by photographing the receipt issued at the time of product purchase, or a receipt file issued in electronic form. According to various embodiments, the digital file transmitted together with the request for issuing the NFT may further include a digital file not related to the receipt. For example, an image file or a video file photographed at the time of purchase of the product regarding the product may also be transmitted to the blockchain network 140 together with the request for issuing the NFT. The processor 210 of the electronic device 200 can identify a digital file related to a receipt for a purchase of a product and a request for issuing an NFT related to the receipt.

[0080] Assume a case where a request for issuing an NFT related to a receipt is requested using the terminal 120 for explanation. After purchasing a product, the user can obtain a digital file related to the receipt (e.g., an image or video of the photographed receipt) by photographing the receipt for the purchase of the product using the terminal 120. The terminal 120 can transmit a digital file related to the receipt for the purchase of the product and a request for issuing an NFT related to the receipt to the blockchain network 140. The terminal 120 can identify a digital file related to the receipt for the purchase of the product and a request for issuing an NFT related to the receipt through a virtual machine.

[0081] This time, assuming a case where a server 110 that implements a platform for managing NFTs related to receipts is used to request the issuance of NFTs related to receipts, an explanation will be given. After purchasing a product, the user can obtain a digital file related to the receipt by photographing the receipt related to the purchase of the product using the terminal 120. The user can upload (transmit) the digital file related to the receipt to the platform. The server 110 can obtain the digital file related to the receipt. The server 110 can transmit the digital file related to the receipt related to the purchase of the product and the request for the issuance of NFTs related to the receipt to the blockchain network 140. The server 110 can identify the digital file related to the receipt related to the purchase of the product and the request for the issuance of NFTs related to the receipt through a virtual machine.

[0082] The request for the issuance of NFTs related to receipts can also be made by a platform for managing product evaluation information (e.g., review information) or a token developer, in addition to the platform for managing NFTs. For example, a server that implements a platform for managing product evaluation information can also transmit the digital file related to the receipt related to the purchase of the product and the request for the issuance of NFTs related to the receipt to the blockchain network 140. Another example is that the server of the token developer can also transmit the digital file related to the receipt related to the purchase of the product and the request for the issuance of NFTs related to the receipt to the blockchain network 140. That is, as described above, the entity that transmits the request for the issuance of NFTs related to receipts can be one of the user's terminal 120, the server 110 that implements a platform for managing NFTs, the server that implements a platform for managing product evaluation information, or the server of the token developer.

[0083] In one embodiment, the processor 210 of the electronic device 200 can issue an NFT related to a receipt at step 420. The processor 210 can issue an NFT related to a receipt as a response to the issuance request identified at step 410. That is, the smart contract can include instructions to issue an NFT related to a receipt as a response to the identified issuance request. The address (e.g., URI) where the digital file related to the receipt is stored on the distributed file system by the processor 210 can be recorded in one or more blocks on the blockchain network 140. The processor 210 can issue an NFT related to the receipt by recording the address where the digital file related to the receipt is stored on the distributed file system in one or more blocks on the blockchain network 140. Alternatively, the address where the digital file related to the receipt is stored on the distributed file system by the processor 210 can be recorded in the metadata of the NFT related to the receipt. That is, the smart contract can include instructions to store the digital file related to the receipt in the distributed file system as a response to the identified issuance request. The smart contract can include instructions to issue an NFT related to the receipt by recording the address where the digital file related to the receipt is stored on the distributed file system in one or more blocks on the blockchain network 140. The processor 210 of the electronic device 200 can verify the metadata of the NFT stored in the blockchain-based distributed file system through the IPFS protocol. The metadata of the NFT can include information generated as a specific format at the time of minting the NFT. The processor 210 of the electronic device 200 can record the wallet address of the first account corresponding to the purchaser who purchased the product in the metadata of the NFT related to the issued receipt. That is, the smart contract can include instructions to record the wallet address of the first account corresponding to the purchaser who purchased the product in the metadata of the NFT related to the receipt.

[0084] On the other hand, different from what is shown in FIG. 4, before performing step 420, the processor 210 of the electronic device 200 can verify (confirm) whether the purchaser who purchased the product has transmitted a request for issuing an NFT related to the receipt. The smart contract can include instructions for verifying whether the creator who created the evaluation information related to the product is the holder of the NFT related to the receipt. That is, the processor 210 can verify whether the requester who transmitted the request for issuing the NFT related to the receipt is the actual purchaser who purchased the product.

[0085] According to one embodiment for performing the above verification, the server 110 can confirm whether the applicant is the purchaser of the product and provide the confirmed result on the blockchain network 140. The server 110 operating a platform for managing NFTs related to receipts can obtain the wallet address of the first account corresponding to the purchaser who purchased the product from the purchaser's terminal 120. That is, the server 110 can obtain the wallet address of the first account, which is the purchaser's account, while obtaining the digital file related to the receipt from the purchaser's terminal 120. The identification information of the applicant (e.g., the wallet address corresponding to the applicant's account, personal information) can be obtained at the time of joining the platform and stored in the server 110. The server 110 can verify whether the applicant who transmitted the issuance request for the NFT is the purchaser who purchased the product based on the wallet address. Specifically, the server 110 can verify whether the applicant is the actual purchaser of the product by comparing the wallet address of the account corresponding to the applicant who transmitted the issuance request for the NFT with the wallet address of the first account corresponding to the purchaser. Alternatively, the server 110 can extract the settlement information recorded in the receipt from the digital file related to the receipt and obtain the identification information of the settler (e.g., the wallet address corresponding to the settler's account, personal information) from the card company's server based on the settlement information recorded in the receipt. The server 110 can verify whether the applicant is the actual purchaser of the product by comparing the identification information of the settler with the identification information of the applicant. Through the above-described method, when it is verified that the applicant is the purchaser who purchased the product, the server 110 can provide an identifier to the blockchain network 140. The identifier can be, for example, information indicating that the applicant who transmitted the issuance request for the NFT is the purchaser who purchased the product.

[0086] According to still other embodiments for verifying whether the requester who transmitted the NFT issuance request related to the receipt is the actual purchaser of the product, on the blockchain network 140, it is also possible to confirm whether the requester is the purchaser of the product. The server of the credit card company can record the receipt or payment information related to the purchase of the product in one block of the blockchain network 140. Through this, the electronic device 200 corresponding to one node included in the blockchain network 140 can, through the virtual machine, confirm the receipt or payment information recorded in one block and obtain the identification information of the purchaser corresponding to the receipt or payment information. The electronic device 200 can verify whether the requester is the actual purchaser of the product by comparing the identification information of the purchaser with the identification information of the requester who transmitted the NFT issuance request.

[0087] The processor 210 of the electronic device 200 according to an embodiment can identify evaluation information regarding a product at stage 430. Specifically, the smart contract can include instructions for identifying evaluation information regarding a product. The processor 210 of the electronic device 200 according to an embodiment can record the evaluation information regarding the product in the metadata of the NFT associated with the receipt when the creator who created the evaluation information regarding the product is the purchaser who purchased the product at stage 440. Specifically, the smart contract can include instructions for recording the evaluation information regarding the product in the metadata of the NFT associated with the receipt when the creator who created the evaluation information regarding the product is the purchaser who purchased the product. The processor 210 can transmit the evaluation information regarding the product to the blockchain network 140. The processor 210 can identify the evaluation information regarding the product. The processor 210 can verify (confirm) whether the creator who created the evaluation information regarding the product through the virtual machine is the purchaser (actual purchaser) who purchased the product. The specific verification method will be described later with reference to FIG. 5. The evaluation information regarding the product can include at least one of the name of the product, identification information regarding the product, an image of the product, a video of the product, or a review of the product.

[0088] It is assumed that the creator who created the evaluation information regarding the product is the purchaser who purchased the product. That is, it is assumed that the actual purchaser of the product creates the evaluation information regarding the product. In the above case, the purchaser who purchased the product can create the evaluation information regarding the product using the terminal 120, and the terminal 120 can transmit the evaluation information regarding the product to the blockchain network 140. Or, the purchaser who purchased the product can create the evaluation information regarding the product using the terminal 120 and transmit the evaluation information regarding the product created to the platform that manages the NFT related to the receipt. In this case, the server 110 operating the platform can transmit the evaluation information regarding the product to the blockchain network 140. The processor 210 can confirm (verify) whether the creator who created the evaluation information regarding the product through the virtual machine is the holder of the NFT related to the receipt. If the creator is the holder of the NFT, the processor 210 of the electronic device 200 can record the evaluation information regarding the product in the metadata of the NFT related to the receipt. In the above case, since the creator is the holder of the NFT related to the receipt, the creator is the purchaser who purchased the product. Therefore, in the above case, the processor 210 can record the evaluation information regarding the product in the metadata of the NFT related to the receipt.

[0089] According to one embodiment for checking whether the creator who created the evaluation information about the product is the holder of the NFT related to the receipt, the server 110 can check whether the creator is the holder of the NFT related to the receipt. The server 110 operating the platform for managing the NFT related to the receipt can receive and store the identification information of the holder who holds the NFT related to the receipt (e.g., the personal information of the holder, the wallet address of the account corresponding to the holder) from the terminal 120 at the time of NFT issuance. The server 110 can receive the identification information of the creator who created the evaluation information about the product (e.g., the personal information of the creator, the wallet address of the account corresponding to the creator) from the terminal 120. The server 110 can check whether the creator who created the evaluation information about the product is the holder of the NFT related to the receipt by comparing the identification information of the creator with the identification information of the holder.

[0090] According to still another embodiment, it is assumed and explained that the creator who created the evaluation information about the product is not the purchaser who purchased the product. That is, it may be the case where a person who is not the actual purchaser of the product creates the evaluation information about the product. In the above case, a person who is not the purchaser can use the terminal 120 to create the evaluation information about the product, and the terminal 120 can transmit the evaluation information about the product to the blockchain network 140. The processor 210 can check (verify) whether the creator who created the evaluation information about the product through the virtual machine is the holder of the NFT related to the receipt. In the above case, since the creator is not the holder of the NFT related to the receipt, the creator is not the purchaser who purchased the product. Therefore, in the above case, the processor 210 can decide not to record the evaluation information about the product in the metadata of the NFT related to the receipt.

[0091] According to the method described above, at the request of the purchaser who has purchased the product, an NFT related to the receipt for the purchase of the product can be issued, and the evaluation information regarding the product created by the purchaser can be recorded in the metadata of the NFT related to the receipt. When a person who has not purchased the product requests the issuance of an NFT related to the receipt, the NFT related to the receipt is not issued, and the evaluation information regarding the product created by the person who has not purchased the product is not recorded in the NFT related to the receipt.

[0092] FIG. 5 is a flowchart of an electronic device 200 showing a process of recording evaluation information regarding a product in metadata of an NFT related to a receipt according to an embodiment of the present disclosure. Specifically, FIG. 5 is a flowchart regarding a method for verifying whether the creator who created the evaluation information regarding the product is the purchaser who has purchased the product. The operations illustrated in this drawing may be operations corresponding to one or more instructions included in a smart contract distributed on the blockchain network 140. That is, the flowchart illustrated in FIG. 5 is a drawing illustrating operations corresponding to one or more instructions included in a smart contract when the processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). In FIG. 5, a series of operations performed by the processor 210 of the electronic device 200 may be performed through a virtual machine.

[0093] Referring to flowchart 500, in step 510, the processor 210 of the electronic device 200 according to an embodiment can identify information of the creator who created the evaluation information regarding the product. The creator's information can include, for example, the wallet address of the creator's account and personal information. The processor 210 can identify the wallet address of the creator's account or the personal information of the creator transmitted from the server 110 or the terminal 120. That is, the smart contract can include instructions for identifying the wallet address of the creator's account.

[0094] In step 520, the processor 210 of the electronic device 200 according to one embodiment can check whether the creator who created the evaluation information regarding the product is the holder of the NFT associated with the receipt. The processor 210 can compare the wallet address of the account corresponding to the creator with the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network 140. Alternatively, the wallet address of the first account corresponding to the holder of the NFT associated with the receipt may be recorded in the metadata of the NFT associated with the receipt. The processor 210 can check whether the wallet address of the account corresponding to the creator who created the evaluation information is the same as the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network 140. That is, the smart contract can further include an instruction to check whether the creator who created the evaluation information regarding the product is the holder of the NFT associated with the receipt based on the wallet address of the creator's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network 140.

[0095] According to yet another embodiment, the processor 210 can check whether the creator who created the evaluation information regarding the product is the holder of the NFT associated with the receipt, using the identification information of the creator. The identification information of the creator who created the evaluation information regarding the product can be transmitted from the server 110 or the terminal 120 to the blockchain network 140. The processor 210 can check the identification information of the creator who created the evaluation information regarding the product. Identification information regarding the holder can be recorded in the metadata of the NFT associated with the receipt or in one or more blocks of the blockchain network 140. For example, the metadata of the NFT associated with the receipt can record identification information regarding the holder (e.g., account information corresponding to the holder). That is, the smart contract can include instructions to obtain the identification information regarding the creator who created the evaluation information regarding the product. The processor 210 can check whether the creator is the holder of the NFT associated with the receipt by comparing the identification information of the creator with the identification information of the holder of the NFT recorded in one or more blocks of the blockchain network 140. That is, the smart contract can include instructions to verify whether the creator is the purchaser who purchased the product based on the identification information regarding the creator who created the evaluation information regarding the product.

[0096] If the creator who created the evaluation information about the product is the holder of the NFT related to the receipt, branching to step 530 (step 520 - yes), the processor 210 can determine that the creator is the purchaser who purchased the product. That is, the smart contract can include instructions to determine that the creator is the purchaser who purchased the product if the creator is the holder of the NFT related to the receipt. According to one embodiment, the processor 210 of the electronic device 200 can record the evaluation information about the product in the metadata of the NFT related to the receipt at step 540. According to one embodiment, the evaluation information about the product can be stored in a distributed file system, and the address where the evaluation information about the product is stored on the distributed file system can be recorded in the metadata of the NFT related to the receipt. That is, the smart contract can include instructions to store the evaluation information about the product in a distributed file system in response to the creator being the purchaser who purchased the product. The smart contract can include instructions to record the address where the evaluation information about the product is stored on the distributed file system in the metadata of the NFT related to the receipt. The metadata of the NFT related to the receipt can include at least one of, for example, detailed information about the product, evaluation information, creator information who created the evaluation information, or creation date and time information. The evaluation information about the product can include at least one of, for example, the name of the product, identification information related to the product, an image, a video, or a review.

[0097] If the creator who created the evaluation information about the product is not the holder of the NFT related to the receipt, branching to step 550 (step 520 - no), the processor 210 can determine that the creator is not the purchaser who purchased the product. The processor 210 according to one embodiment can determine not to record the evaluation information about the product in the metadata of the NFT related to the receipt at step 560. That is, the smart contract can include instructions not to record the evaluation information about the product in the metadata of the NFT related to the receipt if the purchaser who purchased the product that created the evaluation information about the product is not the case.

[0098] According to the method described above, evaluation information regarding a product created by a person who is not the actual purchaser of the product cannot be recorded in the metadata of the NFT (or one block of the blockchain network 140). That is, according to the method described above, only the purchaser who has purchased the product can record the evaluation information of the product in the metadata of the NFT associated with the receipt for the purchase of the product, so that transparent and accurate management of the evaluation information can be performed.

[0099] FIG. 6 is a flowchart of an electronic device 200 showing a process of changing the holder of an NFT associated with a receipt according to an embodiment of the present disclosure. Specifically, FIG. 6 is a flowchart regarding a method of changing the holder of an NFT associated with a receipt. The operations illustrated in this drawing may be operations corresponding to one or more instructions included in a smart contract distributed on the blockchain network 140. That is, the flowchart illustrated in FIG. 6 is a drawing illustrating operations corresponding to one or more instructions included in the smart contract when the processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). In FIG. 6, a series of operations performed by the processor 210 of the electronic device 200 may be performed through the virtual machine.

[0100] In the case of second-hand transactions, purchasing agency services, and e-commerce services, instead of purchasing a product directly from the official seller of the product, the product can be repurchased from the purchaser of the product. For example, after the first customer purchases a product from the official seller, the first customer can resell the product to the second customer. For example, on a purchasing agency platform, after purchasing a product from the official seller, the product can be sold to the second customer. In this case, a problem may occur in that it is difficult for the repurchaser (e.g., the second customer) who has repurchased the product to confirm whether the repurchased product is genuine or fake.

[0101] According to one embodiment of the present disclosure, by minting a receipt related to the purchase of a product, an NFT related to the receipt can be issued, and detailed information about the product or information about the purchaser of the product can be recorded in the metadata of the NFT related to the receipt. Therefore, a repurchaser who repurchases the corresponding product can confirm whether the corresponding product is genuine through the NFT related to the receipt, and can also receive (or purchase) the NFT related to the receipt together with the product.

[0102] According to one embodiment of the present disclosure, a distributed file system can store not only digital files related to receipts but also digital files not related to receipts. For example, regarding a product, an image file or a video file taken at the time of purchase of the product can also be stored in the distributed file system, and the address where the image file or the video file is stored on the distributed file system can be recorded in one or more blocks on the blockchain network 140. The image file or the video file may include information about the purchaser of the product (e.g., the first customer). In this case, a repurchaser (e.g., the second customer) who repurchases the corresponding product can confirm the purchaser (e.g., the first customer) who purchased the corresponding product through the NFT related to the receipt. In one embodiment, if the first customer is a famous person such as a singer or an actor, it can be proved through the NFT that the corresponding product was used by the famous person in the past, and the value of the corresponding product can be further highly evaluated.

[0103] Referring to flowchart 600, in step 610, the processor 210 of the electronic device 200 according to one embodiment can identify a change request asking to change the holder of the NFT related to the receipt from the first account to the second account. For example, the first account can be an account corresponding to the purchaser who first purchased the product (hereinafter referred to as the first purchaser), and the second account can be an account of the repurchaser who repurchased the product from the first purchaser. For example, when the product is sold from the first purchaser to the repurchaser, the server 110 operating the platform for managing the NFT related to the receipt can transmit a change request asking to change the holder of the NFT related to the receipt from the first account corresponding to the first purchaser to the second account corresponding to the repurchaser to the blockchain network 140. That is, the smart contract can include instructions for identifying a change request asking to change the holder of the NFT related to the receipt from the first account to the second account.

[0104] In step 620, the processor 210 of the electronic device 200 according to one embodiment can verify whether the second account is an account of the repurchaser who repurchased the product from the purchaser. The server 110 operating the platform can transmit identification information about the repurchaser who repurchased the product to the blockchain network 140. The identification information about the repurchaser can include, for example, the wallet address of the second account corresponding to the repurchaser. That is, the smart contract can include instructions for verifying whether the second account is an account of the repurchaser who repurchased the product from the purchaser.

[0105] In step 630, the processor 210 of the electronic device 200 according to one embodiment can record the wallet address of the second account in the metadata of the NFT related to the receipt in response to the second account being the account of the repurchaser. The processor 210 can change the holder of the NFT related to the receipt from the first account to the second account and record the wallet address of the second account in the metadata of the NFT related to the receipt. That is, the smart contract can include instructions to record the wallet address of the second account in the metadata of the NFT related to the receipt in response to the second account being the account of the repurchaser.

[0106] Through the method described above, since it is possible to confirm who sold the product to whom through the NFT related to the receipt, the information regarding the product can be managed transparently and fairly.

[0107] FIG. 7 is a flowchart of the electronic device 200 showing the process of associating the NFT related to the receipt with the NFT related to the additional receipt according to an embodiment of the present disclosure. Specifically, FIG. 7 is a flowchart regarding a method of issuing an NFT related to an additional receipt related to the repurchase of a product, and can be a flowchart regarding operations additionally performed after the flowchart illustrated in FIG. 6.

[0108] The operations illustrated in this drawing can be operations corresponding to one or more instructions included in a smart contract distributed on the blockchain network 140. That is, the flowchart illustrated in FIG. 6 is a drawing illustrating operations corresponding to one or more instructions included in a smart contract when the processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). In FIG. 7, a series of operations performed by the processor 210 of the electronic device 200 can be performed through the virtual machine.

[0109] Referring to flowchart 700, in step 710, the processor 210 of the electronic device 200 according to one embodiment can identify a digital file related to an additional receipt related to the repurchase of a product and a request for issuance of an NFT related to the additional receipt. When the product is sold from the first purchaser to the repurchaser, the repurchaser can receive an additional receipt for the repurchase of the product. For example, if the first purchaser of the product is a purchasing agency platform, an additional receipt can be issued to the repurchaser who repurchased the product. The processor 210 can transmit the request for issuance of the NFT related to the additional receipt while transmitting the digital file related to the additional receipt related to the repurchase of the product to the blockchain network 140. The digital file related to the receipt related to the repurchase of the product may be, for example, an image of the received receipt by photographing the receipt issued at the time of the repurchase of the product, or a receipt file issued in an electronic form. The processor 210 can identify a digital file related to an additional receipt related to the repurchase of the product and a request for issuance of an NFT related to the additional receipt. That is, the smart contract can include instructions for identifying a digital file related to an additional receipt related to the repurchase of the product and a request for issuance of an NFT related to the additional receipt.

[0110] In one embodiment, the processor 210 of the electronic device 200 can issue an NFT related to an additional receipt as a response to a request for issuance of the NFT related to the additional receipt at step 720. The processor 210 can issue an NFT related to an additional receipt as a response to the identified request for issuance at step 710. The address (e.g., URI) where the digital file related to the additional receipt is stored by the processor 210 on the distributed file system can be recorded in one or more blocks on the blockchain network 140. That is, the processor 210 can issue an NFT related to the additional receipt by recording the address where the digital file related to the additional receipt is stored on the distributed file system in one or more blocks on the blockchain network 140. Alternatively, the address where the digital file related to the additional receipt is stored by the processor 210 on the distributed file system can be recorded in the metadata of the NFT related to the additional receipt. That is, the smart contract can include instructions to issue an NFT related to the additional receipt as a response to a request for issuance of the NFT related to the additional receipt.

[0111] In one embodiment, the processor 210 of the electronic device 200 can associate the NFT related to the receipt and the NFT related to the additional receipt with each other at step 730. The processor 210 can associate the NFT related to the receipt and the NFT related to the additional receipt with each other in order to verify that the NFT related to the receipt and the NFT related to the additional receipt are NFTs regarding the same product. That is, the smart contract can include instructions for associating the NFT related to the receipt and the NFT related to the additional receipt with each other. For example, the processor 210 can record information regarding the NFT related to the receipt in the metadata of the NFT related to the additional receipt. For example, the processor 210 can record information regarding the NFT related to the additional receipt in the metadata of the NFT related to the receipt. That is, the smart contract can include instructions for recording information regarding the NFT related to the receipt in the metadata of the NFT related to the additional receipt.

[0112] According to one embodiment, the processor 210 can also synthesize the NFT related to the receipt and the NFT related to the additional receipt. For example, the processor 210 can generate a new third NFT by synthesizing the NFT related to the receipt and the NFT related to the additional receipt. In the above case, the NFT related to the receipt and the NFT related to the additional receipt are set so as not to be traded any more, and only the synthesized third NFT can be the object of trading. Information regarding the NFT related to the receipt and information regarding the NFT related to the additional receipt may be recorded in the metadata of the third NFT. In the above case, the NFT related to the receipt and the NFT related to the additional receipt may be deleted, and only the synthesized third NFT may exist. That is, the smart contract can include instructions for synthesizing the NFT related to the receipt and the NFT related to the additional receipt.

[0113] FIG. 8 is a flowchart of an electronic device 200 showing a process of processing an NFT related to a receipt for purchasing a service according to an embodiment of the present disclosure. Specifically, FIG. 8 is a flowchart regarding a method of issuing an NFT related to a receipt using a digital file related to a receipt for purchasing a service and recording evaluation information regarding the service in the metadata of the NFT. The operations illustrated in this drawing may be operations corresponding to one or more instructions included in a smart contract distributed on the blockchain network 140. That is, the flowchart illustrated in FIG. 8 is a drawing illustrating operations corresponding to one or more instructions included in a smart contract when a processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). In FIG. 8, a series of operations performed by the processor 210 of the electronic device 200 may be performed through a virtual machine. Regarding the content overlapping with that already described in FIGS. 4 and 5, additional explanation will be omitted. The service described in the present disclosure may be a concept including services provided in various fields such as the food and beverage industry, the accommodation industry, the transportation industry, and the tourism industry.

[0114] Referring to flowchart 800, in step 810, the processor 210 of the electronic device 200 according to one embodiment can identify a digital file related to a receipt related to the purchase of a service and a request for issuing an NFT related to the receipt. The processor 210 can transmit the digital file related to the receipt related to the purchase of the service to the blockchain network 140 while also transmitting the request for issuing the NFT related to the receipt. For example, by photographing a receipt issued when a customer visits a restaurant and purchases a dining service using the terminal 120, a digital file related to the receipt related to the purchase of the service can be obtained. The terminal 120 can transmit the digital file related to the receipt related to the purchase of the product and the request for issuing the NFT related to the receipt to the blockchain network 140. The terminal 120 can identify the digital file related to the receipt related to the purchase of the service and the request for issuing the NFT related to the receipt through a virtual machine. That is, the smart contract can include instructions for identifying the digital file related to the receipt related to the purchase of the service and the request for issuing the NFT related to the receipt.

[0115] In one embodiment, the processor 210 of the electronic device 200 can issue an NFT related to a receipt at stage 820. That is, the smart contract can include instructions to issue an NFT related to a receipt in response to an identified issuance request. The address (e.g., URI) where the digital file related to the receipt is stored on the distributed file system by the processor 210 can be recorded in one or more blocks on the blockchain network 140. That is, the processor 210 can issue an NFT related to the receipt by recording the address where the digital file related to the receipt is stored on the distributed file system in one or more blocks on the blockchain network 140. Alternatively, the address where the digital file related to the receipt is stored on the distributed file system by the processor 210 can be recorded in the metadata of the NFT related to the receipt. The processor can record the wallet address of the first account corresponding to the purchaser who purchased the service in the metadata of the NFT related to the receipt.

[0116] In one embodiment, the processor 210 of the electronic device 200 can identify evaluation information related to a service at stage 830. The evaluation information related to the service can include, for example, at least one of the store name that provided the service, the fee related to the service, an image, a video, or a review. That is, the smart contract can include instructions to identify evaluation information related to the service.

[0117] In step 840, the processor 210 of the electronic device 200 according to one embodiment can verify whether the creator who created the evaluation information related to the service is the purchaser who purchased the service. For example, the processor 210 can compare the wallet address of the account corresponding to the creator who created the evaluation information with the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network 140. Alternatively, the wallet address of the first account corresponding to the holder of the NFT related to the receipt may be recorded in the metadata of the NFT related to the receipt. The processor 210 can check whether the wallet address of the account corresponding to the creator who created the evaluation information is the same as the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network 140. That is, the smart contract can include instructions for verifying whether the creator who created the evaluation information related to the service is the purchaser who purchased the service by verifying whether the creator who created the evaluation information related to the service is the holder of the NFT related to the receipt.

[0118] In step 850, when the creator is the purchaser who purchased the service, the processor 210 of the electronic device 200 according to one embodiment can record the evaluation information related to the service in the metadata of the NFT related to the receipt. The metadata of the NFT related to the receipt can include, for example, at least one of detailed information about the service, evaluation information, creator information who created the evaluation information, or creation date and time information. That is, the smart contract can include instructions for recording the evaluation information related to the service in the metadata of the NFT related to the receipt when the creator is the purchaser who purchased the service.

[0119] In one embodiment, the processor 210 of the electronic device 200 can provide compensation to a first account corresponding to the purchaser at stage 860. The processor 210 can provide compensation to a first account corresponding to the purchaser in response to recording evaluation information regarding the service in the metadata of the NFT. For example, the processor 210 can provide virtual currency as compensation to the wallet address of the first account corresponding to the purchaser. For example, the processor 210 can provide, as compensation, points that can be used on a platform that manages NFTs related to receipts to the first account corresponding to the purchaser. That is, the smart contract can include instructions to provide compensation to the first account in response to recording evaluation information regarding the service.

[0120] According to the method described above, when a purchaser who has purchased a service records evaluation information regarding the service, it is possible to induce the creation of evaluation information by providing compensation therefor to the purchaser.

[0121] According to one embodiment of the present disclosure, a smart contract for processing an NFT related to a receipt can be distributed to a blockchain network 140. The smart contract can include one or more instructions. Specifically, the smart contract can include instructions for identifying a digital file related to a receipt for the purchase of a product and a request for issuance of an NFT related to the receipt. The smart contract can include instructions for issuing an NFT related to the receipt as a response to the identified request for issuance. The smart contract can include instructions for identifying evaluation information regarding the product. The smart contract can include instructions for recording the evaluation information regarding the product in the metadata of the NFT related to the receipt if the creator who created the evaluation information regarding the product is the purchaser who purchased the product. The smart contract can include instructions for storing the digital file related to the receipt in a distributed file system as a response to the identified request for issuance. The smart contract can include instructions for issuing an NFT related to the receipt by recording the address where the digital file related to the receipt is stored on the distributed file system in one or more blocks on the blockchain network 140.

[0122] The smart contract can include instructions to record, in the metadata of the NFT associated with the receipt, the wallet address of the first account corresponding to the purchaser who purchased the product. The smart contract can include instructions to confirm whether the creator who created the evaluation information regarding the product is the holder of the NFT associated with the receipt. The smart contract can include instructions to determine that the creator is the purchaser who purchased the product if the creator is the holder of the NFT associated with the receipt. The smart contract can include instructions to identify the wallet address of the creator's account. The smart contract can further include instructions to confirm whether the creator who created the evaluation information regarding the product is the holder of the NFT associated with the receipt based on the wallet address of the creator's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network 140. The smart contract can include instructions to store the evaluation information regarding the product in a distributed file system in response to the creator being the purchaser who purchased the product. The smart contract can include instructions to record, in the metadata of the NFT associated with the receipt, the address where the evaluation information regarding the product is stored on the distributed file system.

[0123] A smart contract can include instructions not to record evaluation information about a product in the metadata of an NFT associated with a receipt if the purchaser is not the one who purchased the product for which the evaluation information about the product was created. The smart contract can include instructions to obtain identification information about the creator who created the evaluation information about the product. The smart contract can include instructions to verify whether the creator is the purchaser who purchased the product based on the identification information about the creator who created the evaluation information about the product. The smart contract can include instructions to identify a change request that requests to change the holder of the NFT associated with the receipt from a first account to a second account. The smart contract can include instructions to verify whether the second account is the account of a repurchaser who repurchased the product from the purchaser. The smart contract can include instructions to record the wallet address of the second account in the metadata of the NFT associated with the receipt in response to the second account being the account of the repurchaser. The smart contract can include instructions to identify a digital file related to an additional receipt related to the repurchase of the product and an issuance request for the NFT associated with the additional receipt. The smart contract can include instructions to issue the NFT associated with the additional receipt as a response to the issuance request for the NFT associated with the additional receipt. The smart contract can include instructions to associate the NFT associated with the receipt and the NFT associated with the additional receipt with each other. The smart contract can include instructions to record information about the NFT associated with the receipt in the metadata of the NFT associated with the additional receipt. The smart contract can include instructions to synthesize the NFT associated with the receipt and the NFT associated with the additional receipt.

[0124] A smart contract can include instructions for identifying digital files related to receipts for service purchases and instructions for requesting the issuance of NFTs related to the receipts. The smart contract can include instructions for issuing NFTs related to the receipts in response to the identified issuance requests. The smart contract can include instructions for identifying evaluation information regarding the service. The smart contract can include instructions for verifying whether the creator who created the evaluation information regarding the service is the holder of the NFT related to the receipt, thereby verifying whether the creator who created the evaluation information regarding the service is the purchaser who purchased the service. The smart contract can include instructions for recording the evaluation information regarding the service in the metadata of the NFT related to the receipt if the creator is the purchaser who purchased the service. The smart contract can include instructions for providing compensation to a first account in response to recording the evaluation information regarding the service.

[0125] The electronic device according to the foregoing embodiment may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with an external device, a touch panel, a user interface device such as a key, a button, and the like. A method embodied by a software module or an algorithm may be stored on a computer-readable recording medium as computer-readable code or program instructions executable on the processor. Here, examples of the computer-readable recording medium include a magnetic storage medium (e.g., ROM (read-only memory), RAM (random-access memory), floppy disk, hard disk, etc.) and an optical reading medium (e.g., CD-ROM (compact disc read-only memory), DVD (digital versatile disc), etc.). The computer-readable recording medium may be distributed to a computer system connected to a network, and the computer-readable code may be stored and executed in a distributed manner. The medium may be readable by a computer, stored in a memory, and executed by a processor.

[0126] This embodiment can be shown in a functional block configuration and various processing stages. Such functional blocks can be implemented in various numbers of hardware and / or software configurations that perform specific functions. For example, the embodiment can adopt a direct circuit configuration such as a memory, a processor, a logic, a look-up table, etc., which can execute various functions under the control of one or more microprocessors or other control devices. Just as the components can be executed by software programming or software elements, this embodiment includes various algorithms embodied in a combination of data structures, processes, routines, or other programming configurations, and can be embodied in programming or scripting languages such as C, C++, Java, assembler, etc. The functional aspect can be embodied by an algorithm executed by one or more processors. Also, this embodiment can adopt prior art for electronic environment setting, signal processing, and / or data processing, etc. Terms such as "mechanism", "element", "means", "configuration" can be widely used and are not limited to a mechanical and physical configuration. The above terms can include the meaning of a series of software routines in cooperation with a processor, etc.

[0127] The foregoing embodiments are merely examples, and other embodiments can be implemented within the scope of the claims described below.

Claims

1. In a method for an electronic device to process a non-fungible token (NFT), a processor of the electronic device connected to a computer network including a blockchain network executes a smart contract for processing an NFT related to a receipt, the smart contract includes one or more instructions, the one or more instructions, when executed, cause the processor to identify a digital file related to a receipt for the purchase of a product and a request for issuance of an NFT related to the receipt, issue an NFT related to the receipt as a response to the identified request for issuance, identify evaluation information regarding the product, and record the evaluation information regarding the product in metadata of the NFT related to the receipt if the creator who created the evaluation information regarding the product is the purchaser who purchased the product. A method for processing an NFT configured as such.

2. The one or more instructions, when executed, cause the processor to save the digital file related to the receipt in a distributed file system as a response to the identified request for issuance, and further configured to issue an NFT related to the receipt by recording an address where the digital file related to the receipt is saved on the distributed file system in one or more blocks on the blockchain network. The method for processing an NFT according to Claim 1.

3. The one or more instructions, when executed, cause the processor to further configured to record a wallet address of a first account corresponding to a purchaser who purchased the product in metadata of the NFT related to the receipt. The method for processing an NFT according to Claim 1.

4. The one or more instructions, when executed, cause the processor to confirm whether the creator who created the evaluation information regarding the product is the holder of the NFT related to the receipt, and further configured to determine that the creator is the purchaser who purchased the product if the creator is the holder of the NFT related to the receipt. The method for processing an NFT according to Claim 3.

5. The one or more instructions, when executed, cause the processor to identify the wallet address of the creator's account, further configured to confirm, based on the wallet address of the creator's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks of the blockchain network, whether the creator is the holder of the NFT related to the receipt, the method for processing an NFT according to claim 4. **Claim 6** The one or more instructions, when executed, cause the processor to in response to the creator being the purchaser who purchased the product, store evaluation information about the product in a distributed file system, further configured to record the address where the evaluation information about the product is stored on the distributed file system in the metadata of the NFT related to the receipt, the method for processing an NFT according to claim 4. **Claim 7** The one or more instructions, when executed, cause the processor to if the creator is not the purchaser who purchased the product, further configured not to record the evaluation information about the product in the metadata of the NFT related to the receipt, the method for processing an NFT according to claim 1. **Claim 8** The one or more instructions, when executed, cause the processor to obtain identification information about the creator, further configured to verify, based on the identification information about the creator, whether the creator is the purchaser who purchased the product, the method for processing an NFT according to claim 3. **Claim 9** The one or more instructions, when executed, cause the processor to identify a change request that requests the processor to change the holder of the NFT related to the receipt from the first account to a second account, verify whether the second account is the account of a repurchaser who repurchased the product from the purchaser, further configured to record the wallet address of the second account in the metadata of the NFT related to the receipt in response to the second account being the account of the repurchaser, the method for processing an NFT according to claim 3. **Claim 10** The one or more instructions, when executed, cause the processor to Identify a digital file related to an additional receipt related to the repurchase of the product and a request for issuance of an NFT related to the additional receipt, As a response to the request for issuance of an NFT related to the additional receipt, issue an NFT related to the additional receipt, The method for processing an NFT according to claim 9, further configured to relate the NFT related to the receipt and the NFT related to the additional receipt to each other.

11. When executed, the one or more instructions cause the processor to The method for processing an NFT according to claim 10, further configured to record information about the NFT related to the receipt in the metadata of the NFT related to the additional receipt.

12. When executed, the one or more instructions cause the processor to The method for processing an NFT according to claim 10, further configured to synthesize the NFT related to the receipt and the NFT related to the additional receipt.

13. The metadata of the NFT related to the receipt includes at least one of detailed information about the product, the evaluation information, author information that created the evaluation information, or creation date and time information. The method for processing an NFT according to claim 1.

14. The evaluation information includes at least one of the name of the product, identification information related to the product, an image, a video, or a review. The method for processing an NFT according to claim 1.

15. In a method for an electronic device to process a non-fungible token (NFT), Including the step of a processor connected to a computer network including a blockchain network executing a smart contract for processing an NFT related to a receipt, The smart contract includes one or more instructions, The one or more instructions Identify a digital file related to a receipt related to the purchase of a service and a request for issuance of an NFT related to the receipt, As a response to the identified request for issuance, issue an NFT related to the receipt, Identify evaluation information related to the service, Verify whether the creator who created the evaluation information regarding the service is the holder of the NFT associated with the receipt, thereby verifying whether the creator who created the evaluation information regarding the service is the purchaser who purchased the service. When the creator is the purchaser who purchased the service, record the evaluation information regarding the service in the metadata of the NFT associated with the receipt. A method for processing an NFT, which is configured to provide compensation to a first account corresponding to the purchaser in response to recording the evaluation information regarding the service.

16. The metadata of the NFT associated with the receipt includes at least one of detailed information regarding the service, evaluation information, creator information of the evaluation information, or creation date and time information. The method for processing an NFT according to claim 15, wherein the evaluation information includes at least one of the name of the store that provided the service, the fee regarding the service, an image, a video, or a review.

17. In an electronic device, A communication circuit that communicates with a computer network including a blockchain network; A memory in which a smart contract for processing an NFT associated with a receipt is stored; A processor, and The processor is Configured to execute the smart contract including one or more instructions, By executing the one or more instructions, the processor Identifies a digital file regarding a receipt related to the purchase of a product and a request for issuance of an NFT associated with the receipt; In response to the identified request for issuance, issues the NFT associated with the receipt; Identifies the evaluation information regarding the product; An electronic device configured to record the evaluation information regarding the product in the metadata of the NFT associated with the receipt when the creator who created the evaluation information regarding the product is the purchaser who purchased the product.

Images