Non-fungible token determination system and determination data generation method

Abstract

To provide a determination system of a non-fungible token and a generation method of determination data which enhance safety of transaction of a non-fungible token (NFT).SOLUTION: A system 10 is a determination system of a non-fungible token at a blockchain. The system comprises: an acquisition machine 510 which acquires first data related to a first non-fungible token which is a determination object; an NFT determiner 520 for determining authenticity of the first non-fungible token, on the basis of the first data; and a determination data generator 530 which generates second data indicating a determination result by the NFT determiner.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a system for determining non-fungible tokens and a method for generating determination data. [Background technology]

[0002] Patent Document 1 discloses a non-fungible token (NFT) in a blockchain. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-89640 Summary of the Invention

[0004] NFTs are attracting attention as a technology that allows digital data such as digital art or digital content to have unique value. As shown in Patent Document 1, NFTs are also being associated with real-world objects.

[0005] Digital data is easily copied, and it is often difficult to distinguish between original and copied digital data. However, because NFTs are unique, NFTed digital data is easily distinguishable from other copies, making it one-of-a-kind. Furthermore, because NFTs are recorded on the blockchain, which cannot be rewritten or tampered with, the uniqueness of NFTs can be proven by the blockchain. NFTs can also be used to prove ownership of digital data.

[0006] In this way, NFTs can function as a kind of certificate for digital data. Taking advantage of these characteristics of NFTs, buying and selling of NFTs has become popular in recent years. NFTs, which are tokenized scarce digital data, can sometimes be traded for extremely high amounts.

[0007] However, NFTs recorded on the blockchain are not always genuine NFTs that are tokenized versions of original digital data. For example, counterfeit NFTs may be created that are tokenized versions of illegally copied data. In other words, counterfeit NFTs that look identical to genuine NFTs may be created for the purpose of obtaining illicit profits.

[0008] For example, multiple genuine NFTs with the same image data may be legally created in limited quantities. In this case, multiple genuine NFTs with identical appearances may be listed on a marketplace where NFTs are traded. Even if a counterfeit NFT created by illegally copying the image data of a genuine NFT is listed on that marketplace, it may be difficult for NFT traders to distinguish between genuine and counterfeit NFTs. Furthermore, because NFTs are circulated frequently on the market, once a counterfeit NFT is believed to be a genuine NFT and circulates on the market, it becomes extremely difficult for ordinary traders to distinguish it from a counterfeit NFT.

[0009] There is also a risk that counterfeit NFTs, which are tokenized digital data different from that of genuine NFTs, could be falsely represented as genuine NFTs. For example, image data of a certain character that does not actually exist could be illegally created by a third party and then turned into an NFT.

[0010] As such, even if an NFT itself functions as a certificate, the existence of counterfeit or other non-genuine NFTs could jeopardize the security of NFT transactions.

[0011] Therefore, it is desirable to improve the security of NFT transactions.

[0012] One aspect of the present disclosure is a system for determining a non-fungible token in a blockchain. The disclosed system includes an acquirer that acquires first data related to a first non-fungible token to be determined, a determiner that determines the authenticity of the first non-fungible token based on the first data, and a generator that generates second data indicating the determination result made by the determiner.

[0013] Another aspect of the present disclosure is a method for generating verification data for a non-fungible token in a blockchain, the method comprising: acquiring, by a generation system, first data regarding a first non-fungible token to be verified; verifying, by the generation system, the authenticity of a second non-fungible token based on the first data; and generating, by the generation system, verification data indicating the verification result regarding the authenticity of the first non-fungible token.

[0014] Further details will be described in the following embodiments. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a schematic diagram showing the configuration of the system. [Figure 2] Figure 2 is a schematic diagram showing a genuine NFT and a counterfeit NFT. [Figure 3] Figure 3 is a schematic diagram showing the recording of authentic and counterfeit NFTs on a blockchain. [Figure 4] FIG. 4 is a configuration diagram showing a first example of the system. [Figure 5] FIG. 5 is a flowchart showing the procedure for determining NFT. [Figure 6] FIG. 6 is a configuration diagram showing a second example of the system. [Figure 7] FIG. 7 is a flowchart showing the procedure for NFT determination. [Figure 8] FIG. 8 is a schematic diagram illustrating a proof NFT. [Figure 9] FIG. 9 is a flowchart showing the procedure for using the system. DETAILED DESCRIPTION OF THE INVENTION

[0016] <1. Overview of the non-fungible token determination system and the method for generating determination data>

[0017] (1) The system according to the embodiment is a system for determining a non-fungible token in a blockchain, and includes an acquirer that acquires first data regarding a first non-fungible token to be determined, a determiner that determines the authenticity of the first non-fungible token based on the first data, and a generator that generates second data indicating the determination result by the determiner.

[0018] (2) It is preferable that the determiner is configured to determine the authenticity of the first non-fungible token using at least one of a first list regarding genuine non-fungible tokens and a second list regarding non-genuine non-fungible tokens.

[0019] (3) Preferably, the determiner is configured to determine the authenticity of the first non-fungible token by providing the first data to a classification model configured to classify non-fungible tokens.

[0020] (4) The acquirer is preferably configured to acquire the first data from a user terminal connected via a network.

[0021] (5) Preferably, the acquirer is configured to acquire the first data from a blockchain in which the first non-fungible token is recorded.

[0022] (6) The second data preferably includes a second non-fungible token recorded in the blockchain, and the second non-fungible token preferably has the determination result.

[0023] (7) It is preferable that the second non-fungible token further includes a transaction record of the first non-fungible token.

[0024] (8) When the determination machine determines that the first non-fungible token is a genuine non-fungible token, it is preferable that the generator is configured to generate the second data including proof data that the first non-fungible token is a genuine non-fungible token.

[0025] (9) A method according to an embodiment is a method for generating judgment data for a non-fungible token in a blockchain, comprising: acquiring first data regarding a first non-fungible token to be judged by a generation system; making a judgment regarding the authenticity of the second non-fungible token based on the first data by the generation system; and generating judgment data indicating the judgment result regarding the authenticity of the first non-fungible token by the generation system.

[0026] (10) The judgment data preferably includes a second non-fungible token recorded in the blockchain, and the second non-fungible token preferably has the judgment result.

[0027] (11) The second non-fungible token is preferably associated with the first non-fungible token.

[0028] <2. Example of a system for determining non-fungible tokens and a method for generating determination data>

[0029] FIG. 1 shows a system 10 according to an embodiment. The system 10 is operated, for example, by a non-fungible token (NFT) certification authority 80. The certification authority 80 is an organization that certifies that an NFT is a legitimate NFT. The certification authority 80 can determine the authenticity of the NFT in order to authenticate the NFT. A legitimate NFT certified by the certification authority 80 is also called a "certified NFT." Certified NFTs are more reliable than non-genuine NFTs or uncertified NFTs. Therefore, using certification by the certification authority 80 can ensure the safety of NFT transactions.

[0030] The system 10 according to the embodiment can operate as an NFT determination system. The system 10 can also operate as an NFT determination data generation system.

[0031] The system 10 according to the embodiment may include a server 51 connected to a network 15 such as the Internet. The server 51, for example, executes processing related to the authenticity of an NFT. The server 51 may be configured with multiple computers. The server 51, for example, executes a determination regarding the authenticity of an NFT in order to authenticate a legitimate NFT. The server 51 may generate data indicating the determination result. The server 51 is managed by a certification authority 80, for example.

[0032] The server 51 may be configured by a computer including a processor 51A and a storage device 51B. The storage device 51B is connected to the processor 51A. The storage device 51B includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage device 51B includes a computer program 51C executed by the processor 51A. The processor 51A reads and executes the computer program 51C stored in the storage device 51B. The computer program 51C has program code representing instructions for causing a computer to execute the processing to be performed by the server 51.

[0033] The system 10 according to the embodiment uses a blockchain 20. The server 51 can access the blockchain 20 via a network 15. The blockchain 20 is configured as a P2P (Peer to Peer) computer network system in which multiple computers are interconnected.

[0034] In the blockchain 20, transactions can be made between blockchain addresses. Transactions are recorded in the distributed ledger of the blockchain 20. A blockchain address indicates, for example, a user account in the blockchain 20.

[0035] Blockchain 20 allows for the trading of tokens such as NFTs. To ensure non-fungibility of NFTs, each NFT has a unique token identifier that enables it to be distinguished from other NFTs in the blockchain 20. This token identifier is also called an NFT identifier (NFT_ID). The token identifier is recorded, for example, in the blockchain address (contract address) where the generated NFT is stored.

[0036] The transaction history of the NFT is recorded in the blockchain 20. The transaction history recorded in the blockchain 20 may include a list of past and current owners of the NFT and the transaction date and time. The transaction record of the NFT is recorded, for example, in the blockchain address (contract address) where the NFT is stored. By referring to the transaction record in the blockchain 20, the blockchain address of the current owner of the NFT can be determined. Therefore, the NFT can function as a certificate of ownership of the tokenized digital data.

[0037] Any third party can access the blockchain 20 and refer to the NFT recorded on the blockchain 20. The server 51 and terminals 31 and 32 described below can both access the blockchain 20.

[0038] An NFT transaction is recorded in the blockchain 20 as a change in the owner of the NFT. The operation of changing the owner of an NFT performed in the blockchain 20 is also called sending an NFT. That is, changing the owner of an NFT from a first blockchain address to a second blockchain address is equivalent to sending tokens from the first blockchain address to the second blockchain address. NFT operations such as sending an NFT can be performed by the server 51 or the terminals 31 and 32 described below.

[0039] A user who uses the system 10 can access the system 10 using the user's terminal 31, 32. That is, the terminal 31, 32 can access the server 51 via the network 15. The terminal 31, 32 can also access the blockchain 20 via the network 15.

[0040] The terminal 31 is, for example, a mobile device such as a smartphone or a tablet. The configuration of the terminal 31 will be described below, but the terminal 32 may also have a similar configuration.

[0041] The terminal 31 can be connected to a network 15 such as the Internet. The terminal 31 can be configured by a computer including a processor 31A and a storage device 31B. The storage device 31B is connected to the processor 31A. The storage device 31B includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage device 31B includes a computer program 31C executed by the processor 31A. The processor 31A reads and executes the computer program 31C stored in the storage device 31B. The computer program 31C has program code that indicates instructions to be executed by the computer functioning as the terminal 31.

[0042] Additionally, the computer program 31C may be, for example, a wallet application program for displaying tokens such as NFTs stored in a user account on the blockchain 20 on the terminal 31. Such a program may provide functionality for user operations for storing, sending, and receiving tokens.

[0043] FIG. 2 shows examples of a legitimate NFT 62 and a counterfeit NFT 72, which is an unauthorized NFT. The legitimate NFT 62 is what is known as the real thing. The legitimate NFT 62 is created by, for example, an artist or creator C1 who creates digital content such as digital image data. The digital content 61 created by the artist or creator C1 is legitimate content. The artist or creator C1 tokenizes the legitimate content 61. Note that tokenization is also referred to as NFTing. The legitimate NFT 62 is generated by NFTing the legitimate content 61. The digital content to be NFTed is, for example, at least one of still image or video image data, sound data, text data, and a uniform resource identifier.

[0044] The counterfeit NFT 72 is an NFT other than the legitimate NFT 62, and is generated, for example, by converting illegal content 71 that has been illegally copied or created into an NFT. The counterfeit NFT 72 is created, for example, by an illegal copyr C2. The illegal content 71 may appear identical or exactly identical to the legitimate content 61 at first glance. Therefore, the counterfeit NFT 72 may be difficult to distinguish from the legitimate NFT 62 at first glance.

[0045] If the appearance of the counterfeit NFT 72 is almost identical to that of the genuine NFT 62, the content displayed on the terminals 31 and 32 will be almost identical even if the NFT is displayed on the terminals 31 and 32. For this reason, anyone looking at the display will be unable to distinguish whether the NFT is a genuine NFT 62 or a counterfeit NFT 72.

[0046] FIG. 3 shows an example of recording NFTs 62, 64, 72, and 74 in the blockchain 20. An NFT created in the blockchain 20 is recorded, for example, at a contract address in the blockchain 20. When an NFT is recorded at a contract address, it is also referred to as the NFT being stored at the contract address. A contract address is an address assigned to a contract in the blockchain 20. Multiple NFTs can be stored at one contract address.

[0047] An NFT can be generated by, for example, recording a token identifier (NFT_ID) for identifying each NFT in the contract address used to generate the NFT. That is, each NFT has a token identifier. Because the token identifier of an NFT uniquely identifies each NFT, the token identifier can be used to determine the authenticity of the NFT, as described below.

[0048] Furthermore, since an NFT is stored at a contract address, the NFT is considered to have a contract address. Even if an NFT is traded and its owner changes, the contract address of the NFT does not change. Furthermore, since the contract address of an NFT is used by the creator of the NFT, the contract address of the NFT can indicate the creator of the NFT. Using this, in this embodiment, the contract address of an NFT can be used to determine the authenticity of the NFT, as described below. Note that when an NFT is traded and its owner changes, for example, a record of a blockchain address indicating the latest owner of the NFT is added to the contract address where the NFT is stored.

[0049] The contract address may record names for one or more NFTs. Thus, an NFT may have a name recorded on the blockchain 20. The name of an NFT may be used to determine the authenticity of the NFT, as described below.

[0050] In FIG. 3, the legitimate NFTs 62, 64 are stored in the first contract address 22A. In FIG. 3, the first contract address 22A is, for example, 0x123456. The first contract address 22A is a blockchain address owned by a provider that provides the creator of the legitimate NFTs 62, 64 with a website for creating NFTs. The creator of the legitimate NFTs 62, 64 uses the terminal 31 to access the website for creating NFTs. The creator uses the terminal 31 to perform an operation to convert the digital content 61, 63 into an NFT, whereby the legitimate NFTs 62, 64 are recorded in the first contract address 22A and the NFTs 62, 64 are generated. Note that, as shown in FIG. 3, the NFTed digital content 61, 63 is also referred to as NFT-constituting data 61, 63.

[0051] In FIG. 3, as an example, the legitimate NFT 62 has "nft_id01" as the token identifier (NFT_ID). The legitimate NFT 64 has "nft_id02" as the token identifier (NFT_ID). The first contract address 22A has "AAA" as the name for the recorded NFT. In other words, in FIG. 3, the multiple legitimate NFTs 62, 64 have "AAA" as the common name.

[0052] Also, in FIG. 3, the counterfeit NFTs 72 and 74 are stored in the second contract address 22B. In FIG. 3, the second contract address 22B is an address different from the first contract address 22A, and is, for example, 0x778899. The second contract address 22B is, for example, a blockchain address used by the illegal copyist C2 to generate the counterfeit NFTs 72 and 74. In FIG. 3, as an example, the counterfeit NFTs 72 and 74 are generated by converting the digital contents 71 and 73 created by the illegal copyist C2 through illegal copying of the digital contents 61 and 63 into NFTs, and are recorded in the second contract address 22B.

[0053] In FIG. 3, as an example, the fake NFT 72 is a fake of the genuine NFT 62 and has "nft_idxx01" as the token identifier (NFT_ID). The fake NFT 72 has the same NFT configuration data 71 as the NFT configuration data 61 that the genuine NFT 62 has. Furthermore, the fake NFT 74 is a fake of the genuine NFT 64 and has "nft_idxx02" as the token identifier (NFT_ID). The fake NFT 74 has the same NFT configuration data 73 as the NFT configuration data 63 that the genuine NFT 64 has.

[0054] As an example, the second contract address 22B has a name "aaaa" similar to the legitimate NFTs 62 and 64 as the name for the recorded NFTs 72 and 74 in order to misrepresent them as legitimate NFTs 62 and 64.

[0055] Note that some of the data contained in NFTs 62, 63, 71, and 73 (for example, image data) may be recorded outside the blockchain 20. When data outside the blockchain 20 is converted into an NFT, a link (such as a URI) indicating the data outside the blockchain 20 is recorded in the blockchain 20 as NFT configuration data 61, 63, 71, and 73.

[0056] As shown in FIG. 3, counterfeit NFTs 72, 74 may have the same NFT constituent data 71, 73 as the NFT constituent data 61, 63 held by genuine NFTs 62, 64. However, even in this case, the contract address 22B of the counterfeit NFTs 72, 74 may differ from the contract address 22A of the genuine NFTs 62, 64. The token identifier of the counterfeit NFTs 72, 74 may also differ from the token identifier of the genuine NFTs 62, 64. The name of the counterfeit NFTs 72, 74 may also differ from the name of the genuine NFTs 62, 64. The counterfeit NFTs 72, 74 may also have NFT constituent data 71, 73 that differs from the NFT constituent data 61, 63 held by the genuine NFTs 62, 64. In this embodiment, these differences in the data related to the NFTs 62, 64, 72, 74 are used to determine the authenticity of the NFTs.

[0057] FIG. 4 shows a first example of the configuration of the system 10 according to the embodiment. The system 10 shown in FIG. 4 includes a determinator 520 that executes a determination process related to an NFT. The determinator 520 determines the authenticity of the NFT to be determined. The determinator 520 may be a software module implemented by, for example, the processor 51A of the server 51 executing a computer program 51C having program code for the determination process. The determinator 520 may also be a hardware module configured by hardware including a logic circuit, memory, and the like.

[0058] Determining the authenticity of an NFT may include, for example, at least one of determining whether the NFT being determined is a legitimate NFT, determining whether the NFT being determined is an illegitimate NFT, and determining whether the NFT being determined is a legitimate NFT or an illegitimate NFT.

[0059] Furthermore, determining the authenticity of an NFT may include, for example, determining at least one of: determining a first probability that the NFT being determined is a legitimate NFT; determining a second probability that the NFT being determined is a non-genuine NFT; or determining the first probability that the NFT being determined is a legitimate NFT and the second probability that the NFT being determined is a non-genuine NFT. Determining the authenticity of an NFT may include comparing at least one or both of the first probability and the second probability with a threshold. Based on the comparison result with the threshold, at least one of determination results of whether the NFT being determined is a legitimate NFT, whether the NFT being determined is a non-genuine NFT, and whether the NFT being determined is a legitimate NFT or a non-genuine NFT may be determined.

[0060] The determiner 520 can determine the authenticity of the NFT based on first data 101 related to the NFT to be determined. Hereinafter, the NFT to be determined will be simply referred to as the "target NFT." The first data 101 related to the target NFT is, for example, at least one of the contract addresses 22A and 22B of the target NFT, the name of the target NFT, the token identifier (NFT_ID) of the target NFT, and the NFT configuration data 61, 63, 71, and 73. In FIG. 4, as an example, the contract addresses 22A and 22B of the target NFT, the name of the target NFT, and the token identifier (NFT_ID) of the target NFT are used as the first data 101.

[0061] The first data 101 provided to the determiner 520 may be acquired by the acquirer 510. The acquirer 510 may be, for example, a software module realized by the processor 51A of the server 51 executing a computer program 51C having program code for a first data acquisition process. The acquirer 510 may include a communication device for communicating with an external device of the acquirer 510. The acquirer 510 may acquire the first data 101 from the terminals 31 and 32, for example, by communicating with the terminals 31 and 32 via the network 15. The acquirer 510 may also acquire the first data from the blockchain 20 by referencing the blockchain 20 via the network 15. The acquirer 510 may provide the acquired first data 101 to the determiner 520. The determiner 520 may use the acquired first data 101 to perform a determination process regarding the target NFT.

[0062] The determiner 520 shown in Fig. 4 makes a determination regarding the target NFT using lists 523A and 523B related to NFTs. The lists 523A and 523B may be stored, for example, in the storage device 51B of the server 51 or in a storage device of a computer other than the server 51. The lists 523A and 523B shown in Fig. 4 include both a first list 523A related to legitimate NFTs and a second list 523B related to non-genuine NFTs. The list used by the determiner 520 for determination may be either the first list 523A or the second list 523B.

[0063] The first list 523A may be configured as a list of data related to genuine NFTs. The first list 523A may be a so-called whitelist (positive list) that defines genuine NFTs. The data related to genuine NFTs included in the first list 523A may be data related to NFTs that are known to be genuine NFTs, or data related to NFTs that are likely to be genuine NFTs. The data related to genuine NFTs included in the first list 523A may be at least one of the contract address 22A of the genuine NFT, the name of the genuine NFT, the token identifier (NFT_ID) of the genuine NFT, and NFT configuration data 61, 63 of the genuine NFT.

[0064] Here, as an example, a genuine NFT is an NFT registered with the certification authority 80 as a genuine NFT. An NFT can be treated as a genuine NFT by being registered in the first list 523A. For example, when a person (applicant) who wishes to register an NFT with the certification authority 80 as a genuine NFT applies for registration of the NFT to the certification authority 80, the certification authority 80 reviews the NFT. If the NFT passes the review, the NFT is registered in the first list 523A as a genuine NFT. In the application process for NFT registration, the applicant may provide data related to the NFT to the certification authority 80. The applicant is, for example, the artist / creator C1 who created the genuine content 61, 63. Note that the certification authority 80 may independently obtain data related to the NFT from the blockchain 20 or the like and conduct a review regarding the genuine NFT, without waiting for the applicant's application procedure. A genuine NFT that the certification authority 80 independently reviews and certifies may also be registered in the first list 523A.

[0065] The second list 523B may be configured as a list of data related to non-genuine NFTs. The second list 523B may be a so-called blacklist (negative list) that defines non-genuine NFTs. The data related to non-genuine NFTs included in the second list 523B may be data related to NFTs that are known to be non-genuine NFTs, or may be data related to NFTs that are likely to be non-genuine NFTs. The data related to non-genuine NFTs included in the second list 523B may be at least one of the following data: the contract address 22B of the non-genuine NFT, the name of the non-genuine NFT, the token identifier (NFT_ID) of the non-genuine NFT, and NFT configuration data 71, 73 of the non-genuine NFT.

[0066] Here, as an example, an unauthorized NFT is an NFT registered with the certification authority 80 as an unauthorized NFT. An NFT can be treated as an unauthorized NFT by being registered in the second list 523B. For example, the certification authority 80 reviews an NFT upon notification from a person who has purchased an unauthorized NFT. If the NFT is found to be an unauthorized NFT as a result of the review, the NFT is registered in the second list 523B as an unauthorized NFT. When reporting an unauthorized NFT, the declarant may provide data related to the NFT to the certification authority 80. Note that the certification authority 80 may obtain data related to the NFT from the blockchain 20 or the like and conduct a review of the unauthorized NFT. An unauthorized NFT that the certification authority 80 has independently reviewed may also be registered in the second list 523B.

[0067] The determiner 520 may include a collator 521 for collating the first data 101 with the lists 523A and 523B. The collator 521 refers to the lists 523A and 523B and searches for data that matches the first data 101 in the lists 523A and 523B.

[0068] The collation result by the collation unit 521 may be provided to the generator 530 as the determination result of the determiner 520. The generator 530 generates second data indicating the determination result by the determiner 520. The second data is also referred to as determination data. The second data is used, for example, to present the determination result to a user who wishes to refer to the determination result. The generator 530 may be, for example, a software module realized by the processor 51A of the server 51 executing a computer program 51C having program code for generating the second data. The generator 530 may be configured by a computer separate from the server 51. Note that the determiner 520 may generate the second data using the blockchain 20. The generated second data may be stored in the server 51, transmitted to the terminals 31 and 32, or stored in the blockchain 20.

[0069] The second data may be, for example, at least one of data indicating that the target NFT is a regular NFT, data indicating that it is unknown whether the target NFT is a regular NFT, data indicating that the target NFT is a non-regular NFT, data indicating that it is unknown whether the target NFT is a non-regular NFT, data indicating the probability that the target NFT is a regular NFT, and data indicating the probability that the target NFT is a non-regular NFT.

[0070] The data indicating that the target NFT is a legitimate NFT functions as proof that the target NFT is a legitimate NFT. The existence of proof data for the target NFT allows anyone who references the proof data to trade the target NFT with confidence.

[0071] FIG. 5 shows an example of a procedure for determining a target NFT executed by the system 10 shown in FIG. 4. The system 10 first acquires first data 101 of the target NFT from the user terminal 31 (step S51). The user terminal 31 is, for example, a terminal used by a user who is considering purchasing a target NFT listed on an NFT marketplace and is interested in the authenticity of the target NFT. The user, for example, uses the terminal 31 to acquire the first data 101 related to the target NFT from the blockchain 20 or an online marketplace, and transmits the first data 101 to the system 10. The transmitted first data 101 may be received by the acquirer 510. The received first data 101 may be provided to the determiner 520.

[0072] The determiner 520 compares the first data 101 with the first list 523A, which is a whitelist that defines legitimate NFTs (step S52). The comparison may be performed by the verifier 521. If data that matches the first data 101 exists in the whitelist 523A, determination data (second data) indicating that the target NFT is a legitimate NFT is generated (step S53; legitimate NFT proof data generation). The generation of the determination data may be performed by the generator 530.

[0073] If data matching the first data 101 does not exist in the whitelist 523A, the determiner 520 compares the first data 101 with the second list 523B, which is a blacklist that defines non-genuine NFTs (step S54). If data matching the first data 101 exists in the blacklist 523B, determination data (second data) indicating that the target NFT is a non-genuine NFT is generated (step S55).

[0074] If there is no data matching the first data 101 in the blacklist 523B, determination data (second data) indicating that the target NFT is undeterminable is generated (step S56).

[0075] Note that the execution order of steps S52 and S54 may be reversed, or steps S52 and S54 may be executed in parallel. Furthermore, while the determination shown in FIG. 5 uses both whitelist 523A and blacklist 523B, it may also be a method using whitelist 523A alone, in which case steps S54 and S55 may be omitted. Furthermore, the determination may also be a method using blacklist 523B alone, in which case steps S52 and S53 may be omitted. Furthermore, a gray list may be used in the determination. A gray list may be, for example, a list of NFTs that may be legitimate or illegitimate, but are not certain to be legitimate.

[0076] FIG. 6 shows a second example of the configuration of the system 10 according to the embodiment. In the system 10 shown in FIG. 6, the configuration of the determiner 520 and the contents of the acquired first data 101 differ from those of the system shown in FIG. 4. In FIG. 6, NFT configuration data is also acquired as the first data 101. By including the NFT configuration data in the first data 101, it is possible to make an accurate determination using more data. Note that points not specifically described in FIG. 6 are the same as those of the system 10 shown in FIG. 4.

[0077] The determiner 520 shown in FIG. 6 uses a classification model 525 to determine the authenticity of the NFT to be determined. The classification model 525 is configured to output a result of classifying the target NFT when the first data 101 of the target NFT is input. The classification model 525 may classify the NFT from the perspective of authenticity. For example, the classification model 525 may classify whether the target NFT is a legitimate NFT or an illegitimate NFT. The classification model 525 may also classify whether the target NFT is a legitimate NFT, an illegitimate NFT, or unknown.

[0078] The classification model 525 may be, for example, any of logistic regression, k-nearest neighbor, decision tree, support vector machine, and neural network.

[0079] The classification model 525 may be constructed, for example, by using data related to NFTs that are known to be legitimate and / or illegitimate as training data for constructing the model. The classification model 525 may be used to identify unknown NFTs that are not registered in the lists 523A and 523B. The classification model 525 may also be used in conjunction with the lists 523A and 523B to identify NFTs.

[0080] The output of the classification model 525 may be provided to a generator 530 for generation of second data (decision data).

[0081] FIG. 7 shows an example of a procedure for determining a target NFT executed by the system 10 shown in FIG. 6. The system 10 first acquires first data 101 of the target NFT from the user terminal 31 (step S71). The user terminal 31 is, for example, a terminal used by a user who is considering purchasing a target NFT listed on an NFT marketplace and is interested in the authenticity of the target NFT. The user, for example, uses the terminal 31 to acquire the first data 101 related to the target NFT from the blockchain 20 or an online marketplace and transmits the first data 101 to the system 10. The transmitted first data 101 may be received by the acquirer 510. The first data acquired in step S71 may be minimal data capable of identifying the target NFT. For example, the first data acquired in step S71 may be a token identifier of the target NFT or a contract address of the target NFT.

[0082] The acquirer 510 uses the first data (such as a token identifier) ​​acquired in step S71 to refer to the target NFT recorded in the blockchain 20 and additionally acquires first data 101 related to the target NFT (step S72). The additionally acquired first data 101 is, for example, the name of the target NFT and the NFT configuration data of the target NFT. In this way, since the system 10 is configured to acquire the first data 101 related to the target NFT from the blockchain 20, the amount of first data 101 that needs to be transmitted from the terminal 31 can be reduced, thereby reducing the load on the terminal 31 and the user.

[0083] The acquirer 510 provides the first data 101 including the additionally acquired data to the input of the classification model 525 (step S73). Upon receiving the input of the first data 101, the classification model 525 outputs a classification result (determination result). The generator 530 generates determination data indicating the classification result (determination result) from the output of the classification model 525 (step S74).

[0084] FIG. 8 shows an example of an NFT 211, 212 including second data generated by the generator 530 of FIG. 4 or 6. The generator 530 may generate the NFT 211, 212 including the second data. The NFT 211, 212 including the second data indicating the assessment result of the target NFT can be traded in the same way as a normal NFT 62, 66. Therefore, for example, it is possible to sell the target NFT and an NFT indicating the assessment result of the target NFT (a certificate for the target NFT) as a set. In other words, the target NFT can be sold with a certificate certifying the authenticity of the target NFT.

[0085] 8, the NFTs 211 and 212 are created and stored at a third contract address 22D. Thus, the NFTs 211 and 212 have the contract address 22D. The contract address 22D is, for example, 0x223344. The contract address 22D is used by, for example, the generator 530 of the system 10 to generate the NFTs 211 and 212.

[0086] It is preferable that the NFTs 211, 212 are generated only by the system 10 and not by a third party (a party other than the certification authority). To achieve this, it is preferable that the contract address 22D be set so that data can be written for NFT generation or data addition only from a blockchain address corresponding to a private key held by the system 10 (certification authority). In this case, the NFTs 211, 212 stored in the contract address 22D are guaranteed to have been generated by the certification authority 80, improving their reliability as certificates.

[0087] Hereinafter, the NFTs 211 and 212 stored in the contract address 22C will be referred to as the proof NFTs 211 and 212. Here, the proof NFTs 211 and 212 are, as an example, NFTs that prove that the target NFT is a legitimate NFT. In FIG. 8, as an example, the proof NFT 211 is an NFT that proves NFT62 and has "nft_idcert01" as the token identifier (NFT_ID). Furthermore, the proof NFT 212 is an NFT that proves NFT66 and has "nftidcert02" as the token identifier (NFT_ID). Furthermore, the contract address 22C has "CERT" as the name for the recorded NFTs 211 and 212. In other words, in FIG. 8, the multiple proof NFTs 211 and 212 have the common name "CERT."

[0088] The NFT66 certified by the proof NFT212 is stored at contract address 22C and is a legitimate NFT. Contract address 22C is, for example, 0x554433 and has "BBB" as the name for the recorded NFT66.

[0089] The proof NFTs 211, 212 may include proof data 220 as NFT configuration data. The proof data 220 may include second data indicating the determination result by the determiner 520. The proof data 220 may include proof target NFT data 221 for identifying the NFT 62 to be certified. The proof target NFT data 221 may include, for example, the token identifier of the target NFT 62, 66. The proof target NFT data 221 may include the contract address 22A, 22C of the target NFT 62, 66.

[0090] The proof data 220 may include text data representing a statement for proof, such as "I certify that this NFT is authentic." The proof data 220 may also include the name of the certification authority 80.

[0091] For example, in response to the determination that the target NFT 62 is a legitimate NFT in step S52 of FIG. 5, the generator 530 can generate the NFT 211 in step S53 of FIG. 5. In this case, the first data 101 of the target NFT 62 can be used as the NFT data 221 to be certified. The generator 530 uses, for example, the NFT data 221 to be certified and text data corresponding to the determination result, such as "I certify that this NFT is authentic," as the digital data to be converted into an NFT. The generator 530 writes the digital data to be converted into an NFT (NFT configuration data) to the contract address 22D, thereby generating the NFT 211. The NFT 212 can also be generated in a similar manner.

[0092] The proof NFTs 211, 212 generated as described above contain the determination result of the target NFTs 62, 66 by the determiner 520, and can therefore function as certificates indicating the authenticity of the target NFTs 62, 66. A smart contract (not shown) stored in the contract address 22D may be used to generate the NFT. The smart contract can be called from the server 51, for example, and can generate the NFTs 211, 212 by obtaining NFT configuration data from the server 51 and writing the obtained NFT configuration data to the contract address 22D.

[0093] Furthermore, since the proof NFTs 211, 212 generated as described above have the NFT data 221 to be certified, the proof NFTs 211, 212 are associated with the NFTs 62, 66 to be certified. This association is recorded in the blockchain 20, making the association between the two highly reliable. The association between the proof NFTs 211, 212 and the NFTs 62, 66 to be certified may be recorded in the NFTs 62, 66 to be certified, for example. Furthermore, the association between the proof NFTs 211, 212 and the NFTs 62, 66 to be certified does not need to be recorded in the blockchain 20, and may be recorded in a computer outside the blockchain 20, such as the server 51.

[0094] The proof NFT 211, 212 may have a transaction record 230 of the NFT to be certified 62, 66 as NFT configuration data. The transaction record 230 may include, for example, a list of past and current owners of the NFT to be certified 62, 66 and the transaction date and time. The transaction record 230 may only include past transaction records of the NFT to be certified 62, 66 at the time the proof NFT 211, 212 was generated, or may include transaction records of the NFT to be certified 62, 66 after the proof NFT 211, 212 was generated. For the proof NFT 211, 212 to also have transaction records after its generation, the server 51 or the smart contract at the contract address 22D can write a transaction record of the NFT to be certified 62, 66 to the transaction record 230 every time the NFT to be certified 62, 66 is traded.

[0095] The transaction records 230 of the NFTs 62, 66 to be certified are recorded in the blockchain 20 without being recorded as transaction records 230 in the certification NFTs 211, 212. However, because the certification NFTs 211, 212 have transaction records 230, the owners of the certification NFTs 211, 212 can easily understand the transaction records of the NFTs 62, 66 to be certified by simply referring to the certification NFTs 211, 212.

[0096] Furthermore, the transaction records 230 of the NFTs 62, 66 to be certified do not have to be limited to the transaction records 230 recorded in the blockchain 20. For example, the transaction records 230 may include transaction records that are not recorded in the blockchain 20. The transaction records that are not recorded in the blockchain 20 are, for example, the transaction price of the NFTs 62, 66 to be certified or the name of the owner. The transaction records that are not recorded in the blockchain 20 are, for example, transaction records in an NFT marketplace. The marketplace transaction records are obtained, for example, from the marketplace server by the server 51 of the system 10 of the embodiment.

[0097] Note that multiple proof NFTs 211 may be generated for one certification target NFT 62. Furthermore, a proof NFT 211 indicating a transaction record for one certification target NFT 62 may be generated for each transaction, in which case the number of proof NFTs 211 generated may correspond to the number of transactions.

[0098] 9 illustrates an example of a usage scenario of the system 10 according to the embodiment. In FIG. 9, the system 10 provides the issuance of proof NFTs as a paid service, and is used by a user who wants to verify the authenticity of a target NFT. The user may be, for example, a person who wishes to purchase or sell a target NFT.

[0099] First, the user uses the terminal 31 to refer to the record of the target NFT in the blockchain 20 (step S91). Data of the target NFT (first data) is sent from the terminal 31 to the certification authority's server 51 (step S92). Upon receiving the data of the target NFT (step S93), the server 51 uses the data of the target NFT to determine the authenticity of the target NFT (step S94). The server 51 also executes a payment process to receive payment from the user for the issuance fee for the proof NFT, which is a certificate (step S95). The payment process S95 is, for example, a call to an external payment system. The payment is, for example, a credit card payment, an electronic money payment, a points payment, or a virtual currency payment. The timing of executing the payment process in step S95 is not particularly limited, and may be performed before step S94, before step S93, or after step S96.

[0100] For example, when the server 51 determines that the target NFT is a legitimate NFT and the payment process for issuing the certification NFT is completed, the server 51 generates a certification NFT (step S96). The certification NFT certifies that the target NFT is a legitimate NFT.

[0101] The generated proof NFT is sent to the user's blockchain address (step S97). The user can display the received proof NFT on the display of terminal 31 and check the proof content provided by the proof NFT (step S98). The proof content provided by the proof NFT can be made accessible to third parties, so that the proof content provided by the proof NFT can also be presented to third parties.

[0102] If a user is looking to purchase a target NFT, obtaining a proof NFT will incur a cost, but the user can purchase the target NFT with peace of mind. Also, if a user is looking to sell a target NFT, selling the target NFT with a proof NFT will increase the credibility of the target NFT and allow the user to expect it to sell for a higher price.

[0103] In addition to a certification authority, the system 10 may be operated by a company or individual that determines the authenticity of NFTs, or a company or individual that provides a service for determining the authenticity of NFTs for others. The system 10 may be used, for example, in an online NFT marketplace. A marketplace system can use the system 10 of the embodiment to determine the authenticity of NFTs listed on the marketplace and display the determination results on the marketplace along with the listed NFTs. This allows marketplace users to purchase NFTs with confidence, referring to the determination results.

[0104] Note that an NFT is not limited to simply digital data converted into an NFT, but may also be associated with a real-world object. The association between a real-world object and an NFT can be achieved, for example, by the system 10 having data indicating the association between the NFT and an identifier held by the real-world object. The association between an NFT and an identifier held by the real-world object can be achieved, for example, by the NFT having an identifier held by the real-world object. When a target NFT is associated with a real-world object, the verification NFT of the target NFT verifies the authenticity of the real-world object through verification of the authenticity of the target NFT.

[0105] The present invention is not limited to the above-described embodiment, and various modifications are possible. [Explanation of symbols]

[0106] 10: System 15: Network 20: Blockchain 22A: First contract address 22B: Second contract address 22C: Contract address 22D: Third contract address 31: Terminal 31A: Processor 31B: Storage device 31C: Computer Programs 32: Terminal 51: Server 51A: Processor 51B: Storage device 51C: Computer Program 61: Official digital content (NFT configuration data) 62: Official NFT 63: Official digital content (NFT configuration data) 64: Official NFT 66: Official NFT 71: Illegal digital content (NFT configuration data) 72: Fake NFT (non-genuine NFT) 73: Illegal digital content (NFT configuration data) 74: Fake NFT (non-genuine NFT) 80: Certificate Authority 101: First data 211: Proof of Concept NFT 212: Proof of Concept NFT 220: Proof data 221: NFT data to be certified 230: Transaction Record 510: Acquirer 520: Judgment device 521: Matcher 523A: First List (Whitelist) 523B: Second List (Blacklist) 525: Classification model 530: Generator C1: Artist / Creator C2: Illegal copyer

Claims

1. A system for determining non-fungible tokens in a blockchain, comprising: an acquirer that acquires first data related to a first non-fungible token to be determined; a determiner that determines the authenticity of the first non-fungible token based on the first data; a generator that generates second data indicating a determination result by the determiner; Equipped with The determiner is configured to determine the authenticity of the first non-fungible token using at least one of a first list of legitimate non-fungible tokens and a second list of illegitimate non-fungible tokens. Judging system.

2. A system for determining non-fungible tokens in a blockchain, comprising: an acquirer that acquires first data related to a first non-fungible token to be determined; a determiner that determines the authenticity of the first non-fungible token based on the first data; a generator that generates second data indicating a determination result by the determiner; Equipped with The determiner is configured to determine the authenticity of the first non-fungible token by providing the first data to a classification model configured to classify non-fungible tokens. Judging system.

3. The acquirer is configured to acquire the first data from a user terminal connected via a network. The determination system according to claim 1 or 2.

4. The acquirer is configured to acquire the first data from a blockchain on which the first non-fungible token is recorded. The determination system according to claim 1 or 2.

5. The second data includes a second non-fungible token recorded on the blockchain, the second non-fungible token having the determination result. The determination system according to claim 1 or 2.

6. The second non-fungible token further comprises a transaction record of the first non-fungible token. The determination system according to claim 5 .

7. When the determiner determines that the first non-fungible token is a genuine non-fungible token, the generator is configured to generate the second data including proof data that the first non-fungible token is a genuine non-fungible token. The determination system according to any one of claims 1 to 6.

8. A method for generating judgment data for non-fungible tokens in a blockchain, comprising: obtaining, by a generation system, first data relating to the first non-fungible token to be determined; determining, by the generation system, the authenticity of the first non-fungible token based on the first data; The generation system generates determination data indicating a determination result regarding the authenticity of the first non-fungible token. Prepare for this. The determining of authenticity includes determining the authenticity of the first non-fungible token using at least one of a first list of legitimate non-fungible tokens and a second list of illegitimate non-fungible tokens. Generation method.

9. The determination data includes a second non-fungible token recorded on the blockchain, the second non-fungible token having the determination result. The method of claim 8.

10. The second non-fungible token is associated with the first non-fungible token. The method of claim 9.

11. A method for generating judgment data for non-fungible tokens in a blockchain, comprising: obtaining, by a generation system, first data relating to the first non-fungible token to be determined; determining, by the generation system, the authenticity of the first non-fungible token based on the first data; The generation system generates determination data indicating a determination result regarding the authenticity of the first non-fungible token. Prepared for this, determining the authenticity of the first non-fungible token by subjecting the first data to a classification model configured to classify non-fungible tokens; Generation method.

Images