Computer-implemented method and computer system

Abstract

To enhance uniqueness of FT-ed content data.SOLUTION: A computer executes a computer implementation method for a non-fungible token recorded in a blockchain. The non-fungible token is associated with content data. The content data can be edited by an authorized editor but cannot be edited by a non-authorized editor. The computer implementation method receives edited data showing edited content by a user who is the authorized editor and updates the content data associated with the non-fungible token according to the edited data.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to computer-implemented methods and systems for non-fungible tokens. [Background technology]

[0002] Non-Fungible Tokens An NFT (non-transferable fiat currency) is a type of token recorded on a blockchain. NFTs are used to prove ownership of content data such as digital art. NFTs are issued according to the Ethereum Request for Comments (ERC) 721 standard, for example. Patent Document 1 discloses Ethereum. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-160316 Summary of the Invention

[0004] The more unique the NFTed content data, the more likely it is to increase in value. For example, if image data of a celebrity is converted into an NFT and the celebrity's signature is attached to the image data, it will be more unique and more valuable than the image data alone. Furthermore, if a signature addressed to a specific user is attached to the image data, the value to that user will be even higher.

[0005] Therefore, technology to further increase the uniqueness of NFTed content data is desired.

[0006] The above problem is solved by accepting editing data for NFTed content data and updating the content data in accordance with the editing data.

[0007] Further details will be described in the following embodiments. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a configuration diagram of a computer system according to an embodiment. [Figure 2] Figure 2 is a schematic diagram of a method for displaying NFTed content data. [Figure 3] Figure 3 is a flowchart of the NFT management process. [Figure 4] FIG. 4 is a schematic diagram showing a first example of editing. [Figure 5] FIG. 5 is a schematic diagram showing a second example of editing. [Figure 6] FIG. 6 is a schematic diagram showing a third example of editing. [Figure 7] FIG. 7 is a flowchart of the NFT management process. [Figure 8] FIG. 8 is a schematic diagram showing a fourth example of editing. [Figure 9] FIG. 9 is a flowchart of the NFT management process. [Figure 10] FIG. 10 is a schematic diagram showing a fifth example of editing. [Figure 11] FIG. 11 is a diagram showing the configuration of a content print system. DETAILED DESCRIPTION OF THE INVENTION

[0009] 1. Overview of Computer-Implemented Method and Computer System

[0010] (1) A computer-implemented method according to an embodiment is a method executed by a computer for a non-fungible token recorded in a blockchain, wherein the non-fungible token is associated with content data, and the content data can be edited by an authorized user but cannot be edited by a non-authorized user. The computer-implemented method includes accepting editing data indicating the content of edits made by a user who is authorized to edit, and updating the content data associated with the non-fungible token in accordance with the editing data.

[0011] (2) Preferably, the computer-implemented method further comprises determining whether the user is an authorized editor.

[0012] (3) It is preferable that the editing authority includes a person recorded in the blockchain as the owner of the non-fungible token.

[0013] (4) It is preferable that the editing authority includes a person designated by a person recorded on the blockchain as the owner of the non-fungible token.

[0014] (5) It is preferable that the person authorized to edit includes a person who is preset as the person authorized to edit.

[0015] (6) It is preferable that the editing authority is recorded in the blockchain.

[0016] (7) Preferably, the computer-implemented method further comprises transmitting the edited content data to an external computer that executes processing for printing the content data.

[0017] (8) A computer-implemented method according to an embodiment may be a method executed by a computer for a non-fungible token recorded on a blockchain, the non-fungible token being associated with content data, and the computer-implemented method may include receiving editing data indicating edits made by a user and an identifier for identifying the content data to be edited, and updating the content data identified by the identifier in accordance with the editing data.

[0018] (9) It is preferable that the identifier includes data for identifying a non-fungible token associated with the content data to be edited.

[0019] (10) A computer-implemented method according to an embodiment is a method executed by a computer for a non-fungible token recorded in a blockchain, the non-fungible token being associated with content data, the content data being uneditable in a non-editable mode but becoming editable when switching to an edit mode, the computer-implemented method including: switching the content data from the non-editable mode to the edit mode; accepting, in the edit mode, editing data indicating the edit content; updating the content data associated with the non-fungible token according to the editing data; and, after updating the content data, switching the content data from the edit mode to the non-editable mode.

[0020] (11) It is preferable that the switching from the non-editable mode to the editable mode is performed when a user operation for switching is performed.

[0021] (12) Preferably, the computer-implemented method further comprises transmitting the edited content data to an external computer that executes processing for printing the editable data.

[0022] (13) A computer system according to an embodiment is a computer system for a non-fungible token recorded in a blockchain, wherein the non-fungible token is associated with content data, the content data can be edited by an authorized person but cannot be edited by a non-authorized person, and the computer system is configured to accept editing data indicating the edits made by a user who is authorized to edit, and update the content data associated with the non-fungible token in accordance with the editing data.

[0023] (14) A computer system according to an embodiment is a computer system for a non-fungible token recorded in a blockchain, wherein the non-fungible token is associated with content data, the content data is uneditable in a non-editable mode but becomes editable when switched to an edit mode, and the computer system is configured to switch the content data from the non-editable mode to the edit mode, accept editing data indicative of the edit content in the edit mode, update the content data associated with the non-fungible token according to the editing data, and switch the content data from the edit mode to the non-editable mode after updating the content data.

[0024] (15) A computer system according to an embodiment is a computer system for a non-fungible token recorded in a blockchain, the non-fungible token being associated with content data, and the computer system being configured to receive editing data indicating the editing content made by a user and an identifier for identifying the content data to be edited, and to update the content data identified by the identifier in accordance with the editing data.

[0025] 2. Examples of computer-implemented methods and computer systems for NFTs

[0026] FIG. 1 shows an example of a computer system 10 (hereinafter referred to as "system 10") according to an embodiment. The system 10 manages NFTed content data 13A, 13B, etc. The system 10 executes processing for editing the NFTed first content data 13A. Conventionally, NFTed content data has not been expected to be edited after being NFTed. In contrast, in the system 10 according to an embodiment, the first content data 13A can be edited even after being NFTed. By editing the NFTed first content data 13A, the uniqueness of the first content data 13A can be increased even after being NFTed, and an increase in value is expected.

[0027] In the embodiment, there is also second content data 13B that has been converted into NFT. After being converted into NFT, the second content data 13B is uneditable and will never become editable. In the system 10 of the embodiment, there may be first content data 13A that can be edited and second content data 13B that cannot be edited.

[0028] The NFTed content data 13A, 13B refers to the content data 13A, 13B associated with the NFTs 101, 102. The content data 13A, 13B associated with the NFTs 101, 102 may be the content data 13A, 13B stored in association with the NFTs 101, 102 in a computer 13 outside the blockchain 11, or may be data recorded in the blockchain 11 as part of the data constituting the NFTs 101, 102. In other words, the association between the NFTs 101, 102 and the content data 13A, 13B may be performed outside the blockchain 11 or within the blockchain 11.

[0029] The NFTs 101, 102 associated with the content data 13A, 13B are recorded in the blockchain 11. The NFTs 101, 102 can be traded, such as bought, sold, or exchanged, in the blockchain 11, and transaction records are recorded in the blockchain 11. The owners of the NFTs 101, 102 are recorded in the blockchain 11. Ownership of the NFTs 101, 102 can be proven by records in the blockchain 11. Proof of ownership of the NFTs 101, 102 is proof of ownership of the content data 13A, 13B.

[0030] The NFT 101 associated with the editable first content data 13A is also referred to as the first NFT 101. The NFT 102 associated with the uneditable second content data 13B is also referred to as the second NFT 102.

[0031] The first NFT 101 of the embodiment can be considered an NFT (NFT with editing rights) that comes with editing rights for the first content data 13A. In the blockchain 11 where NFTs are recorded, the NFT 101 with editing rights can be the subject of transactions such as buying, selling, and exchanging, just like the non-editable NFT 102. The editing rights may be the right of the owner of the NFT 101 to edit the NFT themselves (self-editing rights), or the right to have someone other than the owner of the NFT 101 edit the NFT 101 (expected editing rights), or may include both rights (self-editing rights and expected editing rights). Note that the second NFT 102 of the embodiment can be considered an NFT without editing rights (normal NFT).

[0032] The fact that editing is possible after conversion to an NFT means that when the NFT 101 is traded, such as bought, sold, or exchanged, and the NFT 101 is owned by any user, the NFT 101 can be edited by the user, such as the owner of the NFT 101. This allows the user who owns the NFT 101 to enjoy editing the NFT-converted first content data 13A or the enjoyment of having the first content data 13A edited by another user.

[0033] It is preferable that editing be permitted only to a limited number of authorized editors and not permitted to non-authorized editors. Non-authorized editors are those other than authorized editors. Limiting the number of authorized editors prevents unintended editing of data by third parties. Editing may be permitted for the entire first content data 13A, or only for part of the first content data 13A.

[0034] The content data 13A and 13B are digital data, such as image data, text data, audio data, other data, or a combination of two or more of these data. The content data 13A and 13B include data (display data) that appears on the screen when the NFTs 101 and 102 are displayed on the displays of the user terminals 30, 31, 33, and 34. The editable content data 13A and the edited content data 13A are preferably display data. The pre-edited content data 13A may be data that does not have any substantial content, such as plain image data. The pre-edited content data 13A may also be a value indicating NULL.

[0035] The image data materials that become content data 13A and 13B are not particularly limited, but may include entertainers, singers, athletes, other famous people, characters from manga, games, animations, etc., game items, vehicles, machines, tools, animals, plants, etc.

[0036] The content data 13A and 13B may include data that does not appear on the screen when the NFT 101 is displayed on a display. The data that does not appear on the screen is, for example, data for managing the content data 13A (management data). The management data is, for example, data indicating the person authorized to edit.

[0037] Editing is preferably at least one of adding data to content data and processing data, but may also include deleting data. Editing may not require deleting data. Data added to content data for editing may be, for example, one or more data selected from image data, text data, and sound data. Data processing is, for example, image processing of image data.

[0038] Editing is, for example, decoration of image data as editable content data 13A. Decoration is, for example, adding handwritten figures or handwritten characters to editable content data 13A, adding decorative images, or adding character data. Editing such as decoration may include writing handwritten characters such as an autograph or signature, a message, or an address. Editing such as decoration may also include drawing handwritten figures.

[0039] The editing may be the addition of audio data, video with audio, or video without audio.

[0040] The system 10 according to the embodiment can make the NFTed content data 13A uneditable after editing the content data. By making the content data uneditable, even an authorized person cannot edit the content data, preventing unnecessary changes to the content data. After making the content data uneditable, the content data may be switched to be re-editable or may not be re-editable at all. By making the content data uneditable, the content of the content data can be finalized.

[0041] The system 10 according to the embodiment can also execute processing for converting the content data 13A into an NFT. Converting the content data 13A into an NFT means associating the content data 13A with the NFT 101. To associate the content data 13A with the NFT 101, the content data 13A may be recorded in the blockchain 11 as part of the data constituting the NFT 101, or the content data 13A may be stored in association with the NFT 101 in a computer 13 outside the blockchain 11.

[0042] In FIG. 1, content data 13A and 13B are stored in a database 13 outside the blockchain 11. The database 13 is configured, for example, by a file system connected to a network 15 such as the Internet. The file system includes one computer or multiple computers connected to the network 15. The database 13 is configured, for example, by IPFS (InterPlanetary File System). IPFS is an example of a P2P (Peer to Peer) distributed file system.

[0043] The content data 13A stored in the database 13 is normally in a non-editable mode, and can be viewed if accessed by a person authorized to view, but cannot be edited. If accessed by a person authorized to edit, the content data 13A stored in the database 13 switches to an edit mode, and becomes editable. When an editing completion operation is performed, the content data 13A returns to the non-editable mode.

[0044] The change to the edit mode is not limited to when an authorized editor accesses the system, but may be made at a predetermined timing, or when other change conditions are satisfied.

[0045] The database 13 constituting the file system controls external access to stored data according to preset access permissions. For example, when a person with editing authority accesses first content data 13A, which is editable data, the database 13 permits access to edit the first content data 13A and sets the first content data to edit mode. When a person without editing authority accesses the first content data 13A, the database 13 denies access to edit the first content data 13A.

[0046] Furthermore, when a person with access authority accesses the first content data 13A, the database 13 permits the access for referencing the first content data 13A. When a person without access authority accesses the first content data 13A, the database 13 denies the access for referencing the first content data 13A.

[0047] When there is an access to edit the second content data 13B, which is non-editable data, the database 13 denies the access. Also, when there is an access to the second content data 13B from a person authorized to view, the database 13 permits the access to view the second content data 13B. When there is an access to the second content data 13B from a person not authorized to view, the database 13 denies the access to view the second content data 13B.

[0048] The authorized editor is, for example, at least one of the user who owns the NFT 101 associated with the content data 13A, a user designated by the user who owns the NFT 101, and a person who has been preset as the authorized editor. A non-authorized editor is a person other than the authorized editor. The authorized editor is indicated by, for example, a blockchain address. The authorized editor for each NFT may be recorded in the blockchain 11 or in the database 13.

[0049] The reference authorized person is, for example, at least one of the user who owns the NFTs 101, 102 to which the content data 13A, 13B are associated, a user designated by the user who owns the NTTs 101, 102, and a person who has been preset as a reference authorized person. The reference authorized person may be all users. The non-reference authorized person is a person other than the reference authorized person. The reference authorized person for each NFT may be recorded in the blockchain 11 or in the database 13.

[0050] When an editing authority or a reference authority is recorded in the blockchain 11, the editing authority or the reference authority may be recorded as part of the data constituting the NFTs 101 and 102. When an editing authority or a reference authority is recorded in the database 13, the editing authority or the reference authority may be recorded as part of the data constituting the content data 13A and 13B.

[0051] In the embodiment, the content data 13A, 13B stored in the database 13 can be displayed on the terminals 30, 31, 33, 34 of users who have editing authority or viewing authority. When the editable content data 13A is displayed on the terminals 30, 31, 33, 34, a message indicating that the content data 13A is editable is displayed on the terminals 30, 31, 33, 34. Furthermore, the terminals 30, 31, 33, 34 on which the editable content data 13A is displayed can accept editing operations.

[0052] In the embodiment, a blockchain 11 is used to manage the content data 13A and 13B. The blockchain 11 is configured by a P2P (Peer to Peer) computer network system in which a plurality of computers are interconnected.

[0053] In the blockchain 11, tokens can be traded between blockchain addresses, and token transaction records are recorded in the distributed ledger of the blockchain 11. A blockchain address indicates, for example, a user account in the blockchain 11. For example, if a user has an account in the blockchain 11, the account has a specific blockchain address.

[0054] There are fungible tokens (FT) and non-fungible tokens (NFT) as tokens that can be traded in the blockchain 11. An example of a fungible token is Ether.

[0055] Unlike such fungible tokens, NFTs 101 and 102 are non-fungible tokens. To ensure non-fungibility, NFTs 101 and 102 each have a unique identifier that enables them to be distinguished from other NFTs in the blockchain 11. Hereinafter, this identifier will be referred to as the NFT identifier. The NFT identifier does not need to be the exact identifier recorded in the blockchain 11; it will suffice as long as it is data that can identify the NFT in the system 10. The NFT identifier is sometimes referred to as the "NFT_ID."

[0056] In the following, as an example, the association between the content data 13A and the NFT 101 is realized by associating the content data 13A with the NFT_ID of the NFT 101 and storing it in the database 13. When one piece of content data 13A is associated with only the NFT_ID of one corresponding NFT 101, a one-to-one association between the NFT 101 and the content data 13A is realized. When the NFT 101 itself does not have the content data 13A, the amount of data for the NFT 101 recorded in the blockchain 11 can be reduced. As a result, the cost of using the blockchain 11 can be reduced. Note that the association between the content data 13B and the NFT 102 is also achieved in the same manner as above.

[0057] Note that one piece of content data 13A may be associated with the NFT_IDs of multiple NFTs. In this case, multiple NFTs are issued with the same content data 13A associated with each of the multiple NFTs. However, editing after the NFT issuance can ensure the uniqueness of the content data associated with each NFT. For example, suppose the content data associated with multiple NFTs is the same image of a celebrity. In this case, all of the content data associated with the multiple NFTs is the same image. However, the owner of each NFT can independently edit the image, such as by adding decorations, and update the content data for each NFT, thereby creating uniqueness for each of the multiple content data associated with the multiple NFTs.

[0058] In an embodiment, the blockchain 11 includes a smart contract 130. The smart contract 130 is software (a computer program) that is executable in the blockchain and automatically executes a predetermined protocol. The smart contract 130 has a contract address, which is a blockchain address. The smart contract 130 is stored at the contract address.

[0059] User accounts A1, A2, A3, and A4 are provided for each user in the blockchain 11. The user accounts A1, A2, A3, and A4 have blockchain addresses. In the blockchain 11, NFTs or fungible tokens owned by users are recorded in association with the user accounts.

[0060] When a token is recorded in association with a user account (blockchain address), it can also be said that "the token is stored in the user account (blockchain address)." Also, when a token is stored in an account (blockchain address), it can also be said that "the account (blockchain address) owns the token." Note that a contract address is a type of blockchain address.

[0061] In Fig. 1, an NFT 101 associated with content data 13A is stored in account A1 of user G1. In other words, the owner of NFT 101 shown in Fig. 1 is user G1, who has user account A1. Therefore, the owner of content data 13A associated with NFT 101 is user G1, who has user account A1.

[0062] Similarly, in Figure 1, account A2 of user G2 stores NFT 102 associated with content data 13B. In other words, the owner of NFT 102 shown in Figure 1 is user G2, who has user account A2. Therefore, the owner of content data 13B associated with NFT 102 is user G2, who has user account A2.

[0063] The system 10 according to the embodiment may include a processing server 12 that is outside the blockchain 11. The processing server 12, together with the above-described smart contract 130, may constitute the system 10 according to the embodiment. The processing server 12 is connected to a network 15 such as the Internet. The processing server 12 is operated by, for example, an administrator of the system 10.

[0064] The processing server 12 is configured by a computer including a processor 12A and a memory 12B. The processing server 12 may be configured by one computer or by multiple computers connected via a network 15. The memory 12B is connected to the processor 12A. The memory 12B includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The memory 12B includes a computer program 12C executed by the processor 12A. The processor 12A reads and executes the computer program 12C stored in the memory 12B. The computer program 12C has program code representing instructions to be executed by a computer functioning as the processing server 12. The processing server 12 can execute processes related to editing of the content data 13A.

[0065] User G1 has a user terminal 30. The user terminal 30 is, for example, a mobile device such as a smartphone or a tablet. The user terminal 30 is connectable to the network 15. The user terminal 30 is configured by a computer including a processor 30A and a memory 30B. The memory 30B is connected to the processor 30A. The memory 30B includes, for example, a primary storage device and a secondary storage device. The primary storage device is, for example, RAM. The secondary storage device is, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The memory 30B includes a computer program 30C executed by the processor 30A. The processor 30A reads and executes the computer program 30C stored in the memory 30B. The computer program 30C has program code representing instructions to be executed by the computer functioning as the user terminal 30.

[0066] The computer program 30C is, for example, a wallet application program for displaying on the user terminal 30 tokens stored in the user account A1 of the blockchain 11. The wallet application program provides functions that enable user operations for storing, sending, and receiving tokens.

[0067] The computer program 30C has program code for displaying a token (NFT or fungible token) associated with a user account A1 in the blockchain 11 on the display of the user terminal 30. When displaying the NFT 101, the computer program 30C displays the content data 13A associated with the NFT 101.

[0068] The computer program 30C has program code for accepting an edit request operation, an edit operation, and an edit completion operation for the editable content data 13A from the user.

[0069] The other users G2, T1, and T2 also have user terminals 31, 33, and 34, respectively. The configurations and functions of the user terminals 31, 33, and 34 may be similar to those of the user terminal 30.

[0070] In the embodiment, the users may be general users G1 and G2, and editing users T1 and T2 who edit the content data 13A for the general users G1 and G2. The editing users T1 and T2 may be famous people such as athletes, singers, and actors, and may be subjects of image data that becomes the content data 13A and 13B. The editing users T1 and T2 may also be general users. A general user may also be an editing user.

[0071] The content data 13A and 13B associated with the NFTs 101 and 102 owned by the users are displayed on the user terminals 30, 31, 33, and 34. In other words, the owners of the NFTs 101 and 102 are authorized to view the content data 13A and 13B.

[0072] 2 shows an example of a method for displaying content data 13A associated with an NFT 101 on the terminal 30 of user G1, who is the owner (person authorized to view or edit) of the NTF 101. User G1 signs in to the user's account on the processing server 12 via the terminal 30 (step S201). The sign-in is performed, for example, by an application program installed on the terminal 30. During this sign-in, the processing server 12 can obtain the user's blockchain address (user account in the blockchain) from the user terminal 30.

[0073] The processing server 12, which has the blockchain address of user G1, accesses the blockchain 11 (step S202). The processing server 12 can refer to the records 11B of one or more NFTs for which user G1 is authorized to view or edit in the blockchain 11, and obtain information 120A (e.g., NFT_ID) of one or more NFTs (step S203).

[0074] When the processing server 12 causes an NFT for which user G1 has viewing or editing authority to be displayed on the terminal 30 of user G1, the processing server 12 accesses the database 13 to refer to the content data 13A stored in the database 13. That is, the processing server 12 calls the database 13 to allow user G1 to refer to the content data 13A (step S204).

[0075] The processing server 12 transmits the blockchain address of user G1 to the database 13 to reference the content data 13A associated with the NFT 101 for which user G1 is authorized to view or edit. Upon receiving the blockchain address of user G1, the database 13 accesses the blockchain 11 to reference the NFT for which user G1 is authorized to view or edit, as indicated by the blockchain address (step S205). Through this access, the database 13 acquires the NFT_ID of the NFT for which user G1 is authorized to view or edit (step S206).

[0076] When the database 13 receives a call using the blockchain address of user G1, it responds to the call by permitting access to content data 13A associated with the NFT 101 for which user G1 is authorized to view or edit. That is, the database 13 references the NFT_ID of the NFT for which user G1 is authorized to view or edit in the blockchain 11 (step S205), and permits access to content data 13A associated with the NFT_ID of the NFT 101 for which user G1 is authorized to view or edit, from among the content data stored in the database 13.

[0077] Through the above process, the processing server 12 can refer to the content data 13A associated with the NFT 101 for which the user G1 is authorized to view or edit. This content data 13A is transmitted to the user terminal 30 for display on the user terminal 30, and is displayed on the display of the user terminal 30 (step S207).

[0078] The association between the NFT 101 and the content data 13A may be realized, for example, by the NFT 101 having a uniform resource identifier (URI) that indicates the content data 13A.

[0079] 3 shows the NFT management process executed by the system 10. The NFT management process may be executed by the processing server 12, by the smart contract 130, or by the processing server 12 and the smart contract 130 in cooperation with each other. In the NFT management process, the database 13 is used as needed, and the database 13 executes processing for access control.

[0080] First, an issuance process for an NFT 101 with editing rights is performed (step S301). In the issuance process for an NFT 101, whether the NFT has editing rights or does not have editing rights may be determined randomly or based on predetermined rules. By reducing the number of NFTs 101 with editing rights that are issued, the scarcity of the NFTs 101 with editing rights increases, and their value increases. The issuance process in step S301 may be executed by, for example, the smart contract 130.

[0081] The issuance process is executed, for example, by receiving an issuance request. The issuance request is sent, for example, based on a user operation on the user terminal 30, 31, 33, or 34. The user operation for the issuance request is, for example, an operation to purchase the NFT 101 or an operation to exchange another NFT for the NFT 101. Receiving an issuance request may be receiving a fungible token sent from a user, or may be receiving another NFT sent from a user.

[0082] In the issuance process of step S301, the NFT 101 is associated with the content data 13A. Furthermore, in the issuance process, if the NFT to be issued has editing rights, editing rights are set. When setting editing rights, for example, an editing authority holder is set. The editing authority holder is, for example, the user who owns the NFT 101 to which the content data 13A is associated, or another person set as the editing authority holder. The person set as the editing authority holder is, for example, a person who is the subject of the image data that is the content data 13A. The editing authority holder is, for example, recorded in the blockchain 11 in association with the NFT 101. The editing authority holder is indicated, for example, by a blockchain address.

[0083] The editing authority does not need to be set as a specific person in advance, but may be a person designated by a designated authority (editing authority) such as the owner of the NFT 101. The system 10 only needs to be set to treat the person designated by the designated authority as the editing authority.

[0084] In setting the editing authority, the number of edits allowed may be set for each NFT 101. The number of edits allowed may be, for example, one or more times. By setting the number of edits allowed, the number of edits allowed by a user can be limited. Furthermore, when the number of edits allowed by a user reaches the number of edits allowed, further edits cannot be made, and the content of the content data 13A can be finalized. The number of edits may be, for example, the number of times the edit mode has been switched to.

[0085] The issued NFT 101 with edit rights is sent to the user (step S302). The user to whom the NFT 101 is sent is, for example, the user who sent the issuance request. The user who receives the NFT 101 with edit rights is recorded in the blockchain 11 as the owner of the NFT 101 with edit rights. The NFT 101 with edit rights can be traded, such as exchanged or bought and sold, on the blockchain 11, and the owner may change. The change in owner is recorded in the blockchain 11. The sending process in step S302 may be executed by the smart contract 130.

[0086] Thereafter, the system 10 receives an editing request from the user terminal 30 that owns the editing-right-attached NFT 101 (step S303). Receipt of the editing request and subsequent processing can be performed by the processing server 12.

[0087] The system 10 determines whether the user is an authorized editor (step S304). If the user who sent the edit request is not an authorized editor, the system 10 rejects the edit request. If the user who sent the edit request is an authorized editor, the system 10 accepts the edit request and switches the content data 13A associated with the NFT 101 to edit mode (step S305). The system 10 accepts the editing operation of the authorized editor (step S306). That is, the system 10 receives editing data indicating the editing operation performed on the terminal 30 of the authorized editor. The editing operation is, for example, an operation of writing handwritten characters. The editing operation may also be audio recording and / or video recording.

[0088] When the system 10 receives an editing completion notification from the user's terminal 30 (step S307), it reflects the edited content resulting from the editing operation in the content data 13A stored in the database 13, overwrites and saves it, and updates the content data 13A (step S308). Then, the system 10 switches the content data 13A to the non-editable mode (step S309). If the NFT 101 can only be edited once, switching to the non-editable mode makes it impossible to re-edit, and the content of the content data 13A is finalized. This finalization is also called finalization. Note that if the NFT 101 can only be edited twice or more, it can be re-edited until the maximum number of edits is reached.

[0089] Figure 4 shows a first example of an NFT editing scenario using the NFT management process shown in Figure 3. In this first example, the person with editing rights is the owner of the NFT 101. In this first example, a general user G1 who owns the NFT 101 with editing rights edits the content data 13A associated with the NFT 101.

[0090] General user G1, who owns NFT 101 with editing rights, operates terminal 30 to switch from non-editable mode to edit mode in order to edit content data 13A (step S403). The mode switching operation is transmitted as an editing request from terminal 30 to system 10. This makes content data 13A editable. Note that content data 13A is displayed on the display of terminal 30 of user G1, who has editing rights.

[0091] User G1 edits the content data 13A displayed on the display of terminal 30 by operating the display of terminal 30 with a finger or a touch pen (step S406). The editing is, for example, decoration such as drawing a graphic 13E on the content data 13A. Editing data (data of graphic 13E) indicating the editing content by user G1 is transmitted to system 10.

[0092] When the user G1 completes the editing, the user G1 performs an editing completion operation on the terminal 30 (step S407). The terminal 30 transmits an editing completion notification to the system 10. As a result, the content data 13A is updated according to the edited data, and returns to the edit-disabled mode.

[0093] Through the above operations, the user G1 can obtain the content data 13A that he or she has edited.

[0094] FIG. 5 shows a second example of an NFT editing scenario using the NFT management process shown in FIG. 3. In the second example, the person with editing rights is also the owner of the NFT 101. In the second example, a general user G1 who owns the NFT 101 with editing rights sends the NFT 101 to an editing user T1, who then receives the NFT 101 and edits the content data 13A associated with the NFT 101. Note that the editing user T1 is, for example, a celebrity who is the subject of an image that is the content data 13A. The editing here involves, for example, an editor writing handwritten characters such as an autograph.

[0095] The editing user to whom the NFT 101 is to be sent is preferably set in advance in the system 10 for each NFT. The editing user to whom the NFT 101 is to be sent may be recorded in the blockchain 11 in association with the NFT 101, or may be recorded in the database 13.

[0096] A general user G1 who wants editing user T1 to edit the NFT 101 he or she owns sends the NFT 101 to editing user T1 (step S501). As a result, editing user T1 temporarily becomes the owner of the NFT 101. To ensure that the NFT 101 is returned to general user G1, it is preferable that the NFT 101 be set to be automatically returned to the original general user G1 after a predetermined period of time has passed.

[0097] When sending the NFT 101, the general user G1 may also send to the editing user T1 data (message, destination, etc.) indicating the content that the editing user T1 wants to edit. The editing user T1 can view the content of the data and edit the content according to the general user G1's wishes.

[0098] By becoming the owner of the NFT 101, the editing user T1 becomes an authorized person and can edit the content data 13A. When the NFT 101 is sent to the editing user T1, the content data 13A is switched from non-editable mode to edit mode. The content data 13A is displayed on the display of the terminal 33 of the editing user T1, who is authorized to edit.

[0099] The editing user T1 edits the content data 13A displayed on the display of the terminal 33 by operating the display of the terminal 33 with a finger or a touch pen (step S502). The editing may be, for example, writing handwritten characters such as an autograph on the content data 13A. The editing may also be recording a voice or video of the editing user T1 uttering a message. The message may be content desired by the general user G1. Editing data indicating the content edited by the user T1 is transmitted to the system 10.

[0100] When user T1 completes the editing, he / she performs an editing completion operation on terminal 33. Terminal 33 transmits an editing completion notification to system 10. As a result, content data 13A is updated according to the edited data and returns to the non-editable mode. In addition, NFT 101 is returned to general user G1 (step S503).

[0101] Through the above operations, the user G1 can obtain the content data 13A edited by the editing user T1 (for example, an image with the celebrity's autograph or an image with the celebrity's voice).

[0102] FIG. 6 shows a third example of an NFT editing scenario using the NFT management process shown in FIG. 3. In this third example, the person authorized to edit is the editing user T1, who is preset in the NFT 101. In this third example, a general user G1 who owns the NFT 101 with editing rights can have the content data 13A associated with the NFT 101 edited while still in possession of the NFT 101. The editing user T1, who is authorized to edit, may be a person designated by the general user G1. Note that the editing user T1 is, for example, a celebrity who is the subject of an image that is the content data 13A. The editing here refers to, for example, an editor writing handwritten characters such as an autograph.

[0103] In order to edit the NFT 101 owned by the general user G1, the editing user T1 operates the terminal 33 to switch from non-editable mode to edit mode (step S603). The mode switching operation is transmitted as an editing request from the terminal 33 to the system 10. This makes the content data 13A editable. The content data 13A is displayed on the display of the terminal 33 of the editing user T1, who has editing authority.

[0104] In addition, data (message, destination, etc.) indicating the content that general user G1 wants editing user T1 to edit may be sent from general user G1 to editing user T1 in advance. Editing user T1 can view the content of the data and edit the content according to the general user G1's wishes.

[0105] The editing user T1 edits the content data 13A displayed on the display of the terminal 33 by operating the display of the terminal 33 with a finger or a touch pen (step S606). The editing may be, for example, writing handwritten characters such as an autograph on the content data 13A. The editing may also be recording a voice or video of the editing user T1 uttering a message. The message may be content desired by the general user G1. Editing data indicating the content edited by the editing user T1 is transmitted to the system 10.

[0106] When the editing user T1 completes the editing, the editing user T1 performs an editing completion operation on the terminal 33 (step S607). The terminal 33 transmits an editing completion notification to the system 10. As a result, the content data 13A is updated according to the edited data, and returns to the non-editable mode.

[0107] Through the above operations, the general user G1 can obtain the content data 13A edited by the editing user T1 (for example, an image with the celebrity's autograph or an image with the celebrity's voice).

[0108] 7 shows another example of the NFT management process executed by the system 10. In the example of FIG. 7, points that are not particularly described are the same as the example of FIG.

[0109] In the example of Figure 7, the process of issuing an NFT 101 with editing rights is also performed (step S701), and the issued NFT 101 with editing rights is sent to the user (step S702).

[0110] In the example of FIG. 7, the system 10 receives an editing request from the terminal 30 of a general user who owns the NFT 101 with editing rights (step S703). When the system 10 receives an editing request from the general user who owns the NFT 101 with editing rights, it transmits the editing request to an authorized person (editing user) preset for the NFT 101 (step S704). The system 10 then switches the content data 13A associated with the NFT 101 to edit mode (step S705). The system 10 accepts editing operations by the editing user who has editing rights (step S706). That is, the system 10 receives editing data indicating the edited content made on the terminal 33 of the user who has editing rights.

[0111] When the system 10 receives an edit completion notification from the user terminal 33 (step S707), it updates the content data 13A stored in the database 13 by reflecting the edited content resulting from the edit operation in the content data 13A (step S708), and then switches the content data 13A to an edit-disabled mode (step S709).

[0112] FIG. 8 shows a fourth example of an NFT editing scenario using the NFT management process shown in FIG. 7. In the fourth example, the person authorized to edit is the editing user T1, who is preset in the NFT 101. In the fourth example, a general user G1 who owns the NFT 101 with editing rights can have the content data 13A associated with the NFT 101 edited while still in possession of the NFT 101. The editing user T1, who is authorized to edit, may be a person designated by the general user G1. Note that the editing user T1 is, for example, a celebrity who is the subject of an image that is the content data 13A. The editing here refers to, for example, an editor writing handwritten characters such as an autograph.

[0113] In order to edit the NFT 101 that the general user G1 owns, the general user G1 operates the terminal 30 and sends an editing request to the system 10 (step S703). This editing request may include an identifier indicating the content data 13A to be edited. The identifier may be data directly indicating the content data 13A to be edited, or may be an NFT identifier (NFT_ID) indicating the NFT 101 associated with the content data 13A. The editing request may also include information indicating a person designated by the general user G1 as an authorized person for editing. The editing request may also include data (e.g., a message, a destination) indicating the content that the general user G1 wants the authorized person, editing user T1, to edit. This data is sent to the editing user T1 together with the editing request. The editing user T1 can view the content of the data and edit the content according to the general user G1's wishes.

[0114] The system 10 transmits a request to edit the NFT 101 to the editing user T1, who has the editing authority for the NFT 101 (step S704). The content data 13A associated with the NFT 101 is switched to edit mode. The content data 13A is displayed on the display of the terminal 33 of the editing user T1, who has the editing authority.

[0115] The editing user T1 edits the content data 13A displayed on the display of the terminal 33 by operating the display of the terminal 33 with a finger or a touch pen (step S706). The editing may be, for example, writing handwritten characters such as an autograph on the content data 13A. The editing may also be recording a voice or video of the editing user T1 uttering a message. The message may be content desired by the general user G1. Editing data indicating the content edited by the editing user T1 is transmitted to the system 10.

[0116] When editing user T1 completes the editing, he performs an editing completion operation on terminal 33 (step S707). Terminal 33 transmits an editing completion notification to system 10. As a result, content data 13A is updated according to the edited data and returns to the non-editable mode. The updated content data 13A is displayed on general user terminal 30 (step S708).

[0117] On the terminal 33 of the editing user T1, an operation to select the content data 13A to be edited may be performed by the editing user T1. Even if there is a plurality of content data to be edited by the editing user, the content data 13A to which the editing contents will be reflected is specified by performing an operation to select the content data 13A to be edited. The operation to select the content data 13A to be edited is performed, for example, by displaying on the terminal 33 a list of one or more content data (or NFTs associated with the content data) that can be edited by the editing user T1, and the editing user T1 selecting the content data to be edited from the list. The edited data may be transmitted to the system 10 together with an identifier indicating the selected edited content. The system 10 may update the content data indicated by the identifier according to the edited data.

[0118] Through the above operations, the general user G1 can obtain the content data 13A edited by the editing user T1 (for example, an image with the celebrity's autograph or an image with the celebrity's voice).

[0119] 9 shows another example of the NFT management process executed by the system 10. In the example of FIG. 9, points that are not particularly described are the same as the example of FIG. 3 or FIG.

[0120] In the example of Figure 9, it is assumed that the NFT 101 with editing rights is already owned by a general user. In the example of Figure 9, an editing user T1 is set in advance as the person with editing authority. The editing user T1, who is the person with editing authority, may be designated by the general user who is the owner of the NFT 101 with editing rights.

[0121] The system 10 sends an editing request to editing user T1, who is the person authorized to edit the NFT 101 (step S904). The system 10 is configured to send an editing request to editing user T1, who has been set as the person authorized to edit the NFT 101. The editing request sent by the system 10 to editing user T1 may be based on an editing request from the owner of the NFT 101, or it may not be based on an editing request from the owner of the NFT 101. If the editing request is not based on an editing request from the owner of the NFT 101, the system 10 can, for example, reference data indicating editing user T1 as the person authorized to edit the NFT 101 in advance, and send the editing request to editing user T1 based on that data.

[0122] The editing request sent from the system 10 is received at the terminal 33 of the editing user T1. The editing user T1 may receive multiple editing requests for multiple NFTs 101.

[0123] The editing user T1 performs editing operations on the terminal 33 at any timing or by a deadline specified by the system 10. The system 10 accepts editing operations from the editing user who has editing authority. That is, the system 10 receives editing data indicating the editing content performed on the terminal 33 of the editing user who has editing authority (step S906). The system 10 may receive the editing data all at once after all editing operations are completed, or may receive the editing data that is updated sequentially during the editing operations.

[0124] On the terminal 33 of the editing user T1, an operation to select the content data 13A to be edited may be performed by the editing user T1. Even if there are multiple pieces of content data to be edited by the editing user, the operation to select the content data 13A to be edited identifies the content data 13A to which the editing contents will be reflected. The operation to select the content data 13A to be edited is performed, for example, by displaying on the terminal 33 a list of one or more content data (or NFTs associated with the content data) that can be edited by the editing user T1, and the editing user selecting the content data to be edited from the list. The edited data may be transmitted to the system 10 together with an identifier indicating the selected edited data. The system 10 receives the transmitted identifier (step S906) and may update the content data 13A indicated by the received identifier according to the edited data (step S908).

[0125] FIG. 10 shows a fifth example of an NFT editing scenario using the NFT management process shown in FIG. 9. In the fifth example, the person authorized to edit is editing user T1. In the fifth example, a general user G1 who owns an NFT 101 with editing rights can have the content data 13A associated with the NFT 101 edited while still in possession of the NFT 101. Note that editing user T1 is, for example, a celebrity who is the subject of an image that is content data 13A. The editing here is, for example, an editor writing handwritten characters such as an autograph.

[0126] First, the system 10 transmits a request to edit the NFT 101 to the editing user T1, who has the editing authority for the NFT 101 (step S904). The editing request includes the identifier (NFT_ID) of the NFT 101 as an identifier indicating the content data 13A to be edited. The content data 13A does not need to be displayed on the display of the terminal 33 of the editing user T1, who has the editing authority, but may be displayed.

[0127] The editing user T1 performs editing operations by operating the editing area 33A on the display of the terminal 33 with a finger or a touch pen. By performing the editing operations, editing data for updating the content data 13A is generated. Editing may involve, for example, writing handwritten characters such as an autograph on the terminal 33. Editing may also involve recording the voice or video of the editing user T1 uttering a message. The message may be content desired by the general user G1. Editing data indicating the content edited by the editing user T1 is transmitted to the system 10.

[0128] Before starting editing or after completing editing, editing user T1 performs an operation to select an NFT 101 whose content data 13A will be updated with the editing data. The operation to select an NFT 101 is performed, for example, by selecting selection button 33B displayed on the display of terminal 33 to display a list of NFTs that editing user T1 can edit, and editing user T1 selects the NFT 101 to be edited from the list.

[0129] The edited data is sent to the system 10 together with the identifier of the NFT indicating the selected edit target. The system 10 updates the content data 13 of the NFT 101 indicated by the identifier according to the edited data. The updated content data 13A is displayed on the general user's terminal 30 (step S908).

[0130] Through the above operations, the general user G1 can obtain the content data 13A edited by the editing user T1 (for example, an image with the celebrity's autograph or an image with the celebrity's voice).

[0131] 11 shows a content printing system 100 for printing content data 13A and 13B on a print medium such as paper. This content printing system 100 includes an issuing device 200 and an issuing server 300. The content printing system 100 uses the system 10 shown in FIG. 1 to provide a content printing service, and is used to issue content 1, which is a printed matter.

[0132] When a system 10 using a blockchain 11 accepts a print operation from a user on a terminal 30, it transmits content data 13A, 13B designated as the print target in the print operation to an issuing server 300. The issuing server 300 is an external computer that executes processing for printing the content data. The issuing server 300 transmits the content data 13A, 13B to an issuing device 200 operated by the user. The issuing device 200 prints the received content data 13A, 13B to issue content 1, which is a printed matter.

[0133] By using the content print service, the user can print, for example, the edited content data 13A.

[0134] The printed content 1 is configured by printing content data 13A and 13B on a printing sheet for the content, for example.

[0135] By using this content print service, the user can not only own the content data 13A, which is digital data, but also the printed content 1.

[0136] The issuing device 200 is installed, for example, inside a retail store. The issuing device 200 is configured to print content data 13A, 13B on printing paper and issue the printed content 1. The issuing device 200 is, for example, a multifunction peripheral installed inside a store that provides content printing services, etc. The multifunction peripheral is used to provide not only the content printing service but also other printing services, copying services, and facsimile services. The multifunction peripheral can generally be operated directly by customers visiting the store, but may also be operated by store staff.

[0137] When the issuing device 200 receives an operation from an operator such as a customer (user), it acquires the necessary content data from the issuing server 300 and prints the content data to issue the content 1. The issuing device 200 is configured to receive input of a code indicating the content data to be printed. The code may be machine-readable or may be letters or numbers that are easily readable by humans. The code is input, for example, by key operation or by reading the code with a reader included in the multifunction device.

[0138] The issuing device 200 is configured to execute a payment process to accept a payment operation for the printing fee of the content 1 and settle the payment prior to issuing the content 1. The content 1 is issued after the payment process is completed. A person (user) who wishes to print the content 1 can pay the printing fee of the content 1 at a store such as a convenience store.

[0139] The issuing server 300 is connected to the issuing device 200 and the system 10 via a network 15. The issuing server 300 is connected to, for example, the processing server 12 or the database 13 of the system 10. The issuing server 300 is an external device installed in a location separate from the issuing device 200 so that multiple issuing devices 200 can be connected to the issuing server 300. The issuing server 300 is configured to obtain content data 13A and 13B for content 1 issued by the issuing device 200 from the system 10, and transmit the content data 13A and 13B to the issuing device 200 in response to a request from the issuing device 200.

[0140] The issuing server 300 is configured by a computer having a processor and a memory. The issuing server 300 has a computer program. The computer program has program code for causing a computer to function as the issuing server 300.

[0141] A user who wants to print content data 13A, 13B visits a store such as a convenience store and has content 1 issued. To issue content 1, the user performs a print operation on terminal 30 and obtains a code for printing. The code is generated by system 10, which accepts the user's print operation. System 10 transmits the code and content data 13A to be printed to issuing server 300. Issuing server 300 stores the received content data 13A in association with the code.

[0142] The user inputs the code obtained by the printing operation into the issuing device 200. The input may be manual input by the user, or the code may be read by a reading device included in the issuing device 200. The issuing device 200 transmits the input code to the issuing server 300. Upon receiving the code, the issuing server 300 transmits content data 13A corresponding to the code to the issuing device 200. The issuing device 200 acquires the content data 13A. The issuing device 200 prints the content data 13A on printing paper and publishes the content 1.

[0143] It is preferable that payment for the printing fee be processed before the content data 13A is printed.

[0144] <3. Notes>

[0145] The present invention is not limited to the above-described embodiment, and various modifications are possible. [Explanation of symbols]

[0146] 1: Content 10: Computer Systems 11: Blockchain 11B: Record 12: Processing server 12A: Processor 12B: Memory 12C: Computer Programs 13: Database 13A: First content data 13B: Second content data 13E: Shapes 15: Network 30: User terminal 30A: Processor 30B: Memory 30C: Computer Programs 31: User terminal 33: User terminal 34: User terminal 100: Content Print System 120A: Information 130: Smart Contract 200: Issuing device 300: Issuing Server A1: User Account A2: User Account A3: User Account A4: User Account G1: General users G2: General users T1:Editor user T2:Editor user

Claims

1. 1. A computer-implemented method for a non-fungible token recorded on a blockchain, comprising: updating content data that has been non-fungible tokenized in association with the non-fungible token after the content data has been non-fungible tokenized; Prepare for this. The way computers run.

2. When displaying the non-fungible token after updating, the updated content data is displayed as data associated with the non-fungible token. The method of claim 1.

3. The content data is stored in a database outside the blockchain; Updating the content data after the content data has been converted into non-fungible tokens means updating the content data stored in the database. The method according to claim 1 or claim 2.

4. A computer system for a non-fungible token recorded on a blockchain, comprising: updating content data that has been non-fungible tokenized in association with the non-fungible token after the content data has been non-fungible tokenized; A computer system comprising:

Images