Information processing method, program, information processing system, and smart contract

The smart contract system addresses the permanence and management challenges of NFT metadata by recording metadata on a blockchain, ensuring permanent use and efficient rights management with automatic switching based on conditions.

JP7590047B1Active Publication Date: 2024-11-26FOLIO CORPORATION
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2024107586
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2024-07-03
Publication Date
2024-11-26
Estimated Expiration
2044-07-03

AI Technical Summary

Technical Problem

Existing methods for managing metadata associated with NFTs are not permanent and require additional efforts and costs due to the risk of tampering and the need for off-chain processing systems, making it difficult to manage rights and edit or delete metadata as needed.

Method used

A smart contract system that issues NFTs and records metadata on a blockchain network, allowing for permanent use and easy management of metadata rights by retaining reference destination information, with the ability to switch metadata references based on predetermined conditions.

Benefits of technology

Enables permanent use of metadata managed by NFTs while reducing costs and efforts by eliminating the need for off-chain processing, allowing for efficient and automatic switching of metadata references based on predefined conditions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007590047000001_ABST
    Figure 0007590047000001_ABST
Patent Text Reader

Abstract

The present invention provides an information processing method, program, information processing system, and smart contract that enable the permanent use of content managed by NFT while easily managing the rights to the content. [Solution] The information processing method includes an issuance step in which smart contracts 310, 320 issue an NFT, and a recording step in which the smart contracts 310, 320 record multiple metadata that can be exclusively referenced by the issued NFT and their reference information in the blockchain network 300 in which the smart contract 310 is recorded, and the smart contract 310 holds the reference information for each of the multiple metadata.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to an information processing method, a program, an information processing system, and a smart contract. [Background technology]

[0002] Conventionally, technology has been known to link digital content with NFTs (Non-Fungible Tokens) and manage them. Digital content refers to images, music, videos, files, etc. that are electromagnetically recorded on a network. For example, artistic images managed with NFTs are called NFT art. Hereinafter, content managed with NFTs will be referred to as NFT content. In addition, technology has been known to manage the copyrights of such digital content using blockchain smart contracts.

[0003] For example, Patent Document 1 describes a content contract system that uses a blockchain to distribute rights to content data, in which a rights holder terminal, a transferee terminal, and a blockchain control terminal contain transactions in which a smart contract program for distributing rights is set, and a blockchain that is synchronized between the rights holder terminal, the transferee terminal, and the blockchain control terminal is stored, and the blockchain control terminal contains matching information for the content data and the type of rights to be distributed, and the address of the rights holder is set as owner information, and the content contract system is equipped with a token issuing unit that generates token data identified by a token identifier and registers the token data corresponding to the token identifier in the blockchain. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-068388 A Summary of the Invention [Problem to be solved by the invention]

[0005] The electronic records that constitute the NFT content consist of a smart contract on the blockchain and metadata (content information such as images and text information such as attributes) that is not normally stored on the blockchain.

[0006] When managing metadata using NFTs, the following two methods are currently the most common for storing metadata: (a) The smart contract will be stored and published in a blockchain or blockchain-like processing system such as IPFS (Inter Planetary File System) that is intended for storing relatively large amounts of data and is separate from the blockchain in which the smart contract is stored. (b) Store and publish the data in existing Web 2.0 processing systems, such as cloud service storage.

[0007] Here, NFT content is touted as being "storable once and available forever." Indeed, smart contracts stored on the blockchain and their storage space have this characteristic.

[0008] FIG. 11 is a diagram showing the relationship between a conventional NFT and metadata. Specifically, it shows the relationship between an NFT and metadata in the above case (b). As shown in FIG. 11, only the NFT contract, which is a smart contract that manages the NFT, and the NFT (not shown) are recorded in the blockchain.

[0009] As described above, the metadata and metadata processing system stored in the above (b) method are not permanent because there is a risk of tampering, and since it is a different mechanism from smart contracts that can be used permanently on-chain, and a different processing system must be used in combination off-chain, additional effort and cost are required to change data on the off-chain. In other words, there is an issue that metadata is not "permanently available once it is saved."

[0010] In addition, metadata that includes copyrights or portrait rights must be deleted when the usage period for those rights expires. However, in the above method (a), deletion or editing is not possible in the first place, and in the above method (b), double operations are required for both the smart contract processing system and the metadata processing system.

[0011] On the other hand, it is possible to record metadata for NFTs on the blockchain, which is called a full on-chain NFT. In this case, as with method (a) above, there is an issue that the metadata cannot be deleted or edited, making it difficult to manage rights.

[0012] Therefore, the present disclosure aims to provide an information processing method, program, information processing system, and smart contract that enable the permanent use of metadata managed by NFTs while easily managing the rights to the metadata. [Means for solving the problem]

[0013] The information processing method disclosed herein includes an issuance step in which a smart contract issues an NFT, and a recording step in which the smart contract records multiple metadata that can be exclusively referenced by the issued NFT and their reference information in a blockchain network in which the smart contract is recorded, and the smart contract holds the reference information for each of the multiple metadata.

[0014] The program of the present disclosure is a program recorded in a blockchain network, which causes a computer to execute an issuance step of issuing an NFT and a recording step of recording in the blockchain network multiple metadata that can be exclusively referenced by the issued NFT and their reference information, and retains the reference information for each of the multiple metadata.

[0015] The information processing system of the present disclosure comprises an issuing unit that issues NFTs, and a recording unit that records multiple metadata that can be exclusively referenced by the issued NFTs and their reference information in a blockchain network using a smart contract, and the smart contract holds the reference information for each of the multiple metadata.

[0016] The smart contract of the present disclosure is a smart contract recorded on a blockchain network, which causes a computer to execute an issuance step of issuing an NFT and a recording step of recording on the blockchain network multiple metadata that can be exclusively referenced by the issued NFT and their reference information, and retains each of the reference information of the multiple metadata. Effect of the Invention

[0017] According to the present disclosure, it is possible to provide an information processing method, program, information processing system, and smart contract that enable the permanent use of content managed by NFT while easily managing the rights to the content. [Brief description of the drawings]

[0018] [Figure 1] 1 is a diagram illustrating a configuration of an information processing system according to an embodiment of the present disclosure. [Diagram 2] A block diagram showing the functional configuration of an NFT management server according to an embodiment of the present disclosure. [Diagram 3] FIG. 2 is a block diagram showing a functional configuration of a user terminal according to an embodiment of the present disclosure. [Figure 4] A block diagram showing the functional configuration of an NFT contract according to an embodiment of the present disclosure. [Diagram 5] FIG. 2 is a block diagram showing a functional configuration of a metadata contract according to an embodiment of the present disclosure. [Figure 6] 11 is a sequence diagram showing an operation of a deployment process in an information processing system according to an embodiment of the present disclosure. FIG. [Figure 7] 11 is a sequence diagram showing an operation of an issuing process in an information processing system according to an embodiment of the present disclosure. FIG. [Figure 8] 11 is a sequence diagram showing an operation of a usage management process in an information processing system according to an embodiment of the present disclosure. FIG. [Figure 9] FIG. 9 is a block diagram showing the basic hardware configuration of a computer 900. [Figure 10] A diagram showing the relationship between NFTs and metadata in an information processing system according to an embodiment of the present disclosure. [Figure 11] A diagram showing the relationship between conventional NFTs and metadata. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] The embodiments of the present disclosure will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0020] <Configuration of Information Processing System 1> 1 is a diagram showing the configuration of an information processing system 1 according to this embodiment. The information processing system 1 is a system for providing an NFT management service for managing and using NFT metadata on-chain. In this embodiment, using metadata of an NFT means, for example, referring to and viewing the metadata associated with the NFT as information that identifies the NFT itself.

[0021] The information processing system 1 includes an NFT management server 100 (information processing device), a user terminal 200, and a blockchain network 300 (hereinafter simply referred to as blockchain 300). The blockchain 300 has an NFT contract 310 and a metadata contract 320, which are smart contracts. The NFT management server 100, the user terminal 200, and the blockchain 300 are connected to a network 5 and can communicate with each other via the network 5. The network 5 includes the Internet. The network 5 may include a LAN (Local Area Network) and / or a WAN (Wide Area Network).

[0022] The NFT management server 100, the user terminal 200, and the blockchain 300 each consist of one or more computers. The basic configuration of a computer will be described later.

[0023] The user makes the NFT management service available in advance on the user terminal 200 used by the user. In the following explanation, it is assumed that the user has installed an NFT management app (which may be an extension of a web browser) provided by the NFT management service on the user terminal 200.

[0024] 2 is a block diagram showing the functional configuration of the NFT management server 100 according to this embodiment. The NFT management server 100 is a server device that provides an NFT management service to users. The NFT management server 100 is a server that stands between the user terminal 200 and the smart contracts 310 and 320 and mediates the issuance of NFTs for predetermined digital content and the use of browsing, etc. The NFT management server 100 is, for example, a server device that provides front-end and back-end functions for decentralized applications (hereinafter, DApps: Decentralized Applications) that run on the blockchain 300. The NFT management server 100 may be a server that constitutes a marketplace for non-fungible tokens. The NFT management server 100 includes a communication unit 110, a memory unit 120, and a processing unit 130.

[0025] The memory unit 120 includes an application program 121, a database 122, and a contract address 123 of a smart contract.

[0026] The application program 121 is executed by the processing unit 130 and is a program for mainly implementing each functional unit of the processing unit 130.

[0027] The database 122 stores information about users (user IDs, etc.) who use the NFT management service, as well as information about NFTs and metadata managed by the NFT management service.

[0028] The smart contract address 123 stores the contract address of the smart contract used in the deployment process, issuance process, and usage management process described later. Specifically, the contract address (310) of the NFT contract 310 and the contract address (320) of the metadata contract 320 are stored.

[0029] The processing unit 130 includes, as functional units, a user management unit 131, a deployment unit 132, an issuance unit 133, and a usage management unit 134. The processing unit 130 realizes each functional unit by executing an application program 121 stored in the storage unit 120. The processing unit 130 also executes a part of the deployment process, issuance process, and usage management process executed by the information processing system 1. The deployment process, issuance process, and usage management process will be described in detail later.

[0030] The user management unit 131 executes a user management process to manage users of the NFT management service. Specifically, the user management unit 131 performs service registration processing for a new user and issues a user ID. In addition, the user management unit 131 performs login authentication for a user who has already registered to the NFT management service using the user ID.

[0031] The deployment unit 132 executes a deployment process to deploy a smart contract on the blockchain 300. Specifically, before providing an NFT management service to a user, the deployment unit 132 deploys, on the blockchain 300, an NFT contract 310, which is a smart contract that manages the NFT, and a metadata contract 320, which is a smart contract that manages the NFT metadata referenced by the NFT.

[0032] The issuing unit 133 executes an issuing process to issue an NFT using a smart contract and record the metadata of the NFT in the blockchain 300. Specifically, the issuing unit 133 records an NFT in the blockchain 300 using an NFT contract 310 based on a user request, and records NFT metadata in the blockchain 300 using a metadata contract 320. In this embodiment, the NFT is issued in compliance with ERC721, an Ethereum standard that can implement smart contracts, or a standard equivalent to the same. In addition, the issuing unit 133 records in the blockchain 300 using a signature with the private key of the crypto asset wallet (hereinafter simply referred to as the wallet) connected to the NFT management app.

[0033] The usage management unit 134 executes a usage management process that allows a user to use the metadata of an NFT based on a user request.

[0034] The processing unit 130 also performs processes such as managing the connection between the user's wallet and the NFT management app.

[0035] FIG. 3 is a diagram showing a functional block configuration of the user terminal 200 according to this embodiment.

[0036] The user terminal 200 is a terminal used by a user who uses the NFT management service, and is configured by any computer such as a smartphone, a tablet terminal, a personal computer, etc. The user terminal 200 includes a communication unit 210, an input unit 220, an output unit 230, a storage unit 240, and a control unit 250, which are interconnected via a communication bus 260.

[0037] The input unit 220 includes an input device that accepts operational input from a user. The output unit 230 includes at least a display as an output device.

[0038] The storage unit 240 includes an application program 241 and a user ID 242, both of which are not shown.

[0039] The application program 241 may be pre-stored in the storage unit 240, or may be configured to be downloaded from a web server operated by a service provider via the communication unit 210. The application program 241 includes various application forms such as an extension function of a web browser and a mobile app. The application program 241 includes an NFT management app for using the NFT management service.

[0040] The user ID 242 is a user identifier that uniquely identifies a user. The user ID 242 is information required for authentication, such as a so-called user identifier (user ID) and password, used when logging in to the NFT management service.

[0041] The control unit 250 executes various functions by executing the application programs 241 in the storage unit 240 .

[0042] Returning now to FIG. 1, the blockchain 300 of this embodiment is a network of multiple computers connected by peer-to-peer. There are three types of blockchain 300: a public chain without a specific administrator, a private chain managed by a single organization, and a consortium chain managed by multiple organizations. Although the blockchain 300 of this embodiment mainly targets public chains, the blockchain 300 may be either a private chain or a consortium chain. In a typical example, the blockchain 300 may be a Bitcoin network, an Ethereum network, a Polygon network, etc., which are classified as public chains, or a Hyperledger Fabric, Quorum, LINE blockchain, etc., which are classified as private chains.

[0043] Users of the blockchain 300 use the blockchain 300 via accounts on the blockchain 300 called externally owned accounts (EOA: End of Account). The blockchain 300 is also configured to be able to record various smart contracts (programs). Externally owned accounts are identified by the "wallet address" of a wallet owned by the user, and smart contracts are identified by the "contract address."

[0044] The blockchain 300 is configured to be able to record various transactions in the blockchain (specifically, a ledger). Such a ledger is a ledger held by each computer connected in a peer-to-peer manner, and is also called a distributed ledger. The various transactions include an issue transaction for newly issuing an account, a smart contract, or a token, a transfer transaction for transferring ownership of a token, and the like.

[0045] FIG. 4 is a diagram showing a functional block configuration of the NFT contract 310 according to this embodiment.

[0046] The NFT contract 310 includes an input / output unit 311, an issuing unit 312, a reference unit 313, a management unit 314, NFT information 315, and a smart contract address 316. The NFT contract 310 executes part of the deployment process, issuance process, and usage management process executed by the information processing system 1.

[0047] The input / output unit 311 accepts an issuance request or a usage request for issuing or using an NFT from the externally owned account, and returns the result of executing the process according to the request to the externally owned account. For example, the input / output unit 311 accepts a request to issue a new NFT (X) for specific metadata X specified by the user from the user's externally owned account via an NFT management app connected to the wallet. Also, for example, the input / output unit 311 accepts a usage request (e.g., a request to view) metadata Y linked to an NFT (Y) owned by the user from the user's externally owned account via an NFT management app connected to the wallet. In these cases, the externally owned account is the wallet address of the connected wallet.

[0048] In response to a request to issue a new NFT for metadata X, the issuing unit 312 issues a new NFT (X) and sets ownership to the external ownership account.

[0049] The issuing unit 312 generates a token ID(X) that uniquely identifies the new NFT(X). For example, in an ERC721 standard smart contract, the _tokenIdCounter function can be used to generate new token IDs.

[0050] Here, the token ID of an NFT is an identifier for uniquely identifying each NFT. Usually, each NFT is assigned a unique token ID, which is generated within a smart contract. The token ID distinguishes the NFT from other NFTs and is used to track ownership and transactions. The method for generating the token ID is selected according to the design of the smart contract, such as sequential ID or custom logic. It is common for the token ID of the first NFT issued within a smart contract to be assigned as 1, the next token ID as 2, and so on, in sequential order.

[0051] The issuing unit 312 first sets the contract address (310) of the NFT contract 310 as the owner, sets a token URI (X) corresponding to the token ID (X), and records a new NFT (X) in the blockchain 300. Specifically, the issuing unit 312 uses the generated token ID (X) and the contract address (310) of the NFT contract 310 to record a new NFT (X) in the blockchain 300. That is, the NFT (X) recorded in the blockchain 300 is identified by a combination of the contract address (310) of the NFT contract 310 and the token ID (X) of the NFT (X) (hereinafter, for convenience of explanation, this combination is referred to as an NFT address).

[0052] The issuing unit 312 also sets a token URI corresponding to the token ID of the NFT (X). For example, in a smart contract based on the ERC721 standard, after issuing a new NFT, the _setTokenURI function can be called to set a token URI corresponding to the token ID. Note that a Uniform Resource Identifier (URI) is a notation format for identifying various resources (not limited to those on the Internet), including people and companies.

[0053] The token URI is a reference to metadata related to the NFT. This URI points to where the token's detailed information, such as metadata such as image, name, description, attributes, etc., is stored. The token URI is usually the URL of a JSON (JavaScript Object Notation) file hosted on an IPFS (Inter Planetary File System) or a web server. For example, if there is a token URI of https: / / example.com / nft / metadata / 1.json, the token's metadata can be accessed through that URI. The token ID and the token URI are closely related, and the corresponding token URI is managed by the token ID. The token URI in this embodiment is the URL of a JSON file hosted on the blockchain 300.

[0054] The issuing unit 312 also transfers the ownership of the NFT(X) to the user's externally owned account. As a result, the NFT(X) becomes the property of the user who requested the issuance of the NFT(X).

[0055] The issuing unit 312 also requests the metadata contract 320 to perform metadata processing to record associated metadata in the blockchain when issuing a new NFT (X). Specifically, the issuing unit 312 inputs the token URI(X) of the NFT(X), the metadata X, and the switching conditions into the metadata contract 320.

[0056] When using an existing NFT(Y), the reference unit 313 requests the use of related metadata from the metadata contract 320. For convenience of explanation, the existing NFT is referred to as NFT(Y), but NFT(Y) may be a newly issued NFT(X). Specifically, the reference unit 313 inputs the token URI of the NFT (Y) into the metadata contract 320.

[0057] When an existing NFT (Y) is used, the management unit 314 manages the user's use of metadata Y related to the NFT (Y) owned by the user. Specifically, the management unit 314 identifies the token ID (Y) of the NFT (Y) based on the contract address (Y) of the NFT (Y) accepted by the input / output unit 311 from the externally owned account, and identifies the token URI (Y) corresponding to the token ID (Y). The management unit 314 inputs the token URI (Y) to the metadata contract 320, and receives a JSON file of the metadata Y from the metadata contract 320.

[0058] The NFT information 315 includes a combination of a token ID and a token URI generated corresponding to the token ID. The combination is additionally stored each time a new NFT is issued. The NFT information is actually described in the source code of the NFT contract 310.

[0059] The smart contract address 316 stores the contract address (310) of the NFT contract 310 itself and the contract address (320) of the metadata contract 320 that requests metadata processing. These contract addresses are actually written in the source code of the NFT contract 310.

[0060] FIG. 5 is a diagram showing a functional block configuration of the metadata contract 320 according to this embodiment.

[0061] The metadata contract 320 includes an input / output unit 321, a division unit 322, a recording unit 323, a usage management unit 324, an address array 325, a smart contract address 326, and a judgment condition 327.

[0062] The input / output unit 321 receives a metadata processing request from the NFT contract 310 and returns the result of executing the processing according to the request to the NFT contract 310. Specifically, when issuing a new NFT(X), the input / output unit 321 obtains, as input, from the NFT contract 310, the token URI(X), metadata (X), and switching conditions for the new NFT(X) with respect to the metadata X. For a single NFT(X), multiple non-identical metadata (X1, X2, ...) distinguished by a key (identification data) described later can also be input. Then, the input / output unit 321 returns the completion of recording the metadata X of the new NFT(X) to the NFT contract 310. Furthermore, when an existing NFT (Y) is used, the input / output unit 321 obtains the token URI (Y) of the existing NFT (Y) as input from the NFT contract 310. Then, the input / output unit 321 returns a JSON file of the metadata Y to the NFT contract 310.

[0063] When issuing a new NFT(X), the division unit 322 divides the metadata X acquired via the input / output unit 321 into n pieces of partial data PD (n is an integer equal to or greater than 1). Hereinafter, when the n pieces of partial data PD are to be individually distinguished, they will be referred to as partial data PD1, partial data PD2, partial data PD3, ... partial data PDn, and will be collectively referred to as the partial data array PD(1, 2, ..., n). n may be determined, for example, by specifying the size of the partial data in advance, or may be determined according to the type of metadata.

[0064] Furthermore, when issuing a new NFT(X), the division unit 322 generates n data addresses APD corresponding to the n partial data PDs, respectively. The n data addresses APD are collectively referred to as a data address array APD(1, 2, ..., n). Hereinafter, when the n data addresses APD are to be individually distinguished, they are referred to as data address APD1, data address APD2, ..., data address APDn.

[0065] Furthermore, when issuing a new NFT(X), the division unit 322 stores the data address array APD(1, 2, ..., n) in the address array 325. Specifically, the division unit 322 generates a hash value H from the NFT address (X) of the NFT(X), the token ID (X), and the array identifier, and stores the data address array APD(1, 2, ..., n) in the address array 325 using the hash value H as a key. Note that the array identifier is automatically assigned as a consecutive integer number (which may include 0) according to the number of input metadata. This makes it possible to assign multiple address arrays to the same combination of NFT address and token ID.

[0066] When issuing a new NFT (X), the recording unit 323 records each partial data PD divided by the division unit 322 in the blockchain 300 using the corresponding data address APD. If there are multiple metadata (X1, X2, ...), each metadata is recorded.

[0067] When an existing NFT(Y) is used, the usage management unit 324 switches the reference destination of the metadata Y linked to the NFT(Y) according to a predetermined switching condition stored in the determination condition 327. The switching condition is, for example, a conditional expression that determines one of multiple options by referring to an oracle (external information) such as the passage of a predetermined amount of time, weather, or market prices (gold, oil).

[0068] Each record in the address array 325 has a key-value type data structure consisting of key information for identifying data and a value paired with the key information. Such an array is sometimes called "mapping." In this embodiment, the key information is a hash value H generated by the division unit 322, and the paired value is a data address array APD. These arrays are actually described in the source code of the metadata contract 320.

[0069] The smart contract address 326 stores the contract address (320) of the metadata contract 320 itself and the contract address (310) of the NFT contract 310 that requested the metadata processing. These contract addresses are actually described in the source code of the metadata contract 320.

[0070] The judgment condition 327 stores a judgment condition related to the NFT. In this embodiment, a switching condition for switching between multiple metadata is stored as the judgment condition. The judgment condition is actually described in the source code of the metadata contract 320.

[0071] <Operation of Information Processing System 1 (Information Processing Method)> Each process of the information processing system 1 will be described below. <Deployment process> FIG. 6 is a diagram showing the operation of the deployment process (deployment step) in the information processing system 1 according to this embodiment.

[0072] In step S101, an issuer of an NFT (e.g., the NFT management server 100) makes a deploy request to the blockchain 300 to deploy the NFT contract 310 and the metadata contract 320 to the blockchain 300.

[0073] In step S102, the blockchain 300 saves the setting values ​​of step S101 and deploys the NFT contract 310 and the metadata contract 320. This makes the NFT contract 310 and the metadata contract 320 available for use.

[0074] In step S103, the blockchain 300 returns a deployment completion confirmation to the issuer account indicating that the deployment has been completed.

[0075] <Issue process> 7 is a diagram showing the operation of the issuance process in the information processing system 1 according to this embodiment. In the issuance process of this embodiment, the user S issues a new NFT in which two pieces of metadata that can be used are switched according to a predetermined switching condition, using the NFT contract 310 and the metadata contract 320. The following description is based on the assumption that the user S requests the issuance of an NFT by specifying two pieces of metadata.

[0076] In step S201, user S specifies multiple pieces of metadata and predetermined switching conditions for switching between these multiple pieces of metadata in an NFT management app, and makes a request to issue one NFT for the multiple pieces of metadata. Specifically, the NFT management app of the user terminal 200 specifies the first metadata (X1), the second metadata (X2), and a predetermined switching condition (X) for switching between these two metadata to the NFT contract 310, and requests the issuance of one NFT (X) for the two metadata. This NFT issuance request also includes the externally owned account EOA of the wallet of the user S connected to the NFT management app. The NFT contract 310 obtains the first metadata (X1), the second metadata (X2), the externally owned account (EOA), and the switching condition (X) as input.

[0077] In step S202, the NFT contract 310 requests the blockchain 300 to record the issuance of an NFT (X) with the NFT contract 310 set as the owner (issuance step). Specifically, the NFT contract 310 generates a token ID (X) for the NFT (X), sets a token URI corresponding to the token ID (X), generates an NFT address (310X) from the contract address (310) of the NFT contract 310 and the token ID (X), and requests the blockchain 300 to record the new issuance of an NFT (X) that is uniquely identifiable by the NFT address (310X).

[0078] In step S203, the blockchain 300 records the issuance of the NFT (X), and when the recording is complete, it notifies the NFT contract 310 of confirmation of the completion of the issuance recording.

[0079] In step S204, the NFT contract 310 requests the blockchain 300 to record the transfer of ownership of the NFT (X) to the user's external ownership account EOA.

[0080] In step S205, the blockchain 300 records the transfer of ownership of the NFT (X), and when the recording is completed, notifies the NFT contract 310 of confirmation of the completion of the transfer recording. As a result, it is trackably recorded in the blockchain 300 that the NFT (X) identified by the NFT address (310X) has been transferred to the externally owned account EOA of the user S.

[0081] In step S206, the NFT contract 310 requests the metadata contract 320 to record the first metadata (X1) and the second metadata (X2) full on-chain (recording step). The NFT contract 310 inputs the token URI (X) of the NFT (X), the first metadata (X1), the second metadata (X2), and the switching condition (X) to the metadata contract 320.

[0082] In step S207, the metadata contract 320 divides each of the multiple metadata X input in step S206 into n pieces of partial data PD, and generates a partial data array PD(1, 2, ..., n) which is a group of partial data PD (recording step). This step is performed for each metadata. Specifically, the JSON of the first metadata (X1) is converted into a data URI scheme format and divided to generate a partial data array PDX1 (1, 2, ..., n), and the JSON of the second metadata (X2) is converted into a data URI scheme format and divided to generate a partial data array PDX2 (1, 2, ..., n).

[0083] In step S208, the metadata contract 320 acquires data addresses APD corresponding to each element of the partial data array PDX (1, ​​2, ..., n) generated in step S207, and generates a data address array APDX (1, ​​2, ..., n). Then, the metadata contract 320 generates a hash value H from the NFT address (X), the token ID (X), and the array identifier, and stores the hash value H and the data address array APDX (1, ​​2, ..., n) in the address array 325 (recording step). This step is performed for each metadata. Specifically, the metadata contract 320 generates a data address array APDX1 (1, 2, ..., n) for each element of the partial data array PDX1 (1, 2, ..., n) of the first metadata (X1), generates a hash value H1 as the NFT address (X), the token ID (X), and the array identifier (for example, 1), and stores the set of the hash value H1 and the data address array APDX1 (1, 2, ..., n) in the address array 325. Similarly, it generates a data address array APDX2 (1, 2, ..., n) for each element of the partial data array PDX2 (1, 2, ..., n) of the second metadata (X2), generates a hash value H2 as the NFT address (X), the token ID (X), and the array identifier (for example, 2), and stores the set of the hash value H2 and the data address array APDX (1, ​​2, ..., n) in the address array 325.

[0084] In step S209, the metadata contract 320 associates the metadata corresponding to the switching condition (X) acquired in step S206 with the array identifier used to generate the hash value H in step S208, and stores the result in the judgment condition 327 (recording step). Specifically, the first metadata (X1) included in the switching condition (X) is replaced with the sequence identifier numerical value 1, and the second metadata (X2) included in the switching condition (X) is replaced with the sequence identifier numerical value 2, and this is stored as switching condition (XH) in the judgment condition 327. For example, if the switching condition (X) is a condition that "until December 31, 20XX, the address array of the metadata (X1) is used, and thereafter the address array of the metadata (X2) is used", then the condition becomes "until December 31, 20XX, the address array with the sequence identifier 1 is used, and thereafter the address array with the sequence identifier 2 is used".

[0085] In step S210, the metadata contract 320 requests the blockchain 300 to record a pair of the partial data array PDX(1, 2, ..., n) and its data address array APDX(1, 2, ..., n) (recording step). Specifically, the blockchain 300 is requested to record each of the pair of the partial data array PDX1(1, 2, ..., n) of the first metadata (X1) and its data address array APDX1(1, 2, ..., n), and the pair of the partial data array PDX2(1, 2, ..., n) of the second metadata (X2) and its data address array APDX2(1, 2, ..., n).

[0086] In step S211, the blockchain 300 records a pair of the partial data array PD(X1, X2, ..., Xn) and its data address array APD(X1, X2, ..., Xn), and notifies the metadata contract 320 of a metadata recording completion confirmation indicating that recording is complete. Specifically, the set of the partial data array PDX1(1, 2, ..., n) of the first metadata (X1) and its data address array APDX1(1, 2, ..., n), and the set of the partial data array PDX2(1, 2, ..., n) of the second metadata (X2) and its data address array APDX2(1, 2, ..., n) are recorded, and a metadata recording completion confirmation is sent to the metadata contract 320 to inform that the recording of these has been completed.

[0087] In step S212, the metadata contract 320 notifies the NFT contract 310 of a processing completion confirmation indicating that the metadata processing is completed. The NFT contract 310 receives the processing completion confirmation.

[0088] In step S213, the NFT contract 310 notifies the NFT management app of the user terminal 200 of an issuance completion confirmation indicating that the issuance of the NFT (X) has been completed. The NFT management app receives the issuance completion confirmation of the NFT (X).

[0089] <Usage management processing> 8 is a diagram showing the operation of the usage management process in the information processing system 1 according to this embodiment. The usage management process according to this embodiment will be described below assuming a case where a user T requests the use of metadata of an NFT (Y) that he owns. Note that user T may be the same as user S who issued the NFT (Y).

[0090] In step S301, user T requests use of metadata of an existing NFT (Y) owned by the user in the NFT management app of the user terminal 200. The user terminal 200 inputs the NFT address (Y) of the NFT (Y) to the NFT contract 310. The NFT contract 310 obtains the NFT address (Y).

[0091] In step S302, the NFT contract 310 requests the metadata contract 320 to use the metadata of the NFT (Y). Specifically, the management unit 314 of the NFT contract 310 identifies the token ID (Y) of the NFT (Y) from the NFT address (Y) acquired in step S301, and acquires the token URI (Y) corresponding to the token ID (Y). In the ERC721 standard, the token URI corresponding to the token ID can be acquired by the tokenURI function. Then, the NFT contract 310 requests the metadata contract 320 to reference the token URI (Y) using the reference source address. The reference source address is the contract address (310) of the NFT contract 310. The metadata contract 320 acquires the token ID (Y) and the contract address (310).

[0092] In step S303, the metadata contract 320 determines the sequence identifier by referring to the switching condition of the NFT(Y) (switching step).

[0093] In step S304, the metadata contract 320 identifies the data address array APD(Y) of the NFT(Y) by using the array identifier determined in step S303 (switching step). Specifically, the usage management unit 324 of the metadata contract 320 generates a hash value H from the token ID (Y) acquired in step S302, the contract address (310), and the array identifier determined in step S303, and identifies the value whose key is the hash value H as the data address array APD (1, 2, ..., n) by referring to the address array 325.

[0094] In step S305, the metadata contract 320 acquires the partial data array PD on the blockchain 300 using the data address array APD(1, 2, . . . , n) identified in step S304 (switching step).

[0095] In step S306, the metadata contract 320 restores the metadata from the partial data acquired in step S305 (switching step). Specifically, the metadata contract 320 combines the partial data array PD(1, 2, . . . , n) acquired in step S305, and generates a token URI in the data URI scheme format.

[0096] In step S307, the metadata contract 320 provides the metadata restored in step S306 to the user terminal 200 via the NFT contract 310 (switching step). Specifically, the metadata contract 320 returns the token URI generated in step S306 as an output of the metadata usage request of the NFT contract 310. The NFT contract 310 transmits the token URI to the user terminal 200 via the NFT management server 100. The user terminal 200 refers to the metadata included in the token URI.

[0097] 9 is a diagram showing the relationship between the NFT and metadata in the information processing system 1 according to an embodiment of the present disclosure. As shown in FIG. 9, the NFT and its metadata are recorded in the blockchain 300, and these processes are completed by a smart contract in the blockchain 300. This makes it possible to reduce the cost of processing while avoiding the risk of tampering.

[0098] <Basic computer configuration> 10 is a block diagram showing a basic hardware configuration of a computer 900. The computer 900 has a processing unit 901, a storage unit 902, a communication unit 903, an input unit 904, and an output unit 905. The processing unit 901, the storage unit 902, the communication unit 903, the input unit 904, and the output unit 905 are electrically connected to each other via a communication bus 910.

[0099] The processing unit 901 includes a CPU (Central Processing Unit) and is a device that controls each unit of the computer 900 and also reads and executes various programs stored in the storage unit 902 .

[0100] The storage unit 902 includes a main storage device such as a dynamic random access memory (DRAM) and an auxiliary storage device such as a hard disk, and is a device that stores various programs for executing the operating system and various applications of the computer 900, as well as data used by these programs. The processes shown in the various flowcharts described above are realized by the processing units 901 of the NFT management server 100, the user terminal 200, and each computer constituting the blockchain 300 executing the programs stored in the respective storage units 902.

[0101] The communication unit 903 is a device for communicating with external devices, and transmits and receives data according to instructions from the processing unit 901. The NFT management server 100, the user terminal 200, and each computer constituting the blockchain 300 each use this communication unit 903 to communicate with other devices, including the network 5 shown in FIG.

[0102] The input unit 904 is a device that receives input from the outside and supplies it to the processing unit 901, and is configured to include, for example, a keyboard, a mouse, a touch panel, and a camera. The output unit 905 is a device that outputs the processing result of the processing unit 901 to the outside, and is configured to include, for example, a display and a speaker. <Program> Here, we will explain the details of the programs for realizing each function that constitutes the NFT management server 100 according to each embodiment.

[0103] The NFT management server 100 is implemented in a computer 900. The operation of each component of the NFT management server 100 is stored in the auxiliary storage device of the storage unit 902 in the form of a program. The processing unit 901 reads the program from the auxiliary storage device of the storage unit 902, expands it in the main storage device of the storage unit 902, and executes the above-mentioned processing in accordance with the program. The processing unit 901 also secures a memory area corresponding to the above-mentioned memory unit 120 in the main storage device of the storage unit 902 in accordance with the program.

[0104] Specifically, the program is a program for causing a computer having a processor and a memory unit to execute the program in computer 900, and the program causes the processor to execute an issuance step of issuing an NFT and a recording step of recording multiple metadata that can be exclusively referenced by the issued NFT and their reference information in the blockchain network 300 in which smart contracts 310, 320 are recorded, and is characterized in that the program retains the reference information for each of the multiple metadata.

[0105] The auxiliary storage device of the storage unit 902 is an example of a non-transient tangible medium. Other examples of non-transient tangible media include a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, and a semiconductor memory connected via the input unit 904. When this program is distributed to the computer 900 via the network 5, the computer 900 that has received the program may load the program into the main storage device of the storage unit 902 and execute the above process.

[0106] The program may be for realizing part of the above-mentioned functions. Furthermore, the program may be a so-called difference file (difference program) that realizes the above-mentioned functions in combination with another program already stored in the auxiliary storage device of the storage unit 902.

[0107] As described above, according to the information processing system 1 of the present disclosure, the metadata of the NFT is recorded in the blockchain 300, and the metadata can be used permanently. In other words, the process is completed by referencing only on-chain data, and an off-chain processing system is not required, thereby reducing costs and labor. In addition, the metadata can be referred to permanently at low cost (free of charge).

[0108] Moreover, according to the information processing system 1, the metadata referenced by the NFT can be changed by changing the hash value H for reference of the NFT to identify the data address array. Furthermore, according to the information processing system 1, since there are a plurality of pairs of the reference hash value H and the data address array, it becomes possible to exclusively switch the reference destination of the metadata. The switching conditions for switching the reference destination of the metadata are implemented in the metadata contract 320 on the blockchain 300, and by setting the time and reference data as the switching conditions in advance, the information processing system 1 can automatically determine the switching conditions and change the metadata to be referenced. For example, the reference of on-chain data can be automatically replaced depending on the rights status such as copyright and portrait right of the metadata.

[0109] In other words, the information processing system 1 according to the present disclosure makes it possible to easily manage the rights to content while enabling permanent use of content managed by NFT.

[0110] <Modification> Although each embodiment of the present disclosure has been described above, these embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are within the scope of the invention and its equivalents as described in the claims, as well as the scope and spirit of the invention.

[0111] For example, in each of the above-described embodiments, the NFT contract 310 and the metadata contract 320 are separated into two smart contracts, but they may also be implemented as a single smart contract.

[0112] In the above embodiment, two pieces of metadata are used for switching. However, if three or more pieces of metadata are input in step S206, the metadata contract 320 repeats steps S207 to S210 for each piece of metadata.

[0113] <Additional Notes> The matters described in the above embodiments will be supplemented below. (Appendix 1) an issuance step in which the smart contract issues the NFT; A recording step in which the smart contract records a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information in a blockchain network in which the smart contract is recorded; having The smart contract holds reference information of each of the plurality of metadata. Information processing methods. This allows the metadata to be used permanently. (Appendix 2) The smart contract further includes a switching step of switching the reference information referenced by the NFT, 2. An information processing method as described in Appendix 1. This makes it possible to refer to metadata according to conditions regarding the use of the metadata. (Appendix 3) The switching step is a step in which the smart contract switches the reference information referenced by the NFT based on a predetermined switching condition stored in the smart contract. 2. An information processing method as described in Appendix 2. This makes it possible to set various switching conditions and refer to metadata according to conditions regarding the use of the metadata. (Appendix 4) and deploying the smart contract on the blockchain network. 4. An information processing method according to any one of appendix 1 to 3. This allows NFT and metadata processing to be permanently available on-chain. (Appendix 5) The predetermined switching condition is the passage of a predetermined time. 5. An information processing method as described in Appendix 3. This makes it possible to automatically switch the metadata to be referenced as time passes as a condition for using the metadata. (Appendix 6) The predetermined switching condition is an oracle. 5. An information processing method as described in Appendix 3. This makes it possible to set a variety of switching conditions using external information (oracles). (Appendix 7) The recording step is a step in which the smart contract divides the metadata for each of the plurality of metadata and records the divided metadata on the blockchain network. 7. An information processing method according to claims 1 to 6. This reduces metadata storage costs. (Appendix 8) The issuing step is a step in which an NFT contract, which is a smart contract that manages an NFT, issues the NFT, The recording step is a step in which a metadata contract, which is a smart contract that manages metadata referenced by the NFT, records a plurality of metadata referenced by the issued NFT and their reference destination information in the blockchain network. 8. An information processing method according to any one of appendix 1 to 7. (Appendix 9) A program recorded on a blockchain network, An issuance step for issuing an NFT; A recording step of recording a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information on the blockchain network; Run the following on your computer: The reference destination information of each of the plurality of metadata is stored. program. (Appendix 10) An issuing department that issues NFTs; A recording unit that records a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information on a blockchain network by a smart contract; Equipped with The smart contract holds reference information for each of the plurality of metadata. Information processing system. (Appendix 11) A smart contract recorded on a blockchain network, An issuance step for issuing an NFT; A recording step of recording a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information on the blockchain network; Run the following on your computer: The reference destination information of each of the plurality of metadata is stored. Smart contracts. [Explanation of symbols]

[0114] 1: Information processing system 5: Network 100: NFT management server 131: User Management Section 132:Deployment Department 133: Publishing Department 134: Usage Management Department 200: User terminal 300: Blockchain Network 310: NFT contract (smart contract) 311: Input / output section 312: Publishing Department 313 :Reference section 314: Management Department 315:NFT Information 316: Smart contract address 320: Metadata Contract (Smart Contract) 321: Input / output section 322 :Divided part 323: Recording Department 324: Usage Management Department 325: Address array 326: Smart contract address 327: Judgment condition

Claims

1. an issuing step in which the smart contract issues the NFT; A recording step in which the smart contract records a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information in a blockchain network in which the smart contract is recorded; having The smart contract holds reference information of each of the plurality of metadata. Information processing methods.

2. An issuance step in which a smart contract issues an NFT; A recording step in which the smart contract records a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information in a blockchain network in which the smart contract is recorded; A switching step in which the smart contract switches the reference information referenced by the NFT; having The smart contract holds reference information of each of the plurality of metadata. Information processing methods.

3. The switching step is a step in which the smart contract switches the reference information referenced by the NFT based on a predetermined switching condition stored in the smart contract. The information processing method according to claim 2 .

4. The method further includes, prior to the issuing step, a deployment step of deploying the smart contract on the blockchain network.

3. The information processing method according to claim 1.

5. The predetermined switching condition is the passage of a predetermined time. The information processing method according to claim 3.

6. The predetermined switching condition is an oracle. The information processing method according to claim 3.

7. The recording step is a step in which the smart contract divides the metadata for each of the plurality of metadata and records the divided metadata on the blockchain network. The information processing method according to claim 1 .

8. The issuing step is a step in which an NFT contract, which is a smart contract that manages an NFT, issues the NFT, The recording step is a step in which a metadata contract, which is a smart contract that manages metadata referenced by the NFT, records a plurality of metadata referenced by the issued NFT and their reference destination information in the blockchain network. The information processing method according to claim 1 .

9. A program recorded on a blockchain network, An issuing step of issuing an NFT; A recording step of recording a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information on the blockchain network; Run the following on your computer: The reference information of each of the plurality of metadata is stored. program.

10. An issuing unit that issues NFTs; A recording unit that records a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information on a blockchain network by a smart contract; Equipped with The smart contract holds reference information for each of the plurality of metadata. Information processing system.

11. A smart contract recorded on a blockchain network, An issuing step of issuing an NFT; A recording step of recording a plurality of metadata that can be exclusively referenced by the issued NFT and their reference destination information on the blockchain network; Run the following on your computer: The reference information of each of the plurality of metadata is stored. Smart contracts.

Citation Information

Patent Citations

  • Content contract system, content contract method, right holder terminal, assignee terminal, control terminal, content storage server, right holder program, assignee program, control program, and content storage program

    JP2020068388A

  • System and method for using digital asset

    JP2024037151A

  • Systems and methods for providing a digital media rental platform

    WO2023082008A1

  • Information processing system, information processing method, and program

    WO2023204214A1