Method and system including computer-implemented steps

Abstract

To provide a method for reducing complexity when executing processing of a plurality of non-fungible tokens.SOLUTION: A method including the steps executed by a computer, the method causes one or a plurality of computers to: read a plurality of codes provided in each of a plurality of articles with a reader so as to acquire the plurality of codes; and execute batch processing of the plurality of non-fungible tokens corresponding to the plurality of acquired codes.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] The present disclosure relates to a method and a system including steps executed by a computer.

Background Art

[0002] Patent Document 1 discloses that a smart contract implemented on a blockchain executes an operation on a non-fungible token identified by an identifier included in the code assigned to an object.

[0003] Patent Document 2 discloses receiving a unique identifier of an object and generating a non-fungible token.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

[0005] There may be a case where it is desired to execute processing on a plurality of non-fungible tokens. For example, when transferring a plurality of articles, there may be a case where it is desired to transfer a plurality of non-fungible tokens associated with the plurality of articles. However, if it is only possible to read the code provided in one article and execute processing on one non-fungible token corresponding to that code, then when there are a plurality of articles, the work of a user or the like increases and becomes complicated as the number of articles increases.

[0006] Thus, when attempting to execute processing on a plurality of non-fungible tokens, the complexity increases.

[0007] Therefore, when executing processing on a plurality of non-fungible tokens, it is desirable to reduce the complexity.

[0008] One aspect of the present disclosure is a method. The disclosed method is a method including steps executed by a computer, the steps including: one or more computers obtaining a plurality of codes by reading, with a reader, the codes provided in each of the plurality of articles, and performing batch processing on a plurality of non-fungible tokens corresponding to the obtained plurality of codes.

[0009] Another aspect of the present disclosure is a system. The disclosed system is configured to obtain a plurality of codes by reading, with a reader, the codes provided in each of the plurality of articles, and perform batch processing on a plurality of non-fungible tokens corresponding to the obtained plurality of codes.

[0010] Further details will be described as embodiments hereinafter.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Modes for Carrying Out the Invention

[0012] <Overview of the Method and System Executed by the Computer>

[0013] (1) The method according to the embodiment can be a method including steps executed by a computer. The steps may include one or more computers obtaining a plurality of codes by reading, with a reader, the codes provided in each of the plurality of articles, and performing batch processing on a plurality of non-fungible tokens corresponding to the obtained plurality of codes. By the batch processing, since a plurality of non-fungible tokens are processed collectively, the complexity is reduced.

[0014] The plurality of non-fungible tokens corresponding to the plurality of codes may be a plurality of non-fungible tokens generated corresponding to the plurality of codes, or may be a plurality of generated non-fungible tokens corresponding to the plurality of codes. The batch processing on the plurality of non-fungible tokens may be generating a plurality of non-fungible tokens, or may be processing on the plurality of generated non-fungible tokens, or may be both generating and other processing (such as transfer processing) on the non-fungible tokens.

[0015] The batch processing may include non-fungible token processing that is collectively executed for each of the plurality of non-fungible tokens. The non-fungible token processing that is collectively executed for each of the plurality of non-fungible tokens may be the same processing.

[0016] The batch processing may include collectively executing a plurality of non-fungible token processes. Each of the plurality of non-fungible token processes may include a process executed on a blockchain for a non-fungible token corresponding to the obtained code. The batch processing may include non-fungible token processes executed on a blockchain for each of the plurality of non-fungible tokens corresponding to the obtained plurality of codes. A non-fungible token is, for example, a transfer of ownership of a non-fungible token, setting / modifying / deleting a user of a non-fungible token, or generation of a non-fungible token.

[0017] (2) Preferably, the batch processing includes associating the same blockchain address with each of the plurality of non-fungible tokens. Associating a blockchain address with a non-fungible token is, for example, associating a transfer destination blockchain address with the non-fungible token.

[0018] In the batch processing, it is preferable to record the same blockchain address on the blockchain as at least one of the owner and the user of each of the plurality of non-fungible tokens in the non-fungible token process executed for each of the plurality of non-fungible tokens.

[0019] In the batch processing, it is preferable that the non-fungible token process executed for each of the plurality of non-fungible tokens includes changing at least one of the owner and the user recorded on the blockchain of each of the plurality of non-fungible tokens.

[0020] (3) The process may further include providing, for display on a display device, confirmation display data for confirming whether to permit execution of the batch process. For example, in the case of transfer of a non-fungible token, the confirmation display data may be displayed on either one or both of the source terminal and the destination terminal. It is preferable that the batch process is executed after a user operation for permitting execution of the batch process is performed.

[0021] The non-fungible token is a rental non-fungible token, and preferably, the non-fungible token process includes a process of changing the user of the rental non-fungible token.

[0022] (4) Preferably, the process further includes the one or more computers providing, for display on a display device, display data. The display data may include confirmation display data. The confirmation display data may include at least one or both of value display data indicating the total value of value data associated with each of the plurality of non-fungible tokens and a breakdown of the total value, the code corresponding to each of the plurality of non-fungible tokens, data regarding the article having the code corresponding to each of the plurality of non-fungible tokens, and the plurality of non-fungible tokens. The confirmation display data may include at least one or more data selected from the group consisting of.

[0023] The confirmation display data may include at least the value display data. The value data may be data recorded on a blockchain in association with each of the plurality of non-fungible tokens. The value data may indicate the value of the article having the code corresponding to the non-fungible token with which the value data is associated.

[0024] (5) Preferably, the batch process is executed after receiving a user operation that is performed after acquiring the plurality of codes.

[0025] (6) The article may be a casino article provided to a player in a casino. The method may be performed for registering the transfer of the casino article.

[0026] (7) The system according to an embodiment may be configured to acquire a plurality of codes by reading, by a reader, the codes provided in each of the plurality of articles, and execute a batch process on a plurality of non-fungible tokens corresponding to the acquired plurality of codes.

[0027] <2. Examples of a method and a system executed by a computer>

[0028] FIG. 1 shows an example of the distribution of casino articles provided to a player in a casino. Here, the casino article is, as an example, a prize provided to the player. The prize is, as an example, a special prize in the three-store system. The special prize is an article handled by a merchant in the three-store system, and is an article that can be exchanged by the player for pachinko balls or cash, etc.

[0029] The merchants in the three-store system are casino 1A, 1B, prize exchange 2, and prize wholesalers 3A, 3B. Here, the casino may be a company that operates one or more casinos (stores), or may be an individual casino (store). The prize exchange may be a company that operates one or more prize exchanges (stores), or may be an individual prize exchange (store). The prize wholesaler may be a company that operates one or more prize wholesalers (stores), or may be an individual prize wholesaler (store).

[0030] A player 4 such as a pachinko player obtains prizes by exchanging pachinko balls for prizes at a game arcade 1A such as a pachinko parlor. That is, prizes are provided from the game arcade 1A to the player 4. The player 4 can exchange the prizes for property values such as legal tender or cryptocurrency at the prize exchange 2. That is, the player 4 can sell special prizes to the prize exchange 2 and obtain property values such as electronic money or points as consideration therefor.

[0031] The property value (for example, electronic money or points) exchanged for an item such as a prize is transmitted to the wallet application of the player 4. The wallet application is application software for managing property values. The player 4, who is a user of the wallet application, can withdraw the property value deposited in the wallet application or use it for settlement for payment.

[0032] The prize wholesaler 3 purchases prizes from the prize exchange 2 and wholesales them to the game arcades 1A, 1B. The prize wholesaler 3 can also purchase prizes from the prize manufacturer 5 and wholesale them to the game arcades 1A, 1B. The prize manufacturer 5 manufactures and sells prizes.

[0033] In this way, prizes transfer in a distribution route including the game arcades 1A, 1B, the prize exchanges 2, and the prize wholesalers 3.

[0034] The prize manufacturer 5 can be, for example, the system administrator 5 of the system 10 according to the embodiment. The prizes according to the embodiment are attached with non-fungible tokens of the blockchain. A non-fungible token (NFT) has a unique token identifier (TokenID) in the blockchain 2 for ensuring non-fungibility. The token identifier enables distinction from other NFTs. The non-fungible token is attached to the prize, for example, by recording in a computer the correspondence between the code provided in the prize and the identifier provided in the non-fungible token.

[0035] The system 10 according to the embodiment may be a casino item management system 10. The system 10 is constituted by, for example, one or a plurality of computers. As shown in FIG. 2, the system 10 may include, as an example, a server 51 and terminals 31. The terminals 31 can access the server 51 via a network 15 such as the Internet. The server 51 is managed and operated by a system administrator 5. The system 10 may utilize a blockchain 20. The system 10 may include the blockchain 20.

[0036] The terminal 31 may include, as an example, a casino terminal 31-1, an exchange terminal 31-2, and a prize wholesaler terminal 31-3. The casino terminal 31-1 is a terminal installed in the casinos 1A, 1B or a terminal used by the staff of the casinos 1A, 1B. The exchange terminal 31-2 is a terminal installed in the exchange 2 or a terminal used by the staff of the exchange 2. The prize wholesaler terminal 31-3 is a terminal installed in the prize wholesaler 3 or a terminal used by the staff of the prize wholesaler 3.

[0037] The terminal 31 may include, as an example, a player terminal 31-4. The player terminal 31-4 is a terminal used by the player 4.

[0038] Note that the casinos 1A, 1B, the prize exchange 2, the prize wholesaler 3, and the player 4 are users of the system 10. Therefore, each of the terminals 31-1, 31-2, 31-3, 31-4 may be called a user terminal.

[0039] The terminal 31 is used, as an example, as a transfer source terminal for a prize (item) or an NFT. The transfer source terminal may be called a seller terminal. Also, the terminal 31 is used, as an example, as a transfer destination terminal for a prize (item) or an NFT. The transfer destination terminal may be called a buyer terminal. For example, when a prize is transferred from the player 4 to the exchange 2, the player terminal 31-4 is used as the transfer source terminal, and the exchange terminal 31-2 is used as the transfer destination terminal.

[0040] The blockchain 20 is composed of a P2P (Peer to Peer) computer network. The blockchain 20 preferably enables the rental of NFTs. The rental of NFTs means renting an NFT to a user other than the owner of the NFT. By renting an NFT, a user other than the owner of the NFT can use the NFT.

[0041] The rental function of NFTs is defined, for example, in the Ethereum EIP4907 standard. EIP4907 is an extension of the Ethereum token standard ERC721. On Ethereum or a blockchain compliant with Ethereum, NFTs can be rented based on EIP4907.

[0042] In EIP4907, the role of "user" is added. The EIP4907 "user" is the lessee of the rented NFT and the user of the rented NFT. The EIP4907 "user" is different from the owner of the non-fungible token and cannot transfer the non-fungible token. However, the EIP4907 "user" can use the non-fungible token in the same way as the owner. Thus, the EIP4907 "user" has restricted rights to the non-fungible token compared to the owner.

[0043] In the blockchain 20, transactions are possible between blockchain addresses. The transaction of the transaction is recorded in the distributed ledger of the blockchain 20. The blockchain address indicates, for example, an account in the blockchain 20. The blockchain address is, for example, a wallet address. The blockchain address is, for example, an Externally Owned Account (EOA). For example, if a user has an account in the blockchain 20, that account has a predetermined blockchain address (wallet address).

[0044] In FIG. 3, as an example, the blockchain address 25A of the game arcade 1A, the blockchain address 25B of the prize exchange 2, the blockchain address 25C of the prize wholesaler 3, and the blockchain address 25D of the player 4 are shown. These addresses 25A, 25B, 25C, and 25D are the user's wallet addresses. By setting the addresses 25A, 25B, 25C, and 25D of the game arcade 1A, the prize exchange 2, the prize wholesaler 3, and the player 4 in the blockchain 20, transactions in which these users 1A, 2, 3, and 4 are involved can be recorded in the blockchain 20.

[0045] Also, in FIG. 3, the blockchain address 25E of the administrator 5 is shown. This blockchain address 25E is the wallet address of the administrator 5. By setting the address 25E of the administrator 5 in the blockchain 20, transactions in which the administrator 5 is involved can be recorded in the blockchain 20.

[0046] In FIG. 3, the address 25A of the game arcade 1A is "0x1111". The address 25B of the prize exchange 2 is "0x2222". The address 25C of the prize wholesaler 3 is "0x3333". The address 25D of the player 4 is "0x4444". The address 25E of the administrator 5 is "0x1234". In FIG. 3, although only one address each of the game arcade, the prize exchange, the prize wholesaler, and the player, i.e., 25A, 25B, 25C, and 25D, is set, since there can be a plurality of game arcades, prize exchanges, prize wholesalers, and players respectively, a plurality of each may be set. That is, in the blockchain 20, addresses of a plurality of each of the game arcades, prize exchanges, prize wholesalers, and players can be set.

[0047] In blockchain 20, for example, token transactions are possible. Token transactions are recorded on blockchain 20. Tokens that can be traded on blockchain 20 include, for example, fungible tokens (fungible tokens; FT) and non-fungible tokens (non-fungible tokens; NFT). Fungible tokens are, for example, cryptocurrency assets (native tokens) such as Ether in Ethereum. Fungible tokens may also be unique fungible tokens issued on the blockchain by a specific issuer such as a company or an individual.

[0048] In blockchain 20, tokens are recorded in association with the blockchain addresses of their owners. For example, non-fungible tokens or fungible tokens owned by users 1A, 2, 3, 4 or administrator 5 are recorded in association with the blockchain addresses 25A, 25B, 25C, 25D, 25E of users 1A, 2, 3, 4 or administrator 5.

[0049] The addresses 25A, 25B, 25C, 25D, 25E set in blockchain 20 can be recorded on blockchain 20 in association with the transferred NFT as the transfer source address or transfer destination address of tokens such as NFTs in the record of NFT transactions. For example, when an NFT is transferred from player 4 to exchange 2, it is recorded on blockchain 20 that the NFT has been transferred from the address of player 4 (0x4444: transfer source address) to the address of the exchange (0x2222: transfer destination address).

[0050] The blockchain 20 may include a smart contract 22. The system 10 may include a smart contract 22 implemented on the blockchain 20. The smart contract 22 is composed of software (computer program) implemented to be executable on the blockchain. The smart contract 22 automatically executes a predetermined protocol such as an automatic transaction. The smart contract 22 of the embodiment may execute a process for transmitting an NFT (transfer of ownership or usage right) or a process for generating an NFT.

[0051] The aforementioned blockchain address may indicate the contract address of the smart contract 22. The contract address is the blockchain address where the smart contract 22 is stored. In FIG. 3, the contract address of the smart contract is, as an example, "0x8888".

[0052] The smart contract 22 executes a predetermined process, for example, when called from a computer outside the smart contract 22. The smart contract 22 is called, for example, by the administrator 5 or the users 1A, 2, 3, 4.

[0053] The process executed by the smart contract 22 is, for example, an operation of a token. The operation of the token is, for example, a change of the token owner or a change of the token user (user setting). The operation of changing the token owner or the token user may be called the transmission of the token. That is, changing the token owner from the first blockchain address to the blockchain address may also be sending the token from the first blockchain address to the second blockchain address.

[0054] In an embodiment, as an example, prizes 401, 402, 403 (articles) are used for such transmission and reception of NFTs. In other words, in the embodiment, as the prizes 401, 402, 403 are transferred, the NFTs are also transferred. Note that the prizes 401, 402, 403 are attached with characters or symbols indicating the name or type of the prize. The characters or symbols indicating the name or type of the prize are, for example, "AAA" for the prize 401, "BBB" for the prize 402, and "CCC" for the prize 403. As an example, the prizes 401, 402, 403 are purchased at a predetermined price, and the characters or symbols indicating the name or type of the prize may also be the characters or symbols indicating the price. For example, the price of the prize 401 of "AAA" is ¥5,000, the price of the prize 402 of "BBB" is ¥2,500, and the price of the prize 403 of "CCC" is ¥1,000. Note that the prizes 401, 402, 403 may be attached with the price itself of the prize.

[0055] Note that the operation of the token is not limited to changing the owner (sending) of the token, and any process related to the token is sufficient. The operation of the token may be, for example, the generation (issuance) of a non-fungible token.

[0056] As shown in FIG. 4, the server 51 can 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, a 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 codes indicating instructions for causing the computer to execute various processes such as a registration process 51F described later.

[0057] The storage device 51B of the server 51 may include a corresponding data table 51E. The corresponding data table 51E shows the correspondence between the code described later and the token identifier of the NFT. The code and the NFT are associated with each other by the corresponding data table 51E.

[0058] Since the correspondence between the code and the NFT is recorded in the corresponding data table 51E, it becomes possible to use an article (such as a prize) having the code for the operation of the NFT. That is, the code included in the article can be used as the identifier of the NFT to be operated. The server 51 can identify the NFT corresponding to the code by referring to the corresponding data table 51E. The server 51 can perform processing on the identified NFT.

[0059] As an example, the code is a unique identifier. The code may be composed of any one of symbols, characters, and numbers or a combination thereof. In FIG. 4, as an example, the code (unique identifier): 00:00:00:00:00:0a is associated with the token identifier: token_id01, the code: 00:00:00:00:00:0b is associated with the token identifier: token_id02, and the code: 00:00:00:00:00:0c is associated with the token identifier: token_id03.

[0060] The corresponding data indicating the correspondence between the code and the token identifier may be recorded in a computer outside the blockchain 20 other than the server 51, or may be recorded in the blockchain 20. The corresponding data may be included in the data constituting the NFT recorded in the blockchain 20.

[0061] As shown in FIG. 4, the terminal 31 may be configured by a computer including a processor 31A and a storage device 31B. The computer that can configure the terminal 31 is, for example, a personal computer, a smartphone, a tablet, or a wearable device.

[0062] 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, a RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The storage device 31B stores a computer program 31C to be 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 codes that indicate instructions for causing a computer to execute various processes such as a registration process 31F described later.

[0063] The terminal 31 includes a reader 31D for reading a code. The reader 31D is connected to the processor 31A and can transmit the read code to the processor 31A. The reader 31D may be built into the terminal 31 or may be externally attached to the terminal 31.

[0064] The reader 31D may read a code by wireless communication or may read a code by a camera or other optical sensor. The code read by the reader 31D may be represented in a machine-readable format such as a two-dimensional code like a QR code (registered trademark). In this case, the original code can be obtained by decoding the two-dimensional code.

[0065] The code read by the reader 31D may be provided on an article. The article having the code is, for example, the aforementioned gaming hall article, and more specifically, a prize (special prize) in the gaming hall. That is, the special prize according to the embodiment has a code that can be read by the reader 31D.

[0066] The type of medium on which the code is recorded is not particularly limited. As an example, the medium having the code is an integrated circuit 40 (IC) having the code. The code can be a unique identifier or other data recorded in the integrated circuit 40. The integrated circuit 40 may be, for example, an integrated circuit module (IC module) equipped with a memory for storing data such as a unique identifier and configured to be able to communicate data such as a unique identifier with the outside. Depending on its form, the integrated circuit module 40 may be called an integrated circuit tag (IC tag) or an integrated circuit card (IC card).

[0067] The integrated circuit module 40 may be a contact type or a non-contact type. The contact integrated circuit module (contact IC module) has a contact with an external communication device such as a reader / writer device, and can communicate by the contact contacting the external communication device. The non-contact integrated circuit module 40 (non-contact IC module 40) has an antenna and can communicate non-contact with the reader 31D.

[0068] The reader 31D is preferably configured to be able to read a plurality of codes at once. For example, the reader 31D preferably has a batch reading function of reading codes from each of a plurality of IC modules 40 (integrated circuits 40) by wireless communication. The reader 31D having the batch reading function can, for example, irradiate radio waves for reading and read codes and the like transmitted from each of the plurality of IC modules within the irradiation range of the radio waves. By using the reader 31D having the batch reading function, a large number of codes can be read at once, improving work efficiency.

[0069] As shown in FIG. 5, the integrated circuit 40 includes a memory 44 that stores data such as a unique identifier. The memory 44 is, for example, a read-only memory (ROM). The unique identifier 46 of the integrated circuit 40 is preferably stored in the read-only memory. The memory 44 preferably includes a non-volatile memory. The non-volatile memory 44 may constitute a read-only memory. The unique identifier 46 of the integrated circuit 40 is preferably stored in the non-volatile memory 44. The non-volatile memory 44 is, for example, a mask ROM, PROM, EPROM, EEPROM, or FeRAM, or a flash memory.

[0070] The unique identifier 46 of the integrated circuit 40 is preferably a non-rewritable unique identifier assigned to the integrated circuit 40 by the manufacturer of the integrated circuit 40. The unique identifier 46 (Unique Identifier: UID) of the integrated circuit 40 is used to identify the integrated circuit 40 separately from other integrated circuits. The unique identifier 46 (UID) assigned by the manufacturer to the integrated circuit 40 is written, for example, into the memory 44 during the manufacture of the integrated circuit 40. The unique identifier 46 is written into the memory 44 at least by the time the manufacturer ships the integrated circuit 40. The memory 44 of the integrated circuit 40 may have an area where the purchaser or user of the integrated circuit 40 can write data. Other data read by, for example, the reader 31D may be written into the memory area where the user or the like can write data.

[0071] A non-contact IC module having a unique identifier is also called a Radio Frequency Identification (RFID) device. The RFID device wirelessly transmits data such as a unique identifier to an external wireless communication device such as a reader 31D. The data to be transmitted is the data recorded in the memory 44 and may include data used by the system 10 to identify the NFT to be operated. The reader 31D can read the unique identifier by receiving data such as the unique identifier transmitted from the RFID device. When the RFID device has a tag form, it may also be called an RFID tag.

[0072] The RFID device may be a Near Field Communication device. The near field communication preferably conforms to the NFC standard. NFC is, for example, wireless communication using a frequency in the 13.56 MHz band. The communication distance of the near field communication is preferably 10 cm or less. When the Near Field Communication (NFC) device has a tag form, it may also be called a Near Field Communication (NFC) tag.

[0073] The medium with the code is not limited to an integrated circuit having a unique identifier and may be other media indicating the code. The code may be, for example, printed.

[0074] As shown in FIG. 4, the NFC tag 40 includes an antenna 41, a wireless circuit 42 connected to the antenna 41, a controller 43 connected to the wireless circuit 42, and a memory 44 connected to the controller 43. The unique identifier 46 of the NFC tag 40 is written in the memory 44. Other data may be written in the memory 44. The memory 44 is, for example, a non-volatile memory such as EEPROM.

[0075] In an embodiment, as an example, prize items 401, 402, 403 that are casino items each incorporate an NFC tag 40 with a code.

[0076] As shown in FIG. 6, in the embodiment, as an example, codes and the like are transmitted from the NFC tag 40 to the terminal 31 including the reader 31D. For example, a staff member of the amusement arcade 1A, a staff member of the prize exchange place 2, a staff member of the prize wholesaler, or the player 4 holds the reader 31D of the terminal 31 (31-1, 31-2, 33-3, 33-4) over the NFC tag 40, and data such as the unique identifier 46 (code) is transmitted to the terminal 31 by short-range wireless communication. The unique identifier 46 (code) read by the reader 31D is transmitted to the server 51. The unique identifier 46 (code) read by the reader 31D can be used to identify the NFT corresponding to the code in the system 10.

[0077] A plurality of prizes 401, 402, 403 are stored, for example, in the prize storage unit 450 for batch reading of codes. The storage unit 450 has, for example, an electromagnetic shielding function, and can limit the objects for code reading to the articles 401, 402, 403 inside the storage unit 450.

[0078] The reader 31D reads a code (unique identifier) from each of the NFC tags 40 of one or more prizes 401, 402, 403 stored in the storage unit 450. The terminal 31 that has acquired one or more codes via the reader 31D can transmit the acquired codes to the server 51.

[0079] The system 10 of the embodiment can execute processing on the NFT corresponding to the code read by the reader 31D. Further, when the reader 31D reads a plurality of codes in batch, the system 10 can collectively execute the processing 51F on the plurality of NFTs corresponding to the plurality of codes read in batch.

[0080] FIG. 7 shows an example of batch processing 51F for a plurality of NFTs corresponding to a plurality of codes. Batch processing is to execute a plurality of processes together. Here, the process for one NFT is referred to as "non-fungible token processing" or "NFT processing". In this case, batch processing for a plurality of NFTs is to execute a plurality of NFT processes together.

[0081] By batch processing 51F for a plurality of NFTs, the processes for the plurality of NFTs can be automatically executed collectively. Therefore, there is no need for an operation to execute the processes for each of the plurality of NFTs one by one, avoiding complexity and improving the efficiency of the processes. Also, in the embodiment, since a plurality of NFTs are identified by a plurality of codes obtained by batch reading, a plurality of NFTs to be the target of batch processing can be efficiently specified. That is, in the embodiment, even for processes for a plurality of NFTs, the burden on the user can be made comparable to that for one NFT. For example, a plurality of codes can be read by a single reading operation, and a plurality of NFTs corresponding to the plurality of codes can be processed collectively by batch processing.

[0082] NFT processing includes processes recorded in blockchain 20. By batch processing a plurality of NFT processes, for a plurality of NFTs, they can be recorded collectively in blockchain 20.

[0083] Regarding NFTs, the processes recorded in the blockchain are, for example, the transfer of NFTs. The transfer of NFTs is, for example, the change of the owner of the NFT. The transfer of NFTs may be the change of the user (borrower) of the rental NFT.

[0084] As shown in FIG. 7, by executing the batch process 51F, a plurality of NFTs can be transferred in a batch in the blockchain 20. In FIG. 7, before the NFT transfer, four NFTs are associated with the transfer source address (0x1111). Therefore, the transfer source address (0x1111) is the owner or user (borrower) of the four NFTs. The token identifiers (TokenID) of the four NFTs of the transfer source address are token_id01, token_id02, token_id03, and token_id04, respectively.

[0085] In the example shown in FIG. 7, a plurality of NFTs are transferred in a batch from the transfer source (current owner or user) to the transfer destination (new owner or user) by the batch process. In FIG. 7, for the transfer of a plurality of NFTs, the codes of the NFC tags 40 of the prizes 401, 402, and 403 are read in a batch by the reader (see also FIG. 6). Here, 00:00:00:00:00:0a is recorded as the code (unique identifier) in the tag 40 of the prize 401. 00:00:00:00:00:0b is recorded as the code (unique identifier) in the tag 40 of the prize 402. 00:00:00:00:00:0c is recorded as the code (unique identifier) in the tag 40 of the prize 403.

[0086] As shown in Table 51E of FIG. 4, token_id01 is associated with the code: 00:00:00:00:00:0a, token_id02 is associated with the code: 00:00:00:00:00:0b, and token_id03 is associated with the code: 00:00:00:00:00:0c. Therefore, the system 10 can identify a plurality of NFTs (token_id01, token_id02, token_id03) to be batch-processed from a plurality of codes (00:00:00:00:00:0a, 00:00:00:00:00:0b, 00:00:00:00:00:0c) read in batch by referring to Table 51E. The system 10 executes a batch process of transferring (sending) the identified plurality of NFTs from the transfer source address to the transfer destination address. In FIG. 7, among the four NFTs (token_id01, token_id02, token_id03, token_id04) owned by the transfer source address, three NFTs (token_id01, token_id02, token_id03) corresponding to the three read codes are batch-transferred to the transfer destination address.

[0087] The transfer (sending) of a plurality of NFTs is recorded on the blockchain 20. The record on the blockchain 20 may include the transfer source address and the transfer destination address for each NFT. Note that in the transfer of an NFT, the transfer destination of the NFT can be specified by a user or the like as appropriate. Also, in the transfer of an NFT, it is not necessary for the NFT to be directly transferred from the transfer source to the transfer destination, and it may be transferred from the transfer source to the transfer destination via an intermediate address. The intermediate address can be, for example, the contract address of the smart contract 22.

[0088] In the batch process, the NFT processing for each of the plurality of NFTs does not have to be executed simultaneously and may be executed sequentially during the batch process.

[0089] Figure 8 shows an example of the procedure of the registration process 51F for the transfer of casino items using batch processing. The system 10 according to the embodiment can be a management system 10 that manages the transfer of casino items such as prizes 401, 402, 403. The system 10 transfers the corresponding NFTs along with the transfer of casino items such as prizes 401, 402, 403. Therefore, the transfer of casino items can be recorded on the blockchain 20 as the transfer of NFTs. Since the record on the blockchain 20 is difficult to tamper with, recording the transfer of casino items on the blockchain 20 can enhance the reliability and transparency of the record. Note that the process 51F shown in Figure 8 can also be understood as a process for simply batch-transferring a plurality of NFTs, apart from the registration of the transfer of items such as prizes.

[0090] The blockchain 20 may record the code of the item to be transferred together with the transfer destination. However, by recording the transfer of the item as the transfer of the NFT corresponding to the item, the infrastructure regarding the NFT in the blockchain 20 can be utilized.

[0091] The registration process 51F in Figure 8 is executed by one or more computers included in the system 10. Hereinafter, as an example, the server 51 and the terminal 31 cooperate to execute the registration processes 51F and 31F. However, the registration process 51F may be executed by the terminal 31 alone, or may be executed by the server 51 via the terminal 31. Also, a part of the registration process may be executed by the smart contract 22. The smart contract 22 is called from the server 51 or the terminal 31, etc., and executes a predetermined process in the blockchain 20. The smart contract 22 executes, for example, an NFT process 22A such as NFT transfer.

[0092] The smart contract 22 may be configured to execute the processing in the blockchain 20 for each specified single NFT every time it is called. In this case, in the batch processing of a plurality of NFTs, the smart contract 22 is called as many times as the number of NFTs to be processed from a server 51 or the like that executes the batch processing. Also, the smart contract 22 may be configured to collectively execute the processing in the blockchain 20 for a plurality of specified NFTs in one call. That is, the smart contract 22 may also be configured to perform batch processing. In this case, by calling the smart contract 22 once, transfers of a plurality of NFTs and the like can be performed collectively.

[0093] In the registration processes 51F and 31F shown in FIG. 8, in step S81, the server 51 acquires a plurality of codes read by the reader 31D. The codes are acquired from the prizes 401, 402, and 403 to be transferred. For example, the read codes and the like can be acquired by the terminal 31 and transmitted from the terminal 31 to the server 51. The terminal 31 (reader 31D) that reads the code may be the transfer source terminal 31 (reader 31D) or the transfer destination terminal 31 (reader 31D). Also, the codes may be read by both the transfer source and transfer destination terminals 31, 31.

[0094] In step S82, the server 51 acquires transfer party information. The transfer parties include the transfer source and the transfer destination. The transfer party information is represented by, for example, the blockchain address of the transfer party or data that can identify the blockchain address, and other data that can identify the transfer party. Since the transfer source is the current owner or user of the NFT corresponding to the code, the server 51 can acquire the blockchain address of the transfer source by referring to the blockchain address associated with the NFT corresponding to the acquired code. The server 51 may receive transfer source information such as the blockchain address of the transfer source transmitted from the transfer source or transfer destination terminal 31.

[0095] System 10 can obtain transfer destination information from the terminal 31 at the transfer destination. For example, the terminal 31 at the transfer destination sends its blockchain address (e.g., 0x2222) to System 10. Thereby, System 10 can obtain the transfer destination information. For example, when the code is read by the terminal 31 at the transfer destination, the terminal 31 at the transfer destination can send the blockchain address of the terminal 31 at the transfer destination, etc. to the server 51 together with the code. The server 51 can identify the transfer source from the code and identify the blockchain address sent together with the code as the transfer destination.

[0096] Also, System 10 can obtain transfer destination information from the terminal 31 at the transfer source. For example, the terminal 31 at the transfer destination gives the blockchain address of the transfer destination to the terminal 31 at the transfer source by wireless communication or the like. The terminal 31 at the transfer source can send the obtained blockchain address of the transfer destination to System 10. For example, when the code is read by the terminal 31 at the transfer source, the terminal 31 at the transfer source obtains the blockchain address of the transfer destination from the terminal 31 at the transfer destination by wireless communication or the like, and can send the obtained blockchain address of the transfer destination to the server 51 together with the read code.

[0097] In the embodiment, the transfer party information is information common to a plurality of NFTs to be processed. In batch processing, the same NFT processing is executed for a plurality of NFTs. The same NFT processing is, for example, a process of transferring each of a plurality of NFTs to the same transfer destination indicated by the transfer destination information common to the plurality of NFTs. Since a plurality of NFTs are transferred to the same transfer destination by batch processing, the user does not need to perform an operation of setting a transfer destination for each of the plurality of NFTs, and the operation becomes easier. Also, in batch processing, since the same NFT processing is executed for a plurality of NFTs, the user does not need to perform an operation of specifying the type of NFT processing to be performed on each of the plurality of NFTs or an operation of selecting whether to execute each NFT processing, and the operation becomes easier.

[0098] The terminal 31 or the server 51 executes processing for displaying display data including the reading result and the like on the display device (step S83). The display device is, for example, a display included in the terminal 31. FIG. 9 shows the display data 91 and 92 to be displayed on the display device. The display data 91 and 92 are provided from the server 51 or the like to the display device of the terminal 31 for screen display.

[0099] FIG. 9 shows the first display data 91 and the second display data 92. The first display data 91 can be displayed on the display device of the terminal 31 of the transfer source (for example, the seller of the prize). The second display data 92 can be displayed on the display device of the terminal 31 of the transfer destination (for example, the buyer of the prize).

[0100] Each of the first display data 91 and the second display data 92 can be confirmation display data for confirming whether to execute the transaction process of the NFT corresponding to the read code.

[0101] The first display data 91 is, for example, displayed on the display device of the terminal 31 of the transfer source after the code is read by the terminal 31 of the transfer source. For example, when the server 51 acquires the read codes (00:00:00:00:00:0a, 00:00:00:00:00:0b, 00:00:00:00:00:0c), it identifies the NFTs (token_id01, token_id02, token_id03) corresponding to the codes as processing targets.

[0102] The server 51 acquires the amount (value data) associated with each of the NFTs to be processed. The amount is the selling price (buying price) of the prize with NFT. The amount (value data) may be a numerical value in units of fiat currency, a numerical value in units of cryptocurrency, or other data having electronic value. The amount may be regarded as the selling price (buying price) of the NFT alone or the selling price (buying price) of the prize alone. Note that the selling price (buying price) may vary depending on the transfer parties. The amount associated with each NFT may be set for each transfer party. This will be described later.

[0103] The amount associated with the NFT may be recorded on the server 51 or other computers outside the blockchain in association with the NFT, or may be recorded on the blockchain in association with the NFT. Since it is difficult to tamper with the data recorded on the blockchain 20, if the amount associated with the NFT is recorded on the blockchain 20, it is possible to prevent the tampering of the amount and ensure the transparency of the prize trading. Note that when the amount is recorded on the blockchain 20, it may be difficult to flexibly change the amount, but there is no particular problem when the transaction price (selling price or buying price) is fixed.

[0104] As an example, as shown in FIG. 7, for the NFT of token_id01, it is recorded on the blockchain 20 in association with the NFT that the selling price (buying price) of the prize with the NFT is ￥5,000. For the NFT of token_id02, it is recorded on the blockchain 20 in association with the NFT that the selling price (buying price) of the prize with the NFT is ￥2,500. For the NFTs of token_id03 and token_id04, it is recorded on the blockchain 20 in association with the NFTs of token_id03 and token_id04 respectively that the selling price (buying price) of the prize with the NFT is ￥1,000.

[0105] Note that the value of the prize with the NFT or the NFT can be guaranteed by content data such as image data associated with the NFT. The NFT can, for example, make unique valuable content data (digital data) such as a professional athlete or a musician. Therefore, the prize with the NFT or the NFT can have a value corresponding to the digital data authenticated by the NFT.

[0106] Server 51 acquires the respective amounts associated with one or more token identifiers (token_id01, token_id02, token_id03) identified as processing targets, and calculates the total value of those amounts (value data). As an example, the total value of the amounts associated with the three token identifiers (token_id01, token_id02, token_id03) is ¥8,500.

[0107] Server 51 generates value display data as a component of the confirmation display data 91. The value display data includes value display data indicating the total value (¥8,500) and its breakdown. In the first display data 91 of FIG. 9, the value display data includes the part of "Total price ¥8,500" and the parts of "Breakdown" and "AAA ¥5,000 × 1 = ¥5,000", "BBB ¥2,500 × 1 = ¥2,500", "CCC ¥1,000 × 1 = ¥1,000". The value display data may include only either the total value or its breakdown. The same applies to the second display data 92.

[0108] Server 51 acquires or generates, from the blockchain 20 or the like, data for displaying on the screen the NFTs (token_id01, token_id02, token_id03) identified as processing targets as a component of the confirmation display data 91. In the first display data 91 of FIG. 9, the data for displaying the NFTs (token_id01, token_id02, token_id03) on the screen are three elements shown in the "List of target NFTs". In the first display data 91, in the "List of target NFTs", there are shown three elements: the NFT (token_id01) corresponding to the prize 401 which is "AAA" and its amount (¥5,000), the NFT (token_id02) corresponding to the prize 402 which is "BBB" and its amount (¥2,500), and the NFT (token_id03) corresponding to the prize 403 which is "CCC" and its amount (¥1,000). The same applies to the second display data 92.

[0109] Although not shown in FIG. 9, the confirmation display data 91, 92 may include codes (00:00:00:00:00:0a, 00:00:00:00:00:0b, 00:00:00:00:00:0c) corresponding to each of one or more NFTs (token_id01, token_id02, token_id03) to be processed. That is, the confirmation display data 91 may include one or more codes ((00:00:00:00:00:0a, 00:00:00:00:00:0b, 00:00:00:00:00:0c)) read by the reader 31D.

[0110] Also, like "AAA", "BBB", "CCC" shown in FIG. 9, the confirmation display data 91, 92 may include data related to articles (prizes 401, 402, 403) having codes corresponding to each of one or more NFTs to be processed. That is, the confirmation display data 91, 92 may include data related to the articles (prizes 401, 402, 403) from which the codes have been read. The data related to the articles (prizes 401, 402, 403) may be characters or symbols indicating names or types such as "AAA", "BBB", "CCC", or may be the price of the article or other data related to the article.

[0111] By the confirmation display data 91, 92 including the above data, the transaction parties (transferor or transferee) can grasp or confirm the articles (prizes 401, 402, 403) and / or NFTs that are the subject of the transaction.

[0112] The confirmation display data 91 and 92 may indicate information indicating the other party of the transfer party. The information indicating the other party is, for example, the other party's blockchain address and / or the other party's name or surname. For example, in the case of the display data 91 for the transferor (seller), the other party is the transferee (buyer: 0x2222). In the case of the display data 92 for the transferee (buyer), the other party is the transferor (seller: 0x1111). By including the other party's information in the confirmation display data 91 and 92, the transfer parties can confirm the other party before executing the transfer. Note that, in this case, the other party is a common other party for a plurality of NFT transfers to be executed in a batch process.

[0113] The confirmation display data 91 may be for confirming whether to permit the execution of processing (NFT processing) for the NFT corresponding to the read code. When batch processing for a plurality of NFTs is executed, this confirmation is for confirming whether to permit the execution of the batch process.

[0114] The confirmation at the transferor is a confirmation of whether to transfer (sell) the prize and the NFT to the transferee (see the first display data 91 in FIG. 9). For this confirmation, the first display data 91 includes a display of "Do you want to sell?" and buttons of "Yes" and "No" (graphical user interface: GUI). When the user permits the sale (transfer), the user performs a user operation of clicking or tapping the "Yes" button. A signal indicating that the user operation has been performed is transmitted to the server 51.

[0115] The confirmation at the transferee is a confirmation of whether to transfer (purchase) the prize and the NFT to the transferee (see the second display data 92 in FIG. 9). For this confirmation, the second display data 92 includes a display of "Do you want to purchase?" and buttons of "Yes" and "No" (graphical user interface: GUI). When the user permits the purchase (transfer), the user performs a user operation of clicking or tapping the "Yes" button. A signal indicating that the user operation has been performed is transmitted to the server 51.

[0116] In the embodiment, since the user operation for permitting transfer is a single operation for a plurality of NFTs in a batch, it is advantageous in that it can reduce the number of users compared to the case of transferring each NFT one by one.

[0117] When the server 51 receives a user operation for permitting transfer from both the transfer source and the transfer destination, or either one of them, it determines that the transfer is permitted (step S84), and executes a batch process for transferring a plurality of NFTs to be processed (step S85).

[0118] The batch process includes the transfer of a plurality of NFTs to be processed and the process for payment accompanying the transfer. The transfer of an NFT is, for example, as shown in FIG. 7, to transmit the NFT from the transfer source address (0x1111) to the transfer destination address (0x2222). The payment may be a payment in legal tender or the like, or a payment in cryptocurrency of the blockchain 20 or a payment by other value data. In the embodiment, since the payment may be made for the total amount of a plurality of NFTs, the transfer process is simplified compared to the case of transferring each NFT one by one.

[0119] The batch process including the transfer of a plurality of NFTs and the payment of their total amount can be configured as one transaction. In a transaction, the individual processes constituting it do not complete independently, and the process of the transaction as a whole is completed when all the series of processes constituting the transaction are successful. If some of the processes constituting the transaction fail, the process of the whole transaction fails, and the process of the whole transaction is considered not to have been performed (cancellation of the process). By configuring the transfer of a plurality of NFTs and the payment of their total amount as a transaction, the process can be performed safely. Also, it is possible to prevent only some of the plurality of NFTs to be processed from being transferred.

[0120] The distribution method of the prizes 401, 402, 403 with NFTs using the system 10 according to the embodiment is, for example, as follows. In the method described below, the prizes 401, 402, 403 and the NFTs attached thereto are transferred and distributed among the four parties: the game arcade 1A, the player 4, the prize exchange 2, and the prize wholesaler 3.

[0121] The prize wholesaler 3 sells the prize with an attached NFT to the game arcade 1A. That is, the prize and the NFT are transferred from the prize wholesaler 3 (transferor) to the game arcade 1A (transferee). Before the transfer, the prize is owned by the prize wholesaler 3, and the NFT attached to the prize is owned at the blockchain address of the prize wholesaler 3. At the time of transfer, the code provided for each of one or more prizes is read by the prize wholesaler terminal 31-3 and / or the game arcade terminal 31-1. The system 10 transmits the NFT corresponding to the read code from the blockchain address (0x3333) of the prize wholesaler 3 to the blockchain address (0x1111) of the game arcade 1A. As a result, the owner of the NFT becomes the game arcade 1A. Such a transfer of the prize is recorded on the blockchain 20 as a transfer of the NFT corresponding to the prize. Along with the transfer of the NFT, on the blockchain 20, the NFT, which is the data corresponding to the code, and the blockchain address of the game arcade 1A, which is the transfer destination of the prize, are recorded in association with each other.

[0122] Along with the transfer of the NFT, the physical prize is also transferred from the prize wholesaler 3 to the game arcade 1A. Also, the consideration for the transferred prize with NFT is paid from the game arcade 1A to the prize wholesaler 3. The transfer can be performed collectively for a plurality of prizes and NFTs. Since the transfer is performed collectively, it is easy to sell a large number of prizes and NFTs. Also, the payment is made along with the transfer.

[0123] The game arcade 1A provides one or more prizes with NFTs to the player 4 as prizes to be exchanged for gaming media such as pachinko balls. That is, the prize and the NFT are transferred from the game arcade 1A to the player 4. At the time of this exchange, the codes provided in each of the one or more prizes are read by the game arcade terminal 31-1 and / or the player terminal 31-4. The system 10 transmits the NFT corresponding to the read code from the blockchain address (0x1111) of the game arcade 1A to the blockchain address (0x4444) of the player 4. As a result, the owner of the NFT becomes the player 4. The transfer of such a prize is recorded on the blockchain 20 as the transfer of the NFT corresponding to the prize. Along with the transfer of the NFT, on the blockchain 20, the NFT which is the data corresponding to the code and the blockchain address of the player 4 which is the transfer destination of the prize are recorded in association with each other.

[0124] Along with the transfer of the NFT, the physical prize is also transferred from the game arcade 1A to the player 4. The player 4 gives the game arcade 1A gaming media such as pachinko balls or the rights thereto as the consideration for obtaining the prize with NFT.

[0125] The player 4 has the prize exchange 2 purchase one or more prizes with NFTs in order to exchange the obtained prizes for money or the like. That is, the prize and the NFT are transferred from the player 4 to the prize exchange 2. At the time of this purchase, the codes provided in each of the one or more prizes are read by the prize exchange terminal 31-2 and / or the player terminal 31-4. The system 10 transmits the NFT corresponding to the read code from the blockchain address (0x4444) of the player 4 to the blockchain address (0x2222) of the prize exchange 2. As a result, the owner of the NFT becomes the prize exchange 2. The transfer of such a prize is recorded on the blockchain 20 as the transfer of the NFT corresponding to the prize. Along with the transfer of the NFT, on the blockchain 20, the NFT which is the data corresponding to the code and the blockchain address of the prize exchange 2 which is the transfer destination of the prize are recorded in association with each other.

[0126] With the transfer of the NFT, the physical prize is also transferred from player 4 to the prize exchange 2. Also, the consideration for the transferred prize with the NFT is paid from the prize exchange 2 to player 4. The transfer can be performed in a batch for a plurality of prizes and NFTs. Since the transfer is performed in a batch, it is easy to sell a large number of prizes and NFTs. Also, the payment is made along with the transfer.

[0127] The prize exchange 2 sells one or more prizes with NFTs to the prize wholesaler 3. That is, the prize and the NFT are transferred from the prize exchange 2 to the prize wholesaler 3. The prize wholesaler 3 can resell the prize with the NFT purchased from the prize exchange 2 to the casino 1A or another casino 1B again.

[0128] In the distribution of casino items, when using the system 10 of the embodiment, the data (NFT) corresponding to the code included in the casino item and the blockchain address of the transfer destination (and the transfer source) of the casino item can be associated and recorded in the blockchain 20. Since the data recorded in the blockchain 20 is difficult to tamper with, the distribution of casino items can be reliably recorded. This record is highly reliable and is useful as statistical data related to gaming or big data related to gaming.

[0129] Moreover, with the transfer, the blockchain addresses recorded in the blockchain 20 include the first blockchain address (0x1111) of the casino 1A, the second blockchain address (0x2222) of the prize exchange 2, and the third blockchain address (0x3333) of the prize wholesaler 3. Therefore, a record of the distribution of prizes among these three parties can be obtained. Also, since the blockchain addresses recorded in the blockchain 20 also include the fourth blockchain address (0x4444) of player 4, a record of the distribution of prizes among the four parties including player 4 can be obtained.

[0130] In the above description, the transfer of an NFT is carried out as a change in NFT ownership from the transfer source to the transfer destination. In other words, the transfer of NFT ownership is recorded on the blockchain 20. However, the transfer of an NFT may also be carried out as a change in NFT usage rights from the transfer source to the transfer destination. In this case, the transfer of NFT usage rights is recorded on the blockchain 20. When the transfer of an NFT is carried out as a change in NFT usage rights, the ownership of the NFT does not need to change. For example, the administrator 5 of the system 10 can continue to hold the ownership of the NFT regardless of the change in NFT usage rights.

[0131] FIG. 10 shows a blockchain 20 that records the transfer of an NFT as a change in NFT usage rights. In this case, the rental NFT function defined in the EIP4907 standard can be used to set the usage rights. In this case, the holder of the NFT usage rights is a "user" in EIP4907. The holder of the NFT usage rights is the borrower of the rental NFT.

[0132] In FIG. 10, the blockchain address of the user of the rental NFT is shown as the first account, and the blockchain address of the "owner" of the rental NFT is shown as the second account. In FIG. 10, the first accounts are address 25A (0x1111) of the amusement facility 1A, address 25B (0x2222) of the prize exchange center 2, address 25C (03333) of the prize wholesaler 3, and address 25C (0x4444) of player 4. In other words, amusement facility 1A, prize exchange center 2, prize wholesaler 3, and player 4 can each be users (transfer parties) of the rental NFT. Also, in FIG. 19, the second account is address 25E (0x1234) of administrator 5. In other words, administrator 5 is the owner of the NFTs (token_id01, token_id02, token_id03, token_id04). As the owner of the NFT, Administrator 5 can perform operations on the NFT, such as transferring and setting usage rights for the NFT, on behalf of the first account (transfer party).

[0133] Administrator 5, who is the NFT owner, can set the users of the NFTs (token_id01, token_id02, token_id03, token_id04) through System 10. In Figure 10, for the NFTs of token_id01 and token_id02, the address 0x3333 of the prize dealer is set as the user. For the NFT of token_id03, the address 0x4444 of the player is set as the user. For the NFT of token_id04, the address 0x1111 of the game arcade is set as the user.

[0134] For example, when game arcade 1A provides prizes to player 4, first, similar to the case of NFT ownership transfer, the codes included in each of the one or more prizes are read by game arcade terminal 31-1 and / or player terminal 31-4.

[0135] Then, System 10 calls smart contract 22 as the owner of the NFT corresponding to the read code, and changes the user of that NFT from the blockchain address (0x1111) of game arcade 1A to the blockchain address (0x4444) of player 4 with the authority of the NFT owner. In this case, since it is administrator 5, the NFT owner, who calls smart contract 22 to perform the process of NFT usage right transfer, the fee (gas fee) to be paid to blockchain 20 is paid to blockchain 20 by crypto assets such as the FT (fungible token) owned by administrator 5. Therefore, game arcade 1A and player 4, who are the transfer parties, do not need to pay the gas fee. The same applies to the transfer of NFT usage rights between other transfer parties.

[0136] Because NFT users do not have the authority to transfer NFT usage rights themselves, unauthorized transfer of NFT usage rights can be prevented. If an NFT transfer is performed by transferring ownership, even Administrator 5 would have difficulty recovering the NFT if Player 4 or another party sends the NFT to a third party without permission. However, if an NFT transfer is performed by transferring usage rights, the NFT owner has the authority to set or revoke usage rights. Therefore, even if NFT usage rights are transferred by mistake, Administrator 5 can use his or her owner authority to revoke or reset the NFT usage rights and undo the erroneous transfer.

[0137] The gaming facility may be a casino instead of a pachinko parlor, and the gaming facility item may be a casino chip with an NFT. In this case, the casino chip and NFT are transferred between the casino and the player. Furthermore, the item with the code is not limited to a gaming facility item and may be another item. [Explanation of symbols]

[0138] 1: Amusement park 1A: Amusement park 1B: Amusement park 2: Prize Exchange 2A: Prize Exchange 2B: Prize Exchange 3: Prize Wholesaler 3A: Prize Wholesaler 3B: Prize Wholesaler 4: Player 5: Prize manufacturer 5: System administrator 10: Game center item management system 15: Network 20: Blockchain 22: Smart Contract 22A: NFT processing 25A: Blockchain address 25B: Blockchain address 25C: Blockchain address 25D: Blockchain address 25E: Blockchain Address 31: Terminal 31-1: Amusement Hall Terminal 31-2: Prize Exchange Terminal 31-3: Prize Dealer Terminal 31-3: Prize Dealer Terminal 31-4: Player Terminal 31A: Processor 31B: Memory Device 31C: Computer Program 31D: Reader 31F: Registration Process 40: NFC Tag 41: Antenna 42: Wireless Circuit 43: Controller 44: Memory 46: Unique Identifier 51: Server 51A: Processor 51B: Memory Device 51C: Computer Program 51E: Corresponding Data Table 51F: Registration Process (Batch Process) 91: First Display Data (Confirmation Display Data) 92: Second Display Data (Confirmation Display Data) 401: Prize 402: Prize 403: Prize 450: Storage Section 500: Paper

Claims

1. A method including steps executed by a computer, wherein the steps include one or more computers identifying, as objects for batch transfer, a plurality of non-fungible tokens corresponding to a plurality of codes read by a reader by reading, using the reader, the codes provided in each of the plurality of articles to be batch transferred, acquiring a blockchain address serving as a common transfer destination for batch transfer of the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader, and batch transferring the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader to the blockchain address serving as the common transfer destination. The method is characterized by the above.

2. The steps further include the one or more computers providing display data for display on a display device for checking whether to permit batch transfer of the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader to the blockchain address after reading, using the reader, the codes provided in each of the plurality of articles to be batch transferred, and the batch transfer of the plurality of non-fungible tokens to the blockchain address is executed after a user operation permitting the batch transfer of the plurality of non-fungible tokens to the blockchain address is performed. The method according to claim 1.

3. The steps further include the one or more computers providing display data for display on a display device after reading, using the reader, the codes provided in each of the plurality of articles to be batch transferred, wherein the display data includes checking display data, and the checking display data includes at least one or both of value display data indicating either or both of the total value of value data associated with each of the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader and the breakdown of the total value, the code read by the reader, or data regarding the article including the code read by the reader and the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader. The checking display data includes at least one or more data selected from the group consisting of the above. The method according to claim 1.

4. The article is an arcade item provided to a player in an arcade, The method according to any one of claims 1 to 3, which is performed for registering the transfer of the arcade item.

5. By reading the codes provided in each of a plurality of articles to be transferred in a batch by a reader, a plurality of non-fungible tokens corresponding to the plurality of codes read by the reader are identified as objects of the batch transfer, A blockchain address serving as a common transfer destination for the batch transfer of the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader is obtained, A system configured to batch-transfer the plurality of non-fungible tokens corresponding to the plurality of codes read by the reader to the blockchain address, which is the common transfer destination.

Images