Transaction support system, transaction support method and transaction support program

Abstract

To provide an environment for supporting content creators.SOLUTION: A transaction support system includes at least one processor. The at least one processor receives an issuing operation by a content creator, acquires a handwritten electronic signature of the creator input in the issuing operation, and issues an NFT to which the handwritten electronic signature is attached. There is a one-to-one correspondence between the NFT and the handwritten electronic signature.SELECTED DRAWING: Figure 4

Description

[Technical field]

[0001] One aspect of the present disclosure relates to a transaction support system, a transaction support method, and a transaction support program. [Background technology]

[0002] There are known mechanisms for trading digital content. For example, Patent Document 1 describes a system for managing ownership by associating a real card, which is a physical object, with a digital card, which is electronic data. Patent Document 2 describes a system for displaying the name of the owner on the content. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2022-079884 [Patent Document 2] Patent No. 7058898 Summary of the Invention [Problem to be solved by the invention]

[0004] There is a need for a mechanism to support content creators. [Means for solving the problem]

[0005] A transaction support system according to an aspect of the present disclosure includes at least one processor. The at least one processor accepts a publishing operation by a creator of content, acquires the creator's handwritten digital signature input in the publishing operation, and issues an NFT to which the handwritten digital signature is attached. The NFT and the handwritten digital signature have a one-to-one correspondence.

[0006] In this aspect, there is a one-to-one correspondence between NFTs and the creator's handwritten digital signature. This ensures the value of the NFT. This provides an incentive for people who want to support creators to trade NFTs, which in turn stimulates trading. Demand for such NFTs and the trading of such NFTs can help increase the popularity of the creators themselves. As a result, an environment for supporting content creators can be provided. Effect of the Invention

[0007] According to one aspect of the present disclosure, it is possible to provide an environment for supporting content creators. [Brief description of the drawings]

[0008] [Figure 1] 1 is a schematic diagram showing an example of a transaction in a transaction support system. [Diagram 2] FIG. 1 is a diagram illustrating an example of an application of a transaction support system. [Diagram 3] FIG. 2 is a diagram illustrating an example of a hardware configuration related to the transaction support system. [Figure 4] FIG. 2 is a diagram illustrating an example of a functional configuration related to the transaction support system. [Diagram 5] FIG. 2 is a sequence diagram showing an example of an operation of the transaction support system. [Figure 6] A figure showing an example of the display of a master NFT. [Figure 7] FIG. 11 is a sequence diagram showing another example of the operation of the transaction support system. [Figure 8] FIG. 11 is a sequence diagram showing yet another example of the operation of the transaction support system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the description of the drawings, the same or equivalent elements are designated by the same reference numerals, and duplicated descriptions will be omitted.

[0010] [System Overview] The transaction support system according to the embodiment is a computer system that supports content creators. Content refers to information provided by a computer or a computer system and recognizable by humans. The form of expression of content is not limited, and content may be expressed by images (e.g., photographs, videos, etc.). Content may be provided, for example, by on-demand distribution or live distribution (live broadcast). Creators are people or organizations that create various activities as content. Activities include singing, dancing, musical performance, illustrations, and games (operation or commentary). As an example, a creator creates a video image of singing as content.

[0011] The transaction support system issues a first NFT and a second NFT as non-fungible tokens (NFTs). The first NFT and the second NFT are the subject of trading on a known electronic commerce platform (hereinafter referred to as a "marketplace") or in transactions between individuals. The first NFT and the second NFT are electronic data that can be displayed on a display device, such as digital trading cards. Hereinafter, the first NFT is referred to as a "master NFT" and the second NFT is referred to as a "commemorative NFT."

[0012] A master NFT is issued for a creator. For example, a master NFT is issued for any information (hereinafter referred to as a "label") related to a creator. Examples of labels include, but are not limited to, activities, jobs, tags, fields, and keywords. In one example, a master NFT is issued for a creator's activities. "For a creator's activities" is a concept that includes a creator's activities to create past content and future content, rather than individual content itself. A master NFT issued for an activity can trace a creator's activities. For example, a master NFT enables access to a list of content (e.g., a playlist) corresponding to a specific activity in a channel where a specific creator distributes content (creator's distribution channel). A master NFT can be issued multiple times for the same label. A master NFT is given a handwritten electronic signature of a creator. A master NFT and a handwritten electronic signature have a one-to-one correspondence. In other words, a handwritten electronic signature is unique to each master NFT.

[0013] Commemorative NFTs are issued to creators or content in association with a Master NFT. For example, a commemorative NFT is issued to a creator whose activities are covered by a Master NFT if the creator's activities meet certain conditions. Commemorative NFTs are distributed to holders of Master NFTs. Master NFTs and commemorative NFTs can be bought and sold independently of each other.

[0014] By purchasing a Master NFT, Master NFT owners can support the activities of creators and expect to receive a commemorative NFT in the future in return for their support. Therefore, Master NFTs can be said to be proof of a partnership between creators and Master NFT owners. Hereinafter, Master NFT owners are referred to as "partners."

[0015] FIG. 1 is a schematic diagram showing an example of a transaction in a transaction support system. In process F1, a master NFT with a handwritten electronic signature of a creator is issued. In process F2, the creator puts the master NFT up for sale on a marketplace. In process F3, a third party other than the creator purchases the master NFT. The person who purchases the master NFT becomes a partner. The creator receives a predetermined percentage of the proceeds from the sale and purchase of the master NFT. In processes F1 to F3, an actual token for the master NFT may be issued after a third party purchases a master NFT before it is issued.

[0016] In process F4, the creator's activities meet a predetermined condition. For example, if the creator creates a singing video as content, the condition that the number of times the content is played is equal to or greater than a predetermined number is met. Such a milestone can be considered an anniversary of the activity. In process F5, a commemorative NFT is issued and distributed to the partner.

[0017] In process F6, the partner puts the commemorative NFT on the marketplace. In process F7, a third party other than the creator and the partner purchases the commemorative NFT. The partner receives a predetermined percentage of the sales revenue from the sale of the commemorative NFT. The creator receives a predetermined royalty from the sale of the commemorative NFT.

[0018] In transactions such as those shown in Figure 1, as the popularity of a creator increases, the popularity of the master NFT and commemorative NFT also increases. This may lead to an increase in the trading price and number of transactions of the master NFT and commemorative NFT.

[0019] [System configuration] FIG. 2 is a diagram showing an example of an application of the transaction support system 1. In this embodiment, the transaction support system 1 includes a server 10 (transaction support server). The server 10 is a computer that manages the issuance of master NFTs and commemorative NFTs. The server 10 is connected to a plurality of user terminals 20, a content server 30, a user database 40, an NFT database 50, and a distributed ledger system 60 via a network N. The configuration of the network N is not limited. For example, the network N may be configured to include the Internet or an intranet.

[0020] The user terminal 20 is a computer used by one or more users. A user is a person who uses the transaction support system 1. Examples of users include creators and personnel of a company that operates the server 10. The type of user terminal 20 is not limited. For example, the user terminal 20 may be a portable terminal such as a high-function mobile phone (smartphone), a tablet terminal, a wearable terminal (e.g., a head-mounted display (HMD), smart glasses, etc.), a laptop personal computer, or a mobile phone. Alternatively, the user terminal 20 may be a stationary terminal such as a desktop personal computer. The number of user terminals 20 is not limited.

[0021] The content server 30 is a computer that manages content created by creators. The content in this embodiment is a moving image. The content server 30 provides, for example, a website that distributes moving images. For example, the content server 30 provides a distribution channel for content for each creator. The content server 30 manages images of the master NFT and the commemorative NFT.

[0022] The user database 40 is a non-transitory storage medium or storage device that stores information about users. The user database 40 stores attribute information of users (e.g., creators). The attribute information is various information about users, and may include, for example, a user's identifier, age, sex, and the level of the creator. The level of the creator is determined based on the degree of activity of the creator. For example, the level of the creator may be determined based on the number of times the content has been played (the number of views), the period of activity, the number of followers of the creator, the number of subscribers to the distribution channel of the content, and the number of comments on the content, or may be determined based on information other than these. The higher the level of the creator, the more active the creator may be. The user database 40 may be constructed as a single database, or may be a collection of multiple databases. The location of the user database 40 is not limited. For example, the user database 40 may be provided in a computer system separate from the transaction support system 1.

[0023] The NFT database 50 is a non-transitory storage medium or storage device that stores metadata of the master NFT and the commemorative NFT. Examples of metadata include a title, a description, and a URI (Uniform Resource Identifier) ​​of an image. The title is a character string indicating the name of the master NFT or the name of the commemorative NFT, and is displayed, for example, in a marketplace. The description is a character string indicating a description of the master NFT or the commemorative NFT, or a description of the content. The URI of the image is, for example, information for referencing an image of the master NFT or the commemorative NFT managed by the content server 30. The NFT database 50 may be constructed as a single database or may be a collection of multiple databases. The location of the NFT database 50 is not limited. For example, the NFT database 50 may be provided in a computer system separate from the transaction support system 1. The NFT database 50 may be configured using an IPFS (InterPlanetary File System).

[0024] The distributed ledger system 60 is a computer system that issues master NFTs and commemorative NFTs. The distributed ledger system 60 manages a distributed ledger by a blockchain. The distributed ledger system 60 is constructed using, for example, Ethereum. The distributed ledger system 60 issues master NFTs and commemorative NFTs that comply with the ERC-721 (Ethereum Request for Comments 721) standard. The issued master NFTs and commemorative NFTs are recorded on the blockchain. A user who buys and sells master NFTs and commemorative NFTs has an account on the distributed ledger system 60. For example, a creator has a contract address in the distributed ledger system 60. Each NFT issued on the distributed ledger system 60 is assigned a uniquely identifiable token ID. The token ID is associated with the contract address of the issuer (e.g., the creator).

[0025] Fig. 3 is a diagram showing an example of a hardware configuration related to the transaction support system 1. Fig. 3 shows a server computer 100 functioning as the server 10 or the content server 30, and a terminal computer 200 functioning as the user terminal 20.

[0026] As an example, the server computer 100 includes a processor 101, a main memory unit 102, an auxiliary memory unit 103, and a communication unit 104 as hardware components. The processor 101 is a computing device that executes an operating system and application programs, and is, for example, a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit). The main memory unit 102 is a device that stores programs to be executed, calculation results, and the like, and is, for example, composed of a ROM (Read Only Memory) or a RAM (Random Access Memory). The auxiliary memory unit 103 is a device that can generally store a larger amount of data than the main memory unit 102, and is, for example, composed of a non-volatile storage medium such as a hard disk or a flash memory. The auxiliary memory unit 103 stores a server program P1 and various data for making the server computer 100 function as the server 10. The communication unit 104 is a device that executes data communication with other computers via the network N, and is, for example, composed of a network card or a wireless communication module.

[0027] In this embodiment, the transaction support program is implemented as a server program P1. Each functional element of the server 10 is realized by loading the server program P1 onto the processor 101 or the main memory unit 102 and having the processor 101 execute the program. The server program P1 includes code for realizing each functional element of the server 10. The processor 101 operates the communication unit 104 in accordance with the server program P1, and executes reading and writing of data in the main memory unit 102 or the auxiliary memory unit 103.

[0028] The server 10 may be composed of one or more computers. When multiple computers are used, these computers are connected to each other via a network N to logically configure one server 10.

[0029] As an example, the terminal computer 200 includes a processor 201, a main memory unit 202, an auxiliary memory unit 203, a communication unit 204, an input interface 205, an output interface 206, and an imaging unit 207 as hardware components. The processor 201 is a computing device that executes an operating system and an application program, and is, for example, a CPU or a GPU. The main memory unit 202 is a device that stores a program to be executed, a calculation result, and the like, and is, for example, composed of a ROM or a RAM. The auxiliary memory unit 203 is a device that can generally store a larger amount of data than the main memory unit 202, and is, for example, composed of a non-volatile storage medium such as a hard disk or a flash memory. The auxiliary memory unit 203 stores a client program P2 and various data for causing the terminal computer 200 to function as the user terminal 20. The communication unit 204 is a device that executes data communication with other computers via the network N, and is, for example, composed of a network card or a wireless communication module. The input interface 205 is a device that accepts data based on a user's operation or action, and is composed of at least one of a keyboard, an operation button, a pointing device, a touch panel, a microphone, a sensor, and a camera, for example. The output interface 206 is a device that outputs data processed by the terminal computer 200, and is composed of a display device such as a monitor, a touch panel, and an HMD, for example. The imaging unit 207 is a device that captures an image (video or photo) of the real world, and is, for example, a camera. The imaging unit 207 can also function as the input interface 205.

[0030] Each functional element of the user terminal 20 is realized by loading a corresponding client program P2 into the processor 201 or the main memory unit 202 and having the processor 201 execute the program. The client program P2 includes code for realizing each functional element of the user terminal 20. The processor 201 operates the communication unit 204, the input interface 205, the output interface 206, or the imaging unit 207 in accordance with the client program P2, and reads and writes data from and to the main memory unit 202 or the auxiliary memory unit 203.

[0031] At least one of the server program P1 and the client program P2 may be provided in a form non-temporarily recorded on a tangible recording medium such as a CD-ROM, a DVD-ROM, a semiconductor memory, etc. Alternatively, at least one of these programs may be provided as a data signal superimposed on a carrier wave via the network N. These programs may be provided separately or together.

[0032] FIG. 4 is a diagram showing an example of a functional configuration related to the transaction support system 1. The server 10 includes an acquisition unit 11, a determination unit 12, a storage unit 13, and a request unit 14 as functional elements. The acquisition unit 11 is a functional element that acquires information for generating a master NFT and a commemorative NFT. The determination unit 12 is a functional element that determines whether the issuance conditions for the master NFT and the commemorative NFT are met. The storage unit 13 is a functional element that stores metadata of the master NFT and the commemorative NFT in the NFT database 50. The request unit 14 is a functional element that requests the distributed ledger system 60 to issue the master NFT and the commemorative NFT.

[0033] The user terminal 20 includes, as functional elements, an input unit 21 and a transmission unit 22. The input unit 21 is a functional element that accepts input of information related to the master NFT. The transmission unit 22 is a functional element that transmits information related to the master NFT to the server 10.

[0034] [System Operation] The operation of the transaction support system 1 will be described with reference to Fig. 5, and an example of a transaction support method will be described. Fig. 5 is a sequence diagram showing the operation of the transaction support system 1 as a process flow S1. The process flow S1 shows a process related to the issuance of a master NFT. In the process flow S1, the user terminal 20 is operated by a creator.

[0035] In step S11, the input unit 21 of the user terminal 20 accepts an issuance operation that triggers the issuance of a master NFT. The input unit 21 accepts an input of basic information that specifies various information for generating a master NFT. The basic information includes a design such as a color, a label, the price of the master NFT, and a handwritten electronic signature. The basic information may include an icon that is an automatically acquired image indicating a creator, and a thumbnail image of a video that is a content. The input unit 21 accepts an input of information that specifies, for example, a label. The label may be selected from a plurality of candidates. For example, the input unit 21 may accept a selection from candidates related to an activity, a job, or a tag. In one example, the input unit 21 may accept a selection from candidates of a modifier (keyword) and a job. In this case, the label may be a character string in which the modifier and the job are concatenated.

[0036] The handwritten electronic signature is, for example, handwritten characters of the creator's name. The input format of the handwritten electronic signature may be any input format that retains the creator's handwriting or habits. For example, the handwritten electronic signature may be input by a signature format using a tablet terminal and a touch pen, by operating a mouse, or by tracing with a finger. The input unit 21 may repeatedly accept the input of the handwritten electronic signature in accordance with the desired number of sheets to be issued. As an example, if the desired number of sheets to be issued is three, the input unit 21 may accept the input of the handwritten electronic signature three times. The desired number of sheets to be issued may be the number of times the basic information is input.

[0037] In step S12, the transmission unit 22 of the user terminal 20 transmits a request to issue a master NFT to the server 10. The issuance request may include the basic information entered in step S11.

[0038] In step S13, the acquisition unit 11 of the server 10 acquires various information for generating a master NFT. For example, the acquisition unit 11 acquires basic information included in the request received from the user terminal 20. The acquisition unit 11 acquires, from the user database 40, the level of the creator associated with the user's identifier.

[0039] At this stage, the master NFT may be made available for listing on the marketplace. Here, a description will be given assuming that a third party has purchased the master NFT listed on the marketplace. The acquisition unit 11 may acquire various information regarding the partner who is the purchaser of the master NFT from the marketplace or the user terminal 20, etc. The acquisition unit 11 may generate an image of the master NFT based on the basic information and transmit the image to the content server 30.

[0040] In step S14, the determination unit 12 of the server 10 determines whether the master NFT issuance conditions are met. Examples of the master NFT issuance conditions include whether the desired number of issuances exceeds the upper limit of the number of master NFTs to be issued. The upper limit of the number of master NFTs to be issued may be determined based on the level of the creator. For example, the upper limit of the number of master NFTs to be issued may be determined to be larger as the level of the creator increases. Here, the desired number of issuances is described as being within the upper limit. In this way, the determination unit 12 limits the number of master NFTs to be issued to the upper limit based on the level.

[0041] In step S15, the storage unit 13 of the server 10 stores the metadata of the master NFT in the NFT database 50. The metadata of the master NFT is a title, a description, an image URI, etc. The title is generated based on, for example, the creator's name, the label, and the type of the NFT. The type of the NFT is information that indicates the master NFT here. As an example, the title is generated by concatenating character strings of the creator's name, the label, and the type of the NFT.

[0042] In step S16, the NFT database 50 stores the metadata of the master NFT based on the request received from the server 10.

[0043] In step S17, the request unit 14 of the server 10 sends a request to issue a master NFT to the distributed ledger system 60. The request may include generation information of the master NFT. The generation information of the master NFT may include the creator's contract address, the partner's address, the URI of the master NFT's metadata, and a handwritten electronic signature. The partner's address here is the address of an account on the distributed ledger system 60. The URI of the master NFT's metadata is information for referencing the metadata of the master NFT stored in the NFT database 50.

[0044] In step S18, the distributed ledger system 60 issues a master NFT based on the request received from the server 10. A handwritten digital signature is attached to the master NFT. The master NFT is associated with a URI of the metadata of the master NFT. The metadata of the master NFT records a URI of the image. Therefore, the master NFT can trace the URI of the image via the URI of the metadata of the master NFT.

[0045] The owner of the master NFT is managed by the distributed ledger system 60. Specifically, the owner of the master NFT is recorded on the blockchain. The owner of the master NFT is issued as a partner. When the master NFT is bought and sold, the owner of the master NFT is transferred. At the time of buying and selling, the token ID of the creator's contract address and the partner's address are associated.

[0046] The server 10 and the content server 30 may store information on the issued master NFT. For example, the server 10 and the content server 30 may synchronously or asynchronously store information such as the identifier of the master NFT and the owner of the master NFT. Alternatively, the server 10 and the content server 30 may obtain information on the master NFT from the distributed ledger system 60 as necessary. The server 10 and the content server 30 may store whether or not a master NFT has been issued for each creator.

[0047] 6 is a diagram showing an example of the display of a master NFT 9 according to an embodiment. The master NFT 9 is displayed, for example, on a display device of a user terminal 20 used by the owner (partner) of the master NFT 9. The master NFT 9 includes a creator icon 91, the creator's name 92, a title 93, a handwritten electronic signature 94, a background 95, and a partner icon 96 as screen elements.

[0048] An image representing the creator is displayed in the creator icon 91. The image representing the creator is used, for example, in the creator's distribution channel in the content server 30. "Creator A" is displayed in the creator's name 92. The title 93 displays a label "A singer who was too early for humanity" composed of the modifier "Too early for humanity" and the job "Singer". The title 93 is a character string concatenating the modifier and job selected by the creator. The creator's name 92 may be displayed larger than the title 93. The creator is active under the name "Creator A" and has the title "A singer who was too early for humanity", for example.

[0049] The handwritten electronic signature 94 displays the handwritten electronic signature given to the master NFT 9. The handwritten electronic signature displayed in the handwritten electronic signature 94 indicates that it is a signature that retains handwriting or quirks.

[0050] An image showing the activities of the creator is displayed on the background 95. For example, the background 95 is an image generated based on the content created by the creator. As an example, the background 95 is generated based on thumbnail images of the video images that are the content. The thumbnail images used in the background 95 may be a predetermined number of thumbnail images selected in order of most recently updated. The background 95 may not be a thumbnail image showing the activities of the creator, but may be an illustration or the like. In another example, the background 95 is not limited to an image showing the activities of the creator, and may be, for example, a specified design, color, or a combination thereof.

[0051] An image showing the partner is displayed on the partner icon 96. Information about the partner, including the image showing the partner, may be managed by the content server 30. In the master NFT 9, the creator icon 91 and the partner icon 96 are displayed simultaneously. This allows the master NFT 9 to visually represent the partnership between the creator and the partner. The partner icon 96 does not have to be displayed.

[0052] The operation of the transaction support system 1 will be described with reference to Fig. 7, and another example of a transaction support method will be described. Fig. 7 is a sequence diagram showing the operation of the transaction support system 1 as a process flow S2. The process flow S2 shows a process related to the issuance of a commemorative NFT.

[0053] In step S21, the content server 30 transmits activity information indicating the degree of activity of the creator to the server 10. The activity information includes the identifier of the master NFT, the number of times the content has been played, the period of activity, the number of followers of the creator, the number of subscribers to the distribution channel of the content, and the number of comments on the content. For example, the content server 30 transmits activity information regarding a specific activity of a specific creator for whom a master NFT has been issued to the server 10. The content server 30 may transmit the activity information of the creator to the server 10 periodically, or may transmit the activity information of the creator to the server 10 in response to an anniversary of the creator's activity or the like as a trigger.

[0054] In step S22, the acquisition unit 11 of the server 10 acquires various information for generating a commemorative NFT. For example, the acquisition unit 11 acquires activity information received from the content server 30.

[0055] In step S23, the determination unit 12 of the server 10 determines whether the conditions for issuing the commemorative NFT are met. The conditions for issuing the commemorative NFT include activity information indicated by a quantity or period being equal to or greater than a predetermined threshold. The predetermined conditions include the number of times the content has been played, the period of activity, the number of followers of the creator, the number of subscribers to the content's distribution channel, and the number of comments on the content being equal to or greater than the corresponding predetermined threshold. As an example, the determination unit 12 may determine whether the number of times the content has been played is 10,000 or more. Here, it is assumed that the activity information satisfies the predetermined condition.

[0056] In step S24, the storage unit 13 of the server 10 stores the metadata of the commemorative NFT in the NFT database 50. The metadata of the commemorative NFT is a title, a description, an image URI, etc. The title is generated based on, for example, the creator's name, a label, and the type of the NFT. The type of the NFT is information indicating the commemorative NFT here.

[0057] In step S25, the NFT database 50 stores metadata for the commemorative NFT based on the request received from the server 10.

[0058] In step S26, the request unit 14 of the server 10 requests the distributed ledger system 60 to issue a commemorative NFT. The request may include generation information of the commemorative NFT. Examples of the generation information of the commemorative NFT include the creator's contract address, the partner's address, the URI of the metadata of the commemorative NFT, and a handwritten electronic signature. The URI of the metadata of the commemorative NFT is information for referencing the metadata of the commemorative NFT stored in the NFT database 50. The request may include a contract associated with the sale and purchase of the commemorative NFT. For example, the request may include a contract in which the creator receives royalties associated with the sale and purchase of the commemorative NFT.

[0059] In step S27, the distributed ledger system 60 issues a commemorative NFT based on the request received from the server 10. The commemorative NFT does not have a handwritten digital signature attached to it. The commemorative NFT is associated with a URI in the metadata of the commemorative NFT. The metadata of the commemorative NFT records the URI of the image. Therefore, the commemorative NFT can be traced back to the URI of the image via the URI of the metadata of the commemorative NFT. The commemorative NFT may be provided with a contract whereby the creator receives royalties associated with the sale and purchase of the commemorative NFT. This contract may be implemented, for example, by an Ethereum smart contract.

[0060] The owner of the commemorative NFT is managed by the distributed ledger system 60. Specifically, the owner of the commemorative NFT is recorded on the blockchain. In process flow S2, the owner of the commemorative NFT when it is first issued is the same as the owner of the master NFT. When the commemorative NFT is bought and sold, the owner of the commemorative NFT is transferred. At the time of the sale, the token ID of the creator's contract address and the address of the owner of the commemorative NFT are associated.

[0061] In relation to step S21, the content server 30 may transmit activity information of a creator to the server 10 in response to a request received from the server 10. For example, in response to a request to obtain activity information of a specific creator, the content server 30 may transmit activity information of the creator to the server 10. In relation to steps S21 and S22, the server 10 or the content server 30 may determine a level of the creator based on the activity information and store the level of the creator in the user database 40.

[0062] The operation of the transaction support system 1 will be described with reference to FIG. 8, and another example of a transaction support method will be described. FIG. 8 is a sequence diagram showing the operation of the transaction support system 1 as a processing flow S3. Processing flow S3 is executed before processing flow S1, and shows a process of requesting the issuance of a new master NFT. Hereinafter, the user terminal 20 of the user who wishes to purchase the master NFT will be referred to as the first user terminal, and the user terminal 20 of the creator will be referred to as the second user terminal.

[0063] In step S31, the first user terminal accepts input of search conditions for information on the master NFT. Search conditions include, but are not limited to, the creator's name and label.

[0064] In step S32, the first user terminal transmits a search request to the content server 30. The search request may include search conditions.

[0065] In step S33, the content server 30 transmits the search results to the first user terminal in response to the search request. The search results are displayed on the display device of the first user terminal. The search results may be, for example, information on whether or not a master NFT has been issued for a creator corresponding to the creator name specified in the search conditions. Here, the search results are information indicating that a master NFT has not been issued. Whether or not a master NFT has been issued may be managed by the content server 30, or may be obtained from the distributed ledger system 60.

[0066] In step S34, the first user terminal accepts input of desired request conditions regarding the issuance of a master NFT. The request conditions are conditions indicating what kind of master NFT is desired to be issued. The request conditions include, for example, the creator's name, information about the label, and the desired price of the master NFT.

[0067] In step S35, the first user terminal transmits a request to the content server 30. The request may include a request condition.

[0068] In step S36, the content server 30 transmits the request to the second user terminal. The request conditions included in the request are displayed on the display device of the second user terminal.

[0069] The process flow S3 is executed after the process flow S1, and may be a process of requesting the listing of the master NFT. For example, in the process flow S3, the second user terminal may be the user terminal 20 of the owner of the master NFT. In relation to step S33, the search result may be information indicating that the master NFT has been issued. In relation to step S34, the first user terminal may accept input of desired request conditions regarding the listing of the master NFT. The request conditions may include, for example, the name of the creator, information identifying the label, the desired price of the master NFT, and the like. In relation to steps S35 and S36, a request including the request conditions is transmitted to the second user terminal via the content server 30. In another example, steps S31 to S33 may be omitted.

[0070] [effect] As described above, a transaction support system according to one aspect of the present disclosure includes at least one processor. The at least one processor accepts a publishing operation by a content creator, acquires the creator's handwritten electronic signature input in the publishing operation, and issues an NFT to which the handwritten electronic signature is attached. The NFT and the handwritten electronic signature have a one-to-one correspondence.

[0071] A transaction support method according to an aspect of the present disclosure is executed by a transaction support system having at least one processor. The transaction support method includes accepting a publishing operation by a creator of content, acquiring a handwritten digital signature of the creator input in the publishing operation, and issuing an NFT to which the handwritten digital signature is attached. The NFT and the handwritten digital signature have a one-to-one correspondence.

[0072] A transaction support program according to an aspect of the present disclosure causes a computer to execute the following operations: accepting an issuance operation by a creator of content, acquiring the creator's handwritten electronic signature input in the issuance operation, and issuing an NFT to which the handwritten electronic signature is attached. NFTs and handwritten electronic signatures have a one-to-one correspondence.

[0073] In this aspect, there is a one-to-one correspondence between NFTs and the creator's handwritten digital signature. This ensures the value of the NFT. This provides an incentive for people who want to support creators to trade NFTs, which in turn stimulates trading. Demand for such NFTs and the trading of such NFTs can help increase the popularity of the creators themselves. As a result, an environment for supporting content creators can be provided.

[0074] A transaction support system according to an aspect of the present disclosure includes at least one processor. The at least one processor acquires information input by a content creator and designates a label indicating information about the creator, and issues an NFT for the label.

[0075] A transaction support method according to an aspect of the present disclosure is executed by a transaction support system having at least one processor. The transaction support method includes acquiring information input by a content creator and designating a label indicating information about the creator, and issuing an NFT for the label.

[0076] A transaction support program according to one aspect of the present disclosure causes a computer to acquire information input by a content creator that specifies a label indicating information about the creator, and to issue an NFT for the label.

[0077] In this aspect, NFTs are issued using a label that indicates information about the creator. It is made clear that NFTs are issued for a specific creator. For those who wish to trade NFTs, the purpose of the transaction becomes clear, which promotes trading. Such demand for NFTs and the trading of such NFTs can promote the activities of creators. As a result, an environment for supporting content creators can be provided.

[0078] In the transaction support system, at least one processor may acquire a level determined based on the activity of a creator, determine an upper limit on the number of NFTs to be issued based on the level, and limit the number of NFTs to the upper limit. That is, the number of NFTs to be issued is adjusted to an amount appropriate for the level. In other words, the upper limit on the number of NFTs to be issued changes in conjunction with the activity of the creator. This provides an incentive for creators to raise the upper limit on the number of NFTs to be issued.

[0079] In the transaction support system, at least one processor may transmit request conditions for issuing NFTs, including information about the labels, to a creator's terminal. When issuing NFTs, the request conditions can be used as reference information, improving convenience for creators.

[0080] A transaction support system according to one aspect of the present disclosure includes at least one processor. The at least one processor acquires activity information indicating the degree of activity of a creator targeted by a first NFT, determines whether the activity information satisfies an issuance condition based on a predetermined threshold, and issues a second NFT if the activity information satisfies the issuance condition. At the beginning of issuance of the second NFT, the owner of the first NFT and the owner of the second NFT are the same.

[0081] A transaction support method according to one aspect of the present disclosure is executed by a transaction support system having at least one processor. The transaction support method includes acquiring activity information indicating the degree of activity of a creator targeted by a first NFT, determining whether the activity information satisfies an issuance condition based on the activity information and a predetermined threshold, and issuing a second NFT if the activity information satisfies the issuance condition. At the beginning of issuance of the second NFT, the owner of the first NFT and the owner of the second NFT are the same.

[0082] A transaction support program according to an aspect of the present disclosure causes a computer to execute the following steps: acquire activity information indicating the degree of activity of a creator targeted by a first NFT, determine whether the activity information satisfies an issuance condition based on a predetermined threshold, and issue a second NFT if the activity information satisfies the issuance condition. At the beginning of issuance of the second NFT, the owner of the first NFT and the owner of the second NFT are the same.

[0083] In this aspect, when activity information of a creator who is the subject of a first NFT satisfies a predetermined issuance condition, a second NFT is issued in association with the owner of the first NFT. That is, the owner of the first NFT can obtain a second NFT issued according to the degree of activity of the creator. This provides an incentive for people who wish to trade the first NFT to trade the first NFT, thereby activating trading. Such demand for the first NFT and the trading of the first NFT can promote the activities of creators. As a result, an environment for supporting content creators can be provided.

[0084] In the transaction support system, at least one processor may, when issuing the second NFT, grant a contract to the second NFT under which the creator receives royalties associated with the sale and purchase of the second NFT. In this case, the opportunity for the creator to earn revenue increases when the second NFT is sold and purchased. Therefore, the creator is incentivized to increase the degree of their activity in order to promote the issuance of the second NFT.

[0085] In the transaction support system, the first NFT may be provided with a handwritten digital signature of the creator. At least one processor may issue the second NFT without providing the handwritten digital signature of the creator to the second NFT. In this case, the first NFT and the second NFT are differentiated by whether or not the handwritten digital signature is provided. The purpose of the transaction becomes clear to those who wish to trade the first or second NFT. This enables transactions that meet the needs of the potential buyer.

[0086] [Variations] The present disclosure has been described in detail above based on the embodiments. However, the present disclosure is not limited to the above embodiments. The present disclosure can be modified in various ways without departing from the spirit and scope of the present disclosure.

[0087] In the above embodiment, the server 10 and the user terminal 20 are described as separate computers, but they may be the same computer or the same computer system. In this case, creators can directly access the distributed ledger system 60 to issue master NFTs, etc. In another example, the server 10, the content server 30, and the NFT database 50 may be the same computer or the same computer system. In this case, data management in the transaction support system 1 is facilitated.

[0088] In this disclosure, the expression "at least one processor executes a first process, executes a second process, ... executes an nth process" or a corresponding expression is a concept including a case where the executing entity (i.e., the processor) of n processes from the first process to the nth process changes midway. In other words, this expression is a concept including both a case where all n processes are executed by the same processor and a case where the processor changes among the n processes according to an arbitrary policy.

[0089] The processing procedure of the method executed by at least one processor is not limited to the example in the above embodiment. For example, some of the steps (processing) described above may be omitted, or each step may be executed in a different order. In addition, any two or more of the steps described above may be combined, or some of the steps may be modified or deleted. Alternatively, other steps may be executed in addition to each of the steps described above.

[0090] Any part or all of the functional units described in this specification may be realized by a program. The program mentioned in this specification may be distributed in a non-temporary manner recorded on a computer-readable recording medium, or may be distributed via a communication line (including wireless communication) such as the Internet, or may be distributed in a state in which it is installed on any terminal.

[0091] Based on the above description, a person skilled in the art may be able to conceive additional effects or various modifications of the present disclosure, but the aspects of the present disclosure are not limited to the individual embodiments described above. Various additions, modifications, and partial deletions are possible within the scope of the conceptual idea and intent of the present disclosure derived from the contents defined in the claims and their equivalents.

[0092] For example, a configuration described in this specification as one device (or component; the same applies below) (including a configuration depicted as one device in the drawings) may be realized by multiple devices. Alternatively, a configuration described in this specification as multiple devices (including a configuration depicted as multiple devices in the drawings) may be realized by one device. Alternatively, some or all of the means or functions included in a certain device (e.g., a server) may be included in another device (e.g., a user terminal).

[0093] Not all of the features described in this specification are essential. For example, features that are described in this specification but not in the claims may be considered optional additional features.

[0094] The applicant is merely aware of the known technology described in the "Prior Art Documents" column of this specification. It should also be noted that this disclosure is not necessarily intended to solve the problems in the known technology. The problems to be solved in this disclosure should be identified by taking into consideration the entire specification. For example, if there is a description in this specification that a specific configuration produces a certain effect, it can also be said that the problem corresponding to the certain effect is solved. However, the description of the effect does not necessarily intend that such a specific configuration is an essential requirement. [Explanation of symbols]

[0095] 1...transaction support system, 10...server, 11...acquisition unit, 12...judgment unit, 13...storage unit, 14...request unit, 20...user terminal, 21...input unit, 22...transmission unit, 30...content server, 40...user database, 50...NFT database, 60...distributed ledger system, N...network, P1...server program, P2...client program.

Claims

1. An NFT trading support system comprising at least one processor, wherein the at least one processor obtains a request including request conditions regarding the issuance of an NFT from a first user terminal used by a user who wishes to purchase the NFT, sends the request to a second user terminal used by a content creator, and issues the NFT triggered by an issuance operation by the creator.

2. The NFT trading support system according to Claim 1, wherein the at least one processor obtains the request including at least one of the name of the creator, information regarding a label which is information about the creator, and a desired price of the NFT as the request conditions.

3. The at least one processor obtains a search request including search conditions regarding the NFT from the first user terminal, and in response to the search request, sends a search result indicating whether the NFT has been issued to the first user terminal. The NFT trading support system according to Claim 1.

4. The at least one processor obtains a listing request including request conditions regarding the listing of the NFT from the first user terminal, and sends the listing request to the second user terminal. The NFT trading support system according to Claim 1.

5. The NFT trading support system according to Claim 1, wherein the at least one processor displays the request conditions as candidates in the input of basic information in the issuance operation.

6. A trading support method executed by an NFT trading support system comprising at least one processor, the method comprising: obtaining a request including request conditions regarding the issuance of an NFT from a first user terminal used by a user who wishes to purchase the NFT; sending the request to a second user terminal used by a content creator; and issuing the NFT triggered by an issuance operation by the creator.

7. Obtaining a request including request conditions regarding the issuance of the NFT from a first user terminal used by a user who wishes to purchase the NFT; sending the request to a second user terminal used by a content creator; A step of issuing the NFT triggered by an issuance operation by the creator A transaction support program that causes a computer to execute.

Images