JP2024083998A - Information processing device, method, program, and system manufacturing method - Google Patents

Abstract

[Problem] To provide a technology for adding practical uses to NFTs. [Solution] A program according to one aspect of the present disclosure causes a computer to function as a means for presenting at least one NFT (Non-Fungible Token) held in a wallet, a means for selecting a target NFT that is one of the at least one NFT in response to an instruction from a user, and a means for presenting information on crypto assets associated with the target NFT in a vault defined by a smart contract. [Selected Figure] Figure 5

Description

This disclosure relates to an information processing device, method, program, and system production method.

Non-Fungible Tokens (NFTs) are uniquely associated with digital content, such as digital art. NFTs are used to assert authenticity and ownership of the digital content associated with the NFT.

Owners of NFTs associated with digital content can enjoy that digital content and experience the feeling of owning it. Games using NFTs are also being developed.

Patent document 1 describes a technology that aims to give points to a user based on an NFT associated with the user.

JP 2019-192150 A

It cannot be said that conventional NFTs have sufficient practical applications.
Although the technology of Patent Document 1 may provide users with secondary economic benefits by holding NFTs, it does not expand the uses of NFTs themselves.

The purpose of this disclosure is to provide technology that adds practical applications to NFTs.

A program according to one embodiment of the present disclosure causes a computer to function as a means for presenting at least one NFT (Non-Fungible Token) held in a wallet, a means for selecting a target NFT that is one of the at least one NFT in response to an instruction from a user, and a means for presenting information on crypto assets associated with the target NFT in a vault defined by a smart contract.

1 is a block diagram showing a configuration of an information processing system according to an embodiment of the present invention; FIG. 2 is a block diagram showing a configuration of a client device according to the present embodiment. FIG. 1 is a diagram illustrating a configuration of a distributed ledger system according to an embodiment of the present invention. FIG. 1 is an explanatory diagram of payment using crypto assets held in a wallet. FIG. 1 is an explanatory diagram of one aspect of the present embodiment. 4 is a flowchart of a deposit process according to the present embodiment. 13 is a flowchart of a withdrawal process according to the present embodiment. FIG. 13 is a diagram showing an example of a screen displayed in the withdrawal process of this embodiment. FIG. 13 is a diagram showing an example of a screen displayed in the withdrawal process of this embodiment. FIG. 13 is a block diagram showing a configuration of an information processing system according to a first modified example. FIG. 13 is a block diagram showing a configuration of a server according to the first modified example. 13 is a flowchart of a payment process according to the first modified example.

One embodiment of the present invention will be described in detail below with reference to the drawings. In the drawings used to explain the embodiment, the same components are generally designated by the same reference numerals, and repeated explanations will be omitted.

(1) Configuration of the Information Processing System The configuration of the information processing system will be described below. Fig. 1 is a block diagram showing the configuration of the information processing system according to this embodiment.

As shown in FIG. 1 , the information processing system 1 includes a client device 10 and a distributed ledger system 50 .
The client device 10 and the distributed ledger system 50 are connected via a network NW (e.g., the Internet or an intranet).

The client device 10 is an example of an information processing device that transmits a request to an external device (e.g., the distributed ledger system 50). The client device 10 is, for example, a smartphone, a tablet terminal, or a personal computer. The user of the client device 10 is a person who performs a transaction regarding the transfer of, for example, crypto assets or tokens (which may include NFTs (Non-Fungible Tokens)) in a specific payment system realized by the distributed ledger system 50. Here, the term "crypto assets" is used to include not only crypto assets issued on a unique blockchain (network) (crypto assets in the narrow sense, also called platform tokens), but also unique crypto assets issued using existing blockchain technology (so-called tokens (Fungible Tokens)).

The distributed ledger system 50 manages a distributed ledger. As an example, the distributed ledger system 50 manages a transaction history regarding transfers of crypto assets or tokens (which may include NFTs). In particular, as described below, the distributed ledger system 50 manages crypto assets in association with NFTs in a vault defined by a smart contract. Such management may include at least one of the following:
・Transferring crypto assets from the vault to another wallet ・Receiving crypto assets from another wallet to the vault ・Associating crypto assets with NFTs ・Disassociating crypto assets from NFTs ・Understanding the association status of crypto assets with NFTs

The distributed ledger is, for example, a blockchain. The distributed ledger system 50 includes multiple computers (which may include client devices 10) that are interconnected. The distributed ledger system 50 also stores smart contracts for implementing each function of the payment system, and the smart contracts are executed in response to requests from the client devices 10.

(1-1) Configuration of the Client Device The configuration of the client device will be described below with reference to Fig. 2, which is a block diagram showing the configuration of the client device according to this embodiment.

As shown in FIG. 2, the client device 10 includes a storage device 11, a processor 12, an input/output interface 13, and a communication interface 14. The client device 10 is connected to a display 21.

The storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of Read Only Memory (ROM), Random Access Memory (RAM), and storage (for example, flash memory or a hard disk).

The programs include, for example, the following programs:
- Operating System (OS) programs - Applications (e.g. web browsers) that process information

The data includes, for example, the following data:
- Databases referenced in information processing - Data obtained by executing information processing (i.e., the results of executing information processing)

The processor 12 is a computer that realizes the functions of the client device 10 by running a program stored in the storage device 11. The processor 12 is, for example, at least one of the following:
・CPU (Central Processing Unit)
・GPU (Graphic Processing Unit)
・ASIC (Application Specific Integrated Circuit)
・FPGA (Field Programmable Array)

The input/output interface 13 is configured to obtain information (e.g., a user's instruction) from an input device connected to the client device 10 , and to output information (e.g., an image) to an output device connected to the client device 10 .
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display 21, a speaker, or a combination thereof.

The communication interface 14 is configured to control communication between the client device 10 and an external device (e.g., the distributed ledger system 50).

The display 21 is configured to display an image (still image or video). The display 21 is, for example, a liquid crystal display or an organic EL display.

(1-2) Configuration of the distributed ledger system The configuration of the distributed ledger system will be described. Fig. 3 is a diagram showing the configuration of the distributed ledger system of this embodiment.

As shown in FIG. 3, the distributed ledger system 50 includes multiple node computers 55-1 to 55-4.

The node computers 55 are connected to each other via a network (which may include the network NW of FIG. 1). In this embodiment, the network may include a public network, a private network, a leased line, a Virtual Private Network (VPN), or a combination thereof. The node computers 55 are connected to the network, for example, by wire or wirelessly. The node computers 55 communicate with each other in a peer-to-peer manner.

The node computer 55 manages the distributed ledger using, for example, blockchain technology.
Specifically, one of the node computers 55 acquires data related to cryptocurrency or token transactions to be recorded. The node computer 55 creates a block including the acquired data and adds it to the blockchain. The node computer 55 transmits information about the added block to the other node computers 55. The other node computers 55 verify the correctness of the received block, and if the verification is successful, add the block to the blockchain. The node computer 55 finalizes the blockchain according to, for example, the number of linked blocks (number of approvals). As a result, the same distributed ledger is stored across the multiple node computers 55 that make up the distributed ledger system 50. The stored data is encrypted as appropriate.

The configuration of the distributed ledger system 50 is not limited to that shown in FIG. 3. For example, the distributed ledger system 50 may include five or more node computers 55, or may include two or three node computers 55. In addition, the number of node computers 55 constituting the distributed ledger system 50 may change over time.

The hardware configuration of the node computer 55 may be the same as or similar to that of the client device 10, so a detailed description will be omitted. As an example, the node computer 55 includes a processor, a storage device, an input/output interface, a communication interface, an input device, an output device, or a combination thereof.

(2) One aspect of the embodiment One aspect of the embodiment will be described. Fig. 4 is an explanatory diagram of a settlement using crypto assets held in a wallet. Fig. 5 is an explanatory diagram of one aspect of the embodiment.

The basic functions of the information processing system 1 allow users of the client device 10 to make payments using crypto assets held in their wallets.

As shown in FIG. 4, the client device 10 logs in to the wallet W12 in response to instructions from the user U11. The client device 10 queries the distributed ledger system 50 for information on the crypto assets held in the wallet W12. The client device 10 obtains information on the crypto assets held in the wallet W12 and presents it to the user U11.

User U11 confirms the presented information and selects the crypto asset to be used for payment (e.g., A Coin held in wallet W12). Client device 10 requests a transaction corresponding to the payment using the selected crypto asset from distributed ledger system 50. Distributed ledger system 50 executes the requested transaction.

Furthermore, users of client device 10 can make payments with crypto assets using NFTs (Non-Fungible Tokens) held in their wallets. Specifically, a vault is defined by a smart contract executed by distributed ledger system 50. The vault holds crypto assets in association with NFTs, and is configured to permit access (withdrawal) of the crypto assets held in the vault only to holders of the NFTs associated with the crypto assets and to owner addresses corresponding to the master key. Deposits and withdrawals of crypto assets into the vault are performed by distributed ledger system 50 in response to requests from client device 10.

In other words, as shown in FIG. 5, user U11 may select one of the NFTs (e.g., NFT β) (hereinafter referred to as the "target NFT") instead of the crypto asset (e.g., Coin A) held in wallet W12. In this case, client device 10 queries the distributed ledger system 50 for information on the crypto asset associated with the target NFT in vault V13. Client device 10 obtains information on the crypto asset associated with the target NFT in vault V13 and presents it to user U11.

The user U11 confirms the presented information and selects the crypto asset to be used for payment (e.g., A coin associated with the target NFT in the vault V13). The client device 10 requests the distributed ledger system 50 to make a transaction corresponding to the payment with the selected crypto asset. The distributed ledger system 50 executes the requested transaction.

In this way, according to the information processing system 1, the user can use the NFT held in his/her wallet for payment as if it were a prepaid card. In addition, like a prepaid card, when the NFT is transferred, the cryptocurrency associated with the NFT is also substantially transferred. In other words, the cryptocurrency associated with the NFT in the vault cannot be withdrawn by anyone other than the current holder of the NFT, even if the holder was a past holder. Therefore, the cryptocurrency can be substantially transferred to another person simply by transferring the NFT to another person. By using this mechanism, the NFT to which the cryptocurrency is associated can be presented as a gift. In addition, the cryptocurrency associated with the NFT in the vault is independent of the cryptocurrency associated with other NFTs and the cryptocurrency held in the wallet, so that it is easy to manage deposits or expenditures for different purposes, for example. In short, according to this embodiment, practical uses other than viewing digital content can be added to the NFT.

(3) Information Processing The information processing of this embodiment will be described.
In the following explanation, it may be stated that the distributed ledger system 50 executes some processing, but in reality, such processing will be executed by at least one of the node computers that make up the distributed ledger system 50.

(3-1) Deposit Processing The deposit processing of this embodiment will now be described with reference to the flowchart of FIG.

The deposit process of this embodiment may be started in response to a user's instruction, for example, while the client device 10 is executing a specific application (e.g., a payment application for making a payment with crypto assets, or a web browser for displaying a SaaS (Software as a Service) screen for making a payment with crypto assets).

As shown in FIG. 6, the client device 10 executes the presentation of the NFT (S210).
Specifically, the client device 10 queries the distributed ledger system 50 for information on NFTs held in the currently logged-in wallet. If the client device 10 is not logged in to the wallet, the client device 10 may request the user to log in to the wallet prior to the query. The client device 10 queries the distributed ledger system 50 for information on NFTs held in the wallet. In response to the request, the distributed ledger system 50 transmits the NFT information to the client device 10. The client device 10 presents the NFT information to the user. As an example, the client device 10 displays a screen based on the NFT information on the display 21.

The information in the NFT may include, for example, at least one of the following:
- Digital content corresponding to the NFT (which may include a miniature version, such as a thumbnail image, for example)
・Contract address ・Token ID
・Token standard/vault balance of associated cryptocurrency

After step S210, the client device 10 selects an NFT (S211).
Specifically, the client device 10 receives an instruction from the user to select one of the NFTs from the information presented in step S210. The client device 10 queries the distributed ledger system 50 for information on the crypto asset associated with the selected NFT in the vault.

After step S211, the distributed ledger system 50 obtains information on the crypto assets (S250).
Specifically, in step S211, the distributed ledger system 50 receives the inquiry sent by the client device 10. In response to the received inquiry, the distributed ledger system 50 transmits, in the vault, to the client device 10, information on the crypto asset associated with the NFT selected by the user.

After step S250, the client device 10 presents information about the crypto asset (S212).
Specifically, the client device 10 receives the information transmitted by the distributed ledger system 50 in step S250. The client device 10 presents the received information. As an example, the client device 10 displays a screen based on the crypto asset information on the display 21.

The cryptocurrency information includes information indicating the cryptocurrency brand (e.g., the name of the cryptocurrency, the ticker symbol of the cryptocurrency, the icon of the cryptocurrency, the contract address of the cryptocurrency, or a combination thereof) and information indicating the balance of the cryptocurrency.

After step S212, the client device 10 executes acceptance of a deposit instruction (S213).
Specifically, the client device 10 accepts an instruction from the user to deposit any of the crypto assets associated with the selected NFT based on the information presented in step S212. Here, depositing means transferring the crypto assets in the source from the source to the vault and associating them with the NFT to be deposited in the vault. The source means the source of the crypto assets deposited in the NFT, and may be, for example, a wallet or another NFT associated with the crypto assets in the vault. Note that if the source is another NFT associated with the crypto assets in the vault, there is no need to transfer the NFT (i.e., it is sufficient to simply rewrite the information of the NFT to which the crypto assets to be deposited are associated).

The user can specify the deposit amount and the source (e.g., their wallet, or NFTs held in the wallet and associated with the crypto asset in the vault). The client device 10 generates a deposit request in response to the user's instructions. The deposit request can include information that can identify the brand of NFT and crypto asset to be deposited, the deposit amount, and the source (e.g., wallet address, or NFT contract address and token ID). The client device 10 sends the deposit request to the distributed ledger system 50.

After step S213, the distributed ledger system 50 executes the deposit of crypto assets (S251).
Specifically, the distributed ledger system 50 executes a transaction in response to a deposit request from the client device 10. As a first example, the distributed ledger system 50 executes a transaction to transfer (assign) a designated brand of crypto asset in the amount of the deposit from the wallet in which the client device 10 is logged in to an NFT designated as the deposit target (in other words, a transaction to transfer crypto asset from the logged in wallet to a vault and associate the crypto asset with the designated NFT in the vault). As a second example, the distributed ledger system 50 executes a transaction to transfer a designated brand of crypto asset in the amount of the deposit from another NFT designated as a source to an NFT designated as the deposit target (in other words, a transaction to disassociate the crypto asset from the other NFT and associate the crypto asset with the designated NFT in the vault).

(3-2) Withdrawal Processing The withdrawal processing of this embodiment will now be described. Fig. 7 is a flowchart of the withdrawal processing of this embodiment. Fig. 8 is a diagram showing an example of a screen displayed in the withdrawal processing of this embodiment. Fig. 9 is a diagram showing an example of a screen displayed in the withdrawal processing of this embodiment.

The withdrawal process of this embodiment may be initiated in response to a user's instruction while the client device 10 is executing a specific application (e.g., a payment application for making a payment with crypto assets, or a web browser for displaying a SaaS screen for making a payment with crypto assets). Alternatively, while the client device 10 is executing a wallet app or a web browser (e.g., a payment screen of an EC (Electronic Commerce) site), the above-mentioned specific application may be launched in response to the user selecting a payment method using crypto assets associated with NFT, and the withdrawal process may be initiated.

As shown in FIG. 7, the client device 10 executes the presentation of the NFT (S310).
Specifically, the client device 10 queries the distributed ledger system 50 for information on NFTs held in the currently logged-in wallet. If the client device 10 is not logged in to the wallet, the client device 10 may request the user to log in to the wallet prior to the query. The client device 10 queries the distributed ledger system 50 for information on NFTs held in the wallet. The distributed ledger system 50 transmits the NFT information to the client device 10. The client device 10 presents the NFT information to the user. As an example, the client device 10 displays a screen based on the NFT information on the display 21.

As an example, the client device 10 displays the screen of FIG.
The screen of FIG. 8 includes objects J20 to J23 and J24a to J24d.

Object J20 displays information about the payment amount. The information about the payment amount includes information indicating the type of cryptocurrency that can be used for payment and information indicating the withdrawal amount when making payment with that cryptocurrency.

When making a withdrawal (transfer) other than for settlement, an object that accepts input from the user of the brand of cryptocurrency to be withdrawn and the amount to be withdrawn may be placed on the screen instead of object J20. When not making a withdrawal (for example, when executing a deposit process), object J20 may be removed from the screen.

The objects J21 and J23 are configured so as to be switchable between and displayable in tab format.
Object J21 displays a UI (User Interface) for managing crypto assets held in a wallet (e.g., checking balances or depositing and withdrawing funds). As an example, object J21 displays information about crypto assets held in a wallet and accepts user instructions for managing the crypto assets. The crypto asset information includes information indicating the brand of the crypto asset and information indicating the balance of the crypto asset.

Object J23 displays a UI for managing (e.g., checking balances or depositing and withdrawing) crypto assets associated in the vault with NFTs held in the wallet. In the initial state, object J23 has object J24 placed in it. Objects J24a to J24d each display information about the corresponding NFT (NFT held in the wallet) and accept user instructions to select that NFT. Note that object J24 may display NFTs with no associated crypto asset balance in the vault in a manner that allows distinction from NFTs with such a balance.

After step S310, the client device 10 executes the selection of an NFT (S311).
Specifically, the client device 10 receives an instruction from the user to select one of the NFTs (e.g., selection of one of the objects J24a to J24d (FIG. 8)) based on the information presented in step S310. The client device 10 queries the distributed ledger system 50 for information on the crypto asset associated with the selected NFT in the vault.

After step S311, the distributed ledger system 50 obtains information on the crypto assets (S330).
Specifically, the distributed ledger system 50 receives the inquiry sent by the client device 10 in step S311. In response to the received inquiry, the distributed ledger system 50 inquires about information of the crypto asset associated with the NFT selected by the user in the vault. The distributed ledger system 50 transmits the information of the crypto asset to the client device 10.

After step S330, the client device 10 presents information about the crypto asset (S312).
Specifically, the client device 10 receives the information transmitted by the distributed ledger system 50 in step S330. The client device 10 presents the received information. As an example, the client device 10 displays a screen based on the crypto asset information on the display 21.

As an example, the client device 10 displays the screen of FIG.
The screen of FIG. 9 includes objects J20 to J23, J30, J31a to J31c, and J32 to J33.

Object J30 displays information about the selected NFT (i.e., the NFT selected in step S311).

Objects J31a to J31c display information about each crypto asset associated with the selected NFT in the vault, and accept user instructions to select the crypto asset (brand).

The user may be able to select the brand of cryptocurrency indicated in object J20. Specifically, the distributed ledger system 50 searches for a decentralized exchange (DEX) where the cryptocurrency selected by the user and the (brand of) cryptocurrency that can be used for settlement are pooled as liquidity. When a corresponding DEX is found, the distributed ledger system 50 accepts a settlement request using the cryptocurrency selected by the user and performs a transaction to exchange the cryptocurrency and transfer the cryptocurrency after the exchange.

Object J32 accepts a user instruction to charge (deposit) crypto assets associated with the selected NFT. In response to the selection of object J32, the client device 10 may start the deposit process shown in FIG. 6, for example, from accepting a deposit instruction (S213).

Object J33 accepts a user instruction to return to the NFT selection screen (i.e., the screen in Figure 8).

After step S312, the client device 10 executes acceptance of a withdrawal instruction (S313).
Specifically, the client device 10 accepts an instruction from the user to make a withdrawal of any of the crypto assets associated with the selected NFT based on the information presented in step S312. Here, withdrawal means transferring the crypto assets associated with the NFT to be withdrawn in the vault to a destination. The destination means the destination of the crypto assets associated with the NFT to be withdrawn, and may be, for example, a wallet or another NFT associated with the crypto asset in the vault.

The user can specify the withdrawal amount and destination (e.g., their own wallet, another company's wallet, or another NFT held in one of the wallets and associated with the crypto asset in the vault). When making a withdrawal for settlement, the withdrawal amount and destination are not necessarily specified by the user, but can be specified based on information specified by the user's trading partner or information such as the crypto asset rate. The client device 10 generates a withdrawal request in response to the user's instructions. The withdrawal request can include information that can specify the brand of the NFT and crypto asset to be withdrawn, the withdrawal amount, and the destination. The client device 10 sends the withdrawal request to the distributed ledger system 50.

After step S313, the distributed ledger system 50 executes the withdrawal of the crypto asset (S331).
Specifically, the distributed ledger system 50 executes a transaction in response to a withdrawal request from the client device 10. As a first example, the distributed ledger system 50 executes a transaction to transfer a designated brand of crypto asset in an amount equivalent to the withdrawal quantity from the NFT to be withdrawn to a wallet designated as the destination. As a second example, the distributed ledger system 50 executes a transaction to transfer a designated brand of crypto asset in an amount equivalent to the withdrawal quantity from the NFT to be withdrawn to another NFT designated as the destination.

(4) Summary As described above, the client device 10 of this embodiment presents at least one NFT (Non-Fungible Token) held in the wallet, and selects a target NFT, which is one of the at least one NFT, in response to an instruction from a user. On the other hand, the distributed ledger system 50 manages crypto assets in association with the NFT in a vault defined by a smart contract, and outputs information on the crypto assets associated with the target NFT in response to a request from a user of a wallet that holds the target NFT. The client device 10 presents information on the crypto assets associated with the target NFT in the vault. This allows the user of the wallet to check information on the crypto assets associated with the NFT held in the wallet in the vault and manage assets.

The client device 10 may request the distributed ledger system 50 to transfer crypto assets held in the wallet to the vault and associate the crypto assets with a specified NFT. On the other hand, in response to such a request, the distributed ledger system 50 may transfer crypto assets held in the wallet to the vault and associate the crypto assets with an NFT specified by the user in the vault. This allows the user to add crypto assets held in their wallet as crypto assets associated with a specified NFT, similar to depositing crypto assets into a savings account or charging a prepaid card.

The client device 10 may request the distributed ledger system 50 to transfer the crypto asset associated with the target NFT to a specified wallet. On the other hand, the distributed ledger system 50 may transfer the crypto asset associated with the target NFT to a wallet specified by the user in response to such a request. This allows the user to transfer the crypto asset associated with the target NFT to any wallet. In other words, the user can use the target NFT for payment or remittance as if it were a prepaid card or cash card.

The client device 10 may request the distributed ledger system 50 to disassociate the crypto asset from the target NFT in the vault and associate the crypto asset with an NFT specified in the vault. On the other hand, in response to such a request, the distributed ledger system 50 may disassociate the crypto asset from the target NFT in the vault and associate the crypto asset with an NFT specified by the user. This allows the user to replace the crypto asset associated with the target NFT with any NFT. In other words, the user can use the target NFT for payments or remittances as if it were a prepaid card or cash card.

The client device 10 may present information regarding the respective brands and balances of the crypto assets associated with the target NFT. This allows the user to understand the details of the crypto assets associated with the target NFT.

The client device 10 may present digital content corresponding to the target NFT along with information about the cryptocurrency associated with the target NFT. This allows the user to enjoy the digital content corresponding to the target NFT as an object of appreciation or collection in the same way as the face of a physical prepaid card.

(5) Modifications Modifications of the present embodiment will now be described.

(5-1) Modification 1
Modification 1 will now be described. Modification 1 is an example in which crypto assets associated with NFTs in a safe can be used, for example, when making a payment at a brick-and-mortar store.

(5-1-1) Configuration of the Information Processing System The configuration of the information processing system will be described below. Fig. 10 is a block diagram showing the configuration of the information processing system according to the first modification.

As shown in FIG. 10 , the information processing system 2 includes a client device 10, a server 30, a distributed ledger system 50, and a payment terminal 70.
The client device 10 and the server 30 are connected via a network NW.
The client device 10 and the distributed ledger system 50 are connected via a network NW.
The server 30 and the distributed ledger system 50 are connected via a network NW.
The payment terminal 70 and the server 30 are connected via a network NW.
The payment terminal 70 and the distributed ledger system 50 are connected via a network NW.

The server 30 is an example of an information processing device that provides the client device 10 with a response in response to a request sent from the client device 10. The server 30 has a database for recording changes in the balance accompanying payments using crypto assets associated with NFTs in the vault. In this database, the movement of crypto assets between NFTs is recorded based on the request from the client device 10 before the transaction is completely recorded in the distributed ledger system 50, so that payments can be completed quickly while preventing duplicate payments. The server 30 is, for example, a server computer.

The payment terminal 70 is installed in, for example, a physical store. The payment terminal 70 is configured to be capable of at least one of the following:
Wireless communication via a communication interface (e.g., NFC (Near-field communication))
Reading code information (for example, a two-dimensional code such as a QR code (registered trademark)) using a camera; and Displaying the code information on a display. The payment terminal 70 may be equipped with the same hardware as the client device 10.

An application (e.g., a wallet application) (hereinafter, referred to as a "specific application") that is configured to allow the user to select a payment method is installed on the client device 10. The user can add any NFT to the UI (User Interface) of the specific application.

The client device 10 is configured to be capable of at least one of the following:
Wireless communication via the communication interface 14 (e.g., near-field communication (NFC))
- Reading the code information using a camera (an example of an input device) - Displaying the code information on the display 21

(5-1-1-1) Server Configuration The following describes the server configuration: Fig. 11 is a block diagram showing the server configuration of this embodiment.

As shown in FIG. 11, the server 30 includes a storage device 31, a processor 32, an input/output interface 33, and a communication interface 34.

The storage device 31 is configured to store programs and data. The storage device 31 is, for example, a combination of ROM, RAM, and storage (e.g., flash memory or a hard disk).

The programs include, for example, the following programs:
・OS programs ・Application programs that execute information processing

The data includes, for example, the following data:
- Databases referenced in information processing - Results of information processing

The processor 32 is a computer that realizes the functions of the server 30 by running a program stored in the storage device 31. The processor 32 is, for example, at least one of the following:
CPU
・GPU
・ASIC
・FPGA

The input/output interface 33 is configured to obtain information (e.g., a user's instruction) from an input device connected to the server 30 , and to output information (e.g., an image) to an output device connected to the server 30 .
The input device is, for example, a keyboard, a pointing device, a touch panel, or a combination thereof.
The output device is, for example, a display.

The communication interface 34 is configured to control communication between the server 30 and an external device (e.g., a client device 10, or a distributed ledger system 50).

(3) Information Processing A description will now be given of information processing in Modification 1. Fig. 12 is a flowchart of payment processing in Modification 1.
The payment process of the first variant begins in response to the selection of any NFT on the UI of a specific application.

As shown in FIG. 12, the client device 10 executes an inquiry for crypto asset information (S410).
Specifically, the client device 10 queries the server 30 for information on the crypto asset associated with the selected NFT in the vault.

After step S410, the server 30 acquires information on the crypto asset (S430).
Specifically, the server 30 receives the inquiry sent by the client device 10 in step S410. In response to the received inquiry, the server 30 queries the distributed ledger system 50 as necessary for information on the crypto asset associated with the NFT selected by the user in the vault, and updates the database to reflect information on deposits and withdrawals that the server 30 is not aware of (e.g., the results of the deposit process or withdrawal process of this embodiment). The distributed ledger system 50 transmits the information on the crypto asset to the server 30. The server 30 transmits the information on the crypto asset to the client device 10.

After step S430, the client device 10 presents information about the crypto asset (S411).
Specifically, the client device 10 receives the information transmitted by the server 30 in step S430. The client device 10 presents the received information. As an example, the client device 10 displays a screen based on the crypto asset information on the display 21.

After step S411, the client device 10 executes acceptance of a payment instruction (S412).
Specifically, the client device 10 accepts an instruction from the user to make a payment with any of the crypto assets associated with the selected NFT in response to the information presented in step S411. In response to the acceptance of the user instruction, the client device 10 outputs the payment information to an external device (e.g., the payment terminal 70). As a first example, after the instruction to make a payment, when the user brings the client device 10 close to the payment terminal 70, the payment information is transmitted from the client device 10 to the payment terminal 70 by, for example, NFC. As a second example, after the instruction to make a payment, the client device 10 displays code information representing the payment information on the display 21, and the user brings the display 21 close to the reading means of the payment terminal 70.

The payment information is an example of information necessary to execute a payment using the cryptocurrency associated with an NFT. The payment information includes, for example, information capable of identifying the selected NFT (and, if necessary, the brand of the cryptocurrency) and information (e.g., the user's wallet address) indicating that the user has the authority to dispose of the cryptocurrency associated with the NFT (i.e., that the NFT is held in the user's wallet).

After step S412, the payment terminal 70 acquires payment information (S470).
Specifically, the payment terminal 70 acquires the payment information output from the client device 10 in step S412. As an example, the payment terminal 70 performs a decoding process on the received signal or the read image.

After step S470, the payment terminal 70 executes a payment request (S471).
Specifically, the payment terminal 70 generates a payment request based on the payment information acquired in step S470. The payment request may include information capable of identifying the NFT selected by the user, information capable of identifying the brand and withdrawal amount of the crypto asset used for the payment, information indicating that the user has the authority to dispose of the crypto asset associated with the NFT, and information capable of identifying the NFT for receiving the crypto asset related to the payment. The payment terminal 70 transmits the payment request to the server 30.

After step S471, the server 30 executes the settlement (S431).
Specifically, the server 30 receives the payment request transmitted by the payment terminal 70 in step S471. In response to receiving the payment request, the server 30 requests the distributed ledger system 50 to execute a transaction. The server 30 uses the above-mentioned owner address to access the crypto asset associated in the vault with the NFT specified by the user on behalf of the user. For example, the server 30 requests the distributed ledger system 50 to execute a transaction to transfer the crypto asset associated in the vault with the NFT selected by the user to the above-mentioned specified wallet. The distributed ledger system 50 executes the transaction in response to the request.

Here, as described above, in order to speed up the settlement, the server 30 constructs a database that manages the balance of the crypto asset associated with each NFT in the vault. The server 30 then attempts to update the database in response to the received settlement request, and if the crypto asset associated with the NFT selected by the user in the vault does not become insufficient, the server 30 may request the distributed ledger system 50 to execute the transaction and may send information indicating the success of the settlement to the settlement terminal 70 (and the client device 10, if necessary) without waiting for the completion of the execution of the transaction. In such a case (i.e., if the settlement is successful), the server 30 updates the database based on the settlement request. On the other hand, if the crypto asset associated with the NFT selected by the user in the vault becomes insufficient, the server 30 may send information indicating the failure of the settlement to the settlement terminal 70 (and the client device 10, if necessary) without requesting the distributed ledger system 50 to execute the transaction. In such a case (i.e., if the settlement is unsuccessful), the database is not updated based on the settlement request.

In addition, such a database may also be used in the deposit processing and withdrawal processing described in this embodiment. In other words, the above-mentioned deposit processing and withdrawal processing may be performed via the server 30.

In the example of FIG. 12, the client device 10 outputs payment information to an external device in response to receiving a payment instruction. However, instead, the client device 10 may obtain information necessary to execute a payment using the crypto asset associated with the NFT from an external device (e.g., a payment terminal 70). The client device 10 may then generate a payment request in accordance with the obtained information, instead of the payment terminal 70, and transmit the payment request to the server 30.

The information acquired by the client device 10 may include, for example, information capable of identifying the brand of cryptocurrency used in the payment and the withdrawal amount, and information capable of identifying the NFT for transferring the cryptocurrency related to the payment (for example, a contract address and a token ID). As a first example, when a user brings the client device 10 close to a payment terminal 70, information is transmitted from the payment terminal 70 to the client device 10, for example, by NFC. As a second example, the payment terminal 70 displays code information representing information on its display, and the user brings the camera of the client device 10 close to the display.

As described above, when a target NFT is selected in response to a user instruction on the UI of an application configured to allow selection of a payment method, the client device 10 of variant 1 starts the payment by outputting to an external device or acquiring from an external device information required to execute a payment using the cryptocurrency associated with the target NFT. This allows the user to use the NFT in physical stores, etc. in the same way as a physical prepaid card.

(6) Other Modifications The storage device 11 may be connected to the client device 10 via the network NW. The display 21 may be built into the client device 10. The storage device 31 may be connected to the server 30 via the network NW.

Each step of the above information processing can be executed by either the client device 10 or the server 30. For example, a process described as being performed by one device may be executed by another device, or a process described as being performed by the interaction of multiple devices may be executed by a single device. In addition, the above explanation shows an example in which each step in each process is executed in a specific order, but the execution order of each step is not limited to the example described, as long as there is no dependency.

The information processing system 1 of the embodiment can be produced by providing a program for a computer to execute the above-mentioned information processing to each device constituting the information processing system 1 (e.g., the client device 10, the server 30, each node computer constituting the distributed ledger system 50, and the payment terminal 70).

The NFT with which the cryptocurrency is associated in the vault may be a non-transferable token, such as a Soulbound Token (SBT). In this case, such an NFT may also act like a debit card.

In the present embodiment, in accepting a deposit instruction (S213), the client device 10 may accept a deposit instruction from a user that includes a locking period for the crypto asset. In this case, the crypto asset associated with the NFT in the vault due to the deposit instruction will be locked (i.e., it cannot be used for withdrawal or settlement) until the locking period expires. However, the locked crypto asset is otherwise treated the same as a normal crypto asset associated with an NFT. For example, when the associated NFT is transferred, the locked crypto asset is effectively transferred together with the normal crypto asset associated with the NFT.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above-mentioned embodiments. Furthermore, the above-mentioned embodiments can be improved or modified in various ways without departing from the spirit of the present invention. Furthermore, the above-mentioned embodiments and modifications can be combined.

1: Information processing system 10: Client device 11: Storage device 12: Processor 13: Input/output interface 14: Communication interface 21: Display 30: Server 31: Storage device 32: Processor 33: Input/output interface 34: Communication interface 50: Distributed ledger system 70: Payment terminal

Claims (16)

Computer,
A means for presenting at least one non-fungible token (NFT) held in the wallet;
A means for selecting a target NFT, which is any one of the at least one NFT, in response to an instruction from a user;
A means for presenting information about a crypto asset associated with the target NFT in a vault defined by a smart contract;
A program that functions as a and causing the computer to function as a means for requesting a distributed ledger system to transfer crypto assets held in the wallet to the vault and to associate the crypto assets with a designated NFT.
The program according to claim 1. The requesting means further requests the distributed ledger system to lock the crypto asset associated with the specified NFT for a locking period.
The program according to claim 2. causing the computer to function as a means for requesting a distributed ledger system to transfer crypto assets associated with the target NFT to a designated wallet;
The program according to claim 1. and causing the computer to function as a means for requesting a distributed ledger system to disassociate the crypto asset from the target NFT in the vault and to associate the crypto asset with a specified NFT in the vault.
The program according to claim 1. The means for presenting information on the cryptocurrency presents information on the name and balance of each of the cryptocurrency associated with the target NFT;
The program according to claim 1. The means for presenting information on the cryptocurrency presents digital content corresponding to the target NFT together with information on the cryptocurrency associated with the target NFT.
The program according to claim 1. When the target NFT is selected in response to an instruction from the user on a UI (User Interface) of an application configured to allow selection of a payment method, the computer is caused to function as a means for initiating a payment by outputting to an external device or acquiring from an external device information necessary for executing a payment using the cryptocurrency associated with the target NFT.
The program according to claim 1. Computer,
A means for managing crypto assets in a vault defined by a smart contract in association with a non-fungible token (NFT);
A program that functions as a means for outputting information about the cryptocurrency associated with a target NFT in response to a request from a user of a wallet that holds a target NFT that is any of the NFTs. a means for causing the computer to transfer crypto assets held in the wallet to the vault in response to a request from a user of the wallet, and to associate the crypto assets in the vault with an NFT designated by the user;
The program according to claim 9, The associating means further locks the crypto asset associated with the specified NFT for a locking period in response to a request from the user of the wallet.
The program according to claim 10, A means for causing the computer to transfer crypto assets associated with the target NFT to a wallet designated by a user in response to a request from the user of the wallet;
The program according to claim 9, means for disassociating a crypto asset from the target NFT in the vault and associating the crypto asset with an NFT designated by the user, in response to a request from the user of the wallet;
The program according to claim 9, further functioning as: A means for managing crypto assets in a safe defined by a smart contract in association with a non-fungible token (NFT);
and means for outputting information about a crypto asset associated with a target NFT in response to a request from a user of a wallet that holds a target NFT that is any of the NFTs. The computer
Managing crypto assets in a safe defined by a smart contract in association with a non-fungible token (NFT);
and outputting information about the crypto asset associated with the target NFT in response to a request from a user of a wallet that holds a target NFT that is any of the NFTs. A method of producing a system, comprising: providing a program according to claim 9 to a plurality of computers.