Platform system

Abstract

To provide a platform system configured to make it easier for a plurality of persons to participate in a co-creation activity thereby facilitating utilization of personnel in content creation, and make it easier to associate a content with information on the content using NFT, thereby facilitating distribution or use of the NFTized content.SOLUTION: A platform system 100 includes a server device 20 which is connected to a blockchain network 10 comprising participant terminals 23. The participant terminal transmits basic information and an application for participating in a project to a server, to enable transactions with other participant terminals. The server device creates and manages project pages according to categories of the received basic information, the project pages being disclosed to the participant terminals, provides a predetermined rule to participant terminals which apply for participation in the project, and concludes a smart contract with the participant terminals that have transmitted agreement about the rule to the server.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a platform system that enables multiple people to create content simultaneously and promotes the distribution and use of NFT-ized content. [Background technology]

[0002] Conventionally, platforms that allow users to publish online content, such as novels, manga, illustrations, haiku, lyrics, videos, and music that they have created themselves, and allow their fans to read and listen to them, have been known, for example, as disclosed in Non-Patent Documents 1-6 (hereinafter referred to as "prior art" in this specification).

[0003] In the above-mentioned conventional techniques, it is assumed that the act of creating content itself is carried out by each creator in a manner of their own choosing. [Prior art documents] [Patent documents]

[0004] [Non-Patent Document 1] Hina Project Co., Ltd., "Let's Become a Novelist", [online], April 2004, Hina Project Co., Ltd., [Retrieved May 11, 2023], Internet<URL:https: / / syosetu.com / > [Non-Patent Document 2] Pixiv Inc., “Pixiv”, [online], October 2007, Pixiv Inc., [Retrieved May 11, 2023], Internet<URL:https: / / www.pixiv.net / > [Non-Patent Document 3] Axis Co., Ltd., “DLsite”, [online], July 1996, Axis Co., Ltd., [Retrieved May 11, 2023], Internet<URL:https: / / www.dlsite.com / > [Non-Patent Document 4] SoundCloud Limited, “SoundCloud”, [online], August 2007, SoundCloud Limited, [searched on May 11, 2020], Internet<URL:https: / / soundcloud.com / > [Non-Patent Document 5] KADOKAWA Corporation, Hatena Corporation, “Magical iLand”, [online], 1999, KADOKAWA Corporation, Hatena Corporation, [searched May 11, 2023], Internet<URL:https: / / maho.jp / > [Non-Patent Document 6] Pinterest,Inc., “Pinterest”, [online], March 2010, Pinterest,Inc., [Retrieved May 11, 2023], Internet<URL:https: / / www.pinterest.com / > Summary of the Invention [Problem to be solved by the invention]

[0005] Incidentally, while it may have been possible for multiple people to simultaneously create content online by combining existing technologies, there were no examples of such technologies being provided as a platform.

[0006] In addition, when multiple people create content, the copyright and other rights, as well as the handling of income and expenditures, are left to agreement between the parties. However, negotiating contracts relating to rights and the handling of income and expenditures, and putting the agreements into writing, are difficult to determine using only the experience and knowledge of the individual creators, and even if such an agreement was reached, it had to be enforced and managed manually.

[0007] As a result, at least in Japan, activities in which multiple creators collaborate to create a single piece of content (hereinafter, in this specification, we will refer to this as "co-creation activities" as appropriate) are not widely carried out, and this has been a factor in hindering the utilization of potential creators who are motivated to create content but are unable to work alone due to the constraints mentioned above.

[0008] In addition to the above, the following problems can be mentioned: In recent years, a technology has become known that relates to non-fungible tokens (hereinafter referred to as "NFTs" as appropriate in this specification), which link content such as digital art with information about that content (including the content's owner, creator, date of creation, URL where the original data is located, history of transfer of ownership, etc.) and record this on a blockchain, thereby clarifying the authenticity and owner of the content.

[0009] In this way, when linking content and information related to the content through NFT (i.e., converting content into NFT), the creator of the content, etc., had to create a wallet for electronically storing virtual currency in advance and connect it to a platform that provides digital content trading services. For this reason, from the perspective of promoting the distribution and use of digital content, it was desired to make it easier to convert content into NFT.

[0010] The present invention has been made in consideration of the above-mentioned circumstances, and one of its objectives is to provide a platform system that can promote the utilization of human resources in content creation by making it easier for multiple people to participate in co-creation activities. Another challenge is to provide a platform system that can promote the distribution and use of NFT-ized content by making it easier to link NFT content with information related to the content. [Means for solving the problem]

[0011] The present invention is a platform system including a participant terminal participating in a project related to the creation of content, and a server connected to a blockchain network composed of a plurality of the participant terminals, wherein the participant terminal is capable of inputting basic information of the project when creating the project and transmitting the information to the server, and enables transactions with other participant terminals, and the server is capable of creating and managing a project page according to the classification of the basic information of the project received from the participant terminal, and is capable of issuing and storing tokens to the participant terminal that transmitted the basic information of the project in connection with the creation of the project page, and is capable of issuing and storing tokens linked to the project to participant terminals wishing to participate in the project, and is capable of connecting the participant terminals to the blockchain network.

[0012] The present invention is also characterized in that the server enables contracts regarding the content between the participant terminals by concluding smart contracts on the blockchain network.

[0013] The present invention is also characterized in that, when the smart contract is concluded between the participant terminals, the server is capable of providing the participant terminals with format information regarding the conclusion of the smart contract.

[0014] Furthermore, the present invention is characterized in that when the participant terminal provides economic benefits including money to the project page, the server is capable of issuing and storing a fan token to the participant terminal when the participant terminal is a participant terminal participating in the project page as a fan of the content, and the participant terminal that has been issued the fan token is capable of providing economic benefits including money using the fan token stored on the server on the blockchain network.

[0015] Furthermore, the present invention is characterized in that when the participant terminal makes a contribution of labor and services to the project page, the server is capable of issuing and storing a fan token for the participant terminal when the participant terminal is a participant terminal participating in the project page as a fan of the content, and the participant terminal that has made the contribution of labor and services is capable of obtaining the fan token as compensation for the contribution of labor and services from the server on the blockchain network.

[0016] The present invention is also characterized in that the fan tokens issued and stored on the server include premium tokens, and the participant terminal that has been issued the premium tokens is capable of providing economic benefits including money, or making the contributions of labor and services, on the blockchain network.

[0017] The present invention also provides a platform system including a participant terminal participating in a project related to the creation of content, and a server connected to a blockchain network composed of a plurality of the participant terminals, wherein the participant terminal inputs basic information of the project when creating the project and transmits it to the server, and when wishing to participate in an existing project, transmits an application to participate to the server, and further enables transactions with other participant terminals, and the server creates and manages a project page according to the classification of the basic information of the project received from the participant terminal, and is capable of publishing the created project page to each participant terminal, provides desired rules regarding the operation of the project to the participant terminal that applies to participate in the project, and enables the conclusion of a smart contract on the blockchain network between the participant terminal that inputs and transmits its agreement to the rules.

[0018] In addition, the present invention is characterized in that the server issues and grants tokens to the participant terminals belonging to the project page according to the roles of the participants, and manages the tokens.

[0019] The present invention is also characterized in that, when the participant terminal is the participant terminal that created the project page, the server issues and grants an owner token to the participant terminal and manages the owner token.

[0020] The present invention is also characterized in that, when the participant terminal is a participant terminal participating in the project as a fan of the created content, the server sells fan tokens to the participant terminal and manages the fan tokens.

[0021] The present invention is also characterized in that the server stores the revenue from the sale of the fan tokens in accordance with the smart contract and distributes it to each participant terminal.

[0022] In addition, the present invention is characterized in that on the project page, restrictions on viewing of the content by each of the participant terminals are determined according to the category of the token held by each of the participant terminals.

[0023] The present invention is also characterized in that the server assigns, in accordance with the smart contract, to each participant terminal governance points indicating the proportion of contribution that can be made to decision-making in the project, and revenue points indicating the proportion of the distribution of profits obtained from the project, and manages information on the governance points and the revenue points.

[0024] The present invention is also characterized in that the server is capable of assigning commitment points indicating the degree of contribution to the project to each participant terminal in accordance with the smart contract, managing information about the commitment points, and allocating rewards determined for each project according to the commitment points.

[0025] The present invention is also characterized in that the project page enables each participant terminal to input voting information when making decisions in the project and transmit it to the server, and the server performs processing based on the received voting information and the amount of governance points held by each participant terminal, and transmits the voting results derived by this processing to the project page.

[0026] The present invention is also characterized in that the transactions between the participant terminals on the project page are irreversibly recorded on the blockchain network. Effect of the Invention

[0027] According to the present invention, it is possible to facilitate the participation of multiple creators in co-creation activities, thereby making it possible to promote the utilization of human resources in content creation. In addition, according to the present invention, it is possible to easily link NFT content with information related to the content, thereby making it possible to promote the distribution and use of NFT content. [Brief description of the drawings]

[0028] [Figure 1] 1A and 1B are conceptual diagrams showing the present invention and a conventional example, in which FIG. 1A is a conceptual diagram showing a platform system according to the conventional example, and FIG. 1B is a conceptual diagram showing a platform system according to the present invention. [Diagram 2] 1 is a schematic diagram showing an entire platform system according to a first embodiment of the present invention. [Diagram 3] FIG. 10 is a diagram illustrating a flow of creating a project. [Figure 4] A diagram illustrating an example of the flow for creating an owner NFT. [Diagram 5] A diagram illustrating the creation flow of a co-creator NFT. [Figure 6] FIG. 13 is a diagram illustrating a flow of participation in a project. [Figure 7] A diagram illustrating a flow for creating a ticket NFT. [Figure 8] FIG. 13 is a diagram illustrating a vote creation flow. [Figure 9] FIG. 13 is a diagram illustrating a voting participation flow. [Figure 10] FIG. 11 is a schematic diagram showing an entire platform system according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] Preferred embodiments of the present invention will now be described with reference to the drawings. Note that the embodiments described below do not limit the contents of the present invention described in the claims. Furthermore, not all of the configurations described below are necessarily essential requirements of the present invention.

[0030] Hereinafter, a first embodiment of the present invention will be described with reference to FIGS.

[0031] <About the present invention and the prior art> First, with reference to FIG. 1, a platform system 100 for content creation according to the present invention and a platform system 300 for content creation according to the related art will be compared and explained.

[0032] In this specification, "content" refers to various creative works resulting from human intellectual creative activity, such as literary works such as novels, haiku, tanka, lyrics, scripts, essays, etc., musical works such as songs, artistic works such as paintings, illustrations, manga, etc., and cinematographic works such as movies, television dramas, videos, animations, etc. (but is not limited to the above examples).

[0033] 1(a) is a system in which a creator 301 creates content 303 and publishes it on the platform system 300, allowing fans 302 of the content 303 to view the content 303 on the platform system 300. Therefore, the platform system 300 does not enable a plurality of creators 301 to simultaneously create content 303, nor does the platform system 300 enable the conclusion of contracts relating to rights such as copyrights and the processing of income and expenditure, or the execution and management of these contracts.

[0034] In contrast, the platform system 100 of the present invention shown in FIG. 1(b) allows anyone to start projects PJ1, PJ2, PJ3, etc. relating to the creation of content 104 as an owner 101, and a co-creator 102 can participate in projects PJ1, PJ2, PJ3, etc. as a participant.

[0035] The owner 101 and co-creators 102 can create, publish, and view content 104 on the platform system 100, and can also receive a share of the profits earned from projects PJ1, PJ2, PJ3, etc. (see arrow A in FIG. 1). Fans 103 can purchase and view content 104 on the platform system 100. The owner 101, co-creators 102, and fans 103 can each perform various exchanges and various processes related to projects PJ1, PJ2, PJ3, etc. with the terminals of other participants via their terminals.

[0036] <Outline of the platform system> 2 includes a block chain network 10 and a server device 20 connected to the block chain network 10. Each component of the platform system 100 will be described below.

[0037] <About Blockchain Network> The blockchain network 10 is composed of multiple participant terminals used by participants who take part in the project. Each component of the blockchain network 10 will be described below.

[0038] <About the Project> In this embodiment, the above-mentioned “project” is, for example, projects PJ1, PJ2, PJ3, . . . shown in FIG.

[0039] <About the participants> In this embodiment, the above-mentioned "participants" are project owners (hereinafter referred to as "owners") 101 who start projects PJ1, PJ2, PJ3, etc., co-creators 102 who participate in projects PJ1, PJ2, PJ3, etc., and fans 103 of content 104 (see Figure 1) created in projects PJ1, PJ2, PJ3, etc.

[0040] <About participant devices> In this embodiment, the "participant terminals" are the terminal 11 used by the owner 101, the terminal 12 used by the co-creator 102, and the terminal 13 used by the fan 103. The terminals 11, 12, and 13 enable transactions with other terminals. The terminal 23 shown in FIG. 2 is a terminal on the server device 20 side.

[0041] The terminal 11 allows the input of basic information of the projects PJ1, PJ2, PJ3, etc. when creating the projects PJ1, PJ2, PJ3, etc., and transmits the information to the server 21. The above-mentioned "basic information" is, for example, information including the title and core story, and information including an outline of the content to be published on the project pages PJP1, PJP2, PJP3, etc. (It is not limited to this, and may include other desired information).

[0042] Furthermore, when the co-creator 102 wishes to participate in existing projects PJ1, PJ2, PJ3, . . . , the terminal 12 enables the co-creator 102 to transmit an application to the server 21 to that effect.

[0043] Furthermore, when a fan 103 wishes to view project pages PJP1, PJP2, PJP3, . . . , the terminal 13 enables the fan 103 to view the project pages PJP1, PJP2, PJP3, . . . by obtaining approval for the projects PJ1, PJ2, PJ3, .

[0044] Furthermore, the terminals 11, 12, 13 are capable of inputting and transmitting voting information to the server 21 when making decisions in the projects PJ1, PJ2, PJ3, . . .

[0045] The terminals 11, 12, 13, and 23 are devices capable of transmitting and receiving various types of information to and from each other via a network, and include, for example, computers, mobile terminals such as smartphones, and the like.

[0046] <About the project page> The above projects PJ1, PJ2, PJ3... are created and published as project pages PJP1, PJP2, PJP3... in the blockchain network 10. When published as project pages PJP1, PJP2, PJP3..., a prescribed explanation regarding the governance of the projects PJ1, PJ2, PJ3... is added.

[0047] On project pages PJP1, PJP2, PJP3, etc., restrictions on viewing content by terminals 11, 12, and 13 are determined according to the category of tokens held by each terminal 11, 12, and 13. The above "tokens" are non-fungible tokens created on the blockchain, and may be referred to as "NFTs" where appropriate.

[0048] The project pages PJP1, PJP2, PJP3 . . . enable the input of voting information when making decisions in the projects PJ1, PJ2, PJ3 .

[0049] Transactions between terminals 11, 12, and 13 on project pages PJP1, PJP2, PJP3, etc. are irreversibly recorded on server device 20 in blockchain network 10.

[0050] The above-mentioned "transaction" is data to which an electronic signature is added to a predetermined unit of information that records various interactions and results of various processes related to projects PJ1, PJ2, PJ3, etc. between terminals 11, 12, 13 on project pages PJP1, PJP2, PJP3, etc.

[0051] <About the server device> The server device 20 is configured to include a server 21 equipped with various functional units, and a database 22 capable of storing various information. The server device 20 is capable of transmitting and receiving various information via a network to a terminal 23, a terminal 11 of an owner 101 constituting projects PJ1, PJ2, PJ3, etc., and a terminal 12 of a co-creator 102. Each component of the server device 20 will be described below.

[0052] <About the server> The server 21 is configured to include, as the above-mentioned "various functional units", a project providing unit 24, a token issuing unit 25, a wallet management unit 26, a revenue management unit 27, a revenue distribution unit 28, a search unit 29, an application management unit 30, a contract conclusion unit 31, a voting rights registration unit 32, a voting rights exercise unit 33, a point allocation management unit 34, and an additional functional unit 35.

[0053] The project provision unit 24 is a functional unit that creates and manages project pages PJP1, PJP2, PJP3, etc. according to the classification of basic information of projects PJ1, PJ2, PJ3, etc. received from terminal 11, and makes the created project pages PJP1, PJP2, PJP3, etc. available on terminals 11, 12, and 13.

[0054] The token issuing unit 25 is a functional unit that issues and grants tokens to the terminals 11, 12, 13 belonging to the project pages PJP1, PJP2, PJP3, . . . according to the roles of the participants (owner 101, co-creator 102, fan 103).

[0055] The token issuing unit 25 is a functional unit that issues and grants an owner token (owner NFT) to the terminal 11, for example, when the participant terminal is the terminal 11 of the owner 101 who created the project pages PJP1, PJP2, PJP3, etc.

[0056] In addition, the token issuance unit 25 is a functional unit that issues and grants a co-creator token (co-creator NFT) to the terminal 12, for example, when the participant terminal is the terminal 12 of a co-creator 102 participating in project pages PJP1, PJP2, PJP3, etc.

[0057] In addition, the token issuing unit 25 is a functional unit that sells fan tokens (ticket NFTs) to the terminal 13, for example, when the participant terminal is a terminal 13 participating in projects PJ1, PJ2, PJ3, etc. as a fan 103 of the content.

[0058] The wallet management unit 26 is a functional unit that manages various tokens issued by the token issuing unit 25.

[0059] The revenue management unit 27 is a functional unit that stores the revenue obtained from projects PJ1, PJ2, PJ3, etc. in accordance with a smart contract. The above "revenue" includes revenue obtained from the issuance and sale of various tokens.

[0060] The revenue distribution unit 28 is a functional unit that distributes revenues obtained from projects PJ1, PJ2, PJ3, etc. (for example, revenues obtained by issuing and selling various tokens) to the terminals 11, 12, and 13 in accordance with a smart contract. The revenue distribution unit 28 can distribute rewards determined for each project PJ1, PJ2, PJ3, etc. according to various points including commitment points, which will be described later, assigned to the terminals 11, 12, and 13.

[0061] The search unit 29 is a functional unit that searches the server device 20 for already created and existing project pages PJP1, PJP2, PJP3, . . . .

[0062] The application management unit 30 is a functional unit that provides desired rules regarding the management of the projects PJ1, PJ2, PJ3, . . . to terminals that apply for participation in the projects PJ1, PJ2, PJ3, .

[0063] The above-mentioned "desired rules" are rules including, for example, the distribution of profits obtained from projects PJ1, PJ2, PJ3, . . ., the management of copyrights for the created content, and methods for determining these.

[0064] The contract conclusion unit 31 is a functional unit that enables the conclusion of a smart contract on the blockchain network 10 between a terminal that has input and transmitted its consent to the above rules, and also enables the conclusion of a smart contract as performed in this embodiment.

[0065] The voting rights registration unit 32 is a functional unit that allocates governance points and revenue points to the terminals 11, 12, and 13 in accordance with the smart contract, and manages information on the governance points and revenue points.

[0066] The above "governance points" indicate the percentage that can be contributed to decision-making for projects PJ1, PJ2, PJ3, etc. The above "revenue points" indicate the percentage of revenues earned from projects PJ1, PJ2, PJ3, etc.

[0067] The voting rights exercise unit 33 is a functional unit that executes processing based on the voting information received from the project pages PJP1, PJP2, PJP3, etc. and the amount of governance points held by each terminal 11, 12, 13, and transmits the voting results derived by this processing to the project pages PJP1, PJP2, PJP3, etc.

[0068] The point allocation management unit 34 is a functional unit that allocates and manages various points including governance points and revenue points allocated to the terminals 11, 12, and 13 in accordance with the smart contract. The points allocated by the point allocation management unit 34 include commitment points.

[0069] The above "commitment points" are points indicating the degree of contribution to projects PJ1, PJ2, PJ3, etc., which are allocated to terminals 11, 12, and 13 according to a smart contract. The above "degree of contribution to projects PJ1, PJ2, PJ3, etc." is an effort to increase the value of projects PJ1, PJ2, PJ3, etc., including contributions to the creative content, attracting co-creators, and contributions related to advertising projects PJ1, PJ2, PJ3, etc. Information on commitment points is managed by the point allocation management unit 34, and rewards (e.g., money, crypto assets, project-specific rewards, etc.) determined for each project PJ1, PJ2, PJ3, etc. can be allocated according to the commitment points.

[0070] The additional function unit 35 is a function unit that enables functions to be added to the server 21. Therefore, the server 21 may include other function units by adding a desired function unit (not shown in FIG. 2) by the additional function unit 35.

[0071] <About the database> In the database 22, desired information including project information 36, transaction information 37, and token identifier information 38 is stored as the above-mentioned "various information."

[0072] The project information 36 includes various information about the projects PJ1, PJ2, PJ3, . . .

[0073] The transaction information 37 is information including history information of transactions between the terminals 11, 12, and 13 on the project pages PJP1, PJP2, PJP3, . . .

[0074] The token identifier information 38 is information that is associated with various tokens and is used to identify the tokens when the token issuing unit 25 issues the various tokens.

[0075] <Project creation flow> Next, a project creation flow will be described with reference to Fig. 3. Note that the project creation flow shown in Fig. 3 is an example, and is not limited to the flow described below.

[0076] First, in step S1 shown in Fig. 3, a core story is set, and the process proceeds to step S2 shown in Fig. 3. The "core story" is information including, for example, a title and a core story, and this information is inputted into the terminal 11 and transmitted to the server 21.

[0077] In step S2 shown in Fig. 3, a story is set, and the process proceeds to step S3 shown in Fig. 3. The above-mentioned "story" is information including, for example, an outline of the content (information published on project pages PJP1, PJP2, PJP3, etc. shown in Fig. 2) and an eye-catching image, and this information is inputted into the terminal 11 and transmitted to the server 21 side.

[0078] 3, the presence or absence of reference information is inputted at the terminal 11 and transmitted to the server 21. The above-mentioned "reference information" is information including, for example, information on other projects (reference projects) that are referenced in a spin-off project when a project is spun off from another project.

[0079] In step S3, if "Yes" is input as the reference information, the process proceeds to step S4 shown in FIG. 3, and if "No" is input as the reference information, the process proceeds to step S8 shown in FIG.

[0080] If the process proceeds to step S4 shown in Fig. 3, a reference project is set, and the process proceeds to step S5 shown in Fig. 3. In step S5 shown in Fig. 3, a reference co-creator is set, and the process proceeds to step S6 shown in Fig. 3. In step S6 shown in Fig. 3, governance points and revenue points to be issued to the co-creator are set, and the process proceeds to step S7 shown in Fig. 3. In step S7 shown in Fig. 3, a memo is added, and the process proceeds to step S8 shown in Fig. 3.

[0081] In step S8 shown in FIG. 3, an upper limit is set for various points (governance points, revenue points, commitment points, etc.) to be issued to co-creators, and the process proceeds to step S9 shown in FIG.

[0082] In step S9 shown in FIG. 3, it is set whether the project is to be made public or private, and the process proceeds to step S10 shown in FIG.

[0083] In step S10 shown in FIG. 3, sales settings including the sales price of the ticket NFT are made, and the process proceeds to step S11 shown in FIG.

[0084] In step S11 shown in Fig. 3, it is determined whether the platform currency is sufficient to publish the project. The above-mentioned "platform currency" is points obtained by charging, and if the platform currency is "insufficient", the process proceeds to step S12 shown in Fig. 3, and if the platform currency is "sufficient", the process proceeds to step S13 shown in Fig. 3.

[0085] In step S12 shown in Fig. 3, after charging the platform currency in the charging flow, return to step S11 shown in Fig. 3 and judge again whether the platform currency is sufficient to publish the project. If the result is "sufficient", proceed to step S13 shown in Fig. 3.

[0086] In step S13 shown in FIG. 3, the project is made public. The settings made in steps S1 to S10 can be saved at any time. This completes the project creation flow.

[0087] <Owner NFT creation flow> Next, the flow of creating an owner NFT associated with the creation of a project will be described with reference to Fig. 4. Note that the flow of creating an owner NFT shown in Fig. 4 is an example, and is not limited to the flow described below.

[0088] First, a project creation is input on the owner terminal (step S21 shown in FIG. 4), and the platform system approves the project creation (step S22 shown in FIG. 4) and sends a project creation request to the blockchain (step S23 shown in FIG. 4). When the blockchain receives the project creation request, a smart contract regarding the project creation is concluded (step S24 shown in FIG. 4).

[0089] In step S25 shown in Fig. 4, when the blockchain notifies the platform system of the completion of project creation, in step S26 shown in Fig. 4, the platform system issues an owner NFT, transmits a notification of the completion of project creation, and makes the project public. This completes the owner NFT creation flow.

[0090] <Co-creator NFT creation flow> Next, a flow of creating a co-creator NFT accompanying the addition of a co-creator will be described with reference to Figure 5. Note that the flow of creating a co-creator NFT shown in Figure 5 is an example, and is not limited to the flow described below.

[0091] First, when a request to add a co-creator is input at the owner terminal (step S31 shown in FIG. 5), the platform system transmits a notification of a request for approval of the co-creator to the co-creator terminal (step S32 shown in FIG. 5). When the co-creator terminal that has received the notification of the request for approval of the co-creator approves the addition as a co-creator (step S33 shown in FIG. 5), the platform system approves the addition of the co-creator (step S34 shown in FIG. 5).

[0092] In step S34 shown in FIG. 5, when the platform system approves the addition of the co-creator, the platform system sends a request to issue a co-creator NFT to the blockchain (step S35 shown in FIG. 5) and notifies the co-creator terminal of the provisional issuance of the co-creator NFT (step S36 shown in FIG. 5). In addition, in step S35 shown in FIG. 5, when the blockchain receives the request to issue a co-creator NFT, a smart contract regarding the issuance of the co-creator NFT is concluded (step S37 shown in FIG. 5).

[0093] In step S35 shown in FIG. 5, after the platform system sends a request to issue a co-creator NFT to the blockchain, the owner terminal inputs an invitation to the co-creator terminal to join the project chat and sends it to the platform system (step S38 shown in FIG. 5). In step S39 shown in FIG. 5, the platform system sends an invitation to the co-creator terminal to join the project chat. The co-creator terminal approves the transmission in step S39.

[0094] When the smart contract for the issuance of the co-creator NFT is concluded in step S37 shown in FIG. 5, the blockchain notifies the platform system of the completion of issuance of the co-creator NFT (step S40 shown in FIG. 5), and the platform system sends a notification of issuance of the co-creator NFT to the co-creator terminal (step S41 shown in FIG. 5). This completes the flow for creating the co-creator NFT.

[0095] <Project participation flow> Next, a flow of participating in a project will be described with reference to Fig. 6. Note that the flow of participating in a project shown in Fig. 6 is an example, and is not limited to the flow described below.

[0096] First, in step S42 shown in FIG. 6, a project is searched for on the terminal, a list of projects is viewed, and the process proceeds to step S43 shown in FIG.

[0097] In step S43 shown in FIG. 6, the details of a desired project are viewed from the project list on the terminal, and if participation in the project is desired, the process proceeds to step S44 shown in FIG.

[0098] In step S44 shown in FIG. 6, an input is made on the terminal to purchase a ticket NFT to participate in the project, and this is transmitted to the server side, and the process proceeds to step S45 shown in FIG.

[0099] In step S45 shown in Fig. 6, it is determined whether the platform currency is sufficient to participate in the project. If the result is "insufficient", the process proceeds to step S46 shown in Fig. 6. If the platform currency is "sufficient", the process proceeds to step S47 shown in Fig. 6, and participation in the project is completed.

[0100] In step S46 shown in Fig. 6, after charging the platform currency in the charging flow, the process returns to step S45 shown in Fig. 6 and again determines whether the platform currency is sufficient to participate in the project. If the result is "sufficient," the process proceeds to step S47 shown in Fig. 6 and participation in the project is completed. This completes the flow of participating in the project.

[0101] <Ticket NFT creation flow> Next, a flow of creating a ticket NFT associated with participation in a project will be described with reference to Fig. 7. Note that the flow of creating a ticket NFT shown in Fig. 7 is an example, and is not limited to the flow described below.

[0102] First, when a fan terminal inputs a desire to participate in the project (step S51 shown in FIG. 7), the platform system sends a participation request notification from the fan terminal to the owner terminal (step S52 shown in FIG. 7), and also sends a ticket NFT issuance request to the blockchain (step S53 shown in FIG. 7), provisionally issuing a ticket NFT to the fan terminal (step S54 shown in FIG. 7). In addition, when the blockchain receives the ticket NFT issuance request, a smart contract regarding the issuance of the ticket NFT is concluded (step S55 shown in FIG. 7).

[0103] In step S56 shown in Fig. 7, an invitation to the fan terminal to join the chat for the project is input at the owner terminal and transmitted to the platform system. In step S57 shown in Fig. 7, a notification of an invitation to the chat for the project is transmitted from the platform system to the fan terminal, and in step S58 shown in Fig. 7, the transmission of step S57 is approved.

[0104] When the blockchain notifies the platform system of the completion of issuance of the ticket NFT in step S59 shown in Fig. 7, a notification of the issuance of the ticket NFT is sent to the communal fan terminal in step S60 shown in Fig. 7. This completes the flow of creating the ticket NFT.

[0105] <Poll creation flow> Next, a vote creation flow in a project will be described with reference to Fig. 8. Note that the vote creation flow shown in Fig. 8 is an example, and is not limited to the flow described below.

[0106] First, in step S61 shown in FIG. 8, a list of projects is viewed on a terminal, and in step S62 shown in FIG. 8, if the user does not own a follower NFT (S62: "Doesn't own"), the process proceeds to step S63 shown in FIG. 8, and if the user owns a follower NFT (S62: "Owns"), the process proceeds to step S64 shown in FIG. 8.

[0107] In step S63 shown in Fig. 8, the project participation flow is started (see Fig. 6), and after the participation in the project is completed, the vote creation flow is started again (see Fig. 8). In step S64 shown in Fig. 8, the desired project home is entered from the project list on the terminal, and the process proceeds to step S65 shown in Fig. 8.

[0108] In step S65 shown in FIG. 8, a list of chat rooms for the project is entered on the terminal, and in step S66 shown in FIG. 8, if the authority level of the terminal is less than "1" (S66: "<1"), viewing is not possible (step S67 shown in FIG. 8), and if the authority level of the terminal is greater than or the same as "1" (S66: ">=1"), the process proceeds to step S68 shown in FIG. 8.

[0109] In step S68 shown in FIG. 8, the desired chat room is entered from the chat room list on the terminal, and in step S69 shown in FIG. 8, if the user does not possess governance points (S69: "Not possessed"), voting is not possible (step S70 shown in FIG. 8), and if the user possesses governance points (S69: "Owned"), the process proceeds to step S71 shown in FIG. 8.

[0110] In step S71 shown in Fig. 8, voting settings are made, and voting starts in step S72 shown in Fig. 8. This completes the vote creation flow.

[0111] <Voting participation flow> Next, a flow of participation in voting in a project will be described with reference to Fig. 9. Note that the flow of participation in voting shown in Fig. 9 is an example, and is not limited to the flow described below.

[0112] First, in step S81 shown in FIG. 9, a list of projects is viewed on a terminal, and in step S82 shown in FIG. 9, if the user does not own a follower NFT (S82: "Not Owned"), the process proceeds to step S83 shown in FIG. 8; if the user owns a follower NFT (S82: "Owned"), the process proceeds to step S84 shown in FIG. 9.

[0113] In step S83 shown in Fig. 9, the project participation flow is started (see Fig. 6), and after the participation in the project is completed, the voting participation flow is started again (see Fig. 9). In step S84 shown in Fig. 9, the desired project home is entered from the project list on the terminal, and the process proceeds to step S85 shown in Fig. 9.

[0114] In step S85 shown in FIG. 9, a list of chat rooms for the project is entered on the terminal, and in step S86 shown in FIG. 9, if the authority level of the terminal is less than "1" (S86: "<1"), viewing is not possible (step S87 shown in FIG. 9), and if the authority level of the terminal is greater than or the same as "1" (S86: ">=1"), the process proceeds to step S88 shown in FIG. 9.

[0115] In step S88 shown in FIG. 9, the desired chat room is entered from the chat room list on the terminal, and in step S89 shown in FIG. 9, if the user does not possess governance points (S89: "Not possessed"), voting is not possible (step S90 shown in FIG. 9), and if the user possesses governance points (S89: "Owned"), the process proceeds to step S91 shown in FIG. 9.

[0116] In step S91 shown in Fig. 9, the vote list is viewed on the terminal, in step S92 shown in Fig. 9, the vote details are viewed on the terminal, and in step S93 shown in Fig. 9, the vote selection is input and transmitted on the terminal. This completes the voting participation flow.

[0117] <Effects Obtained by the Present Embodiment> According to this embodiment having the above configuration, the owner 101 and the co-creator 102 can create, publish, and view content on the platform system 100, and can also receive a share of the profits earned from projects PJ1, PJ2, PJ3, etc. In addition, the fan 103 can view content by purchasing a fan token on the platform system 100. The owner 101, the co-creator 102, and the fan 103 can each perform various exchanges and various processes related to projects PJ1, PJ2, PJ3, etc. with the terminals of other participants via their terminals.

[0118] As a result, according to this embodiment, it becomes possible for multiple people to simultaneously create content on the platform system 100, and it becomes possible to conclude contracts relating to rights such as copyrights and handling of income and expenditure, and to execute and manage these contracts on the platform system 100.

[0119] Therefore, according to the present embodiment, it is possible to facilitate the participation of multiple people in co-creation activities, thereby promoting the utilization of human resources in content creation.

[0120] The platform system according to the present invention can be understood as something disclosed in the following embodiment 2 in addition to the embodiment 1. Hereinafter, a second embodiment of the present invention will be described with reference to Fig. 10. Note that the same components as those in the first embodiment are given the same reference numerals and detailed description thereof will be omitted.

[0121] <Overview of the platform system according to the second embodiment> The platform system 200 of this embodiment shown in Fig. 10 is configured to include a blockchain network 10 and a server device 20 connected to the blockchain network 10, similar to the platform system 100 of embodiment 1 (see Fig. 2). Below, for each component of the platform system 200, the configurations and functions that differ from those of embodiment 1, or the configurations and functions that are further added to the components in embodiment 1 will be described.

[0122] <About the server device> The server device 20 includes a server 21 and a database 22, similar to the platform system 100 of the first embodiment (see FIG. 2).

[0123] <About the server> The server 21 enables a participant terminal (for example, the terminal 13 in FIG. 10) who wishes to participate in the project pages PJP1, PJP2, PJP3, . . . to be connected to the block chain network 10.

[0124] The token issuing unit 25 in the server 21, in addition to the functions in embodiment 1, is a functional unit that issues tokens (owner token, co-creator token) to the terminal 11 that has transmitted the basic information of the projects PJ1, PJ2, PJ3, etc., in conjunction with the creation of project pages PJP1, PJP2, PJP3, etc. in accordance with the classification of the basic information of the projects PJ1, PJ2, PJ3, etc. received from the terminal 11.

[0125] The issuance of the above tokens is similar to the “Owner NFT Creation Flow” (see Figure 4) and the “Co-Creator NFT Creation Flow” (see Figure 5) described in embodiment 1.

[0126] In addition, for example, when terminal 13 is a participant terminal that wishes to participate in project pages PJP1, PJP2, PJP3, etc. as a fan of the content, the token issuing unit 25 is capable of issuing fan tokens linked to projects PJ1, PJ2, PJ3, etc. to this terminal 13.

[0127] The issuance of the above fan tokens is similar to the “Ticket NFT creation flow” described in embodiment 1 (see Figure 7).

[0128] As described above, the wallet management unit 26 in the server 21 is a functional unit that stores tokens issued to the terminal 11 in conjunction with the creation of the project pages PJP1, PJP2, PJP3, . . . .

[0129] Furthermore, the wallet management unit 26 is capable of storing tokens linked to the projects PJ1, PJ2, PJ3, . . . that are issued to terminals 13 that wish to participate in the project pages PJP1, PJP2, PJP3, . . . as fans of the content.

[0130] Therefore, when terminal 13 provides economic benefits, including money, to project pages PJP1, PJP2, PJP3, etc., terminal 13 that has been issued a fan token can provide the economic benefits, including money, using the fan token stored in the wallet management unit 26 on the blockchain network 10.

[0131] The above-mentioned "provision of economic benefits, including money" includes, for example, so-called "social tipping," in which fans who have viewed content published online by a creator or distributor send money online to the creator or distributor as a sign of support or gratitude.

[0132] In addition, when a terminal 13 makes labor and service contributions to project pages PJP1, PJP2, PJP3, etc., the terminal 13 that has made the labor and service contributions can obtain fan tokens from the server 21 on the blockchain network 10 as compensation for the labor and service contributions.

[0133] The above "contributions of labor and services" include, for example, actions such as reviewing content and writing comments on project pages PJP1, PJP2, PJP3, etc., and sharing and spreading information about projects PJ1, PJ2, PJ3, etc. on social media.

[0134] The fan tokens include premium tokens. Here, the "premium tokens" are tokens that grant various rights to terminals 13 that have been issued with premium tokens that cannot be obtained by terminals 13 that have not been issued with premium tokens. The "various rights" are rights that allow only fans of a specific terminal 13 that has been issued with a premium token to obtain rare privileges, including the right to view initial setting materials related to content creation for projects PJ1, PJ2, PJ3, etc., and materials that are not made public on project pages PJP1, PJP2, PJP3, etc. (but are not limited to the above).

[0135] The terminal 13 that has been issued the premium token can provide economic benefits, including money, or contribute labor and services on the blockchain network 10. Therefore, the owners 101 of the projects PJ1, PJ2, PJ3, etc. can easily raise funds for the initial stage of carrying out the projects PJ1, PJ2, PJ3, etc., and can easily promote the projects PJ1, PJ2, PJ3, etc.

[0136] The contract conclusion unit 31 in the server 21 is a functional unit that enables the buying and selling of tokens between multiple terminals 11 and 13 by concluding a smart contract on the blockchain network 10, and also enables contracts regarding content between multiple terminals 11 and 13 by concluding a smart contract on the blockchain network 10.

[0137] The "content-related contract" may be any of a variety of contracts, including a contract regarding the use of content and a contract regarding the transfer of copyright of content.

[0138] Furthermore, when concluding the smart contract, the contract conclusion unit 31 can provide format information 39 regarding the conclusion of the smart contract. Examples of the "format information" include templates of various contracts including contracts regarding the buying and selling of various tokens, contracts regarding secondary use of content, and contracts regarding the transfer of copyrights of content.

[0139] <About the database> In the present embodiment, the database 22 stores format information 39 as one of various types of information.

[0140] <Effects Obtained by the Present Embodiment> According to the present embodiment having the above configuration, in addition to the effects of the first embodiment, the following effects can be achieved.

[0141] In other words, according to this embodiment, it is possible to issue and store various tokens in server 21, and it is also possible to issue and store tokens linked to a project to participant terminals who wish to participate in the project, and to connect the participant terminals to the blockchain network. Therefore, when linking content and information related to the content using NFT (i.e., converting the content into NFT), it is possible to easily convert the content into NFT without the need for the content creator or other co-creator to first create a wallet for electronically storing virtual currency and connect it to a platform that provides digital content trading services.

[0142] Therefore, according to this embodiment, it is possible to easily link NFT content with information related to the content, thereby making it possible to promote the distribution and use of NFT content.

[0143] The configurations described in the above embodiment can be modified as appropriate within the scope of the present invention, and are not limited to the configurations of the above embodiment. [Explanation of symbols]

[0144] 10. Blockchain network 11, 12, 13, 23...Terminal 20...Server equipment 21…Server 22…Database 24…Project Delivery Department 25…Token issuing department 26…Wallet Management Department 27…Revenue Management Department 28…Revenue Distribution Department 29…Search section 30…Application Management Department 31…Contract conclusion section 32…Voting Rights Registration Department 33…Voting Department 34…Points Management Department 35…Additional function section 36…Project Information 37…Transaction information 38...Token Identifier Information 39…Format information 100, 200… Platform System 101…Project Owner 102…Co-creator 103...Fan 104…Content PJ1, PJ2, PJ3…Projects PJP1, PJP2, PJP3…Project page

Claims

1. A platform system including a participant terminal participating in a content creation project and a server connected to a blockchain network consisting of a plurality of the participant terminals, The participant terminal includes: When creating a project, basic information of the project can be input and transmitted to the server, and transactions can be performed between the project and other participant terminals; The server, A platform system capable of creating and managing a project page according to the classification of the basic information of the project received from the participant terminal, issuing and storing tokens to the participant terminal that sent the basic information of the project in conjunction with the creation of the project page, issuing and storing tokens linked to the project to participant terminals who wish to participate in the project, and connecting the participant terminals to the blockchain network.

2. The server, The platform system described in claim 1, characterized in that a contract regarding the content between the participant terminals can be concluded by concluding a smart contract on the blockchain network.

3. The server, The platform system described in claim 1 or 2, characterized in that when the smart contract is concluded between the participant terminals, format information regarding the conclusion of the smart contract can be provided to the participant terminals.

4. When the participant terminal provides economic benefits, including money, to the project page, The server, When the participant terminal is a participant terminal that participates in the project page as a fan of the content, fan tokens can be issued and stored for the participant terminal; The participant terminal that has received the fan tokens, The platform system described in claim 1, characterized in that it is possible to provide economic benefits including money using the fan tokens stored on the server on the blockchain network.

5. When the participant terminal makes a contribution of labor or services to the project page, The server, When the participant terminal is a participant terminal that participates in the project page as a fan of the content, fan tokens can be issued and stored for the participant terminal; The participant terminal that has contributed the labor and services is The platform system described in claim 1, characterized in that the fan tokens can be obtained from the server on the blockchain network as compensation for the labor and service contributions.

6. The fan tokens issued and stored on the server include premium tokens; The participant terminal that has received the premium token, The platform system according to claim 4 or 5, characterized in that it is possible to provide economic benefits including money, or to make contributions of labor and services, on the blockchain network.

7. A platform system including a participant terminal participating in a content creation project and a server connected to a blockchain network consisting of a plurality of the participant terminals, The participant terminal includes: When creating a project, basic information of the project is input and transmitted to the server, and when participating in an existing project, an application to participate is transmitted to the server, and transactions with other participant terminals are made possible; The server, A platform system characterized by creating and managing a project page according to the classification of basic information of the project received from the participant terminal, being able to make the created project page public to each participant terminal, providing desired rules regarding the operation of the project to the participant terminal that applies to participate in the project, and enabling the conclusion of a smart contract on the blockchain network between the participant terminal and the participant terminal that inputs and transmits its agreement to the rules.

8. The server, The platform system according to claim 7, characterized in that a token is issued and granted to the participant terminal belonging to the project page according to the role of the participant, and the token is managed.

9. The server, A platform system as described in claim 8, characterized in that when the participant terminal is the participant terminal that created the project page, an owner token is issued and granted to the participant terminal, and the owner token is managed.

10. The server, The platform system described in claim 8, characterized in that when the participant terminal is a participant terminal participating in the project as a fan of the created content, fan tokens are sold to the participant terminal and the fan tokens are managed.

11. The server, The platform system described in claim 10, characterized in that the revenue from the sale of the fan tokens is stored in accordance with the smart contract and distributed to each participant terminal.

12. The platform system according to claim 8, characterized in that on the project page, restrictions on viewing of the content by each participant terminal are determined according to the category of the token held by each participant terminal.

13. The server, The platform system described in claim 7, characterized in that, in accordance with the smart contract, each participant terminal is assigned governance points indicating the proportion of contribution it can make to decision-making in the project, and revenue points indicating the proportion of the profits earned from the project, and information on the governance points and revenue points is managed.

14. The server, The platform system described in claim 7, characterized in that in accordance with the smart contract, commitment points indicating the degree of contribution to the project are assigned to each participant terminal, information on the commitment points is managed, and rewards determined for each project are allocated according to the commitment points.

15. The project page is Each participant terminal is capable of inputting voting information for decision-making in the project and transmitting the information to the server; The server, A process is executed based on the received voting information and the amount of governance points held by each participant terminal, and the voting result derived by this process is transmitted to the project page. The platform system according to claim 13 .

16. The platform system described in claim 7, characterized in that the transactions between each participant terminal on the project page are irreversibly recorded on the blockchain network.

Images