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

Abstract

Allow the value of non-fungible tokens to be changed after they have been issued. [Solution] The management device 1 includes a token creation unit 131 that creates a non-fungible token associated with an issuer that issues non-fungible tokens and a variable internal value, and stores the issuer and internal value in a token storage unit in association with each other; a token provision unit 132 that provides non-fungible tokens to users; an update unit 133 that updates the internal value stored in the storage unit 12; and an authentication unit 134 that, when it obtains authentication request data for requesting authentication of a non-fungible token from a service provision device that provides services to users, notifies the service provision device 2 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.

Description

Technical Field

[0006] , , ,

[0005] , ,

[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 Art

[0002] Conventionally, a system for granting privileges to a person having a non-fungible token has been known. In the conventional system, a privilege corresponding to the content associated with the serial number attached to the non-fungible token is granted (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the conventional system, there was a problem that the value of the non-fungible token could not be changed after the non-fungible token was issued.

[0005] Therefore, the present invention has been made in view of these points, and an object thereof is to enable the value of a non-fungible token to be changed after the non-fungible token is issued.

Means for Solving the Problems

[0006] An information processing system according to a first aspect of the present invention comprises a management device for managing non-fungible tokens and a service provision device for providing services to users using the non-fungible tokens, wherein the management device includes a token creation unit that creates non-fungible tokens associated with an issuer that issues the non-fungible tokens and a variable internal value, and stores the issuer and the internal value in association in a token storage unit, a token provision unit that provides the non-fungible tokens 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 provision device, prior to the required internal value indicated by the authentication request data The service provider has an authentication unit that notifies the service provider of an authentication result indicating whether the internal value stored in the token storage unit is large or small, and the service provider has a request acquisition unit that acquires service request data from the user for requesting the provision of a service using the non-fungible token, an authentication request unit that transmits the authentication request data to the management device for authenticating the internal value of the non-fungible token indicated by the service request data, and a service provider unit that, based on the authentication result received from the management device, executes a process 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.

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

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

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

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

[0011] The service provider unit may provide the service if the condition is met that the internal value is greater than or equal to the threshold corresponding to the service indicated by the authentication request data.

[0012] The service provider further includes a service content storage unit that stores service content data indicating the content of the service in relation to the issuer, and the service provider unit may provide the service in the service content data that corresponds to the content associated with the issuer 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 a single issuer, the service content storage unit may store service content data in which the content of the service is associated with the type of non-fungible token, and the service provision unit may provide the service in the service content data that is associated with the type of non-fungible token indicated by the authentication request data.

[0014] The token provider may provide a user with a plurality of non-fungible tokens associated with a single issuer, and the service provider may provide services in proportion to the number of non-fungible tokens held by the user that correspond to a single issuer.

[0015] A non-fungible token management device according to a second aspect of the present invention includes: a token creation unit that creates a non-fungible token associated with an issuer that issues non-fungible tokens and a variable internal value, and stores the issuer and the internal value in association 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 it obtains authentication request data for requesting authentication of the non-fungible token from a service provision device that provides services 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 present invention provides a method for managing non-fungible tokens, comprising the steps of: creating a non-fungible token associated with an issuer that issues non-fungible tokens and a variable internal value, and storing the issuer and the internal value in a token storage unit in association with each other; providing the non-fungible token to a user; updating 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 a service provider that provides services to the user, notifying the service provider 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] The program according to the fourth aspect of the present invention causes a computer to create the non-fungible token associated with an issuer that issues the non-fungible token and a variable internal value, associate the issuer and the internal value, and store them in a token storage unit; provide the non-fungible token to a user; update the internal value stored in the token storage unit; and when obtaining, from a service providing device that provides a service to the user, authentication request data for requesting authentication of the non-fungible token, notify 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.

Advantages of the Invention

[0018] According to the present invention, there is an effect that the value of the non-fungible token can be changed after the non-fungible token is issued.

Brief Description of the Drawings

[0019] [Figure 1] It is a diagram for explaining the outline of the information processing system S. [Figure 2] It is a diagram showing the configuration of the management device 1. [Figure 3] It is a diagram showing an example of NFT management data. [Figure 4] It is a diagram showing an example of user management data. [Figure 5] It is a diagram showing an example of update data. [Figure 6] It is a diagram showing an example of an NFT management screen. [Figure 7] It is a diagram showing the configuration of the service providing device 2. [Figure 8] It is a diagram showing an example of service content data. [Figure 9] It is a flowchart showing the processing flow of the method for managing non-fungible tokens executed by the management device 1. [Figure 10]It is a flowchart showing the processing flow of a service provision method executed by the service provision device 2.

Embodiments for Carrying Out the Invention

[0020] [Overview of Information Processing System S] FIG. 1 is a diagram for explaining the overview of the information processing system S. The information processing system S is a system for issuing non-fungible tokens (hereinafter sometimes referred to as "NFTs") and providing services using the issued NFTs to users. In the example shown in FIG. 1, the information processing system S includes a management device 1 and a service provision device 2, but the information processing system S may be constituted by a single device or may include other devices.

[0021] The management device 1 is a non-fungible token management device that creates an NFT in response to receiving a request to issue an NFT from a person who issues the NFT (hereinafter referred to as the "issuer H"), and is, for example, a computer. The management device 1 creates an NFT whose value changes according to the state of the issuer. The issuer H is, for example, a famous person who wants to inform many people of his or her activities or increase his or her fans, and specifically is an entertainer, a politician, a sports player, a corporate manager, or the like.

[0022] The NFT is associated with a variable internal value together with the issuer H. The management device 1 determines the initial value of the internal value at the time of creating the NFT, and stores it in association with 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. Thereafter, the management device 1 updates the internal value based on the instruction of the issuer H associated with the NFT or based on the change in the state of the issuer H.

[0023] Management device 1 records management information regarding the issued NFT on blockchain B. The management information includes the NFT-ID, issuer ID, and the name of the NFT holder. At the time the NFT is created, the holder's name is the name or company name of issuer H.

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

[0025] Service provider 2 is a server that provides services to user U who possesses an NFT issued by management device 1. Service provider 2 is a server operated by, for example, issuer H, or the organization to which issuer H belongs. When service provider 2 receives a usage request from user U, who possesses an NFT issued by issuer H, including the NFT-ID of the NFT, it requests management device 1 to authenticate whether the NFT corresponding to the NFT-ID is an NFT owned by user U. Service provider 2 also requests management device 1 to check 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] Service provider device 2 provides services to user U if it can confirm that the NFT is owned by user U and that the NFT possesses the internal values ​​necessary for providing the service. As will be described in detail later, the services include viewing content, participating in meetings, or providing benefits. The content of the services that user U can receive changes depending on the changes in the internal values ​​held by the NFT.

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

[0028] User terminal 4 is a computer used by user U, who acquires and uses NFTs, and is, for example, a smartphone or tablet. User U can purchase or receive NFTs free of charge by performing predetermined operations on user terminal 4. For example, user U can receive an NFT corresponding to a code (for example, a QR code®) attached to a prize by scanning the code with user terminal 4. Specifically, the NFTs received by user U are stored in user U's wallet.

[0029] User terminal 4 sends and receives data to and from management device 1 and service provider device 2 via the network. In response to user U's search operation, user terminal 4 displays information about NFTs owned by user U and accepts operations to use NFTs.

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

[0031] When Management Device 1 receives an NFT issuance request, it creates an NFT based on the information entered on the management screen. Management Device 1 stores the NFT's name, issuance quantity, and internal values, etc., associated with the issuer ID of the created NFT. Management Device 1 records the management data related to the created NFT on Blockchain B (Figure 1 (2)).

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

[0033] Management device 1 provides a marketplace for selling NFTs issued by, for example, issuer H. When user U purchases an NFT selected on the marketplace, management device 1 records information to identify user U (e.g., user U's name, user U's email address) associated with the NFT-ID on blockchain B. Management device 1 notifies user U that the NFT has been purchased by sending the NFT-ID of the selected NFT to user U's address.

[0034] User U can use the NFTs they own by launching application software for using NFTs on user terminal 4. The application software displays a list of the names of the NFTs owned by user U. When user U selects the name of the NFT they want to use, user terminal 4 sends an NFT usage request to the service provider device 2 that is stored in association with the selected NFT (Figure 1, (4)). The NFT usage request contains information indicating the content of the service that user U wants to receive using the NFT.

[0035] When the service provider 2 receives an NFT usage request, it sends an authentication request to the management device 1 to request authentication of the NFT indicated in the NFT usage request (Figure 1, (5)). The authentication request includes the NFT-ID, a user ID to identify user U, and internal values ​​necessary to provide the service indicated in the NFT usage request (hereinafter referred to as "required internal values").

[0036] When the management device 1 receives an authentication request, it sends the NFT-ID and user ID to blockchain B and verifies that the NFT for which authentication was requested is held by user U corresponding to the user ID (Figure 1, (6)). The management device 1 also verifies 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 the authentication result, including these verification results, to the service provider device 2 (Figure 1, (7)).

[0037] The service provider 2 determines whether or not 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 possesses the NFT indicated by the NFT usage request and that the internal value of the NFT is equal to or greater than the required internal value, the service provider 2 allows user U to receive the service (Figure 1, (8)).

[0038] Thus, because the services that user U, who holds the NFT, can receive change in conjunction with the NFT's internal value, user U can have the expectation that the NFT's value will change. As a result, user U becomes motivated to purchase NFTs. Furthermore, user U becomes motivated to support issuer H so that the internal value increases. The configuration and operation of the management device 1 and the service provision device 2 will be described in detail below.

[0039] [Configuration of Management Device 1] Figure 2 shows 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 sending and receiving data with the service provider device 2, issuer terminal 3, user terminal 4, and blockchain B. The communication unit 11 notifies the control unit 13 of the received data and transmits the data input from the control unit 13 to other devices.

[0041] The storage unit 12 has storage media such as ROM (Read Only Memory), RAM (Random Access Memory), and SSD (Solid State Drive). The storage unit 12 stores the program 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 NFTs issued by issuer H.

[0042] Figure 3 shows an example of NFT management data. In the NFT management data shown in Figure 3, the issuer ID, NFT name, number issued, number made public, sales price, and internal value are associated.

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

[0044] As shown in Figure 3, issuer H with issuer ID ABD may issue NFTs with the same name but different selling prices. Alternatively, as shown in Figure 3, issuer H with issuer ID ABE may issue multiple types of NFTs.

[0045] Furthermore, the storage unit 12 stores user management data that indicates information about the NFTs owned by user U. Figure 4 shows an example of user management data. In the user management data shown in Figure 4, the user ID, the NFT name of the NFT owned by the user, the number of each NFT owned by user U, and the NFT-ID of each NFT are associated.

[0046] Furthermore, the memory unit 12 may store update data that associates the changes in issuer H's state with the amount of change in the internal value. Figure 5 shows an example of update data. As the update data in Figure 5 shows, the amount of change in the internal value differs depending on the changes in state. The amount of change in the internal value corresponding to the changes in state may be negative, and the internal value may decrease as issuer H's state changes. Note that the changes may not be changes in issuer H's own state, but rather changes in the state of others related to issuer H (for example, people belonging to the same organization as issuer H).

[0047] Returning to Figure 2, the configuration of the control unit 13 will be explained. The control unit 13 includes, for example, a CPU (Central Processing Unit). By executing the program stored in the storage unit 12, the control unit 13 functions 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 issuer H and a variable internal value, and stores the associated issuer H and internal value in the storage unit 12. The token creation unit 131 also registers the NFT with blockchain B by sending management information about the created NFT to blockchain B.

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

[0050] Figure 6 shows an example of an NFT management screen. On the NFT management screen, issuer H can set the name of the NFT to be created, issuer name, number of issues issued, number of publicly available, sales price, internal values, and custom parameters. Custom parameters are scores indicating the strength of the issuer's characteristics. For example, custom parameters can be used by issuer H to promote themselves.

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

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

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

[0054] The data relating to the NFT may include the name of the NFT issuer and the NFT's selling price, as well as image data corresponding to the NFT. The data relating to the NFT may also include data indicating the content of the services that can be received using the NFT. When user terminal 4 receives data relating to the NFT, it displays the received data.

[0055] When the token provider 132 receives a purchase request from the user terminal 4 in which the NFT purchase operation was performed, it updates the information of user U who made the purchase request in the user management data. Specifically, the token provider 132 stores the NFT-ID of the purchased NFT in association with user U's user ID, and increases the number of purchased NFTs held.

[0056] Furthermore, the token provider unit 132 also updates the management information regarding NFT holders recorded on blockchain B. Specifically, the token provider unit 132 records the user ID of user U who purchased the NFT as the NFT holder in the management information regarding the NFT recorded on blockchain B.

[0057] Furthermore, if user U purchases an NFT that was previously held by another user, the token provider unit 132 may send a sales notification to the other user who previously held the NFT before user U's purchase, indicating the name of the purchased NFT, the NFT-ID, and the sales price.

[0058] The update unit 133 updates the internal value of the NFT stored in the storage unit 12. 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 setting value received from issuer H. Specifically, the update unit 133 updates the internal value by storing the value of the internal value set by issuer H on the NFT management screen in the storage unit 12, associating it with the NFT-ID of the NFT specified by issuer H. The update unit 133 may also record the fact that the internal value has been updated in the blockchain B, associating it with the NFT-ID whose internal value has been updated.

[0059] The update unit 133 may update the internal value of the NFT stored in the storage unit 12 to a value corresponding to the status data when it receives status data indicating the status of issuer H from an external device. The status of issuer H is represented, for example, by the results of issuer H's activities or the results of other people's activities toward issuer H. The external device is a computer that records the results of issuer H's activities or the results of other people's activities toward issuer H. The results of issuer H's activities include, for example, issuer H posting on social media, issuer H giving a lecture, or issuer H making a donation. The results of other people's activities toward issuer H include showing support for issuer H's posts or making a donation to issuer H.

[0060] The update unit 133 may update the internal value by referring to update data that associates the changes in issuer H's state with the amount of change in the internal value, and adding the amount of change corresponding to the changes in issuer H's state indicated by the state data. The amount of change in the internal value may be negative, in which case the internal value decreases as the state of issuer H changes.

[0061] As shown in Figure 5, in the update data, for example, the number of endorsements for publisher H posted on social media (i.e., the number of "likes") is associated with the amount to increase the internal value, and the update unit 133 updates the internal value based on the number of endorsements. As an example, the update unit 133 updates the internal value by increasing it by 10 every time the number of endorsements 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 each 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 provider 2. As part of the authentication processing, the authentication unit 134 performs a process to determine whether the internal value stored in the storage unit 12 in association with the NFT-ID indicated by the authentication request is greater than the required internal value indicated by the authentication request, and notifies the service provider 2 of the authentication result indicating the result of the determination. As part of the authentication processing, the authentication unit 134 may also query blockchain B to determine whether user U, who is the holder of the NFT indicated by the authentication request, matches the holder recorded in blockchain B.

[0064] [Configuration of Service Provisioning Device 2] Figure 7 shows the configuration of the service provision device 2. The service provision 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 sending and receiving various types of data between the management device 1 and the user terminal 4. When the communication unit 21 receives authentication request data from the user terminal 4 to request the provision of a service using NFTs, it notifies the request acquisition unit 231 of the authentication request data. When the communication unit 21 receives authentication request data from the authentication request unit 232, it 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 the program executed by the control unit 23. The storage unit 22 also functions as a service content storage unit that stores service content data showing the relationship between the content of services that can be provided to user U using NFTs and the internal values ​​necessary to receive those services.

[0067] Figure 8 shows an example of service content data. In the service content data shown in Figure 8, the issuer ID of issuer H who issued the NFT, the NFT name, the required internal value, the number of NFTs to be held in order to receive the service, and the content of the service are associated.

[0068] In the example shown in Figure 8, user U, who possesses an NFT with the name XYZ, can view video content provided by issuer H, for example, if the NFT's internal value is 20 or higher. User U can participate in issuer H's live event if the NFT's internal value is 40 or higher. User U can participate in a golf game with issuer H if the NFT's internal value is 60 or higher and user U possesses two or more NFTs.

[0069] If one issuer H issues multiple types of NFTs, the storage unit 12 may store service content data that associates the content of the service with the type of NFT. The storage unit 12 may also store service content data that indicates only some of the service content corresponding to some of the multiple types of NFTs issued by one issuer H.

[0070] The control unit 23 has, for example, a CPU. The control unit 23 functions as a request acquisition unit 231, an authentication request unit 232, and a service provision unit 233 by executing a program stored in the storage unit 22.

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

[0072] The authentication request unit 232 sends 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 acquired the service request data has the internal value necessary to receive the service indicated by the service request data. To this end, the authentication request unit 232 refers to the service content data stored in the storage unit 22 and identifies the internal value necessary to receive the service indicated by the service request data. The authentication request unit 232 sends an authentication request to the management device 1 indicating the NFT-ID and the necessary internal value indicated by the service request data.

[0073] The authentication request unit 232 may request the management device 1 to authenticate that user U possesses the NFT corresponding to the NFT-ID indicated in the service request data. To this end, the authentication request unit 232 may send authentication request data including user U's user ID along with the NFT-ID to the management device 1. When the authentication request unit 232 receives the authentication result sent from the management device 1, it notifies the service provision unit 233 of the authentication result.

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

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

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

[0077] The service provider 233 may provide services corresponding to the number of NFTs held by user U that correspond to a single issuer H. For example, in the example shown in the service details table in Figure 8, user U, who holds two NFTs with the name XYZ and an internal value of 60, can participate in golf. In this way, providing services according to the number of NFTs incentivizes user U to purchase more NFTs.

[0078] [Processing flow in control device 1] Figure 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 Figure 9 starts from the point when the NFT is issued.

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

[0080] If an 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 an 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 an update is not possible (S14).

[0081] Subsequently, when the authentication unit 134 obtains authentication request data from the service provider 2 to request authentication of the NFT (S15), it verifies with blockchain B the holder of the NFT corresponding to the NFT-ID indicated by the authentication request data (S16). The authentication unit 134 also refers to the NFT management data to verify whether the internal value corresponding to the NFT-ID indicated by the authentication request data is equal to or greater than the required internal value indicated by the authentication request data (S17). The authentication unit 134 then notifies the service provider 2 of the authentication result, including the verification result (S18).

[0082] [Processing flow in service provision device 2] Figure 10 is a flowchart illustrating the processing flow of the service provision method executed by the service provision device 2. When the request acquisition unit 231 acquires service request data from the user terminal 4 to request the provision of a service using an NFT (S21), the authentication request unit 232 identifies the internal values ​​necessary to receive the service indicated by the service request data by referring to the service content data (S22). The authentication request unit 232 transmits authentication request data including the NFT-ID, the necessary internal values, 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 service possesses an NFT and that its internal value is greater than or equal to the required internal value (YES in S24), the service provision unit 233 executes the process to provide the service (S25). If the authentication result indicates that the conditions are not met (NO in S24), the service provision unit 233 sends a notification to the user terminal 4 indicating that the service cannot be provided (S26).

[0084] [Effects of Control Device 1] As explained above, the management device 1 is associated with issuer H and a variable internal value, creates NFTs that can be used to receive services, and stores the association between issuer H and the internal value. Then, it changes the internal value in response to a request from issuer H or in response to a change in issuer H's status. As a result, the value of the NFT changes, so user U can have the expectation that the content of the services that can be received using the NFT will improve. As a result, user U becomes motivated to purchase NFTs. Furthermore, user U becomes motivated to support issuer H so that the internal value increases.

[0085] Although the present invention has been described above using embodiments, 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 its gist. For example, all or part of the apparatus can be configured by functionally or physically distributing and integrating in 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 combinations are combined with the effects of the original embodiments. [Explanation of symbols]

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

Claims

1. The system comprises a management device for managing non-fungible tokens and a service provider device for providing services to users who use the non-fungible tokens, The aforementioned control device is A token creation unit 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 a token storage unit in association with each other. A token provider unit that provides the non-fungible token to the user, An update unit that updates the internal value stored in the token storage unit, An authentication unit that, upon obtaining authentication request data from the service provider for requesting authentication of the non-fungible token, notifies the service provider 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, It has, The aforementioned service provider is A request acquisition unit that acquires service request data from the user for requesting the provision of a service using the non-fungible token, An authentication request unit transmits authentication request data to the management device for authenticating the internal value of the non-fungible token indicated by the service request data. A service provision unit that, based on the authentication result received from the management device, executes a process 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, An information processing system having the following features.

2. The update unit updates the internal value stored in the token storage unit so that it becomes the setting value received from the issuer. The information processing system according to claim 1.

3. The update unit, upon receiving status data indicating the issuer's status 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 updates the internal value by referring to update data which associates the change in the issuer's status with the amount of change in the internal value, and adding the amount of change corresponding to the change in the issuer's status 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 endorsements sent to the issuer. The information processing system according to claim 3.

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

7. The service provision device further includes a service content storage unit that stores service content data indicating the content of the service in relation to the issuer, The service provider unit provides, in the service content data, the service that corresponds to the non-fungible token indicated in the authentication request data and is associated with the issuer. 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 non-fungible token. The service provider unit provides, in the service content data, the service that is associated with the type of non-fungible token indicated in the authentication request data. The information processing system according to claim 7.

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

10. A token creation unit creates a non-fungible token associated with an issuer that issues non-fungible tokens and a variable internal value, and stores the issuer and the internal value in association in a token storage unit, A token provider unit that provides the aforementioned non-fungible token to the user, An update unit that updates the internal value stored in the token storage unit, An authentication unit that, when it obtains authentication request data for requesting authentication of the non-fungible token from a service provider that provides services to the user, notifies the service provider 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, A non-fungible token management device having the following characteristics.

11. A computer executes The steps include creating a non-fungible token associated with an issuer that issues non-fungible tokens and a variable internal value, and storing the issuer and the internal value in a token storage unit in association with each other, The steps include providing the user with the aforementioned non-fungible token, The steps include updating the internal value stored in the token storage unit, When authentication request data for requesting authentication of the non-fungible token is obtained from a service provider that provides services to the user, the service provider is notified 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. A method for managing non-fungible tokens.

12. On the computer, The steps include creating a non-fungible token associated with an issuer that issues non-fungible tokens and a variable internal value, and storing the issuer and the internal value in a token storage unit in association with each other, The steps include providing the user with the aforementioned non-fungible token, The steps include updating the internal value stored in the token storage unit, When authentication request data for requesting authentication of the non-fungible token is obtained from a service provider that provides services to the user, the service provider is notified 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. A program to execute.

Images