JP2024080384A - Computer-Implemented Method and System - Google Patents

Abstract

PROBLEM TO BE SOLVED: To avoid transmitting non-fungible tokens which users already have, while maintaining the advantages of an exchange scheme.

SOLUTION: The disclosed method is a computer-implemented method for a user to obtain a second non-fungible token, which is different from a first non-fungible token, without the user parting with the first non-fungible token that is recorded in a blockchain in association with the user's account. The method includes determining whether a preset condition associated with the first non-fungible token has been met, and, if the condition is determined to have been met, recording the account that is recorded in the blockchain in association with the first non-fungible token in the blockchain in association with the second non-fungible token.

SELECTED DRAWING: Figure 1

COPYRIGHT: (C)2024,JPO&INPIT

Description

This disclosure relates to computer-implemented methods and systems.

Non-fungible tokens (NFTs) in blockchain are known as a technology for making digital data unique.

One way that a user can obtain a non-fungible token is for the user to prepare digital data and then generate a non-fungible token using that digital data.

Alternatively, users can purchase non-fungible tokens from online non-fungible token marketplaces.

As yet another method, Patent Document 1 discloses that when a user transmits a first non-fungible token, a second non-fungible token is obtained.

JP 2021-149904 A

In the following, the method of obtaining a second non-fungible token on condition that a first non-fungible token is transmitted, as in Patent Document 1, is referred to as the exchange method. The exchange method has the advantage that users who can obtain a new non-fungible token (second non-fungible token) can be limited to users who already have a non-fungible token (first non-fungible token).

However, the exchange method has the problem that the processing can be complicated. In other words, if the transmission of the first non-fungible token is required as a condition for obtaining a new second non-fungible token, the transaction of that transmission needs to be recorded on the blockchain, and processing for recording it is required.

In addition, a fee, generally known as a gas fee, must be paid to the blockchain to record data on the blockchain. For this reason, if the first non-fungible token needs to be sent, as in the exchange method, this could result in high costs.

Therefore, new technology is needed that maintains the benefits of the exchange method described above while avoiding the transmission of non-fungible tokens that users already own.

One aspect of the present disclosure is a computer-implemented method. The disclosed method is a computer-implemented method for allowing a user to obtain a second non-fungible token different from a first non-fungible token that is associated with the user's account and recorded in a blockchain without the user giving up the first non-fungible token, the method comprising: determining whether a pre-set condition associated with the first non-fungible token is satisfied; and if it is determined that the condition is satisfied, recording the account that is associated with the first non-fungible token and recorded in the blockchain in association with the second non-fungible token on the blockchain.

Another aspect of the present disclosure is a system. The disclosed system is configured to execute a process that includes determining whether a preset condition associated with a first non-fungible token is satisfied, and if it is determined that the condition is satisfied, recording an account recorded in the blockchain in association with the first non-fungible token in association with a second non-fungible token different from the first non-fungible token in the blockchain.

Further details are described in the embodiments below.

FIG. 1 is a flow chart illustrating a method according to an embodiment. FIG. 2 is an explanatory diagram of the system. FIG. 3 is a diagram showing the hardware configuration of the system. FIG. 4 is an explanatory diagram of the first scenario. FIG. 5 is an explanatory diagram of a first example of the first scenario. FIG. 6 is an explanatory diagram of a second example of the first scenario. FIG. 7 is an explanatory diagram of a third example of the first scenario. FIG. 8 is an explanatory diagram of the second scenario. FIG. 9 is an explanatory diagram of a first example of the second scenario. FIG. 10 is an explanatory diagram of a second example of the second scenario. FIG. 11 is an explanatory diagram of the third scenario. FIG. 12 is an explanatory diagram of a first example of the third scenario. FIG. 13 is an explanatory diagram of a second example of the third scenario. FIG. 14 is a flow chart illustrating a variation of the method according to the embodiment. FIG. 15 is an explanatory diagram showing an example of a display of the first non-fungible token.

<1. Overview of computer implementation method and system>

(1) A method according to an embodiment may be a computer-implemented method for a user to obtain a second non-fungible token that is different from the first non-fungible token without the user giving up the first non-fungible token that is associated with the user's account and recorded on a blockchain.

A computer-implemented method according to an embodiment may include determining whether a preset condition associated with the first non-fungible token is satisfied, and if it is determined that the condition is satisfied, recording the account recorded in the blockchain in association with the first non-fungible token in association with the second non-fungible token in the blockchain. In this case, users who can obtain the second non-fungible token can be limited to users who have the first non-fungible token. Furthermore, when the condition is satisfied, the user can obtain the second non-fungible token.

Note that recording the account in the blockchain in association with the second non-fungible token may include recording the account in the blockchain as the owner of the second non-fungible token. Also, recording the account in the blockchain in association with the second non-fungible token may include recording the account in the blockchain as a user related to the second non-fungible token other than the owner of the second non-fungible token.

(2) The condition may include that two or more of the first non-fungible tokens are recorded in association with a single account on the blockchain.

(3) The conditions may include that parameters associated with the first non-fungible token satisfy preset parameter requirements.

(4) In (2) or (3), the condition may further include detecting a specified operation performed in the account that is recorded in the blockchain in association with the first non-fungible token.

(5) In (1), the condition may include detecting a specified operation performed in the account that is recorded in the blockchain in association with the first non-fungible token.

(6) In any one of (1) to (5), the condition may include detecting an operation performed on a graphical user interface associated with the first non-fungible token.

(7) In any one of paragraphs (1) to (6), the condition may include detecting an operation performed on a graphical user interface provided by an application for displaying the first non-fungible token in the account.

(8) In any one of (1) to (7), the condition may include receiving an identifier indicating the first non-fungible token. Receiving the identifier may be receiving the identifier from the account, or may be receiving the identifier from a source other than the account.

(9) The method of any one of (1) to (8) may further include hiding the first non-fungible token in the account if it is determined that the condition is satisfied.

(10) The method of any one of (1) to (8) may further include, when it is determined that the condition is satisfied, changing at least a portion of the display of the first non-fungible token in the account from the display before the condition was satisfied.

(11) The method according to any one of (1) to (10) may further comprise generating the second non-fungible token when it is determined that the condition is satisfied. It is preferable that the account is recorded in a blockchain in association with the generated second non-fungible token.

(12) The system according to the embodiment may be configured to execute a process that determines whether a predetermined condition associated with a first non-fungible token is satisfied, and if it is determined that the condition is satisfied, records an account recorded in the blockchain in association with the first non-fungible token in association with a second non-fungible token different from the first non-fungible token in the blockchain.

<2. Examples of computer-implemented methods and systems>

FIG. 1 shows steps of a computer-implemented method according to an embodiment. This method may be executed by a computer system configured with one or more computers. This method may be executed in order for a user to obtain a new non-fungible token (NFT) without giving up an NFT that he or she already owns. In the following, an NFT that the user already owns is referred to as a "first NFT," and an NFT that the user newly obtains is referred to as a "second NFT." There may be one first NFT and one second NFT, respectively, or there may be multiple first NFTs and second NFTs.

In step S11, the computer system determines whether the conditions set in association with the first NFT are satisfied. There may be one or more conditions. If there are multiple conditions, the computer system determines whether all of the multiple conditions are satisfied. The conditions are set in advance in the computer system. If the computer system according to the embodiment determines that the conditions are satisfied, in step S12, it records the account (blockchain account) of the user who owns the first NFT in the blockchain in association with the second NFT. That is, the computer system allows the user to obtain a new second NFT without obtaining the first NFT from the user. Note that while it is not determined in step S11 that the conditions are satisfied, the user cannot obtain the second NFT.

In this way, when a condition is met, the computer system of the embodiment allows a user associated with the first NFT associated with that condition (a person who has acquired the first NFT) to acquire the second NFT at that time. This has the advantage that users who can acquire the second NFT can be limited to users who currently have acquired the first NFT.

And according to the method of the embodiment, the user can obtain the second NFT without giving up the first NFT. That is, according to the method of the embodiment, even if the user obtains the second NFT, the first NFT associated with the user's account does not lose its association with the user's account. That is, the user can obtain the second NFT while still having the first NFT.

Here, "giving up an NFT" means that the association with the NFT is no longer present in the blockchain records. "No longer associated with the NFT" means, for example, that the blockchain records make it impossible to recognize the current authorized person for the NFT. An authorized person is, for example, the owner of the NFT. In other words, "giving up an NFT" means, for example, sending the NFT to another user's account, thereby no longer owning the NFT.

In addition, "acquiring an NFT" means being associated with the NFT in the blockchain records. "Being associated with the NFT" means, for example, being recognized as the current authorized person for the NFT in the blockchain records. An authorized person is, for example, the owner of the NFT. In other words, "acquiring an NFT" means, for example, receiving the NFT from another account and thereby coming into possession of the NFT.

Here, the second NFT 420 is given to the user when the conditions are satisfied. Note that "giving an NFT" means that the computer system allows the user to obtain an NFT. The second NFT 420 may be generated in advance so as to be given to the user when the conditions are satisfied. In this case, the second NFT given to the user when the conditions associated with the first NFT are satisfied may be set in advance in the computer system. The computer system may select an NFT to be given to the user from a plurality of second NFTs generated in advance, either randomly or according to a predetermined rule, and give the selected NFT to the user.

Also, as shown in step S12 of FIG. 14, the second NFT 420 may be generated after a condition is satisfied. FIG. 14 shows a modified example of the method shown in FIG. 1. When the second NFT 420 is generated after the condition is satisfied in step S11, the computer system is advantageously not required to hold a large amount of second NFTs in stock in advance. When the second NFT 420 is generated after the condition is satisfied, the computer system may be preset with generation data for the second NFT that is generated when the condition associated with the first NFT is satisfied. The generation data is, for example, content data such as image data that constitutes the second NFT. The computer system may generate the second NFT by tokenizing the content data.

The computer system may select generation data to be used to generate the second NFT from a plurality of generation data prepared in advance, either randomly or according to a predetermined rule, and generate the second NFT using the selected generation data.

As described above, the second NFT or the data for generating the second NFT may be set in the computer system in association with the first NFT or the conditions. Furthermore, the second NFT or the data for generating the second NFT may be appropriately selected by the computer system after the conditions are satisfied.

Figure 2 shows an example of a computer system 10 in which the method according to the embodiment can be executed. Hereinafter, the "computer system 10" will be referred to as the "system 10." The system 10 according to the embodiment executes the method according to the embodiment using a blockchain 20.

The blockchain 20 is composed of a P2P (Peer to Peer) computer network in which multiple computers are interconnected.

The blockchain 20 has an address (blockchain address) that indicates the account 25A of the user U1. The blockchain address that indicates the account 25A is, for example, a wallet address. The blockchain address that indicates the account 25A is, for example, an externally owned account (EOA). For example, when a user U1 has an account 25A in the blockchain 20, the account has a specified blockchain address (wallet address). In FIG. 2, as an example, the blockchain address of the user U1 is "0x11aa".

The blockchain 20 may include a smart contract 21. The smart contract 21 is software (computer program) that is executable in the blockchain. The processing performed by the smart contract 21 may be executed by one or more computers that make up the blockchain.

The smart contract 21 automatically executes a predetermined process. When the smart contract 21 is called, the smart contract 21 may automatically execute a predetermined process. The process executed by the smart contract 21 may include an operation related to an NFT (NFT operation), such as generating and transmitting an NFT. The smart contract 21 may, for example, transmit an NFT to the account 25A. The smart contract 21 may generate an NFT and transmit the generated NFT to the account 25A. The smart contract 21 may generate an NFT such that the generated NFT is owned in the account 25A. The NFT operation executed by the smart contract 21 may be recorded in the blockchain 20.

Smart contract 21 has a contract address that is a blockchain address. In FIG. 2, as an example, the address of smart contract 21 is "0x9999".

Tokens may be recorded in the blockchain 20. Tokens recorded in the blockchain 20 include, for example, fungible tokens (Fungible Token: FT) and non-fungible tokens (Non-Fungible Token: NFT).

A non-fungible token (NFT) is a token that is not fungible, unlike a fungible token (FT). To ensure non-fungibility, an NFT has a unique token identifier (TokenID) that enables it to be distinguished from other NFTs in the blockchain 20. This token identifier is also called an NFT identifier (NFT_ID). The token identifier is recorded, for example, in a blockchain address (contract address) for storing the NFT.

In the blockchain 20, NFTs are recorded in association with the owner's account (blockchain address). In FIG. 2, the address: 0x1111, which is the account 25A of user U1, is recorded in the blockchain 20 as the owner of NFT 411 with Token ID: #0001. That is, in FIG. 2, account 25A owns NFT 411 with Token ID: #0001.

Note that FIG. 2 also shows the second NFT 420. In FIG. 2, the Token ID of the second NFT 420 is #0510. Before being obtained by the user U1, the second NFT 420 is owned, for example, by the smart contract 21.

The system 10 according to the embodiment includes a server computer 50. Hereinafter, the "server computer 50" will be referred to as the "server 50." The server 50 may be composed of multiple computers. The server 50 may be managed by an administrator. The server 50 is, for example, a Web3 server.

The terminal 31 of user U1 may access the computer system 10. The terminal 31 logs into the computer system 10 using the blockchain address of user U1. For example, the terminal 31 of user U1 may log into the server 50 using the address: 0x11aa.

Figure 3 shows the configuration of the terminal 31 and the server 50. The terminal 31 is, for example, a mobile device such as a smartphone or a tablet. The terminal 31 can be connected to a network 15 such as the Internet. The user terminal 31 can be configured by a computer including a processor 31A and a storage device 31B. The storage device 31B is connected to the processor 31A. The storage device 31B includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, 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 (application 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 to the computer to realize the functions of the terminal 31 according to the embodiment.

The functions of the terminal 31 realized by the computer program 31C include, for example, displaying the NFT owned by the user U1 on a display (not shown) of the terminal 31. The functions also include a function for logging in to the server 50.

As shown in FIG. 3, the server 50 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 the method according to the embodiment (see FIG. 1).

The storage device 51B may include condition data 50A. The condition data 50A indicates the conditions used for the judgment in step S11 of FIG. 1. That is, the condition data 50A indicates the conditions set in association with the first NFT. Note that, as shown in FIG. 1, the smart contract 21 may include the condition data 21A used for the judgment in step S11. That is, the condition data may be set in either the server 50 or the smart contract 21, or may be set in both.

The condition data 50A may include, for example, conditions set in association with the Token ID of the first NFT. The conditions may be set in association with each individual Token ID, or may be set in association with multiple Token IDs collectively.

The storage device 51B may include a database 52 having generation data used to generate the second NFT 420 in step S12 of FIG. 14. The generation data is content data including, for example, image data.

The server 50 according to the embodiment may execute the method shown in FIG. 1. The server 50 may also call the smart contract 21 to execute the method shown in FIG. 1.

Below, several scenarios based on the method shown in FIG. 1 are described. The scenarios described below may include additional steps that do not correspond to steps S11 and S12 shown in FIG. 1, but these additional steps may also constitute a method according to the embodiment. These additional steps may be performed by the system 10 shown in FIGS. 2 and 3. These additional steps may also be performed by the server 50 shown in FIGS. 2 and 3.

Figure 4 shows the first scenario. In the first scenario, before the condition indicated by the condition data 50A is satisfied, the account 25A of the user U1 owns one first NFT 411. In this state, it is assumed that the first condition set in association with the first NFT 411 is satisfied. When the system 10 determines that the first condition is satisfied (step S41), it causes the account 25A to acquire the second NFT, the second NFT 420 (step S43). Therefore, after it is determined that the first condition is satisfied, the account 25A has the second NFT 420 in addition to the first NFT 411.

The system 10 can identify the account 25A that should obtain the second NFT 420 by referring to the blockchain 20. That is, when the first condition corresponding to the first NFT 411 is satisfied, the system 10 can identify the person who has the first NFT 411 that corresponds to the first condition (the account associated with the first NFT 411) by referring to the blockchain 20. Here, "person who has an NFT" or "account who has an NFT" includes not only an "owner" or "owner's account" that is recorded in the blockchain 20 as owning the first NFT, but also a "user" or "user's account" that is recorded in the blockchain 20 as having the authority (role) to use the first NFT. The "user" is, for example, a "user" in the EIP4907 standard of Ethereum. The "user" in the EIP4907 standard is recorded in the blockchain as a person who does not own an NFT but has the authority (role) to use an NFT. EIP4907 is an extension of ERC721, the Ethereum token standard.

For example, when the system 10 determines that the first condition associated with the first NFT 411 is satisfied (step S41), the system 10 gives the second NFT 420 to the account 25A that has the first NFT 411 in the record of the blockchain 20 at that time (step S43). In other words, the account 25A is recorded in association with the second NFT 420. Note that the second NFT 420 is, for example, an NFT associated with the first NFT 411 or the first condition.

In step S45, the system 10 may hide the first NFT 411 associated with the first condition in the account 25A. For example, the system 10 may hide the first NFT 411 on the display of the terminal 31 of the user U1 who has the account 25A. By hiding the first NFT 411, the user U1 can get the feeling that he or she has given up the first NFT 411 that meets the first condition and obtained a new second NFT 420.

In the terminal 31, the display of the NFTs 411 and 420 can be performed by the application 31C of the terminal 31. The application 31C has a function of logging in to the server 50, and can cause the display of the terminal 31 to display the NFTs held by the account 25A of the user U1 who is logged in to the server 50. The server 50 can control the application 31C so that the first NFT 411, among the NFTs held by the account 25A, that satisfies the associated condition, is not displayed on the terminal 31 of the logged-in user.

Note that step S45 may be performed approximately simultaneously with step S43, or may be performed before step S43.

FIG. 5 shows a first example of the first scenario. The first condition shown in FIG. 5 is that an operation to exchange an NFT corresponding to the first condition shown in FIG. 5 has been performed. In FIG. 5, the data indicating the first NFT corresponding to the first condition includes image data included in the first NFT, an NFT_Name, and a Token ID. The NFT_Name is the name of the NFT. In FIG. 5, the NFT_Name is "nftX". In FIG. 5, #0001 to #0100 are set as the Token ID. That is, in the first condition shown in FIG. 5, it is set as the first condition associated with the first NFT that any of the 100 first NFTs named "nftX" from #0001 to #0100 is operated on the user terminal 31 of the account having the first NFT. Note that the operation is, for example, an operation on the graphical user interface B1 displayed on the display of the terminal 31 by the application 31C of the terminal 31. In addition, as the second NFT 420 to be given to the user when the first condition is satisfied, the second NFT 420 having the image data shown in FIG. 5 is set in association with the first condition.

In step S51 of FIG. 5, a list of NFTs 411, 411A held by account 25A of user U1 is displayed on the display of terminal 31. Server 50 causes the display of terminal 31 to display, via application 31C of terminal 31, the NFTs held by account 25A of user U1 who is logged in to server 50. Of these NFTs 411, 411A, at least NFT 411 is the first NFT used by user U1 to obtain second NFT 420.

In step S51, user U1 selects the first NFT 411 to be used to obtain the second NFT 420. The selection is, for example, by tapping the first NFT 111 on the display.

When the first NFT 411 is selected, the server 50 causes the application 31C to display a button ("Exchange" button) as a graphical user interface B1 that accepts an exchange operation for the first NFT 411 (an operation for acquiring the second NFT 420). As shown in step S52, when the graphical user interface B1 displayed on the display screen of the application 31C is operated, a signal indicating that the operation has been performed is transmitted from the terminal 31 to the server 50. This signal may be transmitted together with data indicating the first NFT 411 that is the subject of the exchange operation (e.g., Token ID: #0001 of the first NFT 411). The account of the user who performed the operation may be transmitted together with this signal, but this need not be transmitted since the user is logged in to the server 50.

The server 50 detects that an operation has been performed in the account 25A by receiving a signal from the terminal 31 of a user who has the account 25A indicating that the operation has been performed on the graphical user interface B1 in the application 31C of the terminal 31. When the server 50 detects that the operation has been performed, it determines that the first condition shown in FIG. 5 has been satisfied (step S41 in FIG. 4). Note that the Token ID of the first NFT 411 that was the subject of the exchange operation is #0001, and is therefore included in the Token IDs set in the first condition.

The server 50 causes the sender of the signal indicating that the operation has been performed to acquire the second NFT 420, for example by transmitting the second NFT 420 associated with the first condition to the sender (step S43 in FIG. 4). Note that the server 50 may refer to the blockchain 20 to confirm that the sender's account 25A is the account that has the operated first NFT 411, and then cause the account 25A to acquire the second NFT 420. The server 50 also hides the first NFT 411 that was the subject of the exchange operation (step S45 in FIG. 4).

Step S53 in FIG. 5 shows the display of the display of the terminal 31 in a state where the account 25A has acquired the second NFT 420 and the first NFT 411 is hidden. In this way, since the first NFT 411 that was the subject of the exchange operation is hidden, the user U1 feels as if he has given up the first NFT 411 and obtained the second NFT 420. Note that in step S53, the display of the NFT 411A that was not operated is maintained.

Figure 6 shows a second example of the first scenario. The first condition shown in Figure 6 is that the graphical user interface 415 (GUI) of the NFT corresponding to the first condition shown in Figure 6 has been operated. The graphical user interface 415 is, for example, a button that accepts the exchange of the NFT (an "Exchange" button). By the first NFT having the graphical user interface 415, the terminal 31 or the server 50 does not need to have the function of displaying the graphical user interface B1 of Figure 5.

In FIG. 6, the data indicating the first NFT corresponding to the first condition includes image data contained in the first NFT, an NFT_Name, and a Token ID. The NFT_Name and Token ID are the same as in FIG. 5. Also, as in FIG. 5, a second NFT 420 having the image data shown in FIG. 6 is set as the second NFT 420 to be given to the user when the first condition is satisfied.

In step S61 of FIG. 6, the display of the terminal 31 displays the NFT 411 held by the account 25A of the user U1. The server 50 causes the display of the terminal 31 to display the first NFT 411 held by the account 25A of the user U1 who is logged in to the server 50 via the application 31C of the terminal 31.

The first NFT 411 displayed on the display has a graphical user interface 415 that can accept user operations. User U1 operates this graphical user interface 415 by tapping, etc.

When the graphical user interface 415 is operated, a signal indicating that the operation has been performed is transmitted from the terminal 31 to the server 50. This signal is transmitted together with data indicating the first NFT 411 that was the subject of the exchange operation (e.g., Token ID: #0001 of the first NFT 411). Note that the account of the user who performed the operation may be transmitted together with this signal, but since the user is logged in to the server 50, this does not have to be transmitted.

Then, by receiving the signal, the server 50 detects that the graphical user interface 415 of the first NFT 411 has been operated, and determines that the first condition shown in FIG. 6 has been satisfied (step S41 in FIG. 4).

After that, similar to FIG. 5, the server 50 causes the sender of the signal indicating that the operation has been performed to acquire the second NFT 420 (step S43 in FIG. 4). The server 50 also hides the first NFT 411 that has been replaced (step S45 in FIG. 4).

Step S62 in FIG. 6 shows the display of the display of the terminal 31 in a state where the account 25A has acquired the second NFT 420 and the first NFT 411 is hidden. In this way, since the first NFT 411 that is the subject of the exchange operation is hidden, the user U1 can feel as if he or she has given up the first NFT 411 and obtained the second NFT 420.

In the first and second examples of the first scenario described above, the first NFT 411 may function as a voucher used to obtain the second NFT 420. A user who has obtained the first NFT 411 in some way can obtain the second NFT 420 by performing an operation at any time when the user wishes to obtain the second NFT 420. Note that in the first and second examples and other examples, if it is not necessary to hide the first NFT 411, it may be displayed instead of being hidden. For example, if multiple exchange operations are allowed, the first NFT 411 may continue to be displayed even after an exchange operation of the first NFT 411 is performed.

Figure 7 shows a third example of the first scenario. The first condition shown in Figure 7 is that the system 10 receives an identifier of an NFT corresponding to the first condition shown in Figure 7. The identifier is received by, for example, the server 50. The identifier is, for example, a Token ID or other data that can identify the NFT. In Figure 7, the data indicating the first NFT corresponding to the first condition includes image data included in the first NFT, an NFT_Name, and a Token ID. The NFT_Name and the Token ID are the same as in Figures 5 and 6. The image data included in the first NFT includes a two-dimensional code indicating the identifier of the first NFT. The two-dimensional code may be another type of machine-readable code.

The second NFT 420 shown in FIG. 7 is set as the second NFT 420 that is given to the user when the first condition is satisfied.

The first NFT here is, for example, a tokenized digital ticket, and the second NFT is, for example, a tokenized digital stub.

A digital ticket is an electronically issued ticket that includes ticket data for electronically configuring the ticket. A digital ticket is, for example, an electronic version of an admission ticket to an event, an admission ticket to a facility, a ticket for a vehicle, a ticket for enjoying other services, a ticket for exchanging goods, a gift certificate, or a discount coupon. An event is, for example, a concert, a movie, a play, an exhibition, an exposition, a sporting event, or a festival. A facility is, for example, an amusement park, a zoo, a botanical garden, an art gallery, a museum, a movie theater, a store, or a tourist attraction. A vehicle is, for example, an airplane, a ship, a train, a bus, or a taxi.

A digital ticket contains the data required for a ticket. Examples of the data required for a ticket include the venue, event name, date and time, and seating information.

A digital stub is an electronic version of the stub (half ticket) that remains after a paper ticket has been used. A digital stub may be stored in one-to-one correspondence with a digital ticket, or it may be stored in correspondence with multiple digital tickets.

For example, if the digital stub contains data that is the same as data specific to an individual digital ticket, such as seating data, among the data contained in the digital ticket, the digital stub will be in one-to-one correspondence with the digital ticket. Also, if the digital stub contains only data that can be shared by multiple digital tickets, such as data on the event name, among the data contained in the digital ticket, one digital stub can be associated with multiple digital tickets.

A digital stub has data required for a stub (ticket stub). In the case of a digital stub corresponding to a digital ticket for admission to an event, the data required for the stub is, for example, data related to the venue, event name, date and time, and seating. A digital stub does not need to have all of the data that a corresponding digital ticket has; it is sufficient if it has at least some of the data (for example, data related to the venue, event name, date and time, and seating). It is preferable for a digital stub to have data specific to the digital stub that is not included in the digital ticket. The data specific to the digital stub is data indicating that it is a stub, data indicating that the digital ticket has been used, and/or other digital data.

Now, in step S71 of FIG. 7, the display of the terminal 31 shows a first NFT 411, which is a tokenized digital ticket. The displayed first NFT 411 includes a two-dimensional code 413 indicating an identifier of the first NFT 411.

The displayed two-dimensional code 413 is read by a two-dimensional code reader 70. The reader 70 is used, for example, at the venue, facility, or vehicle where the digital ticket is used. For example, in the case of a digital ticket for an event, the two-dimensional code 413 of the first NFT 411 is read by a reader 70 installed at the venue of the event when a user participates in the event. An identifier of the first NFT 411 is obtained by reading with the reader 70. The identifier of the first NFT 411 obtained by the reader 70 is transmitted to the system 10 via the network 15. For example, the identifier is transmitted to the server 50. By receiving the identifier of the first NFT 411, the server 50 determines that the first condition shown in FIG. 7 is satisfied (step S41 in FIG. 4).

The server 50 causes the account 25A having the first NFT 411 indicated by the identifier to acquire the second NFT 420 having digital data such as a digital stub (step S43 in FIG. 4). The server 50 also makes the first NFT indicated by the identifier invisible (step S45).

Step S72 in FIG. 7 shows the display of the display of terminal 31 when account 25A acquires second NFT 420 and first NFT 411 is hidden. In this way, because the used first NFT 411 is hidden, user U1 can feel as if he has given up first NFT 411, which is a digital ticket, and obtained second NFT 420, which is a digital stub. In addition, because first NFT 411 is hidden, the use of the used digital ticket can be essentially prohibited.

Note that if the digital ticket can be used multiple times, the first NFT does not have to be hidden even when the digital ticket is used. In this case, the first NFT may be hidden, for example, when the digital ticket loses its validity. Loss of validity may occur, for example, when the digital ticket's expiration date has passed or when the number of times the digital ticket can be used has been exceeded.

Figure 8 illustrates a second scenario. In the second scenario, the conditions associated with the first NFT include a first condition and a second condition. The system 10 allows the user to obtain the second NFT 420 when both the first condition and the second condition are satisfied. Note that the explanations of the first scenario and its examples are applicable to points that are not specifically explained in the second scenario.

In FIG. 8, the account 25A of the user U1 has two (or more) predetermined first NFTs 411, 412. As an example, the system 10 determines that the first condition is satisfied based on this state (step S81). That is, the system 10 determines that the first condition is satisfied when it references the blockchain 20 and detects that the two predetermined first NFTs 411, 412 are recorded in association with a single account 25A in the blockchain 20. For example, the system 10 references the blockchain 20 based on the account 25A of the user logged in to the server 50, and identifies the NFTs 411, 412 recorded in association with that account 25A.

Also, as an example, when the first condition is satisfied and the second condition is satisfied, the system 10 allows the user to obtain the second NFT 420. The second condition is, for example, detecting an operation to acquire the second NFT 420 (step S82). That is, when a plurality of predetermined first NFTs 411, 412 are present in a single account 25A, the system 10 determines that the first condition and the second condition are satisfied when an operation to acquire the second NFT 420 is performed in the account 25A.

When the system 10 determines that the first condition and the second condition are satisfied (steps S81 and S82), the system 10 gives the second NFT 420 to the account 25A that has the first NFT 411 in the record of the blockchain 20 at that time (step S83). In other words, the account 25A is recorded in association with the second NFT 420.

In addition, in step S85, the system 10 may hide the first NFTs 411 and 412 in the account 25A that has acquired the second NFT 420 in the account 25A. For example, the system 10 may hide the first NFTs 411 and 412 on the display of the terminal 31 of the user U1 who has the account 25A. By hiding the first NFTs 411 and 412, the user U1 can get the feeling that the conditions have been met and that he or she has given up the first NFTs 411 and 412 and acquired the second NFT 420.

Note that step S85 may be performed approximately simultaneously with step S83, or may be performed before step S83.

Figure 9 shows a first example of the second scenario. The first condition shown in Figure 9 is that two (or more) NFTs corresponding to the first condition shown in Figure 9 are present in a single account. In Figure 9, the data indicating the first NFT is the same as that shown in Figure 5. In addition, the second NFT 420 is set as the second NFT 420 given to the user when the first and second conditions are met, similar to Figure 5.

9, a list of NFTs 411 and 412 owned by the account 25A of the user U1 is displayed on the display of the terminal 31. In the state of step S91, the system 10 determines that the first condition is satisfied (step S81 in FIG. 8). For example, the server 50 refers to the blockchain 20 and acquires the Token IDs of the first NFTs 411 and 412 associated with the account 25A of the user who is logged in to the server 50. Here, as shown in FIG. 8, the account 25A is associated with two NFTs, the first NFT 411 with a Token ID of #0001 and the first NFT 412 with a Token ID of #0012. The Token IDs of these two NFTs 411 and 412 are included in the Token IDs of the NFTs corresponding to the first condition shown in FIG. 9. Therefore, the server 50 determines that the first condition is satisfied in the account 25A.

When the server 50 determines that the first condition is satisfied by the two first NFTs 411, 412, the server 50 displays a button ("Exchange" button) as a graphical user interface B1 that accepts an operation to acquire the second NFT 420 via the application 31C of the terminal 31. As shown in step S92, when the graphical user interface B1 displayed on the display screen of the application 31C is operated, a signal indicating that the operation has been performed is transmitted from the terminal 31 to the server 50.

The server 50 detects that an operation has been performed by receiving from the terminal 31 a signal indicating that an operation has been performed on the graphical user interface B1 in the application 31C of the terminal 31. When the server 50 detects that an operation has been performed, the server 50 determines that the second condition has been satisfied (step S82 in FIG. 8).

The server 50 then gives the second NFT 420 to the account 25A that currently has the first NFTs 411 and 412 (step S83 in FIG. 8). The server 50 also hides the first NFTs 411 and 412. Note that the second condition may be omitted, and the second NFT 420 may be given to the account 25A when the first condition is met. In this case, a user who meets the first condition can obtain the second NFT 420 without performing an exchange operation.

Step S92 in FIG. 9 shows the display of the display of the terminal 31 in a state where the account 25A has acquired the second NFT 420 and the two first NFTs 411, 412 are hidden. In this way, because the first NFTs 411, 412 are hidden, the user U1 can feel as if he has given up the first NFTs 411, 412 and acquired the second NFT 420. For example, if the first NFTs 411, 412 are first game items (game characters) in a blockchain game and the second NFT 420 is an evolved item of the first game item, the user U1 can acquire the evolved item by collecting multiple first NFTs 411, 412.

Figure 10 shows a second example of the second scenario. The first condition shown in Figure 10 is that both a first type NFT and a second type NFT corresponding to the first condition shown in Figure 10 are present in a single account. In other words, the first condition in Figure 10 is that a predetermined number of types of NFTs are present in a single account.

In Figure 10, the first type of NFT has an NFT_Name of "nftX" and a TokenID of #0001 to #0100. The second type of NFT has an NFT_Name of "nftY" and a TokenID of #8001 to #8100.

When these two different types of NFTs are collected in user U1's account 25A, the server 50 causes account 25A to acquire a second NFT 420. The other points in the second example shown in FIG. 10 are the same as those in the first example shown in FIG. 9, and therefore will not be described.

FIG. 11 shows the third scenario. In the third scenario, similar to the second scenario, the conditions associated with the first NFT include the first condition and the second condition. When both the first condition and the second condition are satisfied (steps S111 and S112), the system 10 allows the user to obtain the second NFT 420 (step S113). In addition, the first NFT 411 is hidden (step S115). In the third scenario, similar to the first scenario, the account 25A before the conditions are satisfied has one first NFT 411, and the account 25A after the conditions are satisfied has the first NFT 411 and the second NFT 420. Note that the explanations of the first and second scenarios and their examples are used for points that are not specifically explained in the third scenario.

Figure 12 shows a first example of the third scenario. The conditions shown in Figure 12 include a first condition and a second condition. The second condition shown in Figure 12 corresponds to the first condition shown in Figure 6. In other words, the second condition shown in Figure 12 is that the graphical user interface 415 of the NFT has been operated.

The first condition shown in FIG. 12 is that some parameter associated with the first NFT 411 satisfies a preset parameter requirement. Here, the parameter is, as an example, a date and time. The parameter requirement is, for example, a deadline. In FIG. 12, a deadline of "July 1, 2023" is set as the parameter requirement. The system 10, for example, has a system clock and keeps track of the date and time. The system 10 monitors the date and time as a parameter associated with the first NFT, and when the preset deadline has passed, it determines that the parameter requirement has been satisfied. In other words, when the deadline as the parameter requirement has passed, it is determined that the first condition has been satisfied (step S111 in FIG. 11).

The first NFT associated with the first condition is, for example, the NFT shown in the second condition in FIG. 12 (the NFT with Token ID #0001 to #0100).

Step S121 in FIG. 12 shows the display state on the terminal 31 of user U1 before the deadline (July 1, 2023) as a parameter requirement. As an example, in the first NFT in FIG. 12, the graphical user interface 415 is not displayed and operations on the graphical user interface 415 are not possible before the deadline has passed (before the first condition is satisfied). Note that the graphical user interface 415 may be configured to be displayed even before the deadline has passed (before the first condition is satisfied) but not to accept operations.

When the deadline has passed, as shown in step S122 of FIG. 12, the NFT 411 held by the account 25A of the user U1 is displayed on the display of the terminal 31. When the deadline associated with the first NFT 411 has passed, the server 50 causes a graphical user interface 415 to be displayed in the image of the first NFT 411 via the application 31C of the terminal 31. Thus, the user U1 becomes able to operate the graphical user interface 415.

When user U1 operates the graphical user interface 415, a signal indicating that the operation has been performed is transmitted from the terminal 31 to the server 50. This signal is transmitted together with data indicating the first NFT 411 that is the subject of the exchange operation (e.g., Token ID of the first NFT 411: #0001).

Then, by receiving the signal, the server 50 detects that the graphical user interface 415 of the first NFT 411 has been operated, and determines that the second condition shown in FIG. 12 has been satisfied (step S112 in FIG. 11).

After that, similar to FIG. 6, the server 50 causes the sender of the signal indicating that the operation has been performed to acquire the second NFT 420 (step S113 in FIG. 11). The server 50 also hides the first NFT 411 that has been replaced (step S115 in FIG. 11).

Step S123 in FIG. 12 shows the display of the display of the terminal 31 in a state where the account 25A has acquired the second NFT 420 and the first NFT 411 is hidden. In this way, since the first NFT 411 that is the subject of the exchange operation is hidden, the user U1 can feel as if he or she has given up the first NFT 411 and obtained the second NFT 420.

In the example shown in FIG. 12, the first NFT 411 may function as a voucher used to obtain the second NFT 420. A user who obtains the first NFT 411 in some way can obtain the second NFT 420 by performing an operation at any time after the expiration date. Note that the second condition may be omitted. In other words, when the expiration date has passed (when the first condition has been satisfied), the user U1 may be allowed to obtain the second NFT 420 without operating the graphical user interface 415.

The parameter requirement and the parameters that must satisfy the parameter requirement are not limited to a date and time (deadline), and may be other parameters. The other parameters may be, for example, points or a level in an online game such as a blockchain game. When the points or level held by user U1 in the game reaches a specified number of points or level as a parameter requirement, user U1 can obtain the second NFT 420.

The other parameters may also be data relating to user U1 acquired on the terminal 31 of user U1. The data relating to user U1 is, for example, health care data or vital data. The health care data or vital data is, for example, one or more pieces of data selected from the number of steps, walking distance (including running distance), blood pressure, heart rate, energy consumption, sleep time, and exercise time. If any of the data satisfies the parameter requirements, the user may acquire the second NFT 420. For example, if the number of steps taken by the user exceeds the number of steps set as the parameter requirements, the user may acquire the second NFT 420.

The other parameter may be location information of user U1. The location information is, for example, location information in a satellite positioning system such as GNSS. The location information is acquired, for example, by terminal 31. For example, when the location information detects that user U1 is in a predetermined location set as a parameter requirement, the user may acquire the second NFT 420.

Figure 13 shows a second example of the third scenario. The conditions shown in Figure 13 include a first condition and a second condition. The second condition shown in Figure 13 corresponds to the first condition shown in Figure 5. In other words, the second condition shown in Figure 13 is that an operation to obtain a first NFT associated with the second condition has been performed in application 31C. Note that the first NFT associated with the second condition is, for example, an NFT shown in the first condition in Figure 13 (an NFT with a Token ID from #0001 to #0100).

The first condition shown in FIG. 13 is that the system 10 (server 50) receives specific registration data from an account 25A having the first NFT 411. The registration data is data that has been preregistered in the system (server 50). The registration data is acquired from an external source, for example, by the terminal 31 (step S131). The terminal 31 transmits the acquired registration data to the system 10. When the system 10 receives data that is the same as the data that has been preregistered in association with the first NFT 411 from the account 25A having the first NFT 411, it determines that the first condition is met (step S111 in FIG. 11).

When the terminal 31 acquires the registration data from the outside, for example, the terminal 31 reads a two-dimensional code indicating the registration data, or receives the registration data from an external communication device via wireless communication. The external communication device may be, for example, a device for near field communication (NFC). The external communication device may be, for example, an integrated circuit (IC) capable of wireless communication. The integrated circuit capable of wireless communication may be, for example, an IC tag. The IC tag may be, for example, an NFC tag. The registration data may be, for example, a unique identifier (UID) that individually identifies the integrated circuit capable of wireless communication.

The two-dimensional code or external communication device is distributed to user U1 or installed at a location that user U1 visits. User U1 reads the two-dimensional code with terminal 31, or brings terminal 31 close to the external communication device to obtain the registration data. It is preferable that the application 31C of terminal 31 has the function of reading the two-dimensional code and/or the function of communicating with the external communication device.

When the terminal 31 of user U1 is logged in to the server 50 using account 25A and the server 50 receives registration data from the terminal 31, the server 50 causes the application 31C to display a button ("Acquire" button) as a graphical user interface B1 that accepts an acquisition operation of the second NFT 420.

As shown in step S132, when the graphical user interface B1 displayed on the display screen of application 31C is operated, a signal indicating that the operation has been performed is transmitted from terminal 31 to server 50. This signal may be transmitted together with data indicating the first NFT 411 held by user U1's account 25A (e.g., Token ID of first NFT 411: #0001). Note that the account of the user who performed the operation may be transmitted together with this signal, but this need not be transmitted since the user is logged in to server 50.

The server 50 detects that an operation has been performed by receiving from the terminal 31 a signal indicating that an operation has been performed on the graphical user interface B1 in the application 31C of the terminal 31. When the server 50 detects that an operation has been performed, the server 50 determines that the second condition shown in FIG. 13 has been satisfied (step S112 in FIG. 11).

The server 50 causes the account 25A (account having the first NFT 411) of the user U1 that read the registration data to acquire the second NFT 420 associated with the first and second conditions (step S113 in FIG. 1). Note that the server 50 may refer to the blockchain 20 to confirm that the account 25A of the user U1 that read the registration data has the first NFT 411 before causing the account 25A to acquire the second NFT 420. The server 50 also makes the first NFT 411 used to acquire the second NFT 420 invisible (step S115 in FIG. 11).

Step S133 in FIG. 13 shows the display of the display of the terminal 31 in a state where the account 25A has acquired the second NFT 420 and the first NFT 411 is hidden. In this way, since the first NFT 411 used to acquire the second NFT 420 is hidden, the user U1 can feel as if he has given up the first NFT 411 and obtained the second NFT 420.

13, the first NFT 411 may have a role similar to a voucher used to obtain the second NFT 420. Moreover, in the example shown in FIG. 13, in order to obtain the second NFT 420, the user is required to not only have the first NFT 411 but also to obtain the registration data. Therefore, in the example shown in FIG. 13, the users who can obtain the second NFT 420 can be limited to those who have the first NFT 411 and have obtained the registration data. For example, only users who have obtained a two-dimensional code or an external communication device, or only users who have visited a place where a two-dimensional code or an external communication device is installed, can obtain the second NFT 420. Moreover, the second condition may be omitted. In other words, when the registration data is obtained (when the first condition is satisfied), the user U1 may obtain the second NFT 420 without operating the graphical user interface 415.

Figure 15 shows an example (variant) of the display mode of the first NFT 411 after it has been used to acquire the second NFT 420. In Figure 15, in step S151, the first NFT 411 is used to acquire the second NFT 420. In step S152 after the condition is satisfied and the second NFT 420 is acquired, the first NFT 411 is not hidden but remains displayed. However, whereas in step S151 the exchange button 415, which is a graphical user interface, is displayed in the first NFT 411, in step S152 "Exchanged" 411A is displayed. "Exchanged" 411A indicates that the first NFT 411 has already been used to acquire the second NFT 420. No operation can be performed on "Exchanged" 411A. Thus, in the example shown in FIG. 15, when the system 10 determines that the condition associated with the first NFT 411 held by the account 25A is satisfied, the system 10 causes at least a portion of the display of the first NFT 411 in the account 25A to differ from that before the condition was satisfied via the application 31C. This allows the user to know that the first NFT 411 has been used.

The conditions associated with the first NFT 411 are not limited to those exemplified in the above description, and may be other conditions. The other conditions may be, for example, that a fungible token or other digital asset (excluding an NFT) has been sent from the account 25A of the first NFT 411 to the system 10.

Another condition may be that the system 10 detects an action performed by the user U1 having the first NFT 411 in the real world or in a virtual space such as the metaverse. In this case, when the user having the first NFT 411 performs a predetermined action, the second NFT 420 can be obtained. The action performed by the user U1 in the real world may be, for example, visiting a predetermined store, purchasing a product or service at a predetermined store, entering an event venue, visiting a facility or a predetermined place, or reaching the finish line in a competition with a finish line. An example of a competition with a finish line is a marathon or a triathlon. The action performed by the user in the virtual space is, for example, performing an action in the virtual space that corresponds to the action performed by the user U1 in the real world described above. The action performed by the user in the virtual space may also be, for example, completing a game.

In addition, the other condition does not necessarily have to be that the system 10 detects an action actively performed by the user, but may be that the system 10 detects an event occurring in the real world or virtual space related to the user. An event occurring in the real world related to the user is, for example, the user winning a lottery.

The present invention is not limited to the above embodiment, and various modifications are possible.

10: System 15: Network 20: Blockchain 21: Smart contract 21A: Condition data 25A: Account 31: Terminal 31A: Processor 31B: Storage device 31C: Application (computer program)
50: Server 50A: Condition data 51A: Processor 51B: Storage device 51C: Computer program 52: Database 70: Reading device 411: First non-fungible token (first NFT)
412: First non-fungible token (first NFT)
413: Two-dimensional code 415: Graphical user interface (Exchange button)
420: Second non-fungible token B1: Graphical user interface U1: User

Claims (12)

1. A computer-implemented method for a user to obtain a second non-fungible token different from a first non-fungible token without the user giving up a first non-fungible token associated with the user's account and recorded on a blockchain, the method comprising:
determining whether a predefined condition associated with the first non-fungible token is satisfied;
If it is determined that the condition is satisfied, recording the account recorded on the blockchain in association with the first non-fungible token in association with the second non-fungible token on the blockchain. 2. The computer-implemented method of claim 1 , wherein the condition includes that two or more of the first non-fungible tokens are recorded in association with a single account on a blockchain. 2. The computer-implemented method of claim 1, wherein the condition includes that parameters associated with the first non-fungible token satisfy pre-defined parameter requirements. The computer-implemented method of claim 2 or claim 3, wherein the condition further includes detecting a predetermined operation performed on the account recorded in a blockchain in association with the first non-fungible token. The computer-implemented method of claim 1 , wherein the condition includes detecting a predetermined operation performed on the account recorded on a blockchain in association with the first non-fungible token. The computer-implemented method of claim 1 , wherein the condition includes detecting an action taken on a graphical user interface associated with the first non-fungible token. The computer-implemented method of claim 1 , wherein the condition includes detecting an operation performed on a graphical user interface provided by an application for displaying the first non-fungible token in the account. The computer-implemented method of claim 1 , wherein the condition includes receiving an identifier indicative of the first non-fungible token. The computer-implemented method of claim 1 , further comprising: hiding the first non-fungible token from the account if it is determined that the condition is satisfied. 2. The computer-implemented method of claim 1, further comprising: if it is determined that the condition is satisfied, causing at least a portion of the representation of the first non-fungible token in the account to differ from before the condition was satisfied. generating the second non-fungible token if it is determined that the condition is satisfied;
The computer-implemented method of claim 1 , wherein the account is recorded on a blockchain in association with the generated second non-fungible token. determining whether a predefined condition associated with the first non-fungible token is satisfied;
When it is determined that the condition is satisfied, the system is configured to execute a process comprising: recording on the blockchain an account associated with the first non-fungible token in association with a second non-fungible token different from the first non-fungible token.

Images