Information processing system, non-fungible token management device, non-fungible token management method and program

Abstract

The value of non-fungible tokens can be changed after they are issued. [Solution] The management device 1 has a token creation unit 131 that creates a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, and stores the issuer and the internal value in association with each other in a token memory unit; a token provision unit 132 that provides the non-fungible token to a user; an update unit 133 that updates the internal value stored in the memory unit 12; and an authentication unit 134 that, when authentication request data for requesting authentication of the non-fungible token is obtained from a service providing device that provides a service to the user, notifies the service providing device 2 of an authentication result indicating whether the internal value stored in the token memory unit is greater than the required internal value indicated by the authentication request data.

Description

[Technical Field]

[0001] The present invention relates to an information processing system, a non-fungible token management device, a non-fungible token management method, and a program. [Background technology]

[0002] Conventionally, there has been known a system that provides benefits to holders of non-fungible tokens. In the conventional system, a benefit corresponding to a serial number attached to the non-fungible token is provided (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2024-057760 Summary of the Invention [Problem to be solved by the invention]

[0004] In conventional systems, there is a problem in that the value of a non-fungible token cannot be changed after it is issued.

[0005] The present invention has been made in consideration of these points, and aims to make it possible to change the value of a non-fungible token after it has been issued. [Means for solving the problem]

[0006] An information processing system of a first aspect of the present invention comprises a management device that manages non-fungible tokens, and a service providing device that provides services to users who use the non-fungible tokens, wherein the management device comprises a token creation unit that creates a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, and associates the issuer with the internal value and stores it in a token storage unit, a token providing unit that provides the non-fungible token to the user, an update unit that updates the internal value stored in the token storage unit, and when authentication request data for requesting authentication of the non-fungible token is obtained from the service providing device, an update unit that updates the internal value stored in the token storage unit, and and an authentication unit that notifies the service providing device of an authentication result indicating whether the internal value stored in the token memory unit is large or not, and the service providing device has a request acquisition unit that acquires service request data from the user to request the provision of a service using the non-fungible token, an authentication request unit that transmits the authentication request data to the management device to authenticate the internal value of the non-fungible token indicated by the service request data, and a service providing unit that executes processing to provide the service if the internal value of the non-fungible token indicated by the service request data satisfies the conditions for providing the service based on the authentication result received from the management device.

[0007] The update unit may update the internal value stored in the token storage unit to become the set value received from the issuer.

[0008] The update unit may, in response to receiving status data indicating the status of the issuer from an external device, update the internal value of the non-fungible token stored in the token storage unit to a value corresponding to the status data.

[0009] The update unit may update the internal value by referring to update data that associates the change in the issuer's status with the change in the internal value, and adding the change corresponding to the change in the issuer's status indicated by the status data.

[0010] The update unit may update the internal value based on the number of endorsements sent to the publisher.

[0011] The service providing unit may provide the service when the condition that the internal value is equal to or greater than a threshold value corresponding to the service indicated by the authentication request data is satisfied.

[0012] The service providing device may further have a service content memory unit that stores service content data indicating the content of the service in association with the issuer, and the service providing unit may provide the service whose content is associated with the issuer in the service content data, corresponding to the non-fungible token indicated by the authentication request data.

[0013] The token creation unit may create multiple types of non-fungible tokens associated with one issuer, the service content memory unit may store the service content data in which the content of the service is associated with the type of non-fungible token, and the service providing unit may provide the service whose content is associated in the service content data with the type of non-fungible token indicated by the authentication request data.

[0014] The token providing unit may provide a plurality of the non-fungible tokens associated with one of the issuers to one of the users, and the service providing unit may provide the service according to the number of the non-fungible tokens corresponding to one of the issuers held by the user.

[0015] A second aspect of the non-fungible token management device of the present invention includes a token creation unit that creates a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, and associates the issuer with the internal value and stores it in a token storage unit; a token provision unit that provides the non-fungible token to a user; an update unit that updates the internal value stored in the token storage unit; and an authentication unit that, when authentication request data requesting authentication of the non-fungible token is obtained from a service provision device that provides a service to the user, notifies the service provision device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data.

[0016] A third aspect of the non-fungible token management method of the present invention includes the steps of: executing on a computer, creating a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, associating the issuer with the internal value and storing the associated internal value in a token storage unit; providing the non-fungible token to a user; updating the internal value stored in the token storage unit; and, when authentication request data requesting authentication of the non-fungible token is obtained from a service providing device that provides a service to the user, notifying the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data.

[0017] A fourth aspect of the present invention is a program for causing a computer to execute the following steps: creating a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, associating the issuer with the internal value and storing the associated internal value in a token storage unit; providing the non-fungible token to a user; updating the internal value stored in the token storage unit; and, when authentication request data requesting authentication of the non-fungible token is obtained from a service providing device that provides a service to the user, notifying the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data. [Effects of the Invention]

[0018] According to the present invention, it is possible to change the value of a non-fungible token after it has been issued. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a diagram for explaining an overview of an information processing system S. [Figure 2] FIG. 1 is a diagram illustrating a configuration of a management device 1. [Figure 3] FIG. 10 is a diagram illustrating an example of NFT management data. [Figure 4] FIG. 10 is a diagram illustrating an example of user management data. [Figure 5] FIG. 10 is a diagram illustrating an example of update data. [Figure 6] FIG. 10 is a diagram illustrating an example of an NFT management screen. [Figure 7] FIG. 2 is a diagram illustrating a configuration of a service providing device 2. [Figure 8] FIG. 10 is a diagram illustrating an example of service content data. [Figure 9] 10 is a flowchart showing the flow of processing in a non-fungible token management method executed by the management device 1. [Figure 10]10 is a flowchart showing the flow of processing in a service providing method executed by the service providing device 2. DETAILED DESCRIPTION OF THE INVENTION

[0020] [Outline of Information Processing System S] FIG. 1 is a diagram illustrating an overview of an information processing system S. The information processing system S is a system that issues non-fungible tokens (hereinafter sometimes referred to as "NFTs") and enables services that use the issued NFTs to be provided to users. In the example shown in FIG. 1, the information processing system S includes a management device 1 and a service providing device 2, but the information processing system S may be configured by a single device or may include other devices.

[0021] The management device 1 is a non-fungible token management device, such as a computer, that creates NFTs in response to receiving a request to issue an NFT from a person who issues an NFT (hereinafter referred to as "issuer H"). The management device 1 creates NFTs whose value changes depending on the status of the issuer. The issuer H is, for example, a celebrity who wants to let many people know about their activities and increase their fan base, and is specifically an entertainer, politician, athlete, business executive, or the like.

[0022] An NFT is associated with a variable internal value along with its issuer H. The management device 1 determines the initial value of the internal value when creating the NFT, and stores a token ID (hereinafter referred to as "NFT-ID"), which is information for identifying the NFT, information for identifying the issuer H (hereinafter referred to as "issuer ID"), and the internal value in association with each other. Thereafter, the management device 1 updates the internal value based on instructions from the issuer H associated with the NFT, or based on a change in the status of issuer H.

[0023] The management device 1 records management information about the issued NFT in the blockchain B. The management information includes the NFT-ID, the issuer ID, and the name of the NFT holder. At the time the NFT is created, the name of the holder is the name or title of the issuer H.

[0024] The management device 1 can also manage marketplaces where the created NFTs are sold. Specifically, the management device 1 provides a different marketplace site for each issuer H. A user who wishes to purchase an NFT can access the marketplace corresponding to issuer H and purchase an NFT associated with issuer H, for example, by searching for issuer H as a keyword on a portal site provided by the management device 1. The NFT-ID of the purchased NFT is stored in user U's blockchain wallet.

[0025] The service providing device 2 is a server that provides services to users U who hold NFTs issued by the management device 1. The service providing device 2 is, for example, a server operated by issuer H or an organization to which issuer H belongs. When the service providing device 2 receives a usage request from user U who holds an NFT issued by issuer H, including the NFT-ID of the held NFT, the service providing device 2 requests the management device 1 to authenticate whether the NFT corresponding to the NFT-ID is an NFT held by user U. In addition, the service providing device 2 requests the management device 1 to confirm whether the internal value of the NFT corresponding to the NFT-ID included in the usage request is greater than the internal value required to provide the service.

[0026] If the service providing device 2 can confirm that the NFT is held by the user U and that the NFT has an internal value necessary to provide the service, it provides the service to the user U. Details will be described later, but the content of the service may include viewing content, participating in a meeting, or receiving benefits. The content of the service that the user U can receive changes as the internal value of the NFT changes.

[0027] The issuer terminal 3 shown in Figure 1 is a computer used by issuer H. The issuer terminal 3 transmits and receives data to and from the management device 1 via a network. Issuer H requests the issuance of an NFT using an NFT management screen displayed by accessing the management device 1 via the issuer terminal 3.

[0028] The user terminal 4 is a computer, such as a smartphone or tablet, used by a user U who acquires and uses the acquired NFTs. The user U can purchase NFTs or receive them free of charge by performing a predetermined operation on the user terminal 4. For example, the user U can receive an NFT corresponding to a code (e.g., a QR code (registered trademark)) attached to a prize by reading the code with the user terminal 4. Specifically, the NFT received by the user U is stored in the user U's wallet.

[0029] The user terminal 4 transmits and receives data between the management device 1 and the service providing device 2 via the network. In response to a search operation by the user U, the user terminal 4 displays information about the NFTs held by the user U and accepts operations to use the NFTs.

[0030] Below, an overview of the processing flow in the information processing system S will be explained with reference to FIG. 1. When issuer H starts application software for managing NFTs on the issuer terminal 3, a management screen is displayed on the issuer terminal 3. The management screen is a screen provided by the management device 1. Details will be described later, but on the management screen it is possible to set the name of the NFT to be issued, the number to be issued, internal values, etc. When issuer H performs an operation to issue an NFT on the management screen, the issuer terminal 3 sends an NFT issuance request to the management device 1 ((1) in FIG. 1).

[0031] When the management device 1 receives an NFT issuance request, it creates an NFT based on the content entered on the management screen. The management device 1 stores the name, number of issues, internal value, etc. of the NFT in association with the issuer ID of the created NFT. The management device 1 records management data related to the created NFT in blockchain B ((2) in Figure 1).

[0032] Thereafter, when the user U performs an operation to purchase an NFT on the user terminal 4, the management device 1 notifies the user U that the NFT has been purchased by sending the NFT-ID of the NFT purchased by the user U to the user terminal 4 ((3) in FIG. 1). The notification includes the name of the NFT and the NFT-ID.

[0033] The management device 1 provides a marketplace for selling NFTs issued by, for example, issuer H. When user U performs an operation to purchase a selected NFT on the marketplace, the management device 1 associates information for identifying user U who has become the holder of the NFT (e.g., user U's name, user U's email address) with an NFT-ID and records it on the blockchain B. The management device 1 notifies user U that he or she has successfully purchased the NFT by sending the NFT-ID of the selected NFT to user U's address.

[0034] User U can use the NFTs he or she owns by launching application software for using NFTs on the user terminal 4. The application software displays a list of the names of NFTs owned by user U, and when user U selects the name of the NFT he or she wants to use, the user terminal 4 sends an NFT usage request to the service providing device 2 stored in association with the selected NFT ((4) in FIG. 1). The NFT usage request includes information indicating the content of the service user U wants to receive using the NFT.

[0035] When the service providing device 2 receives the NFT usage request, it sends an authentication request to the management device 1 to request the management device 1 to authenticate the NFT indicated in the NFT usage request ((5) in FIG. 1). The authentication request includes the NFT-ID, a user ID for identifying the user U, and an internal value (hereinafter referred to as the "required internal value") required to provide the service indicated by the NFT usage request.

[0036] When the management device 1 receives the authentication request, it sends the NFT-ID and user ID to the blockchain B and confirms that the NFT for which the authentication request was received is held by the user U corresponding to the user ID ((6) in Figure 1). The management device 1 also checks whether the internal value of the NFT is equal to or greater than the required internal value included in the authentication request. The management device 1 sends an authentication result including these confirmation results to the service providing device 2 ((7) in Figure 1).

[0037] The service providing device 2 determines whether to provide the service indicated by the NFT usage request based on the authentication result received from the management device 1. If the authentication result indicates that the user holds the NFT indicated in the NFT usage request and that the internal value of the NFT is equal to or greater than the required internal value, the service providing device 2 allows the user U to receive the service ((8) in FIG. 1).

[0038] In this way, the content of the services available to user U who holds an NFT changes in conjunction with the internal value of the NFT, so user U can have the expectation that the value of the NFT will change. As a result, user U will be motivated to purchase NFTs. User U will also be motivated to support issuer H so that the internal value will increase. The configurations and operations of the management device 1 and the service providing device 2 will be described in detail below.

[0039] [Configuration of management device 1] 2 is a diagram showing the configuration of the management device 1. The management device 1 includes a communication unit 11, a storage unit 12, and a control unit 13.

[0040] The communication unit 11 has a communication interface for transmitting and receiving data between the service providing device 2, the issuer terminal 3, the user terminal 4, and the blockchain B. The communication unit 11 notifies the control unit 13 of the received data and transmits data input from the control unit 13 to other devices.

[0041] The storage unit 12 has storage media such as a ROM (Read Only Memory), a RAM (Random Access Memory), and an SSD (Solid State Drive). The storage unit 12 stores programs executed by the control unit 13. The storage unit 12 stores various data related to the issued NFTs. The storage unit 12 functions as a token storage unit that stores NFT management data related to the NFTs issued by issuer H.

[0042] 3 is a diagram showing an example of NFT management data. In the NFT management data shown in FIG. 3, an issuer ID, an NFT name, the number of issues, the number of publications, the selling price, and an internal value are associated with each other.

[0043] The number of issued NFTs is the number of NFTs recorded on Blockchain B. The number of publicly available NFTs is the number of NFTs that have been made available for purchase on the marketplace. The number of issued NFTs and the number of publicly available NFTs may be the same, or the number of publicly available NFTs may be less than the number of issued NFTs. The selling price is the price at which the NFT is sold on the marketplace.

[0044] As in the case of issuer H with issuer ID ABD in Figure 3, NFTs with the same name but different sales prices may be issued by a single issuer H. Also, as in the case of issuer H with issuer ID ABE in Figure 3, multiple types of NFTs may be issued by a single issuer H.

[0045] The storage unit 12 also stores user management data indicating information about NFTs held by the user U. Fig. 4 is a diagram showing an example of the user management data. In the user management data shown in Fig. 4, the user ID, the NFT names of the NFTs held by the user, the number of each NFT held by the user U, and the NFT-ID of each NFT are associated with each other.

[0046] Furthermore, the storage unit 12 may store update data in which the change in the status of issuer H is associated with the change in the internal value. FIG. 5 is a diagram showing an example of update data. As shown in the update data in FIG. 5, the change in the internal value varies depending on the change in status. The change in the internal value corresponding to the change in status may be negative, and the internal value may decrease as the status of issuer H changes. Note that the change may not be a change in the status of issuer H himself, but may be a change in the status of another person related to issuer H (for example, a person belonging to the same organization as issuer H).

[0047] 2, the configuration of the control unit 13 will be described. The control unit 13 has, for example, a CPU (Central Processing Unit). The control unit 13 executes programs stored in the storage unit 12, thereby functioning as a token creation unit 131, a token provision unit 132, an update unit 133, and an authentication unit 134.

[0048] The token creation unit 131 creates an NFT associated with the issuer H and a variable internal value, and stores the issuer H and the internal value in association with each other in the storage unit 12. The token creation unit 131 also registers the NFT in the blockchain B by sending management information about the created NFT to the blockchain B.

[0049] In response to a request from the issuer terminal 3 that has accepted an operation from issuer H who wishes to issue an NFT, the token creation unit 131 displays an NFT management screen on the issuer terminal 3. The token creation unit 131 creates an NFT based on the data entered on the NFT management screen.

[0050] FIG. 6 is a diagram showing an example of an NFT management screen. On the NFT management screen, issuer H can set the name, issuer name, number of issues, number of publicly available issues, selling price, internal value, and custom parameters of the NFT to be created. The custom parameters are scores that indicate the strength of the issuer's own characteristics. The custom parameters are used, for example, by issuer H to promote itself.

[0051] The token creation unit 131 may create multiple types of NFTs associated with one issuer H. In the NFT management data shown in Figure 3, issuer H, whose issuer ID is ABE, has issued two types of NFTs: an NFT called YYY and an NFT called XXX.

[0052] The token providing unit 132 provides the NFT purchased by user U to user U. Specifically, the token providing unit 132 records the NFT-ID of the NFT purchased by user U in the blockchain B in association with user U's user ID, and provides the NFT to user U by notifying user U of the NFT-ID.

[0053] The token providing unit 132 sells NFTs issued by issuer H, for example, in a dedicated marketplace for issuer H, and notifies a user U who purchases an NFT of the NFT's NFT-ID. When the token providing unit 132 receives a request to access the marketplace from a user terminal 4 that has performed an operation to access issuer H's marketplace, the token providing unit 132 transmits data related to the NFT associated with issuer H in the NFT management data to the user terminal 4 via the communication unit 11. User U can purchase multiple different NFTs, in which case the token providing unit 132 notifies a single user U of multiple NFT-IDs associated with a single issuer H.

[0054] The data related to the NFT may include image data corresponding to the NFT, along with the name of the issuer of the NFT and the selling price of the NFT. The data related to the NFT may also include data indicating the content of services that can be provided using the NFT. Upon receiving the data related to the NFT, the user terminal 4 displays the received data.

[0055] When the token providing unit 132 receives a purchase request from a user terminal 4 that has performed an operation to purchase an NFT, it updates the information of the user U who requested the purchase in the user management data. Specifically, the token providing unit 132 stores the NFT-ID of the purchased NFT in association with the user ID of the user U, and increases the number of purchased NFTs held.

[0056] Furthermore, the token providing unit 132 also updates the management information related to the holder of the NFT recorded in the blockchain B. Specifically, the token providing unit 132 records the user ID of the purchasing user U as the holder of the NFT in the management information related to the NFT recorded in the blockchain B.

[0057] In addition, when user U purchases an NFT held by another user, the token providing unit 132 may send a sales notification indicating the name, NFT-ID, and sales price of the purchased NFT to the other user who held the NFT before user U purchased it.

[0058] The update unit 133 updates the internal value of the NFT stored in the storage unit 12. For example, the update unit 133 updates the internal value in the NFT management data stored in the storage unit 12 so that the internal value of the NFT becomes the set value received from the issuer H. Specifically, the update unit 133 updates the internal value by storing the value of the internal value set by the issuer H on the NFT management screen in the storage unit 12 in association with the NFT-ID of the NFT specified by the issuer H. The update unit 133 may record the update of the internal value in the blockchain B in association with the NFT-ID for which the internal value has been updated.

[0059] In response to receiving status data indicating the status of issuer H from an external device, the update unit 133 may update the internal value of the NFT stored in the memory unit 12 to a value corresponding to the status data. The status of issuer H is represented, for example, by the activity results of issuer H or the activity results of others regarding issuer H. The external device is a computer that records the activity results of issuer H or the activity results of others regarding issuer H. The activity results of issuer H are, for example, that issuer H posted on SNS, that issuer H gave a lecture, or that issuer H made a donation. The activity results of others regarding issuer H are, for example, that issuer H showed support for a post made by issuer H, that issuer H made a donation to issuer H, etc.

[0060] The update unit 133 may refer to update data in which changes in the state of issuer H are associated with changes in the internal value, and update the internal value by adding the change corresponding to the changes in the state of issuer H indicated by the state data. The change in the internal value may be negative, in which case the internal value decreases when the state of issuer H changes.

[0061] 5, in the update data, for example, the number of likes (i.e., the number of "Likes") for publisher H posted on SNS is associated with the amount by which the internal value is to be increased, and the update unit 133 updates the internal value based on the number of likes. As an example, the update unit 133 updates the internal value by increasing the internal value by 10 every time the number of likes for publisher H increases by 100.

[0062] In the update data, the amount donated to issuer H may be associated with the amount by which the internal value is increased. In this case, the update unit 133 increases the internal value by 10 every time the amount donated to issuer H increases by a predetermined amount (for example, 100,000 yen).

[0063] The authentication unit 134 executes authentication processing when it receives an authentication request for authenticating an NFT from the service providing device 2. As the authentication processing, the authentication unit 134 executes processing to determine whether an internal value stored in the storage unit 12 in association with the NFT-ID indicated in the authentication request is greater than a required internal value indicated in the authentication request, and notifies the service providing device 2 of an authentication result indicating the result of the determination. As part of the authentication processing, the authentication unit 134 may inquire of blockchain B about whether user U, the holder of the NFT indicated in the authentication request, matches the holder recorded in blockchain B.

[0064] [Configuration of service providing device 2] 7 is a diagram showing the configuration of the service providing device 2. The service providing device 2 includes a communication unit 21, a storage unit 22, and a control unit 23.

[0065] The communication unit 21 has a communication interface for transmitting and receiving various data between the management device 1 and the user terminal 4. When the communication unit 21 receives authentication request data for requesting the provision of a service that uses NFT from the user terminal 4, it notifies the request acquisition unit 231 of the authentication request data. When the authentication request data is input from the authentication request unit 232, the communication unit 21 transmits the authentication request data to the management device 1 and inputs the authentication result received from the management device 1 to the authentication request unit 232.

[0066] The storage unit 22 has storage media such as ROM, RAM, and SSD. The storage unit 22 stores programs executed by the control unit 23. The storage unit 22 also functions as a service content storage unit that stores service content data indicating the relationship between the content of services that can be provided to the user U using the NFT and the internal values ​​required to receive the provision of the services.

[0067] Fig. 8 is a diagram showing an example of service content data. The service content data shown in Fig. 8 associates the issuer ID of issuer H who issued the NFT, the NFT name, the required internal value, the number of NFTs required to receive the service, and the content of the service.

[0068] In the example shown in FIG. 8, user U who holds an NFT with the NFT name XYZ can watch video content provided by issuer H, for example, if the internal value of the NFT is 20 or more. User U can participate in a live performance by issuer H if the internal value of the NFT is 40 or more. User U can participate in golf with issuer H if the internal value of the NFT is 60 or more and user U holds two or more NFTs.

[0069] When one issuer H issues multiple types of NFTs, the storage unit 12 may store service content data in which the content of the service is associated with the type of NFT. The storage unit 12 may store service content data indicating only the service content corresponding to some types of NFTs among the multiple types of NFTs issued by one issuer H.

[0070] The control unit 23 includes, for example, a CPU. The control unit 23 executes the programs stored in the storage unit 22 to function as a request acquisition unit 231, an authentication request unit 232, and a service provision unit 233.

[0071] The request acquisition unit 231 acquires a service request from the user U to request the provision of a service that uses NFTs. Specifically, when the user U accesses a site for using NFTs using the user terminal 4 and selects the service that he or she wishes to receive, the request acquisition unit 231 acquires service request data for requesting the provision of the service from the user terminal 4 via the communication unit 21. The user U can specify the NFT to use, for example, by accessing the blockchain wallet to display a list of the names of the NFTs that he or she owns and selecting the NFT to use from the multiple NFTs displayed.

[0072] The authentication request unit 232 transmits an authentication request to the management device 1 to authenticate the internal value of the NFT indicated by the service request data. Specifically, the authentication request unit 232 requests the management device 1 to authenticate that the NFT at the time the request acquisition unit 231 acquires the service request data has an internal value required to receive the service indicated by the service request data. To this end, the authentication request unit 232 references the service content data stored in the storage unit 22 and identifies the internal value required to receive the service indicated by the service request data. The authentication request unit 232 transmits an authentication request indicating the NFT-ID and required internal value indicated by the service request data to the management device 1.

[0073] The authentication request unit 232 may make a request to the management device 1 to authenticate that the user U holds an NFT corresponding to the NFT-ID indicated in the service request data. To do so, the authentication request unit 232 may send authentication request data including the user ID of the user U along with the NFT-ID to the management device 1. Upon receiving the authentication result sent from the management device 1, the authentication request unit 232 notifies the service providing unit 233 of the authentication result.

[0074] The service providing unit 233 provides a service with content associated with the issuer H corresponding to the NFT indicated by the service request data in the service content data stored in the memory unit 22. The service providing unit 233 may provide a service with content associated with the type of NFT indicated by the service request data in the service content data. If the internal value of the NFT indicated by the service request data satisfies the conditions for providing the service based on the authentication result received from the management device 1, the service providing unit 233 executes processing to provide the service.

[0075] Specifically, the service providing unit 233 provides the service when the condition that the internal value of the NFT is equal to or greater than the threshold value corresponding to the service indicated by the service request data is satisfied. The threshold value corresponding to the service indicated by the service request data is a required internal value associated with the service indicated by the service request data in the service content data.

[0076] If the authentication result shows that the NFT has an internal value equal to or greater than the required internal value included in the authentication request data, the service providing unit 233 transmits data indicating that the service can be provided to the user terminal 4. For example, if the service is the provision of content, the service providing unit 233 transmits the content to the user terminal 4. If the service is participation in a live performance, the service providing unit 233 transmits an electronic ticket for participating in the live performance to the user terminal 4.

[0077] The service providing unit 233 may provide services according to the number of NFTs corresponding to one issuer H held by user U. For example, in the example shown in the service content table in FIG. 8, user U who holds two NFTs with the NFT name XYZ when the internal value of this NFT is 60 can participate in golf. In this way, by providing services according to the number of NFTs, user U is motivated to purchase many NFTs.

[0078] [Processing flow in management device 1] Fig. 9 is a flowchart showing the processing flow of the non-fungible token management method executed by the management device 1. The flowchart shown in Fig. 9 starts from the point when an NFT is issued.

[0079] When the update unit 133 receives an internal value update request to update an internal value via the NFT management screen (S11), it determines whether the internal value can be updated (S12). For example, the update unit 133 determines that the internal value of the NFT for which an internal value update is requested is updateable if the internal value has not reached its upper limit, and determines that the internal value of the NFT is not updateable if it has reached its upper limit. The upper limit of the internal value may be set in advance for each NFT.

[0080] If the update is possible (YES in S12), the update unit 133 updates the internal value in the NFT management data (S13). The update unit 133 notifies the issuer terminal 3 used by issuer H that the internal value has been updated. If the update is not possible (NO in S12), the update unit 133 does not update the internal value in the NFT management data, and sends a notification to the issuer terminal 3 indicating that the update is not possible (S14).

[0081] Thereafter, when the authentication unit 134 acquires authentication request data for requesting authentication of the NFT from the service providing device 2 (S15), it confirms with the blockchain B the owner of the NFT corresponding to the NFT-ID indicated in the authentication request data (S16). The authentication unit 134 also references the NFT management data to confirm whether the internal value corresponding to the NFT-ID indicated in the authentication request data is equal to or greater than the required internal value indicated in the authentication request data (S17). The authentication unit 134 notifies the service providing device 2 of the authentication result, including the confirmation result (S18).

[0082] [Processing flow in service providing device 2] 10 is a flowchart showing the processing flow of the service providing method executed by the service providing device 2. When the request acquisition unit 231 acquires service request data for requesting to receive the provision of a service using an NFT from the user terminal 4 (S21), the authentication request unit 232 identifies the internal value required to receive the service indicated by the service request data by referring to the service content data (S22). The authentication request unit 232 transmits the authentication request data including the NFT-ID, the required internal value, and the user ID to the management device 1 (S23).

[0083] If the authentication result received by the authentication request unit 232 from the management device 1 indicates that the user U who requested the provision of the service holds an NFT and that the internal value of the NFT is equal to or greater than the required internal value (YES in S24), the service providing unit 233 executes processing to provide the service (S25). If the authentication result indicates that the condition is not met (NO in S24), the service providing unit 233 transmits a notification to the user terminal 4 indicating that the service cannot be provided (S26).

[0084] [Effects of management device 1] As described above, the management device 1 creates an NFT that is associated with issuer H and a variable internal value and can be used to receive services, and stores the NFT in association with issuer H and the internal value. The management device 1 then changes the internal value in response to a request from issuer H or a change in the status of issuer H. This changes the value of the NFT, giving user U the expectation that the content of the services available using the NFT will improve. As a result, user U is motivated to purchase an NFT. User U is also motivated to support issuer H so that the internal value increases.

[0085] The present invention has been described above using embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments, and various modifications and changes are possible within the scope of the gist of the present invention. For example, all or part of the device can be configured by functionally or physically distributing or integrating any unit. Furthermore, new embodiments resulting from any combination of multiple embodiments are also included in the embodiments of the present invention. The effects of the new embodiments resulting from the combination also have the effects of the original embodiments. [Explanation of symbols]

[0086] 1 Management device 2. Service provision device 3 Issuer terminal 4. User terminal 11 Communications Department 12 Storage section 13 Control Unit 21 Communications Department 22 Memory section 23 Control Unit 131 Token Creation Department 132 Token Offering Department 133 Update Department 134 Authentication Department 231 Request acquisition part 232 Authentication Request Section 233 Service Provision Department

Claims

1. A system comprising: a management device that manages non-fungible tokens; and a service providing device that provides services to users who use the non-fungible tokens; The management device a token generating unit that generates a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, and stores the issuer and the internal value in association with each other in a token storage unit; a token providing unit that provides the non-fungible token to the user; an update unit that updates the internal value stored in the token storage unit based on an instruction from the issuer; an authentication unit that, when receiving authentication request data from the service providing device to request authentication of the non-fungible token, notifies the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than a required internal value indicated by the authentication request data; and the service providing device, a service content storage unit that stores service content data indicating the content of the service and the required internal value required to receive the service, in association with the issuer; a request acquisition unit that acquires service request data from the user to request the provision of a service that uses the non-fungible token; an authentication request unit that transmits the authentication request data to the management device to authenticate the internal value of the non-fungible token indicated by the service request data; a service providing unit that executes processing to provide the service when the internal value of the non-fungible token indicated by the service request data satisfies a condition for providing the service based on the authentication result received from the management device; An information processing system having:

2. the update unit updates the internal value stored in the token storage unit to the set value received from the issuer. The information processing system according to claim 1 .

3. the update unit, in response to receiving status data indicating a status of the issuer from an external device, updates the internal value of the non-fungible token stored in the token storage unit to a value corresponding to the status data; The information processing system according to claim 1 .

4. the update unit refers to update data in which the change in the status of the issuer and the amount of change in the internal value are associated, and updates the internal value by adding the amount of change corresponding to the change in the status of the issuer indicated by the status data. The information processing system according to claim 3 .

5. The update unit updates the internal value based on the number of support sent to the issuer. The information processing system according to claim 3 .

6. the service providing unit provides the service when the condition that the internal value is equal to or greater than a threshold value corresponding to the service indicated by the authentication request data is satisfied. The information processing system according to claim 1 .

7. the service providing unit provides the service having content associated with the issuer corresponding to the non-fungible token indicated by the authentication request data in the service content data. The information processing system according to claim 1 .

8. the token creation unit creates multiple types of non-fungible tokens associated with one issuer; the service content storage unit stores the service content data in which the content of the service is associated with the type of the non-fungible token; the service providing unit provides the service whose content is associated with the type of the non-fungible token indicated by the authentication request data in the service content data. The information processing system according to claim 7 .

9. the token provider provides a plurality of the non-fungible tokens associated with a single issuer to a single user; the service providing unit provides the service according to the number of the non-fungible tokens corresponding to one issuer held by the user; The information processing system according to claim 1 .

10. a token generating unit that generates a non-fungible token associated with an issuer that issues a non-fungible token and a variable internal value, and stores the issuer and the internal value in association with each other in a token storage unit; a token providing unit that provides the non-fungible token to a user; an update unit that updates the internal value stored in the token storage unit based on an instruction from the issuer; an authentication unit that, when receiving authentication request data for requesting authentication of the non-fungible token from a service providing device that provides a service to the user, notifies the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data, the required internal value being stored in the service providing device in association with the issuer and the content of the service and being necessary to receive the provision of the service; A non-fungible token management device having:

11. The computer executes A step of creating a non-fungible token associated with an issuer that issues a non-fungible token and a variable internal value, and storing the non-fungible token in a token storage unit in association with the issuer and the internal value; providing the non-fungible token to a user; updating the internal value stored in the token storage unit based on an instruction from the issuer; When authentication request data for requesting authentication of the non-fungible token is obtained from a service providing device that provides a service to the user, notifying the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data, which is stored in the service providing device in association with the issuer and the content of the service and is necessary to receive the provision of the service; A non-fungible token management method comprising:

12. On the computer, A step of creating a non-fungible token associated with an issuer that issues a non-fungible token and a variable internal value, and storing the non-fungible token in a token storage unit in association with the issuer and the internal value; providing the non-fungible token to a user; updating the internal value stored in the token storage unit based on an instruction from the issuer; When authentication request data for requesting authentication of the non-fungible token is obtained from a service providing device that provides a service to the user, notifying the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data, which is stored in the service providing device in association with the issuer and the content of the service and is necessary to receive the provision of the service; A program to execute.

13. A system comprising: a management device that manages non-fungible tokens; and a service providing device that provides services to users who use the non-fungible tokens; The management device a token generating unit that generates a non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, and stores the issuer and the internal value in association with each other in a token storage unit; a storage unit that stores update data in which the change in the status of the issuer, indicated by the number of likes or dislikes for the issuer posted on the SNS, is associated with the amount of change in the internal value; a token providing unit that provides the non-fungible token to the user; an update unit that updates the internal value stored in the token storage unit by adding, when the state of the issuer changes, an amount of change in the internal value associated with the change in the state of the issuer in the update data to the internal value stored in the token storage unit; an authentication unit that, when receiving authentication request data from the service providing device to request authentication of the non-fungible token, notifies the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than a required internal value indicated by the authentication request data; and the service providing device, a service content storage unit that stores the content of the service and the required internal value required to receive the service in association with the issuer; a request acquisition unit that acquires service request data from the user to request the provision of a service that uses the non-fungible token; an authentication request unit that transmits the authentication request data to the management device to authenticate the internal value of the non-fungible token indicated by the service request data; a service providing unit that executes processing to provide the service when the internal value of the non-fungible token indicated by the service request data satisfies a condition for providing the service based on the authentication result received from the management device; An information processing system having:

14. a token generating unit that generates a non-fungible token associated with an issuer that issues a non-fungible token and a variable internal value, and stores the issuer and the internal value in association with each other in a token storage unit; a token providing unit that provides the non-fungible token to a user; a storage unit that stores update data in which the change in the status of the issuer, indicated by the number of likes or dislikes for the issuer posted on the SNS, is associated with the amount of change in the internal value; an update unit that updates the internal value stored in the token storage unit by adding, when the state of the issuer changes, an amount of change in the internal value associated with the change in the state of the issuer in the update data to the internal value stored in the token storage unit; an authentication unit that, when receiving authentication request data for requesting authentication of the non-fungible token from a service providing device that provides a service to the user, notifies the service providing device of an authentication result indicating whether the internal value stored in the token storage unit is greater than the required internal value indicated by the authentication request data, the required internal value being stored in the service providing device in association with the issuer and the content of the service and being necessary to receive the provision of the service; A non-fungible token management device having:

Images