Method including steps executed by computer and system

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 methods and systems that include computer-implemented steps. [Background technology]

[0002] Patent document 1 discloses that a smart contract implemented on a blockchain performs operations on a non-fungible token identified by an identifier contained in a code assigned to an object.

[0003] Patent Document 2 discloses receiving a unique identifier possessed by an object and generating a non-fungible token. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2021 / 111654 [Patent Document 2] International Publication No. 2023 / 054537 Summary of the Invention

[0005] There are cases where it is desired to execute processing for multiple non-fungible tokens. For example, there are cases where it is desired to transfer multiple non-fungible tokens related to multiple items in conjunction with the transfer of multiple items. However, if it is only possible to read a code provided on one item and execute processing for one non-fungible token corresponding to that code, when there are multiple items, the work of the user, etc. increases as the number of items increases, making things complicated.

[0006] Thus, performing operations on multiple non-fungible tokens increases complexity.

[0007] Therefore, it is desirable to reduce the complexity when performing processing on multiple non-fungible tokens.

[0008] One aspect of the present disclosure is a method including computer-implemented steps of: acquiring a plurality of codes by reading, with a reader, codes provided on a plurality of items, and executing batch processing on a plurality of non-fungible tokens corresponding to the acquired plurality of codes, by one or more computers.

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

[0010] Further details will be described in the following embodiments. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is an explanatory diagram of the distribution channel of prizes. [Diagram 2] FIG. 2 is a configuration diagram of a system according to an embodiment. [Diagram 3] Figure 3 is an explanatory diagram of blockchain. [Figure 4] FIG. 4 is a diagram showing the configuration of the server. [Diagram 5] FIG. 5 is a diagram showing the configuration of a terminal. [Figure 6] FIG. 6 is an explanatory diagram of the simultaneous reading of multiple codes. [Figure 7] FIG. 7 is an explanatory diagram of batch processing. [Figure 8] FIG. 8 is a flowchart of the registration process. [Figure 9] FIG. 9 is an explanatory diagram of the first display data and the second display data. [Figure 10] FIG. 10 is an explanatory diagram of the setting of usage rights for non-fungible tokens. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 1. Overview of computer-implemented method and system

[0013] (1) A method according to an embodiment may include a step executed by a computer. The step may include one or more computers reading a code provided on each of a plurality of items with a reader to obtain a plurality of codes, and executing batch processing on a plurality of non-fungible tokens corresponding to the obtained plurality of codes. The batch processing processes a plurality of non-fungible tokens collectively, thereby reducing complexity.

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

[0015] The batch process may include a non-fungible token process performed in a batch on each of the plurality of non-fungible tokens. The non-fungible token processes performed in a batch on each of the plurality of non-fungible tokens may be the same process.

[0016] The batch processing may include executing a plurality of non-fungible token processes in a batch. Each of the plurality of non-fungible token processes may include a process executed in a blockchain for a non-fungible token corresponding to the acquired codes. The batch processing may include a non-fungible token process executed in a blockchain for each of a plurality of non-fungible tokens corresponding to the acquired codes. The non-fungible token may be, for example, a transfer of ownership of a non-fungible token, setting, changing, or deleting a user of a non-fungible token, or generating a non-fungible token.

[0017] (2) The batch process preferably includes associating each of the plurality of non-fungible tokens with the same blockchain address. Associating a blockchain address with a non-fungible token means, for example, associating a destination blockchain address with a non-fungible token.

[0018] In the batch processing, it is preferable that the non-fungible token processing performed on each of the multiple non-fungible tokens records the same blockchain address in the blockchain as at least one of the owner and user of each of the multiple non-fungible tokens.

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

[0020] (3) The step may further comprise providing a display device with confirmation display data for displaying on the display device to confirm whether execution of the batch processing is permitted. For example, in the case of a transfer of non-fungible tokens, the confirmation display data may be displayed on either or both of the transfer source terminal and the transfer destination terminal. The batch processing is preferably executed after a user operation is performed to permit execution of the batch processing.

[0021] It is preferable that the non-fungible token is a rental non-fungible token, and the non-fungible token processing includes processing for changing the user of the rental non-fungible token.

[0022] (4) Preferably, the steps further comprise the one or more computers providing display data to the display device for display on the display device. The display data may include confirmation display data. The confirmation display data may include: Value display data indicating either or both of a total value of value data associated with each of the plurality of non-fungible tokens and a breakdown of the total value; the codes corresponding to each of the plurality of non-fungible tokens; data relating to the item comprising the code corresponding to each of the plurality of non-fungible tokens; and said plurality of non-fungible tokens; The data may include at least one or more pieces of 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 in a blockchain in association with each of the non-fungible tokens. The value data may indicate a value of the item having the code corresponding to the non-fungible token with which the value data is associated.

[0024] (5) It is preferable that the batch processing is executed upon receipt of a user operation performed after the plurality of codes are acquired.

[0025] (6) The item may be a gaming facility item provided to a player at the gaming facility. The method may be performed for registration of the transfer of the gaming facility item.

[0026] (7) The system of the embodiment may be configured to obtain multiple codes by reading codes provided on each of multiple items using a reader, and to perform batch processing on multiple non-fungible tokens corresponding to the obtained codes.

[0027] 2. Examples of computer-implemented methods and systems

[0028] FIG. 1 shows an example of the distribution of game parlor items provided to players at game parlors. One example of the game parlor items here is a prize provided to players. One example of the prize is a special prize in the three-store system. The special prize is an item handled by a dealer in the three-store system, and is an item that can be exchanged by players for pachinko balls, cash, etc.

[0029] The vendors in the three-store system are amusement arcades 1A, 1B, a prize exchange center 2, and prize wholesalers 3A, 3B. Here, the amusement arcade may be a company that operates one or more amusement arcades (stores), or may be an individual amusement arcade (store). The prize exchange center may be a company that operates one or more prize exchange centers (stores), or may be an individual prize exchange center (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 a prize by exchanging pachinko balls for the prize at an amusement facility 1A, such as a pachinko parlor. That is, the prize is provided to the player 4 from the amusement facility 1A. The player 4 can exchange the prize for financial value such as legal tender or cryptocurrency at the prize exchange facility 2. That is, the player 4 can sell a special prize to the prize exchange facility 2 and obtain financial value such as electronic money or points in return.

[0031] The monetary value (e.g., electronic money or points) exchanged for an item such as a prize is sent to the wallet application of Player 4. The wallet application is application software for managing monetary value. Player 4, who is a user of the wallet application, can withdraw the monetary value deposited in the wallet application or use it to settle payments.

[0032] The prize wholesaler 3 purchases prizes from the prize exchange 2 and wholesales them to the game parlors 1A and 1B. The prize wholesaler 3 can also purchase prizes from the prize manufacturers 5 and wholesale them to the game parlors 1A and 1B. The prize manufacturers 5 manufacture and sell prizes.

[0033] In this manner, the prizes are transferred through a distribution route including the game centers 1A, 1B, the prize exchange center 2, and the prize wholesaler 3.

[0034] The prize manufacturer 5 may be, for example, a system administrator 5 of the system 10 according to the embodiment. A prize according to the embodiment is accompanied by a non-fungible token of the blockchain. The non-fungible token (non-fungible token; NFT) has a unique token identifier (TokenID) in the blockchain 20 to ensure non-fungibility. The token identifier enables distinction from other NFTs. The non-fungible token is accompanied by the prize, for example, by recording in a computer the correspondence between a code provided in the prize and the identifier provided in the non-fungible token.

[0035] A system 10 according to the embodiment may be a game center item management system 10. The system 10 is configured by, for example, one or more computers. As shown in FIG. 2 , the system 10 may include, as an example, a server 51 and a terminal 31. The terminal 31 may 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 use a blockchain 20. The system 10 may include the blockchain 20.

[0036] The terminals 31 may include, by way of example, an amusement facility terminal 31-1, an exchange terminal 31-2, and a prize wholesaler terminal 31-3. The amusement facility terminal 31-1 is a terminal installed in the amusement facilities 1A and 1B, or a terminal used by staff of the amusement facilities 1A and 1B. The exchange facility terminal 31-2 is a terminal installed in the exchange facility 2, or a terminal used by staff of the exchange facility 2. The prize wholesaler terminal 31-3 is a terminal installed in the prize wholesaler 3, or a terminal used by 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 a player 4.

[0038] The game facilities 1A and 1B, the prize exchange office 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, and 31-4 may be called a user terminal.

[0039] As an example, the terminal 31 is used as a transfer source terminal of a prize (item) or an NFT. The transfer source terminal may be called a seller terminal. Also, as an example, the terminal 31 is used as a transfer destination terminal of 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. It is preferable that the blockchain 20 allows rental of NFTs. Renting an NFT means renting an NFT to a user other than the owner of the NFT. Renting an NFT allows users other than the owner of the NFT to use the NFT.

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

[0042] EIP4907 adds the role of "user." An EIP4907 "user" is the borrower of a rental NFT and the user of the rental NFT. Unlike the owner of a non-fungible token, an EIP4907 "user" cannot transfer the non-fungible token. However, an EIP4907 "user" can use the non-fungible token just like the owner. In this way, an EIP4907 "user" has more limited authority over the non-fungible token than the owner.

[0043] In the blockchain 20, transactions can be made between blockchain addresses. Transactions of transactions are recorded in the distributed ledger of the blockchain 20. A blockchain address indicates, for example, an account in the blockchain 20. A blockchain address is, for example, a wallet address. A blockchain address is, for example, an externally owned account (EOA). For example, when a user has an account in the blockchain 20, the account has a specified blockchain address (wallet address).

[0044] 3, as an example, the blockchain address 25A of the game center 1A, the blockchain address 25B of the prize exchange center 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 wallet addresses of the users. By setting the addresses 25A, 25B, 25C, and 25D of the game center 1A, the prize exchange center 2, the prize wholesaler 3, and the player 4 in the blockchain 20, transactions involving these users 1A, 2, 3, and 4 can be recorded in the blockchain 20.

[0045] 3 also shows a blockchain address 25E of the administrator 5. 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 involving the administrator 5 can be recorded in the blockchain 20.

[0046] In FIG. 3, the address 25A of the game center 1A is "0x1111". The address 25B of the prize exchange center 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, only one address 25A, 25B, 25C, and 25D are set for each of the game center, the prize exchange center, the prize wholesaler, and the player, but since there may be multiple game centers, prize exchange centers, prize wholesalers, and players, multiple addresses may be set for each. That is, the addresses of each of the multiple game centers, each of the multiple prize exchange centers, each of the multiple prize wholesalers, and each of the multiple players may be set in the blockchain 20.

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

[0048] In the 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 blockchain addresses 25A, 25B, 25C, 25D, 25E ​​of users 1A, 2, 3, 4 or administrator 5.

[0049] Addresses 25A, 25B, 25C, 25D, and 25E set in the blockchain 20 may be recorded in the blockchain 20 in association with the NFT to be transferred as the source address or destination address of a token such as an NFT in recording an NFT transaction. For example, when an NFT is transferred from player 4 to exchange 2, it is recorded in the blockchain 20 that the NFT has been transferred from player 4's address (0x4444: source address) to the exchange's address (0x2222: source address).

[0050] The blockchain 20 may include a smart contract 22. The system 10 may include a smart contract 22 implemented in the blockchain 20. The smart contract 22 is configured by software (computer program) that is executable in 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 sending an NFT (transfer of ownership or usage rights) or a process for generating an NFT.

[0051] The aforementioned blockchain address may also refer to the contract address of the smart contract 22. The contract address is a blockchain address where the smart contract 22 is stored. In FIG. 3, the contract address of the smart contract is, for example, “0x8888”.

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

[0053] The process executed by the smart contract 22 is, for example, a token operation. The token operation 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 changing the token user may be called a token transmission. In other words, changing the token owner from a first blockchain address to a blockchain address also means transmitting the token from the first blockchain address to a second blockchain address.

[0054] In the embodiment, as an example, prizes 401, 402, and 403 (items) are used to transmit and receive such NFTs. In other words, in the embodiment, the NFTs are also transferred with the transfer of prizes 401, 402, and 403. Note that prizes 401, 402, and 403 are provided with letters or symbols indicating the name or type of the prize. As an example, the letters or symbols indicating the name or type of the prize are "AAA" for prize 401, "BBB" for prize 402, and "CCC" for prize 403. As an example, prizes 401, 402, and 403 are purchased at a predetermined price, and the letters or symbols indicating the name or type of the prize may also be letters or symbols indicating the price. For example, the price of the "AAA" prize 401 is 5,000 yen, the price of the "BBB" prize 402 is 2,500 yen, and the price of the "CCC" prize 403 is 1,000 yen. The prizes 401, 402, and 403 may be labeled with their own prices.

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

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

[0057] The storage device 51B of the server 51 may include a correspondence data table 51E. The correspondence data table 51E indicates the correspondence between a code (to be described later) and a token identifier of an NFT. The correspondence data table 51E associates the code with the NFT.

[0058] By recording the correspondence between the code and the NFT in the correspondence data table 51E, it becomes possible to use an item (a prize, etc.) having a code to operate the NFT. In other words, the code of the item can be used as an identifier of the NFT to be operated. The server 51 can identify the NFT corresponding to the code by referring to the correspondence data table 51E. The server 51 can perform processing on the identified NFT.

[0059] The code is, for example, a unique identifier. The code may be composed of any one or a combination of symbols, letters, and numbers. In Fig. 4, for 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 correspondence 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 correspondence data may be included in the data constituting the NFT recorded in the blockchain 20.

[0061] 4, the terminal 31 may be configured by a computer including a processor 31A and a storage device 31B. The computer that may 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 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 indicating instructions for causing the computer to execute various processes such as a registration process 31F described below.

[0063] The terminal 31 includes a reader 31D for reading the 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 the code by wireless communication, or may read the code by a camera or other optical sensor. The code read by the reader 31D may be in a machine-readable format such as a two-dimensional code such as 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 item. The item provided with the code is, for example, the above-mentioned game center item, more specifically, a prize (special prize) at the game center. That is, the special prize according to the embodiment is provided with a code read by the reader 31D.

[0066] The type of medium on which the code is recorded is not particularly limited, but as an example, the medium having the code is an integrated circuit (IC) 40 having a code. The code may 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) that includes a memory for storing data such as the unique identifier and is configured to be able to communicate data such as the unique identifier with the outside. The integrated circuit module 40 may be called an integrated circuit tag (IC tag) or an integrated circuit card (IC card) depending on its form.

[0067] The integrated circuit module 40 may be of 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 is capable of communication by contacting the contact with the external communication device. The non-contact integrated circuit module 40 (non-contact IC module 40) has an antenna, and is capable of non-contact communication with the reader 31D.

[0068] The reader 31D is preferably configured to be capable of reading a plurality of codes at once. For example, the reader 31D is preferably provided with a batch reading function that reads codes from each of the plurality of IC modules 40 (integrated circuits 40) by wireless communication. The reader 31D with 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 with the batch reading function, a large number of codes can be read at once, improving workability.

[0069] As shown in Fig. 5, the integrated circuit 40 includes a memory 44 for storing 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, a PROM, an EPROM, an EEPROM, or a FeRAM, or a flash memory.

[0070] The unique identifier 46 of the integrated circuit 40 is preferably an unrewritable unique identifier given 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 and distinguish it from other integrated circuits. The unique identifier 46 (UID) given to the integrated circuit 40 by the manufacturer is written to the memory 44, for example, when the integrated circuit 40 is manufactured. The unique identifier 46 is written to the memory 44 at the latest by the time the manufacturer ships the integrated circuit 40. The memory 44 of the integrated circuit 40 may have an area in which a purchaser or user of the integrated circuit 40 can write data. In the memory area in which the user or the like can write data, for example, other data to be read by the reader 31D may be written.

[0071] A contactless IC module having a unique identifier is also called a radio frequency identification (RFID) device. The radio frequency identification (RFID) device transmits data such as a unique identifier to an external wireless communication device such as the reader 31D by wireless communication. The transmitted data is 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 radio frequency identification (RFID) device. When the radio frequency identification (RFID) device has the form of a tag, it may be called a radio frequency identification (RFID) tag.

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

[0073] The medium carrying the code is not limited to an integrated circuit having a unique identifier, but may be any other medium that displays the code. The code may be, for example, printed.

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

[0075] In the embodiment, prizes 401, 402, and 403, which are game items, each have an NFC tag 40 with a code built in, for example.

[0076] As shown in FIG. 6, in the embodiment, as an example, a code or the like is transmitted from the NFC tag 40 to a terminal 31 equipped with a reader 31D. For example, a staff member of the game center 1A, a staff member of the prize exchange office 2, a staff member of a prize wholesaler, or a 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 a 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 in the system 10 to identify an NFT corresponding to the code.

[0077] In order to read the codes collectively, the multiple prizes 401, 402, and 403 are stored, for example, in a prize storage section 450. The storage section 450 has, for example, an electromagnetic shielding function, and the code reading target can be limited to the items 401, 402, and 403 in the storage section 450.

[0078] The reader 31D reads a code (unique identifier) ​​from the NFC tag 40 of each 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 code to the server 51.

[0079] The system 10 of the embodiment can execute a process for an NFT corresponding to a code read by the reader 31D. In addition, when the reader 31D reads a plurality of codes at once, the system 10 can execute the process 51F for a plurality of NFTs corresponding to the plurality of codes read at once at once.

[0080] FIG. 7 shows an example of batch processing 51F for multiple NFTs corresponding to multiple codes. Batch processing is the execution of multiple processes together. Note that, here, processing for one NFT is referred to as "non-fungible token processing" or "NFT processing." In this case, batch processing for multiple NFTs is the execution of multiple NFT processes together.

[0081] Batch processing 51F for multiple NFTs allows multiple NFTs to be automatically processed in a batch. Therefore, there is no need to perform operations for processing multiple NFTs one by one, and the processing can be made more efficient by avoiding complexity. In addition, in the embodiment, multiple NFTs are identified by multiple codes obtained by batch reading, so that multiple NFTs to be subject to batch processing can be efficiently identified. That is, in the embodiment, even when processing multiple NFTs, the burden on the user can be made the same as processing one NFT. For example, multiple codes can be read in a single reading operation, and multiple NFTs corresponding to the multiple codes can be processed in a batch by batch processing.

[0082] The NFT process includes a process that is recorded in the blockchain 20. By batch processing multiple NFT processes, multiple NFTs can be recorded in the blockchain 20 at the same time.

[0083] For NFTs, the transaction recorded on the blockchain is, for example, the transfer of the NFT. The transfer of the NFT is, for example, a change in the owner of the NFT. The transfer of the NFT may also be a change in the user (borrower) of a rental NFT.

[0084] As shown in FIG. 7, execution of batch process 51F allows multiple NFTs to be transferred in bulk in the blockchain 20. In FIG. 7, four NFTs are associated with the source address (0x1111) before the NFT transfer. Therefore, the source address (0x1111) is the owner or user (borrower) of the four NFTs. The token identifiers (TokenIDs) held by the four NFTs at the source address are token_id01, token_id02, token_id03, and token_id04, respectively.

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

[0086] As shown in table 51E in FIG. 4, code: 00:00:00:00:00:0a is associated with token_id01, code: 00:00:00:00:00:0b is associated with token_id02, and code: 00:00:00:00:00:00:0c is associated with token_id03. Therefore, the system 10 can refer to table 51E and identify multiple NFTs (token_id01, token_id02, token_id03) to be subjected to batch processing 51F from multiple codes (00:00:00:00:00:00:0a, 00:00:00:00:00:0b, 00:00:00:00:00:00:0c) read in bulk. The system 10 executes a batch process to transfer (send) the identified multiple NFTs from the transfer source address to the transfer destination address. In Figure 7, of the four NFTs (token_id01, token_id02, token_id03, token_id04) held by the source address, the three NFTs (token_id01, token_id02, token_id03) corresponding to the three codes read are transferred in bulk to the destination address.

[0087] The transfer (transmission) of multiple NFTs is recorded in the blockchain 20. The record in the blockchain 20 may include a source address and a destination address for each NFT. In addition, in the transfer of an NFT, the destination of the NFT may be designated by a user or the like as appropriate. In addition, in the transfer of an NFT, the NFT does not need to be transferred directly from the source to the destination, but may be transferred from the source to the destination via an intermediate address. The intermediate address may be, for example, the contract address of the smart contract 22.

[0088] In batch processing, the NFT processing for each of multiple NFTs does not need to be performed simultaneously, but may be performed sequentially during the batch processing.

[0089] FIG. 8 shows an example of the procedure of the registration process 51F of the transfer of the game center item using batch processing. The system 10 according to the embodiment may be a management system 10 that manages the transfer of the game center item such as the prizes 401, 402, and 403. The system 10 transfers the corresponding NFT along with the transfer of the game center item such as the prizes 401, 402, and 403. Therefore, the transfer of the game center item can be recorded in the blockchain 20 as the transfer of the NFT. Since the record of the blockchain 20 is difficult to tamper with, the reliability and transparency of the record can be increased by recording the transfer of the game center item in the blockchain 20. Note that the process 51F shown in FIG. 8 can be understood as a process for simply transferring a plurality of NFTs in a lump sum, apart from the registration of the transfer of the item such as a prize.

[0090] The code of the item being transferred may be recorded in the blockchain 20 along with the transfer destination, but by recording the transfer of the item as the transfer of the NFT corresponding to the item, it is possible to utilize the infrastructure related to NFTs in the blockchain 20.

[0091] The registration process 51F in FIG. 8 is executed by one or more computers included in the system 10. In the following, as an example, the server 51 and the terminal 31 cooperate to execute the registration processes 51F, 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. In addition, 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, and executes a predetermined process in the blockchain 20. The smart contract 22 executes, for example, an NFT process 22A such as an NFT transfer.

[0092] The smart contract 22 may be configured to execute processing in the blockchain 20 for one specified NFT each time it is called. In this case, in batch processing of multiple NFTs, the smart contract 22 is called from the server 51 or the like that executes the batch processing a number of times corresponding to the number of NFTs to be processed. The smart contract 22 may also be configured to execute processing in the blockchain 20 for multiple specified NFTs collectively in one call. In other words, the smart contract 22 may also be configured to perform batch processing. In this case, the transfer of multiple NFTs can be performed collectively by calling the smart contract 22 once.

[0093] In the registration process 51F, 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, 403 to be transferred. For example, the read codes etc. may be acquired by the terminal 31 and transmitted from the terminal 31 to the server 51. The terminal 31 (its reader 31D) that reads the codes may be the terminal 31 (its reader 31D) of the transfer source or the terminal 31 (its reader 31D) of the transfer destination. The codes may also be read by both the terminals 31, 31 of the transfer source and the transfer destination.

[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, or 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] The system 10 may obtain the transfer destination information from the transfer destination terminal 31. For example, the transfer destination terminal 31 transmits its blockchain address (e.g., 0x2222) to the system 10. This allows the system 10 to obtain the transfer destination information. For example, when the code is read by the transfer destination terminal 31, the transfer destination terminal 31 may transmit the blockchain address of the transfer destination terminal 31, etc., together with the code to the server 51. The server 51 may identify the transfer source from the code, and identify the blockchain address transmitted together with the code as the transfer destination.

[0096] In addition, the system 10 may acquire the transfer destination information from the transfer source terminal 31. For example, the transfer destination terminal 31 provides the transfer destination blockchain address to the transfer source terminal 31 by wireless communication or the like. The transfer source terminal 31 may transmit the acquired transfer destination blockchain address to the system 10. For example, when the code is read by the transfer source terminal 31, the transfer source terminal 31 may acquire the transfer destination blockchain address from the transfer destination terminal 31 by wireless communication or the like, and transmit the acquired transfer destination blockchain address to the server 51 together with the read code.

[0097] In an embodiment, the transfer party information is information common to multiple NFTs to be processed. In batch processing, the same NFT processing is performed on multiple NFTs. The same NFT processing is, for example, a process of transferring each of multiple NFTs to the same transfer destination indicated by transfer destination information common to multiple NFTs. Since multiple NFTs are transferred to a common transfer destination by batch processing, the user does not need to perform an operation to set a transfer destination for each of the multiple NFTs, making the operation easier. In addition, in batch processing, since an NFT processing common to multiple NFTs is performed, the user does not need to perform an operation to specify the type of NFT processing to be performed on each of the multiple NFTs or an operation to select whether or not to perform each NFT processing, making the operation easier.

[0098] The terminal 31 or the server 51 executes a process for displaying display data including the read result, etc., on a display device (step S83). The display device is, for example, a display provided in the terminal 31. Fig. 9 shows display data 91, 92 displayed on the display device. The display data 91, 92 are provided from the server 51, etc. to the display device of the terminal 31 for screen display.

[0099] 9 shows first display data 91 and second display data 92. The first display data 91 may be displayed on a display device of a terminal 31 of a transfer source (e.g., a seller of the prize). The second display data 92 may be displayed on a display device of a terminal 31 of a transfer destination (e.g., a buyer of the prize).

[0100] Each of the first display data 91 and the second display data 92 may be confirmation display data for confirming whether or not it is appropriate to execute the transaction processing for the NFT corresponding to the read code.

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

[0102] The server 51 acquires an amount (value data) associated with each NFT to be processed. The amount is the selling price (purchase price) of the prize with the NFT. The amount (value data) may be a numerical value in units of legal tender, a numerical value in units of cryptocurrency, or other data having electronic value. The amount may be regarded as the selling price (purchase price) of the NFT alone, or as the selling price (purchase price) of the prize alone. The selling price (purchase price) may differ depending on the transfer parties. The amount associated with each NFT may be set for each transfer party. This point will be described later.

[0103] The amount associated with the NFT may be recorded in association with the NFT on the server 51 or other computer outside the blockchain, or may be recorded in association with the NFT on the blockchain. Since it is difficult to tamper with data recorded on the blockchain 20, if the amount associated with the NFT is recorded on the blockchain 20, tampering with the amount can be prevented and transparency in the transaction of prizes can be guaranteed. Note that when the amount is recorded on the blockchain 20, it may be difficult to flexibly change the amount, but this is not a problem if the transaction price (selling price or purchase price) is fixed.

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

[0105] The value of the NFT-attached prize or NFT may be secured by content data, such as image data, associated with the NFT. The NFT can make valuable content data (digital data), such as that of a professional athlete or musician, unique. Therefore, the NFT-attached prize or NFT may have value according to the digital data authenticated by the NFT.

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

[0107] The 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 is the portion "Price Total ¥8,500", the "Breakdown" and the portions "AAA ¥5,000 x 1 = ¥5,000", "BBB ¥2,500 x 1 = ¥2,500", and "CCC ¥1,000 x 1 = ¥1,000". The value display data may be only one of the breakdowns of the total value. The same applies to the second display data 92.

[0108] The server 51 acquires or generates data for displaying the NFT (token_id01, token_id02, token_id03) identified as the processing target as a component of the confirmation display data 91 from the blockchain 20, etc. In the first display data 91 of FIG. 9, the data for displaying the NFT (token_id01, token_id02, token_id03) on the screen are three elements shown in the "Target NFT List". In the first display data 91, the "Target NFT List" shows 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 is true for the second display data 92.

[0109] 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:00:0c) corresponding to one or more NFTs (token_id01, token_id02, token_id03) to be processed. In other words, the confirmation display data 91 may include one or more codes ((00:00:00:00:00:00:0a, 00:00:00:00:00:0b, 00:00:00:00:00:0c)) read by the reader 31D.

[0110] 9, the confirmation display data 91, 92 may include data related to the item (prize 401, 402, 403) having a code corresponding to one or more NFTs to be processed. That is, the confirmation display data 91, 92 may include data related to the item (prize 401, 402, 403) from which the code was read. The data related to the item (prize 401, 402, 403) may be letters or symbols indicating the name or type, such as "AAA", "BBB", or "CCC", as well as the price of the item or other data related to the item.

[0111] Since the confirmation display data 91, 92 includes the above data, the parties to the transaction (the transferor or transferee) can understand or confirm the items (prizes 401, 402, 403) and / or NFTs that are the subject of the transaction.

[0112] The confirmation display data 91, 92 may indicate information indicating the counterparty of the transfer parties. The information indicating the counterparty is, for example, the counterparty's blockchain address and / or the counterparty's name or surname. For example, in the case of the display data 91 for the transfer source (seller), the counterparty is the transfer destination (purchaser: 0x2222). In the case of the display data 92 for the transfer destination (purchaser), the counterparty is the transfer source (seller: 0x1111). By including the confirmation display data 91, 92 with information on the counterparty, the transfer parties can confirm the counterparty before executing the transfer. In this case, the counterparty is a common counterparty for multiple NFT transfers executed collectively by batch processing.

[0113] The confirmation display data 91 may be for confirming whether or not to permit execution of processing (NFT processing) for the NFT corresponding to the read code. When batch processing is performed on multiple NFTs, this confirmation is for confirming whether or not to permit execution of the batch processing.

[0114] The confirmation at the transfer source is whether or not to transfer (sell) the prize and NFT to the transfer destination (see 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 "Yes" and "No" buttons (graphical user interface: GUI). If 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 transfer destination is whether or not to transfer (purchase) the prize and NFT to the transfer destination (see 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 "Yes" and "No" buttons (graphical user interface: GUI). If 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 an embodiment, the user operation to allow transfer is a single operation that applies to multiple NFTs at once, which is advantageous as it requires fewer users compared to transferring NFTs one by one.

[0117] When the server 51 receives user operation permitting the transfer from both the source and / or destination, it determines that the transfer is permitted (step S84) and executes batch processing to transfer multiple NFTs to be processed (step S85).

[0118] Batch processing includes processing for the transfer of multiple NFTs to be processed and the payment associated with the transfer. For example, as shown in FIG. 7, the transfer of an NFT is sending an NFT from a source address (0x1111) to a destination address (0x2222). The payment may be a payment of legal tender, etc., a payment of cryptocurrency in the blockchain 20, or a payment of other value data. In an embodiment, the payment only needs to be made for the total amount of multiple NFTs, so the transfer process is simplified compared to the case of transferring NFTs one by one.

[0119] A batch process including the transfer of multiple NFTs and the payment of their total amount can be configured as one transaction. Each of the processes constituting a transaction is not completed independently, and the transaction is completed as a whole when all of the series of processes constituting the transaction are successful. If any of the processes constituting the transaction fail, the entire transaction fails and the entire transaction is considered not to have been processed (processing canceled). By configuring the transfer of multiple NFTs and the payment of their total amount as a transaction, the process can be performed safely. In addition, it is possible to prevent only some of the NFTs of the multiple NFTs targeted for processing from being transferred.

[0120] The method of distribution of the NFT-attached prizes 401, 402, 403 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 four parties: the gaming facility 1A, the player 4, the prize exchange center 2, and the prize wholesaler 3.

[0121] The prize wholesaler 3 sells the prize with the NFT attached to the amusement facility 1A. That is, the prize and the NFT are transferred from the prize wholesaler 3 (transfer source) to the amusement facility 1A (transfer destination). 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 the transfer, the prize wholesaler terminal 31-3 and / or the amusement facility terminal 31-1 reads the code provided on one or more prizes. 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 amusement facility 1A. As a result, the owner of the NFT becomes the amusement facility 1A. The transfer of the prize is recorded in the blockchain 20 as the transfer of the NFT corresponding to the prize. When the NFT is transferred, the NFT, which is data corresponding to the code, is associated with and recorded in the blockchain 20 as the blockchain address of the amusement center 1A to which the prize is to be transferred.

[0122] Along with the transfer of the NFTs, the physical prizes are also transferred from the prize wholesaler 3 to the amusement facility 1A. Furthermore, the price for the transferred prizes with NFTs is paid from the amusement facility 1A to the prize wholesaler 3. The transfer can be performed for multiple prizes and NFTs at once. Since the transfer is performed in a lump sum, it is easy to sell a large amount of prizes and NFTs. Furthermore, payment is made at the same time as the transfer.

[0123] The game center 1A provides one or more prizes with NFTs to the player 4 as prizes to be exchanged for game media such as pachinko balls. That is, the prizes and NFTs are transferred from the game center 1A to the player 4. At the time of this exchange, the game center terminal 31-1 and / or the player terminal 31-4 read the codes provided on each of the one or more prizes. The system 10 transmits the NFT corresponding to the read code from the blockchain address (0x1111) of the game center 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 the prize is recorded in the blockchain 20 as the transfer of the NFT corresponding to the prize. With the transfer of the NFT, the NFT, which is data corresponding to the code, and the blockchain address of the player 4, to which the prize is transferred, are recorded in association with each other in the blockchain 20.

[0124] Along with the transfer of the NFT, the physical prize is also transferred from the game arcade 1A to the player 4. In exchange for acquiring the prize with the NFT, the player 4 hands over gaming media such as pachinko balls or the rights thereto to the game arcade 1A.

[0125] In order to exchange the acquired prize for money or the like, the player 4 has the prize exchange center 2 purchase one or more prizes with NFTs. That is, the prize and the NFT are transferred from the player 4 to the prize exchange center 2. At the time of this purchase, the prize exchange center terminal 31-2 and / or the player terminal 31-4 reads the code of one or more prizes. 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 center 2. As a result, the owner of the NFT becomes the prize exchange center 2. The transfer of the prize is recorded in the blockchain 20 as the transfer of the NFT corresponding to the prize. With the transfer of the NFT, the NFT, which is data corresponding to the code, and the blockchain address of the prize exchange center 2 to which the prize is transferred are recorded in association with each other in the blockchain 20.

[0126] Along with the transfer of the NFTs, the physical prize is also transferred from the player 4 to the prize exchange 2. In addition, the prize exchange 2 pays the player 4 the value of the transferred prize with NFT. The transfer can be performed for multiple prizes and NFTs at once. Since the transfer is performed in a batch, it is easy to sell a large amount of prizes and NFTs. In addition, payment is made at the same time as the transfer.

[0127] The prize exchange center 2 sells one or more prizes with NFTs to the prize wholesaler 3. In other words, the prizes and NFTs are transferred from the prize exchange center 2 to the prize wholesaler 3. The prize wholesaler 3 can sell the prizes with NFTs purchased from the prize exchange center 2 again to the game center 1A or another game center 1B.

[0128] In the distribution of amusement park items, by using the system 10 of the embodiment, data (NFT) corresponding to the code provided on the amusement park item and the blockchain address of the transfer destination (and transfer source) of the amusement park 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 the amusement park item can be reliably recorded. Since this record is highly reliable, it is useful as gaming-related statistical data or gaming-related big data.

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

[0130] In the above description, the transfer of an NFT is performed as a change in NFT ownership from the transfer source to the transfer destination. In other words, the transfer of ownership of the NFT is recorded in the blockchain 20. However, the transfer of an NFT may also be performed as a change in the NFT usage rights from the transfer source to the transfer destination. In this case, the transfer of the usage rights of the NFT is recorded in the blockchain 20. When the transfer of an NFT is performed as a change in the NFT usage rights, the ownership of the NFT does not need to change. The ownership of the NFT can continue to be held by the administrator 5 of the system 10, for example, regardless of the change in the 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 may be used to set the usage rights. In this case, the person who has the NFT usage rights is a "user" in EIP4907. The person who has 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 the address 25A (0x1111) of the amusement facility 1A, the address 25B (0x2222) of the prize exchange facility 2, the address 25C (03333) of the prize wholesaler 3, and the address 25C (0x4444) of the player 4. That is, the amusement facility 1A, the prize exchange facility 2, the prize wholesaler 3, and the player 4 can each be a user (transfer party) of the rental NFT. Also, in FIG. 19, the second account is the address 25E (0x1234) of the administrator 5. That is, the administrator 5 is the owner of the NFTs (token_id01, token_id02, token_id03, token_id04). Administrator 5, as the owner of the NFT, 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] The administrator 5, who is the owner of the NFTs, can set users of the NFTs (token_id01, token_id02, token_id03, token_id04) through the system 10. In FIG. 10, the prize wholesaler's address 0x3333 is set as the user for the NFTs with token_id01 and token_id02. The player's address 0x4444 is set as the user for the NFT with token_id03. The arcade's address 0x1111 is set as the user for the NFT with token_id04.

[0134] For example, when the gaming facility 1A provides a prize to the player 4, first, the gaming facility terminal 31-1 and / or the player terminal 31-4 reads the code provided on each of one or more prizes, similar to the case of NFT ownership transfer.

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

[0136] Since NFT users do not have the authority to transfer NFT usage rights themselves, unauthorized transfer of NFT usage rights can be prevented. When NFT transfer is performed by transferring ownership, even administrator 5 has difficulty recovering the NFT if player 4 or others send the NFT to a third party without permission. However, when NFT transfer is performed by transferring usage rights, the NFT owner has the authority to set and cancel usage rights, so even if the NFT usage rights are transferred by mistake, administrator 5 can use his / her owner authority to cancel and reset the NFT usage rights to undo the mistaken transfer.

[0137] The game center may be a casino instead of a pachinko parlor, and the game center item may be a casino chip with an NFT. In this case, the casino chip and the NFT are transferred between the casino and the player. Also, the item with the code is not limited to the game center 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 Contracts 22A:NFT Processing 25A: Blockchain address 25B: Blockchain address 25C: Blockchain address 25D: Blockchain address 25E: Blockchain address 31: Terminal 31-1: Game terminal 31-2: Prize exchange terminal 31-3: Prize Wholesaler Terminal 31-3: Prize Wholesaler Terminal 31-4: Player terminal 31A: Processor 31B: Storage device 31C: Computer Programs 31D: Leader 31F: Registration process 40: NFC tag 41: Antenna 42: Radio circuit 43: Controller 44: Memory 46: Unique Identifier 51: Server 51A: Processor 51B: Storage device 51C: Computer Programs 51E: Corresponding data table 51F: Registration process (batch process) 91: First display data (confirmation display data) 92: Second display data (confirmation display data) 401: Prizes 402: Prizes 403: Prizes 450: Storage area 500: Paper

Claims

1. 1. A method comprising computer-implemented steps of: The steps include one or more computers: A code provided on each of the plurality of articles is read by a reader to obtain the plurality of codes, performing a batch process on a plurality of non-fungible tokens corresponding to the plurality of codes obtained; A method comprising:

2. The batch processing includes associating each of the plurality of non-fungible tokens with the same blockchain address. The method of claim 1.

3. the step further comprises providing to the display device for display on the display device confirmation display data for confirming whether or not to permit execution of the batch processing; The batch process is executed after a user operation is performed to permit execution of the batch process. The method of claim 1.

4. the process further comprising the one or more computers providing display data to a display device for display on the display device; The display data includes confirmation display data, The confirmation display data is Value display data indicating either or both of a total value of value data associated with each of the plurality of non-fungible tokens and a breakdown of the total value; the codes corresponding to each of the plurality of non-fungible tokens; data relating to the item comprising the code corresponding to each of the plurality of non-fungible tokens; and said plurality of non-fungible tokens; The data includes at least one or more data selected from the group consisting of: The method of claim 1.

5. The batch process is executed after accepting a user operation performed after acquiring the plurality of codes. The method according to any one of claims 1, 2 and 4.

6. The item is a gaming item provided to a player at the gaming facility, 5. A method according to any one of claims 1, 2 and 4 performed for the registration of a transfer of the playground item.

7. A code provided on each of the plurality of articles is read by a reader to obtain the plurality of codes, and performing a batch process on a plurality of non-fungible tokens corresponding to the obtained plurality of codes.

Images