Method for processing non-homogenized token, electronic device, and recording medium

Abstract

There is provided a method of processing a non-homogenous token (NFT) by an electronic device, the method comprising executing, by a processor of an electronic device connected to a computer network comprising a blockchain network, a smart contract to process an NFT associated with a receipt, and the smart contract comprising one or more instructions, and the one or more instructions are configured, when executed, to cause the processor to identify a digital file about a receipt related to purchasing a product and an issue request for an NFT associated with the receipt, issue the NFT associated with the receipt, identify evaluation information about the product, and issue the evaluation information about the NFT associated with the receipt. And recording the evaluation information about the product in metadata of the NFT associated with the receipt if the writer of the evaluation information about the product is a purchaser performing the purchase of the product.

Description

[0001] Cross - reference to related applications

[0002] This application claims the benefit of Korean Patent Application No. 10 - 2024 - 0009607, filed with the Korean Intellectual Property Office on January 22, 2024, the disclosure of which is incorporated herein by reference. Technical field

[0003] Exemplary embodiments relate to a technology for processing non - fungible tokens, and more particularly, to a method, an electronic device, and a recording medium for processing non - fungible tokens related to receipts. Background art

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

[0005] At the same time, the development of Internet services such as social network services (SNS) has led to a growing trend for potential purchasers of a specific product or service to identify purchase reviews from previous purchasers of that product or service before making a purchase. Summary of the invention

[0006] One aspect of the present disclosure provides a guarantee of the purchase of a product or service using a non - fungible token (NFT) associated with a receipt related to the purchase of the product or service.

[0007] Another aspect of the present disclosure provides for an actual purchaser of a product or service to record evaluation information (e.g., a review) in the metadata of an NFT associated with a receipt related to the purchase of the product or service.

[0008] The exemplary embodiments are not limited to the above - mentioned technical features, and other technical features can be inferred from the following exemplary embodiments.

[0009] According to one aspect, a method for an electronic device to process a non-fungible token (NFT) is provided. The method includes executing, by a processor of an electronic device connected to a computer network including a blockchain network, a smart contract to process an NFT associated with a receipt. According to an example embodiment, the smart contract may include one or more instructions, and the one or more instructions may be configured to, when executed, cause the processor to: identify a digital file of a receipt related to the purchase of a product and a request for the issuance of an NFT associated with the receipt; in response to the identified issuance request, issue an NFT associated with the receipt; identify evaluation information about the product, and if the writer of the evaluation information about the product is the purchaser who executed the purchase of the product, record the evaluation information about the product in the metadata of the NFT associated with the receipt.

[0010] According to an example embodiment, the one or more instructions may further be configured to, when executed, cause the processor to: store the digital file of the receipt in a distributed file system in response to the identified issuance request, and publish the NFT associated with the receipt by recording the address where the digital file of the receipt is stored in the distributed file system in one or more blocks on the blockchain network.

[0011] According to an example embodiment, the one or more instructions may further be configured to, when executed, cause the processor to record the wallet address of a first account corresponding to the purchaser of the product in the metadata of the NFT associated with the receipt.

[0012] According to an example embodiment, the one or more instructions may further be configured to, when executed, cause the processor to identify whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt, and if the writer is the holder of the NFT associated with the receipt, determine that the writer is the purchaser of the product.

[0013] According to an exemplary embodiment, the one or more instructions are further configured to, when executed, cause the processor to identify the wallet address of the writer's account, and based on the wallet address of the writer's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks on the blockchain network, identify whether the writer is the holder of the NFT associated with the receipt.

[0014] According to an example embodiment, the one or more instructions may further be configured to, when executed, cause the processor to store the evaluation information about the product in a distributed file system in response to the writer being the purchaser of the product, and record the address where the evaluation information about the product is stored in the distributed file system in the metadata of the NFT associated with the receipt.

[0015] According to an example embodiment, the one or more instructions may also be configured to, when executed, cause the processor not to record evaluation information about a product in the metadata of an NFT associated with a receipt if the writer is not the purchaser of the product.

[0016] According to an example embodiment, the one or more instructions may also be configured to, when executed, cause the processor to obtain identification information about the writer and, based on the identification information about the writer, verify whether the writer is the purchaser of the product.

[0017] According to an example embodiment, the one or more instructions may also be configured to, when executed, cause the processor to: identify a change request for changing the holder of an NFT associated with a receipt from a first account to a second account; verify whether the second account is an account of a repurchaser who repurchases the product from the purchaser; and in response to the second account being an account of the repurchaser, record the wallet address of the second account in the metadata of the NFT associated with the receipt.

[0018] According to an exemplary embodiment, the one or more instructions may also be configured to, when executed, cause the processor to: identify a digital file of an additional receipt related to the repurchase of a product and a request for issuing an NFT associated with the additional receipt; in response to the request for issuing an NFT associated with the additional receipt, issue the NFT associated with the additional receipt; and associate the NFT associated with the receipt and the NFT associated with the additional receipt with each other.

[0019] According to an exemplary embodiment, the one or more instructions may also be configured to, when executed, cause the processor to record information about the NFT associated with the receipt in the metadata of the NFT associated with the additional receipt.

[0020] According to an exemplary embodiment, the one or more instructions may also be configured to, when executed, cause the processor to combine the NFT associated with the receipt and the NFT associated with the additional receipt.

[0021] According to an exemplary embodiment, the metadata of the NFT associated with the receipt may include at least one of detailed information about the product, evaluation information, information about the writer of the evaluation information, and information about the writing date and time.

[0022] According to an example embodiment, the evaluation information may include at least one of the name of the product, identification information, an image, a video, and a comment about the product.

[0023] According to another aspect, a method for an electronic device to process an NFT is provided. The method includes executing a smart contract by a processor connected to a computer network including a blockchain network to process the NFT associated with a receipt. According to an example embodiment, the smart contract may include one or more instructions, and the one or more instructions may be configured to: identify a digital file of a receipt related to a purchased service and a request for issuing an NFT associated with the receipt; in response to the identified issuing request, issue the NFT associated with the receipt; identify evaluation information about the service; verify whether the writer of the evaluation information about the service is the purchaser of the service by verifying whether the writer of the evaluation information about the service is the holder of the NFT associated with the receipt; if the writer is the purchaser of the service, record the evaluation information about the service in the metadata of the NFT associated with the receipt; and in response to recording the evaluation information about the service, provide a reward to a first account corresponding to the purchaser.

[0024] According to an example embodiment, the metadata of the NFT associated with the receipt may include at least one of detailed information about the service, evaluation information, information about the writer of the evaluation information, and information about the writing date and time, and the evaluation information may include at least one of the name of the store providing the service, the fee, an image, a video, and a comment about the service.

[0025] According to another aspect, an electronic device is provided, including: a communication circuit configured to perform communication 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; and a processor. According to an example embodiment, the processor may be configured to execute the smart contract including one or more instructions, and the processor may be configured to perform, by executing the one or more instructions: identify a digital file of a receipt related to a purchased product and a request for issuing an NFT associated with the receipt; in response to the identified issuing request, issue the NFT associated with the receipt; identify evaluation information about the product, and if the writer of the evaluation information about the product is the purchaser who executed the purchase of the product, record the evaluation information about the product in the metadata of the NFT associated with the receipt.

[0026] Additional aspects of the example embodiments will be partially set forth in the following description and will be partially apparent from the description.

[0027] According to an example embodiment, it is possible to technically guarantee the purchase of a product or service using an NFT associated with a receipt related to the purchase of the product or service. More specifically, it is possible to technically guarantee whether a product or service is purchased by a specific user.

[0028] According to an example embodiment, evaluation information (e.g., reviews) can be recorded by an actual purchaser of a product or service in the metadata of an NFT associated with a receipt related to the purchase of the product or service. By this, it can be technically ensured that the evaluation information about the product or service is written by the actual purchaser, and an intended purchaser of the product or service can trust the evaluation information of the actual purchaser before purchase.

[0029] According to an example embodiment, the authenticity of a product can be technically ensured during a secondary transaction of the product through evaluation information or purchase history from a previous owner, and the product value can be preserved or enhanced.

[0030] The technical benefits achieved by the example embodiments are not limited to those described above, and other technical benefits can be clearly understood by those skilled in the art from the appended claims.

[0031] The descriptions in this application should not be construed as implying that any particular element, step, or function is an essential element that must be included in the scope of the claims. The scope of the subject matter for which patent protection is sought is defined only by the claims. Additionally, unless the exact phrase "means for" is followed by a participle, none of the claims are intended to invoke 35 U.S.C. § 112(f). The use of any other term within the claims, including but not limited to "mechanism", "module", "device", "unit", "component", "element", "member", "apparatus", "machine", "system", "processor", or "controller", is understood by the applicant to refer to a structure known to those skilled in the relevant art and is not intended to invoke 35 U.S.C. § 112(f). BRIEF DESCRIPTION OF THE DRAWINGS

[0032] These and / or other aspects, features, and advantages of the present disclosure will become apparent and be more readily understood from the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

[0033] Figure 1 is a diagram showing a system for processing non-fungible tokens (NFTs) according to an exemplary embodiment of the present disclosure;

[0034] Figure 2 is a block diagram of an electronic device that can implement any one of the devices according to an example embodiment of the present disclosure;

[0035] Figure 3 is a conceptual diagram of a blockchain network according to an example embodiment of the present disclosure;

[0036] Figure 4 is a flowchart showing a process of processing an NFT associated with a receipt related to the purchase of a product through an electronic device according to an exemplary embodiment of the present disclosure;

[0037] Figure 5 is a flowchart showing a process of recording evaluation information about a product in metadata of an NFT associated with a receipt through an electronic device according to an exemplary embodiment of the present disclosure;

[0038] Figure 6 is a flowchart showing a process of changing a holder of an NFT associated with a receipt through an electronic device according to an exemplary embodiment of the present disclosure;

[0039] Figure 7 is a flowchart showing a process of associating an NFT associated with a receipt with an NFT associated with an additional receipt with each other through an electronic device according to an exemplary embodiment of the present disclosure; and

[0040] Figure 8 is a flowchart showing a process of processing an NFT associated with a receipt related to purchasing a service through an electronic device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] While considering the functions in the present disclosure, when possible, terms used in exemplary embodiments are selected from currently widely used general terms. However, these terms may vary according to the intention of those skilled in the art, cases, emergence of new technologies, etc. In addition, in some cases, there are also terms arbitrarily selected by the applicant, and in these cases, the meanings will be described in detail in the corresponding descriptions. Therefore, the terms used in the present disclosure should not be simply interpreted by their names, but based on the meanings of the terms and the overall context of the present disclosure.

[0042] Throughout the specification, when a component is described as "including or containing" an element, unless otherwise stated, it does not exclude another element, but may also include another element. In addition, terms such as "…… unit", "…… part", and "…… module" described in the specification refer to a unit that processes at least one function or operation, which may be implemented as hardware, software, or a combination thereof, or different from the shown examples, and these terms may not be clearly distinguished in specific operations.

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

[0044] In the present disclosure, a "terminal" or "user terminal" may be implemented as, for example, a computer or a portable terminal capable of accessing a server or another terminal through a network. Here, the computer may include, for example, a notebook, a desktop computer, and / or a laptop equipped with a web browser. The portable terminal may be a wireless communication device ensuring portability and mobility, and includes (but is not limited to) any type of handheld wireless communication device, such as a tablet PC, a smart phone, a communication-based terminal, such as International Mobile Telecommunications (IMT), Code Division Multiple Access (CDMA), W-Code Division Multiple Access (W-CDMA), Long Term Evolution (LTE), etc.

[0045] In the following description, terms such as "transmit", "transfer", "send", "receive" signals, messages or information and other terms having similar meanings not only include directly transferring a signal, a message or information from one element to another element, but also include through other elements. Specifically, "transmitting" or "sending" a signal, a message or information to an element means the ultimate destination of the signal, the message or the information, which does not refer to the direct destination. The same applies to "receiving" a signal, a message or information. In addition, in this specification, two or more pieces of data or information being "related" means that when one piece of data (or information) is obtained, at least a part of other data (or information) can be obtained based on this.

[0046] In addition, although terms such as first, second, etc. may be used to describe various elements, these elements should not be limited to the above terms. The above terms can be used to distinguish one element from another element.

[0047] For example, without departing from the scope of the present disclosure, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element.

[0048] Hereinafter, example embodiments of the present disclosure will be described in detail with reference to the accompanying drawings, so that those of ordinary skill in the art to which the present disclosure pertains can easily implement the example embodiments of the present disclosure. However, the present disclosure can be implemented in various different forms and is not limited to the example embodiments described herein.

[0049] When describing the example embodiments, descriptions of technical content that is well-known in the technical field to which the example embodiments of the present disclosure pertain and is not directly related to the present disclosure will be omitted. By omitting unnecessary descriptions, this will more clearly convey without obscuring the gist of the present disclosure.

[0050] For the same reason, some elements are enlarged, omitted or schematically shown in the accompanying drawings. In addition, the size of each element does not fully reflect the actual size. In each drawing, the same or corresponding elements are assigned the same reference numerals.

[0051] Advantages and features of example embodiments of the present disclosure, and methods for achieving the advantages and features, will become apparent with reference to the example embodiments described in detail below and the accompanying drawings. However, the present disclosure is not limited to the example embodiments disclosed below and can be implemented in various different forms. The example embodiments are provided only to make the present disclosure complete and to fully inform those of ordinary skill in the art to which the present disclosure pertains of the scope of the present disclosure. The present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same elements.

[0052] It should be understood that each block of the flowchart and combinations of blocks can be implemented by computer program instructions. The computer program instructions can be embodied in a processor of a general purpose computer or a special purpose computer, or can be embodied in the processor of other programmable data processing devices. Thus, the instructions executed by the processor of a computer or other programmable data processing device can generate means for performing the functions described in the flowchart block. For the functions to be implemented in a particular manner, the computer program instructions can also be stored in a computer-usable or computer-readable memory, which can direct a computer or other programmable data processing device. Thus, the instructions stored in the computer-usable or computer-readable memory can be produced as an article of manufacture including instructions for performing the functions described in the flowchart block. The computer program instructions can be embodied in a computer or other programmable data processing device. Thus, a series of operations can be performed in a computer or other programmable data processing device to create a computer-executed process, and the computer or other programmable data processing device can provide steps for performing the functions described in the flowchart block.

[0053] In addition, each block can represent a module, segment, or portion of code including one or more executable instructions for performing the specified (one or more) logical functions. It should also be noted that in some alternative embodiments, the functions recited in the blocks may occur out of order. For example, two blocks shown one after another can be executed substantially simultaneously, or these blocks can sometimes be executed in the reverse order depending on the corresponding functions.

[0054] In this disclosure, tokens issued, used, or deleted based on a blockchain network may comply with at least a portion of a set of standards based on the Ethereum request for comment (ERC). For example, a fungible token (FT) may comply with ERC20. ERC20 includes a set of rules required for a token to have FT characteristics, and the rules included in ERC20 may include rules regarding functions such as transferring tokens between addresses, checking the total token supply, and checking the token balance of a specific address. For example, a non-fungible token (NFT) may comply with ERC721. ERC721 includes a set of rules required for a token to have NFT characteristics, and the rules included in ERC721 may include rules regarding functions such as checking the number of tokens held by a specific address, checking the holder of a specific token, transferring tokens between addresses, and returning the addresses approved to transfer a specific token. As another example, a token may comply with ERC1155, which is a standard that covers both FTs and NFTs. ERC1155 is a composite token standard that allows the creation of FTs and NFTs in a single smart contract, reducing fuel costs and increasing scalability by storing multiple token types in a single smart contract compared to ERC721.

[0055] The term "smart contract" as used in this disclosure may refer to a program or application that operates on a virtual machine executed by two or more nodes included in a blockchain network. A smart contract may be a computer protocol for establishing, verifying, and executing a specific contract by itself. A smart contract may refer to a program that automatically executes a contract if the contract conditions programmed based on blockchain technology are met. The virtual machine may include, for example, the Ethereum virtual machine (EVM), which is a distributed computing environment that operates on the Ethereum blockchain and executes and manages smart contracts. The EVM is a Turing machine for processing (e.g., deploying and executing) smart contracts and can process all types of algorithms. The EVM may execute smart contracts based on the rules defined by Ethereum and perform operations to update the state that changes according to it. Smart contracts can be written to comply with a predetermined set of rules or protocols. For example, referring to ERC-721 or ERC-1155, a smart contract can be written to include one or more functions corresponding to each protocol. However, various types of smart contracts can be written by including other functions not included in the example protocols.

[0056] As used in this disclosure, the term "wallet" may refer to an electronic form of tool for securely storing and managing a user's digital assets. A wallet can store and manage information related to cryptocurrencies or digital assets. Digital asset wallets can be classified into hot wallets and cold wallets. A hot wallet is a wallet that is connected to the Internet in a form where cryptocurrencies are accessible in an online environment. Generally, a hot wallet can be provided as a software wallet or an online service. A hot wallet can provide convenient and quick access to transfer 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. Generally, a cold wallet can be provided as a hardware wallet or a paper wallet. Since the private keys are securely protected and stored offline, a cold wallet can provide a high level of security to prevent hacking or malware attacks. A wallet address can be a type of identifier for identifying a wallet. A user can use the wallet address to send and receive digital assets.

[0057] In this disclosure, sending a transaction to a blockchain network may include uploading specific data on the blockchain network, modifying or deleting previously uploaded data on the blockchain network, or executing a smart contract deployed on the blockchain network. A transaction as used in this disclosure may refer to a logical unit of an operation executed on a blockchain network. A transaction may include a transaction recorded on the blockchain network and / or a transaction not recorded on the blockchain network. For example, a transaction on the Ethereum blockchain network may include a transaction recorded on the blockchain network, which includes a transaction hash value and a message (internal transaction) generated when executing the transaction in the EVM.

[0058] Figure 1 FIG. is a diagram showing a system 10 for processing non-fungible tokens (NFTs) according to an exemplary embodiment of the present disclosure. The system 10 may include a server 110, a terminal 120, a blockchain network 140, and / or a computer network 130. The blockchain network 140 may 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 may communicate with each other via the computer network 130. The computer network 130 may be a digital telecommunications network and may refer to the connection between each distributed device via a predetermined communication network. The computer network 130 may be implemented as any type of wired or wireless network, such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, and a wireless broadband Internet (Wibro). The computer network 130 may be a data communication network to enable Figure 1Each of the devices shown can communicate smoothly with each other in an integrated sense and may include a wired Internet network, a wireless Internet network, and a mobile wireless network. The figure shows an environment in which a server 110 communicates with a terminal 120 and two or more nodes through a computer network 130, but this is merely an example, and the number of terminals 120 and the number of nodes may vary.

[0059] According to an example embodiment, the server 110 may be a server 110 that implements (operates) a platform for managing non-fungible tokens associated with receipts (hereinafter referred to as an NFT management platform). The NFT management platform may be understood as a platform for various NFT-related management or processing (such as the issuance, circulation, promotion, trade support, or burning of NFTs). The server 110 may perform various management or processing on NFTs associated with receipts. For example, the server 110 may manage each digital asset wallet address storing a user's NFTs. In the present disclosure, an account may be a unique string for proving a user's identity or identifying a user in the NFT management platform. A user may access the NFT management platform having their account and trade NFTs. If an account is allocated in the NFT management platform, one or more wallets for each account may be issued to the user for NFT trading. For example, NFTs included in a wallet corresponding to one account may be transferred through the NFT management platform to a wallet corresponding to another account. In this specification, transferring an NFT from a wallet corresponding to one account to a wallet corresponding to another account may be understood as being the same as or similar to changing information about the NFT owner (e.g., information about the owner's wallet address) recorded in the metadata of the NFT from a first piece of information to a second piece of information. The server 110 may perform various operations typically required in the NFT management platform (such as communication between users). The server 110 may be involved in issuing and trading NFTs by interacting with at least one node included in the blockchain network 140. The server 110 may be, but is not limited to, one electronic device, and may also refer to a group of multiple electronic devices connected electronically or physically.

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

[0061] The terminal 120 according to an exemplary embodiment may be the terminal 120 of a user who uses the NFT management platform or the terminal 120 of an administrator who manages the NFT management platform. The user may use various functions provided by the NFT management platform through the terminal 120. The user may request to issue an NFT associated with a receipt or perform communication with other users through the terminal 120. The user may use the NFT management platform through a dedicated application or a web browser installed in the terminal 120. The terminal 120 may be any one of, for example, 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 these examples, and may be various types of electronic devices equipped with a computing function. In this figure, the number of terminals 120 is shown as 1, but is not limited thereto, and the number of terminals 120 may also be two or more.

[0062] According to an exemplary embodiment, a node (e.g., node 141) included in the blockchain network 140 may refer to an electronic device of a participant who participates in the blockchain network 140. The node may be a component of the blockchain network 140. The node may perform operations for maintaining the blockchain of the blockchain network 140. For example, any one node of the blockchain network 140 may generate a new block of the corresponding blockchain. The new block may be shared among other nodes of the blockchain network 140 through a distributed consensus process and connected to the subsequent block of the blockchain. In other words, the node may perform operations of generating, verifying, or propagating transactions and recording the blocks of the transactions. Based on the operations performed by the node, the node may be a full node, a light node, a master node, a mining node, a random node, a baking node, or a super node. The node may perform token issuance by interacting with the server 110. Token issuance may refer to a process in which an issuer creates a specific number of tokens using a smart contract and stores the created tokens in a specific wallet.

[0063] According to an exemplary embodiment, the node may be implemented as an electronic device (or a computing device). For example, the above-mentioned electronic device may be a desktop computer, a laptop computer, etc., but is not limited thereto, and may be various types of devices equipped with a computing function. The server 110, the terminal 120, and the node may represent functionally different elements. Two or more elements may be implemented in an integrated form in an actual physical environment. For example, the server 110 and the node included in the blockchain network 140 may be implemented in different logical forms within the same electronic device 200. For example, the server 110 may be implemented to operate as a node of the blockchain network 140, and the terminal 120 may also be implemented to operate as a node of the blockchain network 140.

[0064] According to an example embodiment, the blockchain network 140 may record, approve, or process transactions in a block and may generate a smart contract. In the present disclosure, the blockchain network 140 is shown as one but not limited to this, and may also include a main blockchain network and a side blockchain network. In the above case, the main blockchain network may focus on security and decentralization, and the side blockchain network may focus on speed and reduction of transaction costs (e.g., fuel fees).

[0065] According to an example embodiment, each node of the blockchain network may record a transaction based on operations such as issuance, discard, and update of NFTs in the blockchain network 140. Each node may also read the transactions recorded and verified in the blockchain network 140 and maintain the currency of the information corresponding thereto.

[0066] According to an example embodiment, a smart contract for performing operations such as issuing an NFT and recording information in the NFT metadata may be deployed on the blockchain network 140. The smart contract may be a smart contract for processing an NFT associated with a receipt, and the smart contract may include one or more instructions. A processor of an electronic device connected to a computer network 130 including the blockchain network 140 may execute the smart contract to process the NFT associated with the receipt. The one or more instructions may be configured to cause the processor of the electronic device to perform various determined operations when executed.

[0067] Figure 2 FIG. is a block diagram of an electronic device 200 that may implement any one of the devices according to an example embodiment of the present disclosure. According to the present disclosure, the electronic device 200 may represent a computing device, and the electronic device 200 may be interchangeably referred to as a computing device. Each node included in the above server 110, terminal 120, and blockchain network 140 may be implemented by the electronic device 200.

[0068] The electronic device 200 according to an example embodiment may include a processor 210, a memory 220, and a communication circuit 230. At least one of the elements included in the electronic device 200 may be omitted, or other elements may be added to the electronic device 200. Additionally or alternatively, some elements may be implemented integrally, or may also be implemented as a single entity or multiple entities. At least some of the elements within the electronic device 200 may be implemented integrally or may also be implemented as a single entity or multiple entities. At least some of the elements within the electronic device 200 may be connected to each other through a bus, a general-purpose input / output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI), and may send and receive data and / or signals.

[0069] The processor 210 of the electronic device 200 according to an exemplary embodiment may be configured to perform operations or data processing for controlling and / or communicating with each element of the electronic device 200, and may be operatively connected to the elements of the electronic device 200. The processor 210 may load instructions or data received from other elements of the electronic device 200 into the memory 220, process the instructions or data stored in the memory 220, and store the resulting data. Unless otherwise specified, the processor 210 in the present disclosure may refer to a collection of one or more processors 210.

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

[0071] The communication circuit 230 of the electronic device 200 according to an exemplary embodiment may establish a wired or wireless communication channel with an external device (e.g., the terminal 120), and may transmit various data to the external device and receive various data from the external device. The communication circuit 230 of the electronic device 200 may include at least one port connected to an external device via a wired cable for wired communication with the external device. The communication circuit 230 of the electronic device 200 may be configured to include a cellular communication module and connect to a cellular network (e.g., 3G, LTE, 5G, Wibro, or Worldwide Interoperability for Microwave Access (Wimax)). According to an exemplary embodiment, the communication circuit 230 of the electronic device 200 may include a short-range communication module and may transmit data to and receive data from an external device using short-range communication (e.g., Wi-Fi, Bluetooth, Bluetooth Low Energy (BLE), and Ultra-Wideband (UWB)), but is not limited thereto.

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

[0073] Figure 3It is a conceptual diagram of a blockchain network 140 according to an exemplary 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, and 142c are connected in a chain form. One or more blocks 142a, 142b, and 142c included in the blockchain may be independently stored in one or more nodes included in the blockchain network 140, or may be distributed and stored across multiple nodes. Each of the one or more blocks 142a, 142b, and 142c may include a block hash, a block header, or a block body. The block hash may be unique information that can identify the block, and may be, for example, a string represented by 256 bits. The block header may include, for example, at least one of software or protocol version information, a hash of a previous block based on the connection order of the blocks on the blockchain, a Merkle root, time information indicating the block creation time, a bit representing the computational difficulty, and a nonce, where the nonce is an arbitrary value used to generate the block hash value required in the process of adding a new block to the blockchain. The block body may contain at least one transaction. A transaction may be a data set with a specific data structure and an information unit stored in the block body. A transaction may include information about creating or trading tokens. A transaction may be, for example, information indicating that a first node included in the blockchain network 140 transfers an NFT to a second node.

[0074] The blockchain may 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 be operated by a hierarchical structure. The hierarchical structure may include, for example, at least one of the following: a data layer for defining the data structure processed by the blockchain network 140 and managing data, a consensus layer for performing mining to verify the validity of blocks, creating blocks, and paying processing fees to miners during the mining process, a common layer for implementing or managing peer-to-peer (P2P) network protocols, hash functions, electronic signatures, encoding, and public storage, or an application layer in which various applications are generated or processed.

[0075] At least one node included in the blockchain network 140 may share or store transactions recorded on the blockchain. In addition, at least one node included in the blockchain network 140 may perform a verification operation on a transaction transferred to the blockchain network 140 through the consensus algorithm of the blockchain, and if the verification is completed, perform the function of recording the verified transaction in a block of the blockchain. The type of consensus algorithm executed by the blockchain network 140 is not restricted, and any type of consensus algorithm that can be adopted and modified by those of ordinary skill in the art may be executed. For example, the consensus algorithm may include at least one of a Proof of Work (PoW) algorithm, a Proof of Stake (PoS) algorithm, a Delegated Proof of Stake (DPoS) algorithm, a Practical Byzantine Fault Tolerance (PBFT) algorithm, a Delegated Byzantine Fault Tolerance (DBFT) algorithm, a Redundant Byzantine Fault Tolerance (RBFT) algorithm, a Sieve algorithm, a Tendermint algorithm, a Paxos algorithm, a Raft algorithm, a Proof of Authority (PoA) algorithm, or a Proof of Elapsed Time (PoET) algorithm or an algorithm applying the above consensus algorithms.

[0076] Each of at least one node included in the blockchain network 140 may store a smart contract. With this configuration, at least one node included in the blockchain network 140 may share the same smart contract. In addition, the smart contract may be recorded in a block of the blockchain managed by the blockchain network 140. The smart contract may be, for example, a specification or script written in a programming language (such as Solidity), and may be a program or application operating on a virtual machine executed by at least one node included in the blockchain network 140. The smart contract may include one or more instructions that cause a specific operation to be performed if a specific condition is met. The specific condition may include, for example, a condition of inputting a specific type of token or inputting data in a specific format. The specific operation may include, for example, an operation of transferring a specific type of token to any node of the blockchain network 140.

[0077] The smart contract may be written to conform to a set of predetermined rules (or protocols). For example, the smart contract may be written to include one or more functions corresponding to each protocol of ERC-20 or ERC-721. However, since other functions not included in the example protocols (such as one or more functions corresponding to ERC-1155) are included in the smart contract, various types of smart contracts may be written.

[0078] In the present disclosure, a token may be a token that can be used on a blockchain managed by a blockchain network 140 and may be an NFT. The NFT may refer to a virtual token created based on a smart contract written according to a predefined protocol (e.g., ERC-721 or ERC-1155). The NFT may be recorded in a blockchain that is a distributed storage and can thus maintain integrity. The NFT may be created to include a specific type of data and can thus guarantee the existence of a specific type of data. In the present disclosure, unless otherwise specified in the context, an object referred to as a token may be an NFT.

[0079] In the present disclosure, information about an NFT may be a data set including a plurality of data. The information about the NFT may include at least one of the following: NFT identification information (NFT ID), information indicating a specific object, event identification information (event ID), an issue number regarding an event, information for accessing a digital file of content connected to the NFT (digital file uniform resource identifier (URI)), information for accessing metadata of the NFT (metadata URI), or information about the current token owner (e.g., the wallet address of the holder currently holding the NFT, the ownership period of the NFT, the transaction history on the NFT, and the transaction price). Hereinafter, in the present disclosure, for ease of description, it is assumed and described that the token-related information recorded in the blockchain network 140 includes a digital file URI, a metadata URI, the metadata of the content indicated by the digital file, or the token metadata itself, but the present disclosure is not limited thereto.

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

[0081] In the present disclosure, an NFT may be associated with a specific object (e.g., a receipt). If the digital file connected to the NFT is a digital file of a specific object, the expression that the NFT is associated with the specific object may be an expression indicating the relationship between the NFT and the specific object. The specific object may include, for example, a receipt related to the purchase of a product and a receipt related to the purchase of a service. The digital file regarding the receipt may be, for example, a photo or video of a receipt related to the purchase of a product and a photo or video of a receipt related to the purchase of a service. Alternatively, the digital file regarding the receipt may be, for example, an electronic-form receipt issued according to the product or the purchased service.

[0082] The digital file URI included in the information about the NFT may be the address where the digital file is stored in a distributed file system or the hash value of the stored digital file. The distributed file system may be the InterPlanetary File System (IPFS) that distributes and stores files in multiple devices. The digital file accessible through the digital file URI may be, for example, an image file, a video file, or a sound file. In the present disclosure, unless the context is otherwise used, the digital file connected to the NFT may refer to the expression of the digital file obtained through the digital file URI recorded in the NFT, and may have the same meaning as the expression of, for example, the digital file owned by the NFT or the digital file associated with the NFT.

[0083] The metadata URI included in the information about the NFT may be the hash value of the NFT metadata stored in a distributed file system. The NFT metadata may refer to a data set including various information about the NFT. The metadata may include, for example, at least one of an NFT name, an NFT ID, the name of a receipt associated with the NFT, the NFT creation time point, the current NFT holder information, the NFT holder change history, information related to an event corresponding to the NFT, or the digital file URI.

[0084] At least a part of the various information included in the information about the NFT may be stored in the memory 220 of the electronic device 200. In addition, at least a part of the various information included in the information about the NFT may be recorded in a block managed by the blockchain network 140.

[0085] 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 inclusively refer to various operations, such as the NFT being issued (created) by the smart contract, the NFT being transferred from the address of one user to the address of another user, or the NFT being burned. The smart contract may include various types of functions.

[0086] Smart contracts can be written to conform to a set of predefined rules (or protocols). For example, a smart contract written to conform to any first protocol (e.g., ERC-20) can include a function that returns the total supply of virtual currency tokens. A smart contract written to conform to the first protocol can include a function that obtains the blockchain address of a specific node and returns the quantity of virtual currency tokens held by the corresponding address. A smart contract written to conform to the first protocol can include a function that obtains the quantity of any virtual currency tokens and the blockchain address of the node receiving the virtual currency tokens, and transfers the virtual currency tokens to the address of the receiving node. A smart contract written to conform to the first protocol can include a function that obtains the quantity of any virtual currency tokens, the blockchain address of the node transferring the virtual currency tokens, and the blockchain address of the node receiving the virtual currency tokens, and transfers the virtual currency tokens from the address of the transferring node to the address of the receiving node. A smart contract written to conform to the first protocol can include a function that returns whether token withdrawals are allowed to limit the quantity of virtual currency tokens that can be withdrawn. Additionally, a smart contract written to conform to the first protocol can include a function that returns the remaining quantity of tokens that can be withdrawn.

[0087] A smart contract written to conform to any second protocol (e.g., ERC-721) can include a function to create an NFT based on one or more pieces of information received from a specific node (in other words, an NFT creation function). For example, the NFT creation function can obtain a specific digital file URI received from a specific node and the blockchain address of any node, and create a token corresponding to the corresponding digital file URI. If an NFT is created (issued) through the creation function, information about the holder of the corresponding NFT can be determined based on the blockchain address of any node input to the NFT creation function. The NFT creation function can additionally obtain one or more pieces of information to be included in the NFT metadata (e.g., the NFT name and attributes of the NFT) and create the NFT. In the present disclosure, expressions such as issuing an NFT or creating an NFT can be used interchangeably with expressions such as minting an NFT. Additionally, a smart contract written to conform to the second protocol can include a function that obtains the blockchain address of any node and returns the quantity of tokens held by the corresponding address. A smart contract written to conform to the second protocol can include a function that obtains the NFT ID of any NFT and returns information about the holder of the corresponding NFT. A smart contract written to conform to the second protocol can include a function that obtains the blockchain address of any node and the NFT ID of any NFT and permits transfer authorization for the NFT with the corresponding NFT ID for the corresponding node. A smart contract written to conform to the second protocol can include a function that obtains the NFT ID of any NFT and returns the blockchain addresses of one or more nodes with transfer authorization for the corresponding NFT.

[0088] The above description of the smart contract written to comply with the first protocol and the second protocol is only for describing an example of the functions included in the smart contract, and the present disclosure is not limited thereto, and the smart contract according to the present disclosure may include various types of smart contracts, including at least one function related to NFT.

[0089] Figure 4 FIG. is a flowchart showing a process of an electronic device 200 processing an NFT associated with a receipt related to purchasing a product according to an exemplary embodiment of the present disclosure. A processor 210 of the electronic device 200 connected to a computer network 130 including a blockchain network 140 may execute a smart contract to process the NFT associated with the receipt. The server 110, the terminal 120, and each node included in the above blockchain network 140 may be implemented by the electronic device 200. The processor 210 of the electronic device 200 may transfer a transaction to the blockchain network 140 to process the NFT associated with the receipt. In this case, the smart contract deployed on the blockchain network 140 may be executed through a virtual machine (e.g., EVM). The smart contract may include one or more instructions. In other words, the processor 210 of the electronic device 200 may execute one or more instructions included in the smart contract by executing the smart contract to process the NFT associated with the receipt through the virtual machine. The one or more instructions may be configured to cause the processor 210 of the electronic device 200 to perform a specific operation corresponding to the one or more instructions when executed. Figure 4 The flowchart shown is a diagram showing operations corresponding to one or more instructions included in the smart contract, and these operations are performed when the processor 210 of the electronic device 200 executes the smart contract through the virtual machine. In other words, regarding Figure 4 , a series of operations performed by the processor 210 of the electronic device 200 may be executed through the virtual machine.

[0090] Referring to the flowchart 400, in operation 410, the processor 210 of the electronic device 200 according to an exemplary embodiment may identify a digital file regarding a receipt related to a purchased product and a request for issuing an NFT associated with the receipt. In other words, the smart contract may include instructions for identifying a digital file regarding a receipt related to a purchased product and a request for issuing an NFT associated with the receipt. The processor 210 of the electronic device 200 may send the digital file regarding the receipt related to the purchased product to the blockchain network 140, and send together with it a request for issuing an NFT associated with the receipt. The digital file regarding the receipt related to the purchased product may be, for example, a receipt photo obtained by taking a picture of the issued receipt in the case of purchasing a product, and may also be a receipt file issued in electronic form. According to various exemplary embodiments, the digital file sent together with the request for issuing an NFT may also include a digital file not associated with the receipt. For example, an image file or a video file of the product taken in the case of purchasing a product may also be sent to the blockchain network 140 together with the request for issuing an NFT. The processor 210 of the electronic device 200 may identify a digital file regarding a receipt related to a purchased product and a request for issuing an NFT associated with the receipt.

[0091] It is assumed and described that the terminal 120 is used to request the issuance of an NFT associated with a receipt. The user may use the terminal 120 to take a picture of the receipt related to the purchased product after purchasing the product, thereby obtaining a digital file regarding the receipt (e.g., a photo or video of the receipt). The terminal 120 may send the digital file regarding the receipt related to the purchased product and a request for issuing an NFT associated with the receipt to the blockchain network 140. The terminal 120 may identify the digital file regarding the receipt related to the purchased product and the request for issuing an NFT associated with the receipt through a virtual machine.

[0092] Alternatively, it is assumed and described that the server 110 implementing a platform for managing an NFT associated with a receipt is used to request the issuance of an NFT associated with the receipt. The user may use the terminal 120 to take a picture of the receipt related to the purchased product after purchasing the product, thereby obtaining a digital file regarding the receipt. The user may upload (send) the digital file regarding the receipt to the platform. The server 110 may obtain the digital file regarding the receipt. The server 110 may send the digital file regarding the receipt related to the purchased product and a request for issuing an NFT associated with the receipt to the blockchain network 140. The server 110 may identify the digital file regarding the receipt related to the purchased product and the request for issuing an NFT associated with the receipt through a virtual machine.

[0093] In addition to the platform for managing NFTs, the issuance request for the NFT associated with the receipt may be executed by a platform for managing product evaluation information (e.g., review information) or a token development company. For example, the server implementing the platform for managing product evaluation information may also send a digital file regarding the receipt associated with the purchased product and an issuance request for the NFT associated with the receipt to the blockchain network 140. For another example, the server of the token development company may also send a digital file regarding the receipt associated with the purchased product and an issuance request for the NFT associated with the receipt to the blockchain network 140. In other words, as described above, the sender of the issuance request for the NFT associated with the receipt may be one of the user's terminal 120, the server 110 implementing the platform for managing NFTs, the server implementing the platform for managing product evaluation information, or the server of the token development company.

[0094] In operation 420, the processor 210 of the electronic device 200 according to an exemplary embodiment may issue an NFT associated with the receipt. The processor 210 may issue the NFT associated with the receipt in response to the issuance request identified in operation 410. In other words, the smart contract may include instructions for issuing the NFT associated with the receipt in response to the identified issuance request. The address (e.g., URI) in the distributed file system where the digital file regarding the receipt is stored by the processor 210 may be recorded in one or more blocks on the blockchain network 140. By recording the address of the digital file regarding the receipt stored in the distributed file system in one or more blocks on the blockchain network 140, the processor 210 may issue the NFT associated with the receipt. Alternatively, the address in the distributed file system where the digital file regarding the receipt is stored by the processor 210 may be recorded in the metadata of the NFT associated with the receipt. In other words, the smart contract may include instructions for storing the digital file regarding the receipt in the distributed file system in response to the identified issuance request. The smart contract may include instructions for issuing the NFT associated with the receipt when the address where the digital file regarding the receipt is stored in the distributed file system is recorded in one or more blocks on the blockchain network 140. The processor 210 may identify the metadata of the NFT stored in the blockchain-based distributed file system through the IPFS protocol. If an NFT is minted, the metadata of the NFT may include information generated in a specific format. The processor 210 of the electronic device 200 may record the wallet address of the first account corresponding to the purchaser of the product in the metadata of the issued NFT associated with the receipt. In other words, the smart contract may include instructions for recording the wallet address of the first account corresponding to the purchaser of the product in the metadata of the NFT associated with the receipt.

[0095] Meanwhile, with Figure 4Different from what is shown, before performing operation 420, the processor 210 of the electronic device 200 may verify (identify) whether the issuance request for the NFT associated with the receipt is sent by the purchaser of the product. The smart contract may include instructions for identifying whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt. In other words, the processor 210 may verify whether the requester who sends the issuance request for the NFT associated with the receipt is the actual purchaser of the product.

[0096] According to an exemplary embodiment for performing the above verification, the server 110 may identify whether the requester is the purchaser of the product and provide the identification result to the blockchain network 140. The server 110 that operates the platform for managing the NFT associated with the receipt may obtain the wallet address of the first account corresponding to the purchaser of the product from the purchaser's terminal 120. In other words, the server 110 may obtain the wallet address of the first account that is the purchaser's account from the purchaser's terminal 120 while obtaining the digital file regarding the receipt. If joining the platform, the identification information of the requester (for example, the wallet address and personal information corresponding to the requester's account) may be obtained and stored in the server 110. Based on the wallet address, the server 110 may verify whether the requester who sends the issuance request for the NFT is the purchaser of the product. Specifically, by comparing the wallet address of the account corresponding to the requester who sends the issuance request for the NFT and the wallet address of the first account corresponding to the purchaser, the server 110 may verify whether the requester is the actual purchaser of the product. Alternatively, the server 110 may extract the payment information recorded in the receipt from the digital file regarding the receipt and obtain the identification information of the payer (for example, the wallet address and personal information corresponding to the payer's account) from the server of the card company based on the payment information recorded in the receipt. By comparing the identification information of the payer and the identification information of the requester, the server 110 may verify whether the requester is the actual purchaser of the product. If it is verified through the above method that the requester is the purchaser of the product, the server 110 may provide an identifier to the blockchain network 140. The identifier may be, for example, information indicating that the requester who sends the issuance request for the NFT is the purchaser of the product.

[0097] According to another exemplary embodiment for verifying whether the requester who sends a request for issuing an NFT associated with a receipt is the actual purchaser of the product, it is also possible to identify on the blockchain network 140 whether the requester is the purchaser of the product. The server of the card company can record the receipt or payment information related to the purchased product in a block of the blockchain network 140. By doing so, the electronic device 200 corresponding to one of the nodes included in the blockchain network 140 can identify the receipt or payment information recorded in the block through the virtual machine and obtain the identification information of the purchaser corresponding to the receipt or payment information. By comparing the identification information of the purchaser and the identification information of the requester who sends a request for issuing an NFT, the electronic device 200 can verify whether the requester is the actual purchaser of the product.

[0098] In operation 430, the processor 210 of the electronic device 200 according to the exemplary embodiment can identify evaluation information about the product. Specifically, the smart contract can include instructions for identifying evaluation information about the product. In operation 440, if the writer of the evaluation information about the product is the purchaser who performs the purchase of the product, the processor 210 of the electronic device 200 according to the exemplary embodiment can record the evaluation information about the product in the metadata of the NFT associated with the receipt. Specifically, if the writer of the evaluation information about the product is the purchaser who performs the purchase of the product, the smart contract can include instructions for recording the evaluation information about the product in the metadata of the NFT associated with the receipt. The processor 210 can send the evaluation information about the product to the blockchain network 140. The processor 210 can identify the evaluation information about the product. The processor 210 can verify (identify) whether the writer of the evaluation information about the product is the purchaser (actual purchaser) who performs the purchase of the product through the virtual machine. The following refers to Figure 5 Describe a specific verification method. The evaluation information about the product can include at least one of the name of the product, the identification information about the product, the image of the product, the video of the product, and the comment about the product.

[0099] It is assumed and described that the writer of the evaluation information about the product is the purchaser who executes the product purchase. In other words, it is assumed and described that the actual purchaser of the product writes the evaluation information about the product. In the above case, the purchaser who executes the product purchase can use the terminal 120 to write the evaluation information about the product, and the terminal 120 can send the evaluation information about the product to the blockchain network 140. Alternatively, the purchaser who executes the product purchase can use the terminal 120 to write the evaluation information about the product and send the written evaluation information about the product to the platform that manages the NFT associated with the receipt. In this case, the server 110 of the operating platform can send the evaluation information about the product to the blockchain network 140. The processor 210 can identify (verify) whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt through the virtual machine. If the writer is the holder of the NFT, the processor 210 of the electronic device 200 can record the evaluation information about the product in the metadata of the NFT associated with the receipt. In the above case, since the writer is the holder of the NFT associated with the receipt, the writer is the purchaser who executes the product purchase. Therefore, in the above case, the processor 210 can record the evaluation information about the product in the metadata of the NFT associated with the receipt.

[0100] According to an exemplary embodiment for identifying whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt, the server 110 can identify whether the writer is the holder of the NFT associated with the receipt. If the NFT is issued, the server 110 of the platform that operates the NFT associated with the receipt can receive and store the identification information of the holder who holds the NFT associated with the receipt (for example, the personal information of the holder and the wallet address of the account corresponding to the holder) from the terminal 120. The server 110 can receive the identification information of the writer of the evaluation information about the product (for example, the personal information of the writer and the wallet address of the account corresponding to the writer) from the terminal 120. By comparing the identification information of the writer and the identification information of the holder, the server 110 can identify whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt.

[0101] According to another exemplary embodiment, it is assumed and described that the writer of the evaluation information about the product is not the purchaser who executes the product purchase. In other words, a person other than the actual purchaser of the product can write the evaluation information about the product. In the above case, a person other than the purchaser can use the terminal 120 to write the evaluation information about the product, and the terminal 120 can send the evaluation information about the product to the blockchain network 140. The processor 210 can identify (verify) through the virtual machine whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt. In the above case, since the writer is not the holder of the NFT associated with the receipt, the writer is not the purchaser who executes the product purchase. Therefore, in the above case, the processor 210 can determine not to record the evaluation information about the product in the metadata of the NFT associated with the receipt.

[0102] According to the above method, based on the request of the purchaser who executes the product purchase, the NFT associated with the receipt related to the purchased product can be issued, and the evaluation information about the product written by the purchaser can be recorded in the metadata of the NFT associated with the receipt. If a person other than the purchaser of the product requests the issuance of the NFT associated with the receipt, the NFT associated with the receipt may not be issued, and the evaluation information about the product written by a person other than the purchaser of the product may not be recorded in the metadata of the NFT associated with the receipt.

[0103] Figure 5 It is a flowchart showing the process of recording the evaluation information about the product in the metadata of the NFT associated with the receipt by the electronic device 200 according to an exemplary embodiment of the present disclosure. Specifically, Figure 5 It is a flowchart of a method for verifying whether the writer of the evaluation information about the product is the purchaser who executes the product purchase. The operations shown in this figure can be operations corresponding to one or more instructions included in the smart contract deployed on the blockchain network 140. In other words, Figure 5 The flowchart shown is a diagram showing the operations corresponding to one or more instructions included in the smart contract, and these operations are executed when the processor 210 of the electronic device 200 executes the smart contract through the virtual machine (e.g., EVM). Regarding Figure 5 , a series of operations executed by the processor 210 of the electronic device 200 can be executed through the virtual machine.

[0104] Referring to the flowchart 500, in operation 510, the processor 210 of the electronic device 200 according to the example embodiment may identify information about the writer of the evaluation information regarding the product. The information about the writer may include, for example, the personal information of the writer and the wallet address of the account. The processor 210 may identify the wallet address of the writer's account or the personal information of the writer sent from the server 110 or the terminal 120. In other words, the smart contract may include instructions for identifying the wallet address of the writer's account.

[0105] In operation 520, the processor 210 of the electronic device 200 according to the example embodiment may identify whether the writer of the evaluation information regarding the product is the holder of the NFT associated with the receipt. The processor 210 may compare the wallet address of the account corresponding to the writer with the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks on the blockchain network 140. Alternatively, the wallet address of the first account corresponding to the holder of the NFT associated with the receipt may also be recorded in the metadata of the NFT associated with the receipt. The processor 210 may identify whether the wallet address of the account corresponding to the writer of 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 on the blockchain network 140. In other words, the smart contract may further include instructions for identifying whether the writer of the evaluation information regarding the product is the holder of the NFT associated with the receipt based on the wallet address of the writer's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks on the blockchain network 140.

[0106] According to another exemplary embodiment, the processor 210 may use the identification information of the writer of the evaluation information about the product to identify whether the writer is the holder of the NFT associated with the receipt. The identification information of the writer of the evaluation information about the product may be sent from the server 110 or the terminal 120 to the blockchain network 140. The processor 210 may identify the identification information of the writer of the evaluation information about the product. The identification information of the holder may be recorded in one or more blocks on the blockchain network 140 or in the metadata of the NFT associated with the receipt. For example, the identification information of the holder (e.g., the account information corresponding to the holder) may be recorded in the metadata of the NFT associated with the receipt. In other words, the smart contract may include instructions for obtaining the identification information of the writer of the evaluation information about the product. By comparing the identification information of the writer with the identification information of the holder of the NFT recorded in one or more blocks on the blockchain network 140, the processor 210 may identify whether the writer is the holder of the NFT associated with the receipt. In other words, the smart contract may include instructions for verifying whether the writer is the purchaser of the product based on the identification information of the writer of the evaluation information about the product.

[0107] If the writer of the evaluation information about the product is the holder of the NFT associated with the receipt, then proceed to operation 530 (operation 520 - Yes), and the processor 210 may determine that the writer is the purchaser of the product. In other words, the smart contract may include instructions for determining that the writer is the purchaser of the product when the writer is the holder of the NFT associated with the receipt. According to an exemplary embodiment, in operation 540, the processor 210 of the electronic device 200 may record the evaluation information about the product in the metadata of the NFT associated with the receipt. According to an example embodiment, the evaluation information about the product may be stored in a distributed file system, and the address where the evaluation information about the product is stored in the distributed file system may be recorded in the metadata of the NFT associated with the receipt. In other words, the smart contract may include instructions for storing the evaluation information about the product in the distributed file system in response to the writer being the purchaser of the product. The smart contract may include instructions for recording the address where the evaluation information about the product is stored in the distributed file system in the metadata of the NFT associated with the receipt. The metadata of the NFT associated with the receipt may include at least one of, for example, detailed information about the product, evaluation information, information about the writer of the evaluation information, or information about the date and time of writing. The evaluation information about the product may include at least one of, for example, the product name, identification information, image, video, and comments about the product.

[0108] If the writer of the evaluation information about the product is not the holder of the NFT associated with the receipt, proceed to operation 550 (operation 520 - No), and the processor 210 may determine that the writer is not the purchaser of the product. In operation 560, the processor 210 according to an exemplary embodiment may determine not to record the evaluation information about the product in the metadata of the NFT associated with the receipt. In other words, if the writer of the evaluation information about the product is not the purchaser of the product, the smart contract may include instructions for not recording the evaluation information about the product in the metadata of the NFT associated with the receipt.

[0109] According to the above manner, the evaluation information about the product written by someone other than the actual purchaser of the product may not be recorded in the metadata of the NFT (or the block of the blockchain network 140). In other words, according to the above manner, by recording the evaluation information of the product written only by the purchaser of the product in the metadata of the NFT associated with the receipt related to the purchase of the product, transparent and accurate management of the evaluation information can be achieved.

[0110] Figure 6 is a flowchart showing the process of changing the holder of the NFT associated with the receipt by the electronic device 200 according to an exemplary embodiment of the present disclosure. Specifically, Figure 6 is a flowchart of a method for changing the holder of the NFT associated with the receipt. The operations shown in this figure may be operations corresponding to one or more instructions included in the smart contract deployed on the blockchain network 140. In other words, Figure 6 the shown flowchart is a diagram showing the operations corresponding to one or more instructions included in the smart contract, and these operations are executed when the processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). Regarding Figure 6 this, a series of operations executed by the processor 210 of the electronic device 200 can be executed through the virtual machine.

[0111] In second - hand transactions, purchasing agency services, or e - commerce services, products can be repurchased from the purchaser of the product instead of directly from the authorized seller of the product. For example, after a first customer purchases a product from an authorized seller, the first customer can resell the product to a second customer. For example, after purchasing a product from an authorized seller on a purchasing agency platform, the product can be sold to a second customer. In this case, it may be difficult for the repurchaser of the product (e.g., the second customer) to identify whether the product purchased again is a genuine product or a forged product.

[0112] According to an exemplary embodiment of the present disclosure, by casting a receipt for a product purchase, an NFT associated with the receipt can be issued, and detailed information about the product or information about the product purchaser can be recorded in the metadata of the NFT associated with the receipt. Accordingly, a repurchaser of the corresponding product can identify whether the corresponding product is genuine through the NFT associated with the receipt, and can also receive (or can purchase) the NFT associated with the receipt together with the product.

[0113] According to an exemplary embodiment of the present disclosure, in addition to the digital file associated with the receipt, a digital file not associated with the receipt can be stored in the distributed file system. For example, regarding a product, an image file or a video file taken when the product is purchased can also be stored in the distributed file system, and the address where the image file or the video file is stored in 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 also include information about the purchaser (e.g., the first customer) of the product. In this case, a repurchaser (e.g., the second customer) of the corresponding product can identify the purchaser (e.g., the first customer) of the corresponding product through the NFT associated with the receipt. In the exemplary embodiment, if the first customer is a celebrity (such as a singer and an actor), it can be proven through the NFT that the corresponding product was previously used by the celebrity, and the value of the corresponding product can be considered more highly.

[0114] Referring to the flowchart 600, in operation 610, the processor 210 of the electronic device 200 according to an exemplary embodiment can identify a change request for changing the holder of the NFT associated with the receipt from the first account to the second account. For example, the first account may be an account corresponding to the purchaser (hereinafter referred to as the initial purchaser) who makes the initial purchase of the product, and the second account may be an account of the repurchaser who repurchases the product from the initial purchaser. For example, if the product is sold by the initial purchaser to the repurchaser, the server 110 of the platform that operates the NFT associated with the receipt can send a change request to the blockchain network 140, the change request being for changing the holder of the NFT associated with the receipt from the first account corresponding to the initial purchaser to the second account corresponding to the repurchaser. In other words, the smart contract may include instructions for identifying a change request for changing the holder of the NFT associated with the receipt from the first account to the second account.

[0115] In operation 620, the processor 210 of the electronic device 200 according to an exemplary embodiment may verify whether the second account is the account of the repurchaser who repurchases the product from the purchaser. The server 110 of the operating platform may send the identification information of the repurchaser who repurchases the product to the blockchain network 140. The identification information of the repurchaser may include, for example, the wallet address of the second account corresponding to the repurchaser. In other words, the smart contract may include instructions for verifying whether the second account is the account of the repurchaser who repurchases the product from the purchaser.

[0116] In operation 630, in response to the second account being the account of the repurchaser, the processor 210 of the electronic device 200 according to an exemplary embodiment may record the wallet address of the second account in the metadata of the NFT associated with the receipt. The processor 210 may change the holder of the NFT associated with 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 associated with the receipt. In other words, the smart contract may include instructions for recording 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.

[0117] In the above manner, since who sells the product and to whom it is sold can be identified by the NFT associated with the receipt, information about the product can be managed in a transparent and fair manner.

[0118] Figure 7 is a flowchart showing a process of associating an NFT associated with a receipt and an NFT associated with an additional receipt with each other through the electronic device 200 according to an exemplary embodiment of the present disclosure. Specifically, Figure 7 is a flowchart regarding a manner of issuing an NFT associated with an additional receipt related to the repurchase of a product, and may be a flowchart regarding operations additionally performed after executing the Figure 6 shown flowchart.

[0119] The operations shown in this figure may be operations corresponding to one or more instructions included in a smart contract deployed on the blockchain network 140. In other words, Figure 7 the shown flowchart is a diagram showing operations corresponding to one or more instructions included in a smart contract, and these operations are performed when the processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). Regarding Figure 7 , a series of operations performed by the processor 210 of the electronic device 200 may be executed through a virtual machine.

[0120] Referring to the flow chart 700, in operation 710, the processor 210 of the electronic device 200 according to an exemplary embodiment may identify a digital file of an additional receipt related to the repurchase of a product and a request for the issuance of an NFT associated with the additional receipt. If the product is sold by the initial purchaser to the repurchaser, the repurchaser may receive an additional receipt related to the repurchase of the product. For example, if the initial purchaser of the product is a purchasing agency platform, an additional receipt may be issued to the repurchaser of the product. The processor 210 may send the digital file of the additional receipt related to the repurchase of the product to the blockchain network 140, and together with it, send a request for the issuance of an NFT associated with the additional receipt. The digital file of the receipt related to the repurchase of the product may be, for example, a receipt photo obtained by taking a picture of the issued receipt in the case of a repurchased product, and may also be a receipt file issued in electronic form. The processor 210 may identify a digital file of an additional receipt related to the repurchase of the product and a request for the issuance of an NFT associated with the additional receipt. In other words, the smart contract may include instructions for identifying a digital file of an additional receipt related to the repurchase of the product and a request for the issuance of an NFT associated with the additional receipt.

[0121] In operation 720, the processor 210 of the electronic device 200 according to an exemplary embodiment may issue an NFT associated with the additional receipt in response to a request for the issuance of an NFT associated with the additional receipt. The processor 210 may issue an NFT associated with the additional receipt in response to the issuance request identified in operation 710. The address (e.g., URI) in the distributed file system where the digital file of the additional receipt is stored by the processor 210 may be recorded in one or more blocks on the blockchain network 140. In other words, by recording the address in the distributed file system where the digital file of the additional receipt is stored in one or more blocks on the blockchain network 140, the processor 210 may issue an NFT associated with the additional receipt. Alternatively, the address in the distributed file system where the digital file of the additional receipt is stored by the processor 210 may be recorded in the metadata of the NFT associated with the additional receipt. In other words, the smart contract may include instructions for issuing an NFT associated with the additional receipt in response to a request for the issuance of an NFT associated with the additional receipt.

[0122] In operation 730, the processor 210 of the electronic device 200 according to an exemplary embodiment may associate the NFT associated with a receipt and the NFT associated with an additional receipt with each other. The processor 210 may associate the NFT associated with a receipt and the NFT associated with an additional receipt with each other to verify that the NFT associated with a receipt and the NFT associated with an additional receipt are NFTs for the same product. In other words, the smart contract may include instructions for associating the NFT associated with a receipt and the NFT associated with an additional receipt with each other. For example, the processor 210 may record information about the NFT associated with a receipt in the metadata of the NFT associated with an additional receipt. For example, the processor 210 may record information about the NFT associated with an additional receipt in the metadata of the NFT associated with a receipt. In other words, the smart contract may include instructions for recording information about the NFT associated with a receipt in the metadata of the NFT associated with an additional receipt.

[0123] According to an exemplary embodiment, the processor 210 may also combine the NFT associated with a receipt and the NFT associated with an additional receipt. For example, the processor 210 may create a new third NFT by combining the NFT associated with a receipt and the NFT associated with an additional receipt. In the above case, the NFT associated with a receipt and the NFT associated with an additional receipt may be set to no longer be traded, and only the combined third NFT may be traded. Information about the NFT associated with a receipt and information about the NFT associated with an additional receipt may also be recorded in the metadata of the third NFT. In the above case, the NFT associated with a receipt and the NFT associated with an additional receipt may be deleted, and only the combined third NFT may exist. In other words, the smart contract may include instructions for combining the NFT associated with a receipt and the NFT associated with an additional receipt.

[0124] Figure 8 is a flowchart showing a process of processing an NFT associated with a receipt related to a purchase service by the electronic device 200 according to an exemplary embodiment of the present disclosure. Specifically, Figure 8 is a flowchart of a manner of issuing an NFT associated with a receipt and recording evaluation information about a service in the metadata of the NFT using a digital file related to a receipt related to a purchase service. The operations shown in this figure may be operations corresponding to one or more instructions included in a smart contract deployed on the blockchain network 140. In other words, Figure 8 The flowchart shown is a diagram showing operations corresponding to one or more instructions included in a smart contract, which are executed when the processor 210 of the electronic device 200 executes the smart contract through a virtual machine (e.g., EVM). Regarding Figure 8, a series of operations executed by the processor 210 of the electronic device 200 can be executed through a virtual machine. Repeated descriptions of the content referred to above Figure 4 and Figure 5 will be omitted without further description. The services described herein can be concepts of services provided in various fields such as the food industry, hotel industry, transportation industry, and tourism industry.

[0125] Referring to the flowchart 800, in operation 810, the processor 210 of the electronic device 200 according to an exemplary embodiment can identify a digital file of a receipt related to the purchase of a service and a request for the issuance of an NFT associated with the receipt. The processor 210 can send the digital file of the receipt related to the purchase of the service to the blockchain network 140 and, together with it, send the request for the issuance of the NFT associated with the receipt. For example, by taking a picture of the receipt issued when visiting a restaurant and purchasing food services using the terminal 120, a customer can obtain a digital file of the receipt related to the purchase of the service. The terminal 120 can send the digital file of the receipt related to the purchase of the service and the request for the issuance of the NFT associated with the receipt to the blockchain network 140. The terminal 120 can identify the digital file of the receipt related to the purchase of the service and the request for the issuance of the NFT associated with the receipt through a virtual machine. In other words, the smart contract can include instructions for identifying a digital file of a receipt related to the purchase of a service and a request for the issuance of an NFT associated with the receipt.

[0126] In operation 820, the processor 210 of the electronic device 200 according to an exemplary embodiment issues an NFT associated with the receipt. In other words, the smart contract can include instructions for issuing an NFT associated with the receipt in response to the identified issuance request. The address (e.g., URI) in the distributed file system where the digital file of the receipt is stored by the processor 210 can be recorded in one or more blocks on the blockchain network 140. In other words, by recording the address in the distributed file system where the digital file of the receipt is stored in one or more blocks on the blockchain network 140, the processor 210 can issue an NFT associated with the receipt. Alternatively, the address in the distributed file system where the digital file of the receipt is stored by the processor 210 can be recorded in the metadata of the NFT associated with the receipt. The processor can record the wallet address of the first account corresponding to the purchaser of the service in the metadata of the NFT associated with the receipt.

[0127] In operation 830, the processor 210 of the electronic device 200 according to an example embodiment may identify evaluation information about a service. The evaluation information about the service may include, for example, at least one of a name of a store providing the service, a fee, an image, a video, and a comment about the service. In other words, the smart contract may include instructions for identifying evaluation information about a service.

[0128] In operation 840, the processor 210 of the electronic device 200 according to an example embodiment may verify whether the writer of the evaluation information about the service is the purchaser who performed the service purchase. For example, the processor 210 may compare the wallet address of the account corresponding to the writer of the evaluation information with the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks on the blockchain network 140. Alternatively, the wallet address of the first account corresponding to the holder of the NFT associated with the receipt may also be recorded in the metadata of the NFT associated with the receipt. The processor 210 may identify whether the wallet address of the account corresponding to the writer of 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 on the blockchain network 140. In other words, the smart contract may include instructions for verifying whether the writer of the evaluation information about the service is the purchaser of the service by verifying whether the writer of the evaluation information about the service is the holder of the NFT associated with the receipt.

[0129] In operation 850, if the writer is the purchaser of the service, the processor 210 of the electronic device 200 according to an example embodiment may record the evaluation information about the service in the metadata of the NFT associated with the receipt. The metadata of the NFT associated with the receipt may include, for example, at least one of detailed information about the service, evaluation information, information about the writer of the evaluation information, and information about the date and time of writing. In other words, the smart contract may include instructions for recording the evaluation information about the service in the metadata of the NFT associated with the receipt if the writer is the purchaser of the service.

[0130] In operation 860, the processor 210 of the electronic device 200 according to an example embodiment may provide a reward to the first account corresponding to the purchaser. The processor 210 may provide a reward to the first account corresponding to the purchaser in response to recording the evaluation information about the service in the metadata of the NFT. For example, the processor 210 may provide virtual currency as a reward to the wallet address of the first account corresponding to the purchaser. For example, the processor 210 may provide points that can be used in the platform for managing the NFT associated with the receipt as a reward to the first account corresponding to the purchaser. In other words, the smart contract may include instructions for providing a reward to the first account in response to recording the evaluation information about the service.

[0131] According to the above method, if the purchaser of the service records evaluation information about the service, rewards can be provided to the purchaser in response thereto to encourage the writing of evaluation information.

[0132] According to an example embodiment of the present disclosure, a smart contract for processing NFTs associated with receipts can be deployed on the blockchain network 140. The smart contract can include one or more instructions. Specifically, the smart contract can include instructions for identifying a digital file regarding a receipt associated with a product purchase and an issuance request for an NFT associated with the receipt. The smart contract can include instructions for issuing an NFT associated with the receipt in response to the identified issuance request. The smart contract can include instructions for identifying evaluation information about the product. The smart contract can include instructions for the following processing: if the writer of the evaluation information about the product is the purchaser who made the product purchase, record the evaluation information about the product in the metadata of the NFT associated with the receipt. The smart contract can include instructions for storing the digital file regarding the receipt in a distributed file system in response to the identified issuance request. The smart contract can include instructions for publishing the NFT associated with the receipt as an address when the address where the digital file regarding the receipt is stored in the distributed file system is recorded in one or more blocks on the blockchain network 140.

[0133] The smart contract can include instructions for recording the wallet address of a first account corresponding to the purchaser of the product in the metadata of the NFT associated with the receipt. The smart contract can include instructions for identifying whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt. The smart contract can include instructions for determining that the writer is the purchaser of the product if the writer is the holder of the NFT associated with the receipt. The smart contract can include instructions for identifying the wallet address of the writer's account. The smart contract can further include instructions for identifying whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt based on the wallet address of the writer's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks on the blockchain network 140. The smart contract can include instructions for storing the evaluation information about the product in a distributed file system in response to the writer being the purchaser of the product. The smart contract can include instructions for recording the address where the evaluation information about the product is stored in the distributed file system in the metadata of the NFT associated with the receipt.

[0134] The smart contract may include instructions for not recording evaluation information about a product in the metadata of the NFT associated with the receipt if the writer of the evaluation information about the product is not the purchaser of the product. The smart contract may include instructions for obtaining identification information of the writer of the evaluation information about the product. The smart contract may include instructions for verifying whether the writer is the purchaser of the product based on the identification information of the writer of the evaluation information about the product. The smart contract may include instructions for identifying a change request to change the holder of the NFT associated with the receipt from a first account to a second account. The smart contract may include instructions for verifying whether the second account is the account of a repurchaser who repurchases the product from the purchaser. The smart contract may include instructions for recording 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 may include instructions for identifying a digital file regarding an additional receipt related to the product repurchase and a request for issuing an NFT associated with the additional receipt. The smart contract may include instructions for issuing the NFT associated with the additional receipt in response to the request for issuing the NFT associated with the additional receipt. The smart contract may include instructions for associating the NFT associated with the receipt and the NFT associated with the additional receipt with each other. The smart contract may include instructions for recording information about the NFT associated with the receipt in the metadata of the NFT associated with the additional receipt. The smart contract may include instructions for combining the NFT associated with the receipt and the NFT associated with the additional receipt.

[0135] The smart contract may include instructions for identifying a digital file regarding a receipt related to the purchase of a service and a request for issuing an NFT associated with the receipt. The smart contract may include instructions for issuing the NFT associated with the receipt in response to the identified request for issuing. The smart contract may include instructions for identifying evaluation information about the service. The smart contract may include instructions for verifying whether the writer of the evaluation information about the service is the purchaser of the service by verifying whether the writer of the evaluation information about the service is the holder of the NFT associated with the receipt. The smart contract may include instructions for recording the evaluation information about the service in the metadata of the NFT associated with the receipt if the writer is the purchaser of the service. The smart contract may include instructions for providing a reward to the first account in response to recording the evaluation information about the service.

[0136] The electronic device according to the above exemplary embodiments may include a processor, a memory for storing and executing program data, a permanent memory such as a disk drive, a communication port for communicating with external devices, and a user interface device such as a touch panel, keys, and buttons. The method implemented by a software module or algorithm may be stored as computer-readable code or program instructions capable of being executed on the processor in a computer-readable recording medium. Here, the computer-readable recording medium includes magnetic storage media (e.g., read-only memory (ROM), random access memory (RAM), floppy disks, and hard disks) and optically-readable media (e.g., CD-ROM and digital versatile disc (DVD)). The computer-readable recording medium may be distributed among networked computer systems so that the computer-readable code can be stored and executed in a distributed manner. The medium can be read by a computer, stored in the memory, and executed on the processor.

[0137] The exemplary embodiments may be represented by functional block elements and various processing steps. The functional blocks may be implemented in any number of hardware and / or software configurations for performing particular functions. For example, the exemplary embodiments may employ integrated circuit configurations such as memories, processing, logic, and / or look-up tables, which may execute various functions by controlling one or more microprocessors or other control devices. Similar to the element being implemented as a software programming or software element, the exemplary embodiments may be implemented in programming or scripting languages such as C, C++, Java, assembly language, etc., including various algorithms implemented as combinations of data structures, procedures, routines, or other programming constructs. The functional aspects may be implemented in algorithms running on one or more processors. In addition, the exemplary embodiments may employ the prior art for electronic environment setup, signal processing, and / or data processing. Terms such as "mechanism", "element", "device", and "configuration" may be used broadly and are not limited to mechanical and physical configurations. These terms may include the meaning of a series of software routines associated with a processor, etc.

[0138] The above exemplary embodiments are merely examples, and other exemplary embodiments may be implemented within the scope of the claims described later.

[0139] If concepts of various patents, applications, and publications are needed to provide further embodiments, aspects of the embodiments may be modified.

[0140] Based on the above detailed description, these and other changes may be made to the embodiments. Generally, in the following claims, the terms used should not be construed as limiting the claims to the specific embodiments disclosed in the specification and the claims, but should be construed to include all possible embodiments and the full scope of equivalents to which these claims are entitled. Therefore, the claims are not limited by the disclosure.

Claims

1. A method for an electronic device to process non-fungible tokens (NFTs), the method comprising: Executing, by a processor of the electronic device, a smart contract to process an NFT associated with a receipt, the electronic device being connected to a computer network including a blockchain network, wherein the smart contract includes one or more instructions, and wherein the one or more instructions are configured to, when executed, cause the processor to: Identify a digital file of a receipt related to a purchased product and a request for issuance of an NFT associated with the receipt; In response to the identified issuance request, issue an NFT associated with the receipt; Identify evaluation information about the product; and Based on the writer of the evaluation information about the product being the purchaser who executed the purchase of the product, record the evaluation information about the product in the metadata of the NFT associated with the receipt.

2. The method according to claim 1, wherein the one or more instructions are further configured to, when executed, cause the processor to: In response to the identified issuance request, store the digital file of the receipt in a distributed file system; and Issue the NFT associated with the receipt by recording the address where the digital file of the receipt is stored in the distributed file system in one or more blocks on the blockchain network.

3. The method according to claim 1, wherein The one or more instructions are further configured to: when executed, cause the processor to record the wallet address of a first account corresponding to the purchaser of the product in the metadata of the NFT associated with the receipt.

4. The method according to claim 3, wherein The one or more instructions are further configured to, when executed, cause the processor to: Identify whether the writer of the evaluation information about the product is the holder of the NFT associated with the receipt; and Based on the writer being the holder of the NFT associated with the receipt, determine that the writer is the purchaser of the product.

5. The method according to claim 4, wherein, The one or more instructions are further configured to, when executed, cause the processor to: Identify the wallet address of the writer's account; and Based on the wallet address of the writer's account and the wallet address of the first account corresponding to the holder of the NFT recorded in one or more blocks on the blockchain network, identify whether the writer is the holder of the NFT associated with the receipt.

6. The method according to claim 4, wherein The one or more instructions are further configured to, when executed, cause the processor to: In response to the writer being the purchaser of the product, store the evaluation information about the product in a distributed file system; and Record the address where the evaluation information about the product is stored in the distributed file system in the metadata of the NFT associated with the receipt.

7. The method according to claim 1, wherein The one or more instructions are further configured to: when executed, cause the processor not to record the evaluation information about the product in the metadata of the NFT associated with the receipt based on the writer not being the purchaser of the product.

8. The method according to claim 3, wherein, The one or more instructions are further configured to, when executed, cause the processor to: Obtain identification information about the author; and Based on the identification information about the author, verify whether the author is the purchaser of the product.

9. The method according to claim 3, wherein The one or more instructions are further configured to, when executed, cause the processor to: Identify a change request for changing the holder of the NFT associated with the receipt from the first account to a second account; Verify whether the second account is the account of a repurchaser who repurchases the product from the purchaser; And In response to the second account being the account of the repurchaser, record the wallet address of the second account in the metadata of the NFT associated with the receipt.

10. The method according to claim 9, wherein, The one or more instructions are further configured to, when executed, cause the processor to: Identify a digital file of an additional receipt related to the repurchase of the product and a request for issuing an NFT associated with the additional receipt; In response to the request for issuing the NFT associated with the additional receipt, issue the NFT associated with the additional receipt; and Associate the NFT associated with the receipt and the NFT associated with the additional receipt with each other.

11. The method according to claim 10, wherein The one or more instructions are further configured to: when executed, cause the processor to record information about the NFT associated with the receipt in the metadata of the NFT associated with the additional receipt.

12. The method according to claim 10, wherein, The one or more instructions are further configured to: when executed, cause the processor to combine the NFT associated with the receipt and the NFT associated with the additional receipt.

13. The method according to claim 1, wherein The metadata of the NFT associated with the receipt includes at least one of detailed information about the product, the evaluation information, information about the author of the evaluation information, and information about the date and time of writing.

14. The method according to claim 1, wherein The evaluation information includes at least one of the name of the product, identification information, an image, a video, and a comment about the product.

15. A method for an electronic device to process an NFT, the method comprising: Executing, by a processor, a smart contract to process an NFT associated with a receipt, the processor being connected to a computer network including a blockchain network, Wherein the smart contract includes one or more instructions, and Wherein the one or more instructions are configured to: Identify a digital file of a receipt related to a purchased service and a request for issuing an NFT associated with the receipt; In response to the identified request for issuing, issue the NFT associated with the receipt; Identify evaluation information about the service; Verify whether the author of the evaluation information about the service is the purchaser of the service by verifying whether the author of the evaluation information about the service is the holder of the NFT associated with the receipt; Based on the author being the purchaser of the service, record the evaluation information about the service in the metadata of the NFT associated with the receipt; and In response to recording the evaluation information about the service, provide a reward to a first account corresponding to the purchaser.

16. The method according to claim 15, wherein, The metadata of the NFT associated with the receipt includes at least one of detailed information about the service, the evaluation information, information about the author of the evaluation information, and information about the date and time of writing, and wherein the evaluation information includes at least one of the name of the store providing the service, the fee, an image, a video, and a comment about the service.

17. An electronic device, comprising: a communication circuit configured to perform communication with a computer network including a blockchain network; a memory storing a smart contract for processing an NFT associated with a receipt; and a processor, wherein the processor is configured to execute the smart contract including one or more instructions, and wherein the processor is configured by executing the one or more instructions to: identify a digital file of a receipt related to a purchased product and a request for issuing an NFT associated with the receipt; in response to the identified issuing request, issue the NFT associated with the receipt; identify evaluation information about the product; and based on the author of the evaluation information about the product being the purchaser who executed the purchase of the product, record the evaluation information about the product in the metadata of the NFT associated with the receipt.

Images