Trying supporting system

Abstract

To provide a trying supporting system which allows a user who wants to try a task to achieve the task with a higher success rate.SOLUTION: The present invention includes: a terminal-side contrast generation unit for sending, to a block chain network, contract conditions including the conditions for achieving a task and the length of time to try the task, the amount of funds to deposit for the task, the setting of distribution of the funds in a case where the task has been done successfully, and the setting of distribution of the funds in a case where the task has been done unsuccessfully; and a determination data sending unit for sending, to the block chain network, the determination data used to determine whether the contract conditions are satisfied.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a challenge support system.

Background Art

[0002] People sometimes have tasks that they want to achieve but are unable to achieve. Examples of such tasks include walking for health maintenance and improvement, going for a medical check-up, quitting smoking, studying English conversation, and the like.

[0003] In the case of this type of task, often people other than the person performing the task expect the person to achieve the task for the sake of their health or skill acquisition. For example, the father of a person leading an unhealthy lifestyle wishes to somehow get that person to engage in healthy activities such as walking, and the person's wife and children wish for that person to be healthy for a long time and want to support that person's efforts in healthy activities.

Summary of the Invention

Problems to be Solved by the Invention

[0004] In many cases of this type of task, there is no strict deadline for completion, and even if the task is not completed by the self-set deadline, there is no immediate demerit, so there are many cases where the task remains uncompleted indefinitely.

[0005] Also, it is difficult for other people who expect the person to achieve the task to continuously and actively support the person in a situation where there is no immediate merit for themselves.

[0006] Therefore, an object of the present invention is to provide a challenge support system that increases the possibility of a user challenging a task to achieve the task.

Means for Solving the Problems

[0007] A challenge support system according to an aspect of the present invention includes a blockchain network and an operator server. The operator server has a contract generation unit that transmits contract conditions regarding tasks to be achieved by a user to the blockchain network. The contract conditions include conditions for achieving the tasks and a deadline for achieving the tasks. The operator server also has an entry reception unit that receives information indicating an entry to a task from a participant terminal, and a participant information transmission unit that transmits information of the participant who has received the entry to the blockchain network. The participant terminal has an entry unit that transmits information indicating an entry to a task to the operator server, and a setting transmission unit that transmits to the blockchain network the amount of funds to be deposited for a task, the setting of the distribution of funds in case of success of the task, and the setting of the distribution of funds in case of failure of the task. The setting of the distribution of funds in case of success and the setting of the distribution of funds in case of failure each include one or more distribution destinations and the amount of money distributed to each distribution destination. The participant terminal also has a determination data transmission unit that transmits determination data used to determine whether the contract conditions are satisfied to the blockchain network. The smart contract of the blockchain network determines whether the contract conditions are satisfied based on the determination data transmitted from the participant terminal. If the contract conditions are satisfied by the deadline, the funds are transferred to each distribution destination according to the setting of the distribution of funds in case of success of the task. If the contract conditions are not satisfied by the deadline, the funds are transferred to each distribution destination according to the setting of the distribution of funds in case of failure of the task.

[0008] In the challenge support system, the operator server further includes a key generation unit that generates information for participating in a task and stores it in a storage unit communicably connected to the operator server. The entry reception unit receives information for participating in a task from the participant terminal, and may receive an entry from the participant terminal when the information for participating in the task received from the participant terminal matches the information stored in the storage unit.

[0009] In the above challenge support system, the operator server further includes a content reception unit that receives content and information for identifying the content from the determination data transmission unit of the participant terminal and stores them in a storage unit communicably connected to the operator server. The determination data transmission unit of the participant terminal may transmit determination data including information for identifying the content to the blockchain network and transmit the content and the information for identifying the content to the operator server.

[0010] In the above challenge support system, the prover terminal further includes a transmission unit that transmits the information of the prover to the operator server and a determination data transmission unit that transmits determination data used for determining whether the contract conditions are satisfied to the blockchain network. The operator server further includes a prover registration unit that receives the information of the prover from the prover terminal. The participant information transmission unit may transmit the information of the prover to the blockchain network.

[0011] In the above challenge support system, the participant terminal may include a first participant terminal including at least an entry unit and a setting transmission unit, and a second participant terminal including at least a determination data transmission unit.

[0012] In the above challenge support system, the operator server further includes a token contract generation unit that transmits data related to tokens for each participant to the blockchain network. The smart contract of the blockchain network may transmit tokens to the token contract generated in the blockchain network by transmitting data related to the tokens when the contract conditions are satisfied by the deadline.

[0013] A terminal device according to another aspect of the present invention includes an entry unit that transmits information indicating an entry to a task to be achieved by a user to an operator server, an amount of funds to be deposited for the task, a fund distribution setting at the time of task success, and a fund distribution setting at the time of task failure to a blockchain network, the setting transmission unit including, in the fund distribution setting at the time of success and the fund distribution setting at the time of failure, one or more distribution destinations and an amount to be distributed to each distribution destination, and a determination data transmission unit that transmits determination data used to determine whether contract conditions are satisfied to the blockchain network.

[0014] A method according to another aspect of the present invention includes a step in which a computer transmits information indicating an entry to a task to be achieved by a user to an operator server, a step in which an amount of funds to be deposited for the task, a fund distribution setting at the time of task success, and a fund distribution setting at the time of task failure are transmitted to a blockchain network, the fund distribution setting at the time of success and the fund distribution setting at the time of failure including one or more distribution destinations and an amount to be distributed to each distribution destination, respectively, and a step in which determination data used to determine whether contract conditions are satisfied is transmitted to the blockchain network.

[0015] A program according to another aspect of the present invention causes a computer to execute a process of transmitting information indicating an entry to a task to be achieved by a user to an operator server, a process of transmitting an amount of funds to be deposited for the task, a fund distribution setting at the time of task success, and a fund distribution setting at the time of task failure to a blockchain network, the fund distribution setting at the time of success and the fund distribution setting at the time of failure including one or more distribution destinations and an amount to be distributed to each distribution destination, respectively, and a process of transmitting determination data used to determine whether contract conditions are satisfied to the blockchain network.

[0016] A terminal device according to another aspect of the present invention includes a terminal-side contract generation unit that transmits contract conditions including conditions for achieving a task and a period for challenging the task, the amount of funds deposited for the task, a fund distribution setting at the time of task success, and a fund distribution setting at the time of task failure to a blockchain network, and a determination data transmission unit that transmits determination data used for determining whether the contract conditions are satisfied to the blockchain network.

[0017] The terminal device includes a first terminal device including at least the terminal-side contract generation unit and a second terminal device including at least the determination data transmission unit. The terminal-side contract generation unit may further transmit information of a person who determines whether the contract conditions are satisfied to the blockchain network, and the second terminal device may transmit the determination data together with information associated with the information of the person who determines.

[0018] A system according to another aspect of the present invention includes a terminal device including a first means for transmitting contract conditions including conditions for achieving a task and a period for challenging the task, the amount of funds deposited for the task, a fund distribution setting at the time of task success, and a fund distribution setting at the time of task failure to a server device, and a second means for transmitting determination data used for determining whether the contract conditions are satisfied to the server device, and a server device communicably connected to the terminal device, the server device including means for receiving the contract conditions, the amount of funds, the fund distribution setting at the time of task success, and the fund distribution setting at the time of task failure from the terminal device and storing them in a storage unit, means for confirming the deposit of funds from a user specified by the terminal device to a predetermined account, means for determining whether the contract conditions are satisfied based on the determination data received from the terminal device, and means for moving funds from a predetermined account to each distribution destination according to the fund distribution setting at the time of task success when the contract conditions are satisfied during the period, and means for moving funds from a predetermined account to each distribution destination according to the fund distribution setting at the time of task failure when the contract conditions are not satisfied during the period.

[0019] In the system, the terminal device includes a first terminal device having at least a first means and a second terminal device having at least a second means. The first means may further transmit to the server device the information of the person who determines whether the contract conditions are satisfied. The second terminal device may transmit determination data together with the information associated with the information of the person who determines.

[0020] An information processing system according to another aspect of the present invention includes means for receiving from a first terminal device contract conditions including conditions for achieving a task and a period for challenging the task, an amount of funds deposited for the task, a fund distribution setting at the time of success of the task, and a fund distribution setting at the time of failure of the task and storing them in a storage unit, means for confirming the deposit of funds from a user specified by the first terminal device to a predetermined account, means for receiving determination data used for determining whether the contract conditions are satisfied from a second terminal device, means for determining whether the contract conditions are satisfied based on the determination data, and means for transferring funds from a predetermined account to each payee according to the fund distribution setting at the time of success of the task when the contract conditions are satisfied during the period, and transferring funds from a predetermined account to each payee according to the fund distribution setting at the time of failure of the task when the contract conditions are not satisfied during the period.

Effect of the Invention

[0021] According to the present invention, it is possible to provide a challenge support system that increases the possibility for a user who challenges a task to achieve the task.

Brief Description of the Drawings

[0022]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Embodiments for Carrying Out the Invention

[0023] Embodiments of the present invention will be described with reference to the accompanying drawings. Note that the following embodiments are for facilitating the understanding of the present invention and are not for limiting the interpretation of the present invention. Further, the present invention can be variously modified without departing from its gist. Furthermore, those skilled in the art can adopt embodiments in which each element described below is replaced with an equivalent one, and such embodiments are also included in the scope of the present invention.

[0024] (System Configuration) Figure 1 shows a configuration example of a challenge support system according to an embodiment of the present invention. The challenge support system 1 includes an operator server 10, a blockchain network 20, fund provider terminals 30 (30a to 30L), challenger terminals 40 (40a to 40M), prover terminals 50 (50a to 50N), and a sponsor company server 60, and these are configured to communicate via a network N. The blockchain network 20 includes a smart contract.

[0025] In this embodiment, the blockchain network 20 is a system that uses a blockchain as a ledger and a plurality of nodes share and manage this ledger. The blockchain is data in which a plurality of blocks are connected in a chain in chronological order, and each block includes transaction data for a certain period. In the technology of the blockchain, since a plurality of blocks are added while retaining past information, it has the characteristic that it is difficult to falsify the history. In this embodiment, Ethereum, which can implement a smart contract, is used as the blockchain network 20, but other blockchain networks that can implement a smart contract may also be used.

[0026] Figure 2 is a schematic diagram showing an example of information processing in a challenge support system according to an embodiment of the present invention.

[0027] It is assumed that a sponsor company and an operator have previously concluded a contract to support a challenger who takes on a predetermined task. Here, a campaign of a beverage manufacturer that supports a challenger who takes on a task related to a health activity will be described as an example. Also, here, as in the example shown in the lower center of Figure 13, an example where the challenger is user A, the fund provider is user B, the father of user A who supports the health activity of user A, and the challenger and the fund provider are different will be described. Also, the prover is a third party who proves the health activity of the challenger, and here, it is a fitness club.

[0028] In addition, the operator and the beverage manufacturer have previously generated an Ethereum account (EOA: Externally Owned Account). It is assumed that the storage unit of the operator server 10 and the storage unit of the sponsoring company server 60 store the private key generated at the time of generating the Ethereum account and the public address generated from the public key issued simultaneously with the private key at the time of generating the Ethereum account, respectively. The part where the private key is stored in the storage units of the operator server 10 and the sponsoring company server 60 is usually not connected to the network and is connected to the network only when necessary to enhance security.

[0029] The operator server 10 compiles, using solc, contract code including information such as the public address of the operator, the public address of the sponsoring company, the entry start date and time, the entry end date and time, the challenge start deadline, the challenge period, the smart contract conclusion date and time, and the contract content, which is described in the Solidity language, and transmits it as a transaction to the blockchain network 20 (S1). When the transaction transmitted from the operator server 10 is approved in the blockchain network 20, a smart contract is generated and its contract account is issued (S2).

[0030] The operator server 10 generates, for the number of entries to the sponsoring company's campaign, a pair of a private key S and a public key S for participating in the sponsoring company's campaign (S3), and generates a seal on which a code obtained by encoding the private key S is printed (S4). The code records information by means of the light and dark pattern of modules, and includes a barcode in which the modules are arranged only horizontally, a two-dimensional code in which the modules are arranged in a matrix vertically and horizontally, and the like. In addition, the operator server 10 stores the public address S generated using the public key S in a database (DB) provided in the operator server 10 (S5), and discards the private key S. The generated seal is delivered to the sponsoring company and attached to products handled by the sponsoring company, such as drinking water.

[0031] Challenger User A and Funding Provider User B download Challenge App 70 from the operator's site to their own terminals in advance, and use Challenge App 70 to generate a unique pair of private key M and public key M for each user. When the public key M is generated, Challenge App 70 generates public address M using the public key M and sends the generated public address M to Operator Server 10 (S6, S7). When receiving the public address M, Operator Server 10 saves the public address M in the DB (S8, S9).

[0032] User B who supports User A's task success purchases a sealed beverage maker product, reads the code printed on the seal via Challenge App 70 installed on Funding Provider Terminal 30, and from Funding Provider Terminal 30, sends the public address S generated using the public key S generated from the read private key S and their own public address M to Operator Server 10 (S10). When the sent public address S matches the public address S stored in the DB, Operator Server 10 accepts the entry into the beverage maker's campaign and registers User B's public address M as the funding provider for the beverage maker's campaign (S11). The sponsoring company may transfer a small amount of the virtual currency ETHER on Ethereum to each public address M for which the campaign entry is completed.

[0033] After prior qualification by the operator, the person in charge of the prover's fitness club downloads Prover App 80 from the operator's site to Prover Terminal 50 and uses Prover App 80 to generate a unique pair of private key T and public key T for each prover. When the public key T is generated, Prover App 80 generates public address T using the public key T and sends the generated public address T to Operator Server 10 (S12). When receiving the public address T, Operator Server 10 saves the public address T in the DB (S13).

[0034] The operator server 10 transmits the public address M and the public address T registered in the database in association with the beverage manufacturer's campaign as a transaction to the blockchain network 20 (S14). When the transaction transmitted from the operator server 10 is approved in the blockchain network 20, the public address M and the public address T are held in the smart contract (S15).

[0035] The fund provider user B transmits, via the challenge app 70 installed on the fund provider terminal 30, the setting data including the amount of funds to be deposited for the task, the public address M of the challenger user A, the fund distribution setting when the task is successful, the fund distribution setting when the task fails, etc. as a transaction to the blockchain network 20 (S16). Here, for the fund distribution setting, any number of distribution destinations can be selected from a plurality of distribution destinations holding the Ethereum public address, for example, the challenger user A, the spouse or child of user A, organizations such as the Japanese Red Cross Society and UNICEF, etc., and an arbitrary amount can be specified. When the transaction transmitted from the fund provider terminal 30 is approved in the blockchain network 20, the setting data is held in the smart contract (S17).

[0036] After that, the challenger user A transmits, from the challenger terminal 40, the data serving as evidence of the health activity as a transaction to the blockchain network 20 (S18). When the transaction transmitted from the challenger terminal 40 is approved in the blockchain network 20, the data serving as evidence is held in the smart contract (S19). Also, the fitness club of the prover also transmits, from the prover terminal 50, the data serving as evidence of the health activity of user A as a transaction to the blockchain network 20 (S20). When the transaction transmitted from the prover terminal 50 is approved in the blockchain network 20, the data serving as evidence is held in the smart contract.

[0037] If User A accomplishes a task by satisfying the contract conditions before the smart contract conclusion date and time and during the challenge period, the smart contract is automatically executed, and funds are distributed according to the fund distribution settings at the time of task success. Note that for the determination of time such as the smart contract conclusion date and time, the timestamp information of the blockchain network 20 may be used, or the timestamp information issued by the time certification authority embedded in the transaction by the sender of the transaction may be used.

[0038] If User A fails to accomplish the task before the smart contract conclusion date and time and during the challenge period, when the smart contract has a mechanism to periodically obtain information regarding the date and time by itself, at the point in time when the information regarding the date and time is acquired, it is determined that the task could not be accomplished, the smart contract is automatically executed, and funds are distributed according to the fund distribution settings at the time of task failure. If User A fails to accomplish the task before the smart contract conclusion date and time and during the challenge period, when the smart contract does not have a mechanism to periodically obtain information regarding the date and time by itself, the operator server or the like periodically sends a transaction including the date and time to the smart contract, and at the point in time when the transaction is authenticated on the blockchain, it is determined that the task could not be accomplished, the smart contract is automatically executed, and funds are distributed according to the fund distribution settings at the time of task failure.

[0039] Note that the language used by the operator server 10 is not limited to the Solidity language, and other languages capable of implementing smart contracts can be used. Also, the download of the challenge app 70 and the prover app 80 is not limited to the operator's website, and challengers and provers may download from websites operated by other parties.

[0040] (Operator Server Configuration) FIG. 3 shows the configuration of the operator server 10 according to an embodiment of the present invention. In FIG. 3, a single operator server 10 is assumed, and only the necessary functional configurations are shown. However, the operator server 10 can also be configured as part of a multi-functional distributed system by a plurality of computer systems.

[0041] The operator server 10 is a server device having a function of communicating with the blockchain network 20, the fund provider terminal 30, the challenger terminal 40, the prover terminal 50, and the sponsor company server 60 via the network N. As shown in FIG. 3, the operator server 10 includes an input unit 11, a control unit 12 including a CPU and a memory, a storage unit 13, and a communication unit 14 for connecting to the network N.

[0042] When the program stored in the storage unit 13 is read into the RAM and executed by the CPU, the control unit 12 functions as a site providing unit 121, a member registration unit 122, a prover registration unit 123, a contract generation unit 124, a key generation unit 125, an entry reception unit 126, a participant information transmission unit 127, a challenger reception unit 128, and a content reception unit 129. Further, it is desirable that the storage unit 13 has a campaign DB 131, a member DB 132, a prover DB 133, a content DB 134, a secret key 135, and a public address 136.

[0043] The campaign DB 131 stores information related to the campaign. In one embodiment, it is desirable that a plurality of public addresses S are registered in the campaign DB 131 in association with the campaign ID and the contract account. The campaign ID stores an ID that uniquely identifies the campaign. Note that the ID in this specification is information consisting of one or more of Chinese characters, hiragana, katakana, alphanumeric characters, symbols, etc. The contract account is information that uniquely identifies a smart contract generated on the blockchain network 20. The public address S is information generated using the public key S of a pair of secret key and public key generated for the campaign.

[0044] The member DB 132 stores information about the members of the challenge support system 1. In one embodiment, it is desirable that the member DB 132 registers name, gender, date of birth, public address M, related campaigns, etc. The public address M is information that uniquely identifies a member of the challenge support system 1. The related campaigns store the campaign ID associated with the user of the public address M and the participation attribute in the campaign. For the participation attribute, for example, "fund provider" indicating that the user is a fund provider of the campaign, "challenger" indicating that the user is a challenger of the campaign, etc. are set. Note that the related campaigns can store information about any campaign associated with the user of the public address M.

[0045] The prover DB 133 stores information about the provers of the challenge support system 1. In one embodiment, it is desirable that the prover DB 133 registers prover name, prover qualification, location, public address T, designated campaigns, etc. The public address T is information that uniquely identifies a prover of the challenge support system 1. The designated campaigns store information about the campaigns for which the prover has been qualified by the operator.

[0046] In one embodiment, for the designated campaigns, if the operator has qualified for a specific campaign, the campaign ID of the specific qualified campaign is stored, and if the operator has qualified for all campaigns, "ALL" indicating that all campaigns have been qualified is stored. Also, in one embodiment, after the qualification by the operator, the operator's user may be allowed to store data in the designated campaigns.

[0047] The content DB 134 stores information about content such as images and voices, which serves as evidence of activities for achieving the tasks of the challenge support system 1. In one embodiment, it is desirable that the content DB 134 register a content address and the content. The content address is information that uniquely identifies the content. In one embodiment, a hash value generated from image data or the like may be used as the content address.

[0048] The private key 135 stores the private key generated when an Ethereum account is created. The private key 135 is usually stored offline and is desirably connectable as needed.

[0049] The public address 136 stores the public address generated from the public key generated simultaneously with the private key issued when an Ethereum account is created.

[0050] The site providing unit 121 provides a site for using the challenge support system 1 on the network N. On this site, fund providers, challengers, reimbursers who are the destinations for fund repayment can register as members, certifiers can register as certifiers, and users who have already registered as members or certifiers can download the challenge app 70 or the certifier app 80. For this purpose, the site providing unit 121 transmits a web page described in HTML (HyperText Markup Language) or the like to the terminal used by the user, and receives input results and the like from the user from the terminal.

[0051] The membership registration unit 122 receives membership information from the user's terminal and registers it in the membership DB 132. In the present embodiment, when membership information is transmitted from the terminal in response to the user's operation on the membership registration screen provided by the site providing unit 121, the membership registration unit 122 registers a record in the membership DB 132 based on the received membership information. The membership information includes name, gender, date of birth, and the like.

[0052] In addition, when the membership registration unit 122 receives the public address M from the terminal that has downloaded the challenge app 70 along with the user identification information, it saves the public address M in the record of the member DB 132 specified by the user identification information. The user identification information can be information generated using part or all of the member information obtained by having the user input it, for example, at the time of installation or startup of the challenge app 70.

[0053] The prover registration unit 123 receives prover information from the prover terminal 50 and registers it in the prover DB 133. In the present embodiment, when prover information is transmitted from the prover terminal 50 in response to a user operation on the prover registration screen provided by the site providing unit 121, the prover registration unit 123 registers a record in the prover DB 133 based on the received prover information. The prover information includes the prover name, prover qualification, location, etc.

[0054] In addition, when the prover registration unit 123 receives the public address T from the prover terminal 50 that has downloaded the prover app 80 along with the prover identification information, it saves the public address T in the record of the prover DB 133 specified by the prover identification information. The prover identification information can be information generated using part or all of the prover information obtained by having the prover input it, for example, at the time of installation or startup of the prover app 80.

[0055] The contract generation unit 124 compiles information such as the public address of the operator, the public address of the sponsoring company, the entry start date and time, the entry end date and time, the challenge start deadline, the challenge period, the smart contract conclusion date and time, etc., and the contract code describing the contract content, which are described in the Solidity language, using solc, and transmits it as a transaction to the blockchain network 20 to generate a smart contract. In addition, the contract generation unit 124 saves the contract account issued at the time of generating the smart contract in the campaign DB 131. In the present embodiment, the contract generation unit 124 generates a smart contract as shown in FIG. 7.

[0056] As shown in FIG. 7, in this embodiment, the generated smart contract includes a fund provider data array for storing various setting data from the fund provider, the number of entries into the campaign. For example, in this embodiment, the fund provider data includes the fund provider, the amount of funds, the challenger, the prover, the fund distribution setting when the task is successful, and the fund distribution setting when the task fails, and the value at the time of smart contract generation is null. Through the processing of the participant information transmission unit 127 of the operator server 10 and the setting transmission unit 334 of the fund provider terminal 20 described later, data is stored in each item of the fund provider data.

[0057] In addition, the fund distribution settings each include repayment, donation, and confiscation. From the fund provider terminal 30, a distribution setting is sent such that the total amount of the amounts specified for repayment, donation, and confiscation matches the amount of funds. For repayment, any repayment destination holding an Ethereum public address and any amount can be specified. For donation, any donation destination holding an Ethereum public address and any amount can be specified. For confiscation upon success, usually, the operator fee paid to the operator is set, but any amount equal to or more than the operator fee may be set. For confiscation upon failure, any amount equal to or more than the operator fee can be specified. Further, a bonus may be included in the fund distribution setting upon success. For the bonus, the distribution destination of the funds sent as a bonus when the task is successful can be specified.

[0058] The key generation unit 125 generates a pair of a private key S and a public key S used to verify the user who enters the campaign of the sponsoring company, the number of entries into the campaign. Further, the key generation unit 125 generates a public address S using the public key S and stores it in the campaign DB 131 in association with the campaign ID. The campaign ID may be generated by the key generation unit 125 or may be generated in advance by other functional units of the operator server 10.

[0059] In one embodiment, the key generation unit 125 generates and outputs a code obtained by encoding the secret key S. In this embodiment, the operator generates a seal printed with the encoded code and delivers it to the sponsoring company. However, in another embodiment, the sponsoring company that has obtained the data of the encoded code may generate a seal printed with the encoded code.

[0060] The entry reception unit 126 receives the public address S and the public address M of the user of the fund provider terminal 30 from the fund provider terminal 30, and determines whether the received public address S matches the public address S stored in the campaign DB 131. If they match, the entry reception unit 126 stores the campaign ID associated with the public address S and the participation attribute "fund provider" as related campaigns in the record of the corresponding public address M in the member DB 132. Note that, in order to avoid duplicate use of the public address S, when the received public address S matches the public address S stored in the campaign DB 131, the entry reception unit 126 may set the public address S stored in the campaign DB 131 as "used" and make it non-reusable, or delete it.

[0061] The participant information transmission unit 127 transmits the public address M and the public address T registered in the DB in association with the campaign to the blockchain network 20 as a transaction in order to store them in the smart contract of the campaign. Note that the participant information transmission unit 127 may transmit the received public address M and the public address T as a transaction in response to the entry reception unit 126 receiving the public address M, or may collect the public addresses M received within a certain period and transmit them as a transaction together with the public address T at a predetermined interval. As a result, the transmitted public address M is stored in the "fund provider" of the fund provider data in the smart contract, and the public address T transmitted together with the public address M is stored in the "certifier".

[0062] The challenger reception unit 128 receives information about the campaign and the public address M of the challenger from the fund provider terminal 30, and in the record of the corresponding public address M in the member DB 132, saves the campaign ID specified by the information about the campaign and the participation attribute "challenger" as the relevant campaign. In this embodiment, the challenger reception unit 128 receives the contract account and the public address M from the fund provider terminal 30, and saves the campaign ID specified by the contract account and the participation attribute "challenger" in the record of the received public address M.

[0063] The content reception unit 129 receives content such as image data and audio data from the challenger terminal 40 or the prover terminal 50 and saves it in the content DB 134. In this embodiment, the content reception unit 129 receives the content address uniquely identifying the content and the content, and saves the received content address and content in the content DB 134. The content is data such as images and sounds that serve as evidence of activities for achieving tasks. For example, the images include meal images taken by the challenger, body measurement images taken by the challenger, inspection images taken by the prover, and the like.

[0064] (Fund Provider Terminal Configuration) FIG. 4 shows the configuration of the fund provider terminal 30 according to an embodiment of the present invention. The fund provider terminal 30 is an information processing terminal having a function of communicating with the operator server 10 and the blockchain network 20 via the network N. Specifically, examples include, but are not limited to, mobile phones, smartphones, PCs, PDAs, tablets, and the like.

[0065] As shown in FIG. 4, the fund provider terminal 30 includes an input unit 31 such as a touch panel that receives operations from the user, a display unit 32 such as a display, a control unit 33 including a CPU and a memory, a storage unit 34, a communication unit 35 for connecting to the network N, an imaging unit 36, and the like. In this embodiment, the challenge application 70 is stored in the storage unit 34. Further, it is desirable that the challenge application 70 has a member private key 71, a public address 72, and a campaign private key 73.

[0066] Further, when the challenge application 70 stored in the storage unit 34 is read into the RAM and executed by the CPU, the control unit 33 functions as a member key generation unit 331, a code reading unit 332, a wallet unit 333, and a setting transmission unit 334.

[0067] The member key generation unit 331 generates a pair of a unique private key M and a public key M for each member-registered user, and stores the generated private key M in the member private key 71 of the storage unit 34. The member private key 71 is generated offline and is usually stored offline, and it is desirable that it can be connected as needed. Further, the member key generation unit 331 generates a public address M using the public key M, and stores the generated public address M in the public address 72 of the storage unit 34. Furthermore, the member key generation unit 331 transmits the generated public address M to the operator server 10 together with the user identification information. As described above, the user identification information can be information generated using part or all of the member information obtained by having the user input it, for example, at the time of installation or startup of the challenge application 70.

[0068] The code reading unit 332 reads the private key S from the image including the code acquired by the imaging unit 36, and stores the read private key S in the campaign private key 73. Further, the code reading unit 332 generates a public key S from the read private key S, generates a public address S using the public key S, and transmits the public address S and its own public address M to the operator server 10.

[0069] The wallet section 333 has a function of managing virtual currency. In this embodiment, the wallet section 333 transmits fund payment data including the recipient's account and the transfer amount to the blockchain system 20 as a transaction. For example, the wallet section 333 signs the fund payment data including the contract account and the transfer amount specified by the user via the input section 31 with the member private key 71 of the storage section 34 and transmits it to the blockchain system 20 as a transaction. When the transaction is approved in the blockchain network 20, the funds transferred to the smart contract are stored. The wallet section 333 may obtain a list of contract accounts from the operator server 10 and display it in a selectable format for the user. Also, when obtaining the contract account, the wallet section 333 may transmit the public address 72 of the storage section 34 so that the user can obtain a list of contract accounts of the campaigns registered with the operator server 10 as a fund provider.

[0070] The setting transmission section 334 transmits data including various setting data to the blockchain system 20 as a transaction. In this embodiment, the setting data includes the public address M of the fund provider, the amount of funds, the public address M of the challenger, the fund distribution setting when the task is successful, the fund distribution setting when the task fails, and the like. For example, the setting transmission section 334 signs the various setting data specified by the user via the input section 31 with the member private key 71 of the storage section 34 and transmits it to the blockchain network 20 as a transaction. When the transaction is approved in the blockchain network 20, the various setting data is stored in the smart contract. The setting transmission section 334 may obtain a list of contract accounts from the operator server 10 and display it in a selectable format for the user. Also, when obtaining the contract account, the setting transmission section 334 may transmit the public address 72 of the storage section 34 so that the user can obtain a list of contract accounts of the campaigns registered with the operator server 10 as a fund provider.

[0071] As a result, as shown in FIG. 8, values are stored in each item of the fund provider data in which the public address M of the corresponding fund provider is stored. FIG. 8(A) shows the content of the data set in the challenge app 70 of the fund provider terminal 30, and FIG. 8(B) shows the data structure of the smart contract stored by the transaction transmitted based on the data of FIG. 8(A).

[0072] In addition, the setting transmission unit 334 transmits the public address M of the challenger specified in the setting data to the operator server 10 together with the information of the campaign to be challenged. In the present embodiment, the setting transmission unit 334 transmits the public address M to the operator server 10 together with the contract account.

[0073] (Challenger Terminal Configuration) FIG. 5 shows the configuration of the challenger terminal 40 according to an embodiment of the present invention. The challenger terminal 40 is an information processing terminal having a function of communicating with the operator server 10 and the blockchain network 20 via the network N. Specifically, examples include, but are not limited to, mobile phones, smartphones, PCs, PDAs, tablets, etc.

[0074] As shown in FIG. 5, the challenger terminal 40 includes an input unit 41 such as a touch panel that receives operations from the user, a display unit 42 such as a display, a control unit 43 including a CPU and a memory, a storage unit 44, a communication unit 45 for connecting to the network N, an imaging unit 46, etc. In the present embodiment, the challenge app 70 is stored in the storage unit 44. Further, the challenge app 70 desirably has a member private key 71 and a public address 72.

[0075] In addition, when the challenge app 70 stored in the storage unit 44 is read into the RAM and executed by the CPU, the control unit 43 functions as a member key generation unit 331, a wallet unit 333, and a determination data transmission unit 431.

[0076] The member key generation unit 331 and the wallet unit 333 have already been described in the configuration of the fund provider terminal, so the description thereof is omitted here.

[0077] The determination data transmission unit 431 transmits the determination data used to determine whether the contract conditions are satisfied to the blockchain network 20 as a transaction. In the present embodiment, the determination data transmission unit 431 signs the determination data with the member private key 71 of the storage unit 44 and transmits it to the blockchain network 20. Any data can be used for the determination data, such as data serving as evidence of activities for achieving a task, data including either "success" or "failure" of the task, and the like.

[0078] The determination data transmission unit 431 may acquire a list of contract accounts from the operator server 10 and display it in a selectable format for the user as the destination of the transaction. Further, when acquiring the contract account, the determination data transmission unit 431 may transmit the public address 72 of the storage unit 44 so that the user can acquire a list of contract accounts of the campaigns registered with the operator server 10 as a challenger.

[0079] Regarding the content of the determination data, the determination data transmission unit 431 generates a content address uniquely identifying the content, transmits the generated content address to the blockchain network 20 as a transaction, and transmits the actual content to the operator server 10 together with the content address. As described above, the image includes, for example, a meal image taken by the challenger, a body measurement image taken by the challenger, an inspection image taken by the prover, and the like.

[0080] FIG. 9 is a diagram showing an example of data related to evidence according to an embodiment of the present invention. FIG. 9(A) shows data transmitted from the challenger terminal 40 to the blockchain network 20, and FIG. 9(B) shows the data structure of the smart contract stored by the transmitted transaction. The example shown in FIG. 9 is part of the data that serves as evidence of walking to achieve the task of walking more than 10,000 steps per day for a total of 15 days within a predetermined deadline and within 30 days from the start of the challenge.

[0081] (Prover Terminal Configuration) FIG. 6 shows the configuration of the prover terminal 50 according to an embodiment of the present invention. The prover terminal 50 is an information processing terminal having a function of communicating with the operator server 10 and the blockchain network 20 via the network N. Specifically, examples include, but are not limited to, mobile phones, smartphones, PCs, PDAs, tablets, and the like.

[0082] As shown in FIG. 6, the prover terminal 50 includes an input unit 51 such as a touch panel that receives operations from the user, a display unit 52 such as a display, a control unit 53 including a CPU and a memory, a storage unit 54, a communication unit 55 for connecting to the network N, an imaging unit 56, and the like. In the present embodiment, the prover application 80 is stored in the storage unit 54. Further, it is desirable that the prover application 80 has a prover private key 81 and a public address 82.

[0083] Further, when the prover application 80 stored in the storage unit 54 is read into the RAM and executed by the CPU, the control unit 53 functions as a wallet unit 333, a prover key generation unit 531, a code reading unit 532, and a determination data transmission unit 533.

[0084] Since the wallet unit 333 has already been described in the fund provider terminal configuration, the description thereof is omitted here.

[0085] The prover key generation unit 531 generates a unique pair of a private key T and a public key T for each prover registered by the prover, and stores the generated private key T in the prover private key 81 of the storage unit 54. The prover private key 81 is generated offline, usually stored offline, and desirably can be connected as needed. Also, the prover key generation unit 531 generates a public address T using the public key T, and transmits the generated public address T to the operator server 10 together with the prover identification information. As described above, the prover identification information can be information generated using a part or all of the prover information obtained by being input to the prover, for example, at the time of installation or startup of the prover application 80.

[0086] The code reading unit 532 reads the public address M from the image including the code acquired by the imaging unit 56.

[0087] The determination data transmission unit 533 has the same function as the determination data transmission unit 431 of the challenger terminal 40, and transmits data serving as evidence of activities for achieving a task to the blockchain network 20 as a transaction. In the present embodiment, the determination data transmission unit 533 generates data serving as evidence based on the public address M read by the code reading unit 532, signs it with the prover private key 81 of the storage unit 54, and transmits it to the blockchain network 20.

[0088] The determination data transmission unit 533 may acquire a list of contract accounts from the operator server 10 and display it in a selectable format for the user as the destination of the transaction. Also, when acquiring the contract account, the determination data transmission unit 533 may transmit the public address 82 of the storage unit 54 so that a list of contract accounts of the campaigns registered in the operator server 10 as the designated campaign of the prover can be acquired.

[0089] Regarding the content of the data serving as evidence, the determination data transmission unit 533 generates a content address that uniquely identifies the content, transmits the generated content address to the blockchain network 20 as a transaction, and transmits the actual content to the operator server 10 together with the content address.

[0090] (Sponsor Company Server Configuration) The sponsor company server 60 is a server device having a function of communicating with the operator server 10 and the blockchain network 20 via the network N. In FIG. 1, for simplicity, a single sponsor company server 60 is shown. However, for example, when a plurality of sponsor companies gather for one campaign, there may be a plurality of sponsor company servers 60, and in addition to / or there may be different sponsor company servers 60 related to different campaigns.

[0091] (First Embodiment) In the first embodiment, a campaign of a beverage manufacturer that supports challengers who take on tasks related to health activities will be described as an example. Assume that a beverage manufacturer, which is a sponsor company, and the operator have previously concluded a contract, and the beverage manufacturer has paid the operator a campaign service commission fee of X yen and a corporate sponsorship of 5,000 ETHER. In this embodiment, when the number of days that the challenger has walked 10,000 steps or more in a day reaches 15 days in total over 30 days, the task is considered successful. Here, the challenger is user A, the fund provider is user B, the father of user A who supports the health activities of user A, and an example where the challenger and the fund provider are different will be described. The prover is a fitness club that proves the health activities of the challenger.

[0092] The operator and the beverage manufacturer have generated Ethereum accounts in advance, and the storage unit 13 of the operator server 10 and the storage unit of the sponsor company server 60 respectively store the private key generated at the time of Ethereum account generation and the public address generated from the public key issued at the time of Ethereum account generation. First, the entry preparation process will be described with reference to FIG. 10, then the entry process will be described with reference to FIG. 11, and finally, the determination data transmission process will be described with reference to FIG. 12.

[0093] (Entry Preparation Process) The contract generation unit 124 of the operator server 10 compiles the contract code including information such as the public address of the operator, the public address of the sponsor company, the entry start date and time, the entry end date and time, the challenge start deadline, the challenge period, the smart contract conclusion date and time, and the contract content described in the Solidity language using solc, and transmits it as a transaction to the blockchain network 20 (S101). When the transaction transmitted from the operator server 10 is approved in the blockchain network 20, a smart contract is generated (S102).

[0094] In the present embodiment, a smart contract as shown in FIG. 7 is generated by transmitting a transaction from the contract generation unit 124. The content of the smart contract is as follows.

[0095] (1) During the entry start date and time to the entry end date and time, the fund provider can accept an entry by transmitting data including various setting data (the public address M of the fund provider, the amount of funds, the public address M of the challenger, the fund distribution setting at the time of task success, the fund distribution setting at the time of task failure, etc.) and fund payment data as a transaction.

[0096] (2) Before the challenge start deadline, the challenger starts the challenge by sending, as a transaction, the data serving as evidence of the activities for achieving the task to the blockchain network 20.

[0097] (3) During the challenge period, if the challenger conducts a health activity at the prover's store or the like, the prover sends, as a transaction, the data serving as evidence of the health activity conducted by the challenger to the blockchain network 20.

[0098] (4) If the number of days when the challenger walks 10,000 steps or more a day accumulates to 15 days during the challenge period, the task is considered successful.

[0099] (5) If the challenger achieves the task before the smart contract conclusion date and time, or if the challenger fails to achieve the task before the smart contract conclusion date and time and during the challenge period, the operator's fee is automatically remitted to the operator.

[0100] (6) If the challenger achieves the task before the smart contract conclusion date and time and during the challenge period, or if the challenger fails to achieve the task before the smart contract conclusion date and time and during the challenge period, the reward is automatically remitted to the prover.

[0101] (7) If the challenger achieves the task before the smart contract conclusion date and time, the refund amount is automatically remitted to the refund destination and / or the donation amount is automatically remitted to the donation destination according to the fund allocation setting at the time of task success.

[0102] (8) If the challenger fails to achieve the task before the smart contract conclusion date and time and during the challenge period, the refund amount is automatically remitted to the refund destination and / or the donation amount is automatically remitted to the donation destination according to the fund allocation setting at the time of task failure.

[0103] The amount obtained by subtracting the operator's fee + α to the operator and the reward to the prover from the seizure money is remitted to the public address designated as a bonus upon success in each smart contract so that the remittance amount to each smart contract that has achieved the task becomes equal.

[0104] (10) Agrees to disclose the content regarding its own evidence to the sponsoring company, and further, for challengers who have achieved the task before the smart contract conclusion date and during the challenge period, a predetermined amount is automatically remitted from the company sponsorship amount to the challenger and / or the refund destination.

[0105] (11) The access key and the content address of the content for accessing the data of the challenger who has agreed to disclose various data including the content regarding its own evidence are automatically sent to the sponsoring company.

[0106] (12) The sponsoring company can access the data of the challenger stored encrypted on the operator server using the access key. The content of the challenger on the operator server is managed by the content address.

[0107] Also, as shown in FIG. 7, in this embodiment, the generated smart contract includes a fund provider data array for the number of entries to the campaign for storing various setting data from the fund provider. For example, in this embodiment, the fund provider data includes the fund provider, the amount of funds, the challenger, the prover, the fund allocation setting when the task is successful, and the fund allocation setting when the task fails.

[0108] In addition, the fund distribution settings each include repayment, donation, and confiscation, and the fund provider designates each amount so that the total of the amounts designated for repayment, donation, and confiscation matches the fund amount. For repayment, any repayment destination that holds an Ethereum public address and any amount can be specified. For donation, any donation destination that holds an Ethereum public address and any amount can be specified. For confiscation upon success, an operator fee paid to the operator is set. For confiscation upon success, any amount equal to or greater than the operator fee can be specified. Further, the fund distribution settings upon success may include a bonus. For the bonus, the distribution destination of the funds sent as a bonus upon task success can be specified.

[0109] Returning to FIG. 10, the contract generation unit 124 receives (S103) the contract account issued at the time of smart contract generation from the blockchain network 20 and stores it in the campaign DB 131 (S104). In the present embodiment, it is assumed that the contract generation unit 124 generates a campaign ID "001" and stores the received contract account in the campaign DB 131 in association with the campaign ID "001".

[0110] The key generation unit 125 of the operator server 10 generates a pair of a secret key S and a public key S used to verify users who enter the campaign of the beverage maker for the number of entries into the campaign (S105). Further, the key generation unit 125 generates a public address S using the public key S and stores it in the campaign DB 131 in association with the campaign ID (S106). In the present embodiment, it is assumed that the key generation unit 125 stores 1000 public addresses S in the campaign DB 131 in association with the campaign ID "001".

[0111] Furthermore, the key generation unit 125 generates and outputs a code obtained by encoding the secret key S (S107). In the present embodiment, the operator generates a seal printed with the encoded code and delivers it to the beverage maker.

[0112] When a fund provider accesses the site provided by the operator server 10 using the browser of the fund provider terminal 30 (S108), the site providing unit 121 of the operator server 10 transmits a web page corresponding to the accessed URL to the fund provider terminal 30 (S109).

[0113] When member information necessary for member registration is transmitted from the fund provider terminal 30 in response to an operation by the fund provider on the browser (S110), the member registration unit 122 of the operator server 10 registers a record in the member DB 132 based on the received member information (S111). In this embodiment, it is assumed that member information is transmitted from the fund provider terminal 30 in response to an operation by user B on the member registration screen provided by the site providing unit 121, and the member registration unit 122 registers a record in the member DB 132 based on the received member information. The member information includes name, gender, date of birth, etc.

[0114] When a download request for the challenge app 70 is transmitted from the fund provider terminal 30 in response to an operation by the fund provider on the browser (S112), the site providing unit 121 transmits the challenge app 70 to the fund provider terminal 30 (S113). Thereafter, user B completes the installation of the downloaded challenge app 70.

[0115] In response to an operation by the fund provider on the challenge app 70, the member key generation unit 331 of the fund provider terminal 30 generates a pair of a unique secret key M and a public key M for each member-registered user, and stores the generated secret key M in the member secret key 71 of the storage unit 34 (S114). Also, the member key generation unit 331 generates a public address M using the public key M, and stores the generated public address M in the public address 72 of the storage unit 34 (S115).

[0116] Furthermore, the member key generation unit 331 transmits the generated public address M to the operator server 10 together with the user identification information (S116). In the present embodiment, the member key generation unit 331 uses the user identification information generated using part or all of the member information obtained by having the user B input it at the time of installing the challenge app 70.

[0117] When the member registration unit 122 of the operator server 10 receives the public address M from the fund provider terminal 30 together with the user identification information, it saves the public address M in the record of the member DB 132 specified by the user identification information (S117).

[0118] It is assumed that the challenger, user A, also operates the challenger terminal 40 to perform the processes of S108 to S117, completes the member registration, installs the challenge app 70, and transmits the public address M of user A to the operator server 10.

[0119] The fitness club, which is the prover, also operates the prover terminal 50 to perform the processes of S108 to S109. When the prover information necessary for prover registration is transmitted from the prover terminal 50 (S110’), the prover registration unit 123 of the operator server 10 registers a record in the prover DB 133 based on the received prover information (S111’). In the present embodiment, it is assumed that the prover information is transmitted from the prover terminal 50 in response to the operation of the person in charge of the fitness club on the prover registration screen provided by the site providing unit 121, and the prover registration unit 123 registers a record in the prover DB 133 based on the received prover information. The prover information includes the prover name, prover qualification, location, etc. After that, it is assumed that "ALL" confirmed by the operator is saved in the designated campaign of the record of the fitness club in the prover DB 113.

[0120] When a download request for the prover application 80 is sent from the prover terminal 50 in response to the operation of the prover on the browser (S112’), the site providing unit 121 transmits the prover application 80 to the prover terminal 50 (S113’). Thereafter, the person in charge of the fitness club completes the installation of the downloaded prover application 80.

[0121] In response to the operation of the prover on the prover application 80, the prover key generation unit 531 of the prover terminal 50 generates a pair of a secret key T and a public key T unique for each prover-registered user, and stores the generated secret key T in the prover secret key 81 of the storage unit 54 (S114’). Further, the prover key generation unit 531 generates a public address T using the public key T, and stores the generated public address T in the public address 82 of the storage unit 54 (S115’).

[0122] Furthermore, the prover key generation unit 531 transmits the generated public address T to the operator server 10 together with the prover identification information. In the present embodiment, the prover key generation unit 531 uses the prover identification information generated using some or all of the prover information acquired by having the person in charge of the fitness club input it at the time of installation of the prover application 80.

[0123] When the prover registration unit 123 of the operator server 10 receives the public address T from the prover terminal 50 together with the prover identification information, it stores the public address T in the record of the prover DB 133 specified by the prover identification information (S117’).

[0124] (Entry process) When a fund provider purchases a product of a beverage manufacturer with a seal printed with an encoded code and directs the imaging unit 36 of the fund provider terminal 30 at the seal, the code reading unit 332 of the fund provider terminal 30 reads the private key S from the image containing the code acquired by the imaging unit 36 and stores the read private key S in the campaign private key 73 (S201). Also, the code reading unit 332 generates a public address S using the public key S derived from the read private key S and transmits the public address S and its own public address M to the operator server 10 (S202). In this embodiment, it is assumed that the code reading unit 332 transmits the generated public address S and the public address M of user B stored in the public address 72 to the operator server 10.

[0125] The entry reception unit 126 of the operator server 10 receives the public address S and the public address M of the user of the fund provider terminal 30 from the fund provider terminal 30, and determines whether the received public address S matches the public address S stored in the campaign DB 131 (S203). If they match, the entry reception unit 126 stores the campaign ID associated with the public address S and the participation attribute "fund provider" as related campaigns in the record of the corresponding public address M in the member DB 132 (S204). Here, it is assumed that the public address received from the fund provider terminal 30 of user B matches the public address S stored in the campaign DB 131, and in the record corresponding to the public address M of user B in the member DB 132, the campaign ID "001" and the participation attribute "fund provider" are stored as related campaigns.

[0126] The participant information transmission unit 127 of the operator server 10 transmits the public address M and the public address T registered in the DB in association with the beverage manufacturer's campaign to the blockchain network 20 as a transaction in order to associate them with the smart contract of the campaign (S205).

[0127] In this embodiment, in response to the entry reception unit 126 receiving the public address M, the participant information transmission unit 127 transmits, as a transaction, data regarding the public address M that has entered the campaign with the campaign ID "001" and the public address T of the certifier for which the campaign ID "001" or "ALL" is specified as the designated campaign to the blockchain network 20. As a result, it is assumed that the public address M of user B is stored in the fund provider of the fund provider data array [0], and the public address T of the fitness club is stored in the certifier [0] of the fund provider data array [0] (S206).

[0128] In response to the operation of the fund provider on the challenge app 70, the wallet unit 333 of the fund provider terminal 30 transmits, as a transaction, fund payment data including the account of the payee and the amount of the transfer to the blockchain system 20 (S207). In this embodiment, by the wallet unit 333 transmitting the public address 72 of the storage unit 34 to the operator server 10, a list of contract accounts of the campaigns registered by the user as a fund provider in the operator server 10 is obtained. Here, it is assumed that user B selects the contract account associated with the campaign ID "001", and the wallet unit 333 signs the fund payment data including the payee address and the transfer amount "10 ETHER" with the member private key 71 of the storage unit 34 and transmits it to the blockchain system 20 as a transaction.

[0129] In response to the operation of the fund provider on the challenge app 70, the setting transmission unit 334 of the fund provider terminal 30 transmits various setting data to the blockchain network 20 as a transaction (S208). In this embodiment, the setting data includes the public address M of the fund provider, the amount of funds, the public address M of the challenger, the fund distribution setting when the task is successful, the fund distribution setting when the task fails, and the like. Here, the setting transmission unit 334 signs various setting data specified by the user via the input unit 31 with the member private key 71 of the storage unit 34, and transmits it to the blockchain network 20 as a transaction addressed to the contract account associated with the campaign ID "001".

[0130] As a result, as shown in FIG. 8, values are stored in each item of the fund provider data array [0] in which the public address M of user B is stored for the fund provider (S209). FIG. 8(A) shows the content of the data set in the challenge app 70 of the fund provider terminal 30, and FIG. 8(B) shows the data structure of the smart contract stored by the transaction transmitted based on the data in FIG. 8(A).

[0131] In addition, the setting transmission unit 334 transmits the public address M of the challenger specified in the setting data to the operator server 10 together with the information regarding the campaign (S210). Here, it is assumed that the setting transmission unit 334 transmits the public address M of user A to the operator server 10 together with the contract account.

[0132] Upon receiving information regarding the campaign and the public address M of the challenger from the fund provider terminal 30, the challenger reception unit 128 saves, in the record of the corresponding public address M in the member DB 132, the campaign ID specified by the information regarding the campaign and the participation attribute "challenger" as the related campaign (S211). Here, the challenger reception unit 128 receives the contract account and the public address M of user A from the fund provider terminal 30, and saves the campaign ID "001" specified by the contract account and the participation attribute "challenger" in the record of the received public address M.

[0133] (Judgment data transmission process) In response to operations of the challenger on the challenge app 70 and the like, the judgment data transmission unit 431 of the challenger terminal 40 transmits, as a transaction, data serving as evidence of activities for achieving the task to the blockchain network 20 (S301). In the present embodiment, by transmitting the public address 72 of the storage unit 44 by the judgment data transmission unit 431 to the operator server 10, a list of contract accounts of the campaigns in which the user is registered as a challenger with the operator server 10 is obtained. Here, user A selects the contract account associated with the campaign ID "001", and the judgment data transmission unit 431 signs the data serving as evidence with the member private key 71 and transmits it to the blockchain network 20 as a transaction.

[0134] As described above, in the present embodiment, when the number of days in which the challenger walks 10,000 steps or more per day accumulates to 15 days in 30 days, the task is considered successful. In the present embodiment, as data serving as evidence, in addition to the step count data, a content address for uniquely identifying content such as GPS data during walking and image data of measurement results of weight and blood pressure can be included. The step count data and GPS data may be obtained from a step count app installed on the challenger terminal 40, or may be obtained from a step counter device equipped with a wireless function.

[0135] Here, in response to the operation of user A on the challenge app 70, the determination data transmission unit 431 signs the step count data [0] shown in Fig. 9(A) with the member private key 71 of the storage unit 44 and transmits it to the blockchain network 20 as a transaction. As shown in Fig. 9(A), the first data transmitted from the challenger terminal 40 to the blockchain network 20 includes "data disclosure availability" indicating whether the challenger agrees to disclose their own data to the sponsoring company.

[0136] After the blockchain network 20 approves the transmitted transaction, it stores the data in the smart contract (S302). Fig. 9(B) shows the data structure of the smart contract stored by the transmitted transaction. As shown in Fig. 9(B), on the smart contract side, the "posting date and time" when the transaction was stored in the blockchain and the "type of days to reach 10,000 steps" for counting the cumulative number of days on which 10,000 or more steps were walked are added.

[0137] As described above, for the content of the data serving as evidence, the determination data transmission unit 431 generates a content address that uniquely identifies the content and transmits the generated content address to the blockchain network 20 as a transaction in S301. For the actual content, it is transmitted to the operator server 10 together with the content address (S303). For example, when user A transmits images of weight and blood pressure measurement results together with the step count data, the determination data transmission unit 431 includes the hash value generated from the image data in the Evidence hash value in Fig. 9(A) and transmits it to the blockchain network 20, and for the actual image data, it is transmitted to the operator server 10 together with the content address.

[0138] The content reception unit 129 of the operator server 10 receives the content address and the content from the challenger terminal 40 and stores them in the content DB 134 (S304). Thereby, the content is managed by the content address on the operator server 10.

[0139] Note that the determination data transmission unit 431 may automatically transmit the step count data as a transaction to the blockchain network 20 without depending on the operation of the challenger.

[0140] Also, when the challenger visits the store of the prover or the like, in response to the operation of the challenger on the challenge app 70, the challenge app 70 displays a code in which the public address 72 is encoded on the display unit 42 of the challenger terminal 40 (S305).

[0141] In response to the operation of the prover on the prover app 80, the code reading unit 532 of the prover terminal 50 reads the public address M from the image including the code acquired by the imaging unit 56 (S306). Here, the code reading unit 532 of the prover terminal 50 reads the public address M of user A.

[0142] As a result of the subsequent activities of the challenger in the store, in response to the operation of the prover on the prover app 80, data serving as evidence of the activities for achieving the task can also be transmitted as a transaction from the determination data transmission unit 533 of the prover terminal 50 to the blockchain network 20 (S307). In the present embodiment, the determination data transmission unit 533 generates data serving as evidence such as the store visit record based on the public address M read by the code reading unit 532, signs it with the prover private key 81 in the storage unit 54, and transmits it to the blockchain network 20.

[0143] After the blockchain network 20 approves the transmitted transaction, it stores the data in the smart contract (S308).

[0144] Note that, as described above, for the content of the data serving as evidence, the determination data transmission unit 533 generates a content address that uniquely identifies the content, and transmits the generated content address as a transaction to the blockchain network 20 in S307. For the actual content, it is transmitted to the operator server 10 together with the content address (S309).

[0145] The content reception unit 129 of the operator server 10 receives the content address and the content from the prover terminal 50 and stores them in the content DB 134 (S310).

[0146] If user A achieves the task before the smart contract conclusion date, the smart contract is automatically executed, and funds are distributed according to the fund distribution settings at the time of task success. In this embodiment, 9.5 ETHER is returned to user A's son, and 0.5 ETHER is transferred to the operator. Furthermore, after the smart contract conclusion date, a part of the confiscated funds of other challengers who failed to achieve the task is transferred to user A.

[0147] If user A fails to achieve the task before the smart contract conclusion date and during the challenge period, the smart contract is automatically executed, and funds are distributed according to the fund distribution settings at the time of task failure. In this embodiment, 1 ETHER is returned to user A's son, 5 ETHER is returned to user B, and 1 ETHER is donated to the Japanese Red Cross Society. Of the 3 ETHER of confiscated funds, 0.5 ETHER is transferred to the operator, a predetermined reward is transferred to the prover, and the remaining confiscated funds are evenly transferred to the challengers who achieved the task as a prize.

[0148] Note that the judgment data may be sent only from the challenger terminal 40, only from the prover terminal 50, or from both, depending on the contract details of the task. For example, in the case of a walking task, the judgment data is sent only from the challenger terminal 40. In the case of a task of going to a fitness club, the judgment data is sent only from the prover terminal 50. In the case of a task that includes both walking and going to a fitness club, the judgment data is sent from both. However, even in the case of a task where the judgment data is sent only from the prover terminal 50, it is desirable for the challenger terminal 40 to explicitly indicate the start of the challenge by sending "data disclosure permission / non - permission" data, etc., which indicates whether it agrees to disclose its own data to the sponsoring company, as a transaction to the blockchain network 20 by the challenge start deadline.

[0149] As described above, according to this embodiment, for a task, if the task cannot be completed by a predetermined date and time, by intentionally creating a situation where an economic demerit occurs to the challenger or the people around them or a chance to obtain an economic merit is missed, the possibility of the challenger achieving the task can be increased. User B, who is a fund provider supporting the health activities of User A, can lead User A to achieve the task without directly appealing to User A himself. User A's son can not only contribute to the improvement of his father's health but also obtain economic benefits by supporting User A's health activities. According to this embodiment, the money saved without consumption by the elderly User B can be drawn out by the switch of love for the family and returned to User A and User A's son, who are in the active generation with strong consumption desire, and an economic improvement can be expected by increasing consumption.

[0150] (Another embodiment) In the first embodiment, as shown in the lower - center of FIG. 13, an example where the challenger is User A, the fund provider is User B, who is the father of User A supporting the health activities of User A, and the challenger and the fund provider are different has been described.

[0151] The present invention can also be applied to an example in which user C, who is a challenger, becomes a fund payer, as shown on the lower left side or the lower right side of FIG. 13. In this case, the control unit of the terminal of the fund provider terminal 30 and the challenger terminal 40 includes a member key generation unit 331, a code reading unit 332, a wallet unit 333, a setting transmission unit 334, and a determination data transmission unit 341.

[0152] (Second Embodiment) In the second embodiment, an example of a challenger who takes on tasks related to housework will be described. In the second embodiment, if the challenger cleans up after dinner two or more times a week, the task is considered successful. In the second embodiment, the operator, the sponsoring company, and the certifier do not appear, and user C, who is both a fund provider and a challenger, and user D, who is user C's wife and wants user C, who always says they will help with housework but never actually does, to help with housework when the task fails, and user E, who is user C's child and supports user C's housework activities, appear.

[0153] Regarding user C, who always says they will help with housework but never actually does, user D concludes a contract with an automatic execution function that says, "Using 10 ETHER of user C as the source of funds, if user C does not clean up after dinner two or more times a week, user D will receive 10 ETHER. If user C cleans up after dinner two or more times a week, 8 ETHER will be returned to user C and user E will receive 2 ETHER." Assume that user C sends data on whether they actually cleaned up or not.

[0154] The control unit of user C's terminal includes a terminal-side contract generation unit in addition to the member key generation unit 331, the wallet unit 333, and the determination data transmission unit 341.

[0155] Since the member key generation unit 331 and the wallet unit 333 have already been described, the description will be omitted here.

[0156] The terminal-side contract generation unit generates, compiles, and transmits, as a transaction, code for a smart contract to the blockchain network 20 based on contract conditions including conditions for achieving a task and a period for challenging the task specified by the user via the input unit, the amount of funds deposited for the task, the fund distribution settings in case of success of the task, the fund distribution settings in case of failure of the task, and the person who determines whether the contract conditions are satisfied.

[0157] Specifically, the terminal-side contract generation unit generates, compiles, and transmits, as a transaction, code for a smart contract to the blockchain network 20 based on contract conditions including the condition for achieving the task "clean up after dinner more than twice a week" and the period for challenging the task "from December 15, 2018 to December 22, 2018", the amount of funds deposited for the task "10 ETHER", the fund distribution settings in case of success of the task "8 ETHER to user C, 2 ETHER to user E", the fund distribution settings in case of failure of the task "10 ETHER to user D", and the person who determines whether the contract conditions are satisfied "user C".

[0158] The determination data transmission unit 431 transmits, as a transaction, the determination data used to determine whether the contract conditions are satisfied to the blockchain network 20. In the second embodiment, the determination data transmission unit 431 signs, with the member private key 71 of the storage unit 34, the determination data including either "success" or "failure" of the task based on a user input such as pressing the "success" button or "failure" button of the task displayed on the display unit, and transmits it to the blockchain network 20.

[0159] As described above, according to the present embodiment, for a task, when the task cannot be completed by a predetermined date and time, by intentionally creating a situation where an economic demerit occurs or a chance to obtain an economic merit is missed for the challenger or people around them, the possibility of the challenger achieving the task can be increased. User D who wants User C to help with housework can lead User C to task completion without directly appealing to User C. User E, who is the child of User C, can obtain economic merits by supporting User C in helping with housework.

[0160] In the second embodiment, an example has been described in which User C is the person who determines whether the contract conditions are met. However, the invention of the present application is not limited to such an aspect, and User D or User E may be the person who determines whether the contract conditions are met, or any other arbitrary user may be the person who determines whether the contract conditions are met. When User D or User E is the person who determines whether the contract conditions are met, User D or User E may also transmit determination data that is contrary to the facts. In that case, User D and User E will temporarily obtain improper economic merits. However, since the trust relationship with User C will be damaged, and furthermore, User C will no longer use this mechanism, there will be no chance for User D and User E to continuously obtain economic merits in the future with such a mechanism. In view of such circumstances, it is considered that User D and User E will consider that making a correct determination has economic merits in the long run and will transmit determination data based on the facts.

[0161] In the first and second embodiments, an example in which the blockchain network 20 is used to implement the invention of the present application has been described. However, the invention of the present application is not limited to such an aspect, and it can also be implemented using a server device having a function corresponding to the blockchain network 20. For example, from the terminal device, receive contract conditions including conditions for achieving a task and a period for challenging the task, the amount of funds, the setting of the distribution of funds when the task is successful, and the setting of the distribution of funds when the task fails, and save them in a storage unit communicably connected to the server device; means for confirming the deposit of funds from the terminal device into a predetermined account; means for determining whether the contract conditions are satisfied based on the determination data received from the terminal device; when the contract conditions are satisfied during the period, move the funds from a predetermined account to each distribution destination according to the setting of the distribution of funds when the task is successful, and when the contract conditions are not satisfied during the period, move the funds from a predetermined account to each distribution destination according to the setting of the distribution of funds when the task fails. The invention of the present application may be implemented using a server device provided with such means.

[0162] In this specification, for the terminal device to transmit determination data to the server device, for example, in addition to the determination data transmission unit 431 transmitting the determination data to the server device based on a user input such as pressing the "success" button or "failure" button of the task displayed on the display unit, there are also cases where the terminal device accesses the server device and uploads the determination data, and the determination data is transmitted to the server device based on a user input such as selecting the "success" button or "failure" button of the task displayed on the screen of the web page provided by the server device.

[0163] Also, in the first and second embodiments, a task without a deadline has been described as an example. However, applying the invention of the present application to a task with a deadline does not prevent the application of the invention of the present application to a task with a deadline. By applying the invention of the present application to a task with a deadline, the challenger can be more likely to achieve the task.

[0164] (Additional Embodiment) In Ethereum, the operator may generate and manage a new token contract for health tokens to be distributed to the challenger himself and / or those who supported the challenger. A token contract is a smart contract that has a correspondence table between multiple public addresses and the token balances of those public addresses. For example, when the challenger achieves a task, the contract generation unit 124 of the operator server 10 generates a token contract for the challenger's health tokens, transfers the health tokens issued by the operator or the like to the token contract, and the challenger automatically distributes the health tokens to each public address in the token contract according to the distribution set according to the contribution degree of those who supported himself. Separately from the contract generation unit 124, the operator server 10 may further include a token contract generation unit that generates a token contract for the challenger's health tokens by transmitting the contract data for the challenger's health tokens to the blockchain network 20. Also, the token contract generation unit receives the contract account issued at the time of generating the token contract for the health tokens from the blockchain network 20 and stores it in the member DB 132. The amount of health tokens transferred at the time of task success may be varied according to the difficulty level of the task.

[0165] As described above, the challenger can distribute the health tokens transferred at the time of task success according to the contribution degree of the support during the challenge period. FIG. 14 shows a conceptual diagram of the data structure of the token contract of user A, who is the challenger. As shown in FIG. 14, as the challenger continues to challenge a healthy task and achieves the task, the higher the contribution degree of task success, the higher the token balance.

[0166] By utilizing this token contract, for example, an insurance company may cash back ETHER to the token contract of a policyholder with a large total balance of health tokens, and distribute the cashed-back ETHER to each public address according to the proportion of the remaining balance of the health tokens held in the token contract. This can enhance the motivation of people who support the policyholder's health activities to support the policyholder's health activities.

[0167] In another example, for instance, a health insurance association may transfer a part of the health promotion budget to the token contract of a policyholder, and distribute the transferred ETHER to each public address according to the proportion of the remaining balance of the health tokens held in the token contract. Thus, the health insurance association can support people who support the policyholder's health activities.

Description of Signs

[0168] 1... Challenge Support System, 10... Operator Server, 11... Input Section, 12... Control Section, 121... Site Provision Section, 122... Membership Registration Section, 123... Certifier Registration Section, 124... Contract Generation Section, 125... Key Generation Section, 126... Entry Reception Section, 127... Participant Information Update Section, 128... Challenger Reception Section, 129... Content Reception Section, 13... Memory Section, 131... Campaign DB, 132... Member DB, 133... Certifier DB, 134... Content DB, 135... Secret Key, 136... Public Address, 14... Communication Section, 20... Blockchain Network (Information Processing System), 30... Fund Provider Terminal (Participant Terminal, Terminal Device), 31... Input Section, 32... Display Section, 33... Control Section, 331... Member Key Generation Section, 332... Code Reading Section (Entry Section), 333... Wallet Section, 334... Setting Transmission Section, 34... Memory Section, 35... Communication Section, 36... Imaging Section, 40... Challenger Terminal (Participant Terminal, Terminal Device), 41... Input Section, 42... Display Section, 43... Control Section, 431... Judgment Data Transmission Section, 44... Memory Section, 45... Communication Section, 46... Imaging Section, 50... Certifier Terminal, 51... Input Section, 52... Display Section, 53... Control Section, 531... Certifier Key Generation Section (Transmission Section), 532... Code Reading Section, 533... Judgment Data Transmission Section, 54... Memory Section, 55... Communication Section, 56... Imaging Section, 60... Sponsor Company Server, 70... Challenge App, 71... Member Secret Key, 72... Public Address, 73... Campaign Secret Key, 80... Certifier App, 81... Certifier Secret Key, 82... Public Address, N... Network

Claims

1. A challenge support system comprising an operator server, a blockchain network, and participant terminals, wherein the operator server, is a contract generation unit that transmits contract conditions regarding tasks to be achieved by users to the blockchain network, the contract conditions including conditions for achieving the tasks and a deadline for achieving the tasks, a contract generation unit, an entry reception unit that receives information indicating entry to the tasks from the participant terminals, a participant information transmission unit that transmits information of participants who have received the entry to the blockchain network, and is provided with, wherein the participant terminals, an entry unit that transmits information indicating entry to the tasks to the operator server, and a setting transmission unit that transmits to the blockchain network the amount of funds deposited for the tasks, the fund distribution setting at the time of success of the tasks, and the fund distribution setting at the time of failure of the tasks, the fund distribution setting at the time of success and the fund distribution setting at the time of failure each including one or more distribution destinations and the amount of money distributed to each distribution destination, a setting transmission unit, a determination data transmission unit that transmits determination data used to determine whether the contract conditions are satisfied to the blockchain network, and is provided with, The smart contract included in the blockchain network determines whether the contract conditions are satisfied based on the determination data transmitted from the participant terminal, and if the contract conditions are satisfied by the deadline, transfers the funds to each distribution destination according to the fund distribution setting at the time of success of the tasks, A challenge support system that transfers the funds to each distribution destination according to the fund distribution setting at the time of failure of the tasks if the contract conditions are not satisfied by the deadline.

2. The operator server, further includes a key generation unit that generates information for participating in the tasks and stores it in a storage unit communicably connected to the operator server, The entry reception unit receives information for participating in the tasks from the participant terminal, and accepts the entry from the participant terminal when the information for participating in the tasks received from the participant terminal matches the information stored in the storage unit. The challenge support system according to claim 1.

3. The operator server, The system further includes a content reception unit that receives content and information for identifying the content from the determination data transmission unit of the participant terminal and stores them in a storage unit communicably connected to the operator server. The determination data transmission unit of the participant terminal transmits the determination data including the information for identifying the content to the blockchain network, and transmits the content and the information for identifying the content to the operator server. The challenge support system according to claim 1 or 2.

4. The challenge support system further includes a transmitter that transmits information of a certifier to the operator server, and a determination data transmission unit that transmits determination data used for determining whether the contract conditions are satisfied to the blockchain network and includes a certifier terminal. The operator server further includes a certifier registration unit that receives the information of the certifier from the certifier terminal. The participant information transmitter transmits the information of the certifier to the blockchain network. The challenge support system according to any one of claims 1 to 3.

5. The participant terminal includes a first participant terminal including at least the entry unit and the setting transmitter, and a second participant terminal including at least the determination data transmission unit. The challenge support system according to any one of claims 1 to 4.

6. The operator server further includes a token contract generation unit that transmits data related to tokens for each participant to the blockchain network. When the contract conditions are satisfied by the deadline, the smart contract of the blockchain network transmits tokens to the token contract generated in the blockchain network by transmitting the data related to the tokens. The challenge support system according to any one of claims 1 to 5.

7. An entry unit that transmits information indicating the user's entry into a task to be achieved to the operator server ​ ​ ​ A setting transmission unit that transmits to the blockchain network the amount of funds to be deposited for the task, the fund distribution setting upon success of the task, and the fund distribution setting upon failure of the task, wherein the fund distribution setting upon success and the fund distribution setting upon failure each include one or more distribution destinations and the amount to be distributed to each distribution destination, the setting transmission unit A determination data transmission unit that transmits to the blockchain network determination data used to determine whether the contract conditions regarding the task are satisfied A terminal device comprising the same. **Claim 8** A computer performs a step of transmitting to an operator server information indicating a user's entry into a task to be achieved; a step of transmitting to the blockchain network the amount of funds to be deposited for the task, the fund distribution setting upon success of the task, and the fund distribution setting upon failure of the task, wherein the fund distribution setting upon success and the fund distribution setting upon failure each include one or more distribution destinations and the amount to be distributed to each distribution destination; a step of transmitting to the blockchain network determination data used to determine whether the contract conditions regarding the task are satisfied A method including the above. **Claim 9** A computer is caused to perform a process of transmitting to an operator server information indicating a user's entry into a task to be achieved; a process of transmitting to the blockchain network the amount of funds to be deposited for the task, the fund distribution setting upon success of the task, and the fund distribution setting upon failure of the task, wherein the fund distribution setting upon success and the fund distribution setting upon failure each include one or more distribution destinations and the amount to be distributed to each distribution destination; a process of transmitting to the blockchain network determination data used to determine whether the contract conditions regarding the task are satisfied A program for causing the above to be executed. **Claim 10** A terminal-side contract generation unit that transmits to the blockchain network contract conditions including conditions for achieving a task and a period for challenging the task, the amount of funds to be deposited for the task, the fund distribution setting upon success of the task, and the fund distribution setting upon failure of the task; A determination data transmission unit that transmits to the blockchain network determination data used to determine whether the contract conditions are satisfied A terminal device comprising the same. **Claim 11** The terminal device includes a first terminal device including at least the terminal-side contract generation unit, and a second terminal device including at least the determination data transmission unit. The terminal-side contract generation unit further transmits information of a person who determines whether contract conditions are satisfied to the blockchain network. The second terminal device transmits the determination data together with information associated with the information of the person who makes the determination. The terminal device according to claim 10.

12. A first means for transmitting to a server device contract conditions including conditions for achieving a task and a period for challenging the task, an amount of funds deposited for the task, a fund distribution setting at the time of task success, and a fund distribution setting at the time of task failure; A second means for transmitting determination data used to determine whether the contract conditions are satisfied to the server device A terminal device comprising: Means for receiving from the terminal device the contract conditions, the amount of the funds, the fund distribution setting at the time of task success, and the fund distribution setting at the time of task failure, and storing them in a storage unit communicably connected to the server device; Means for confirming the deposit of the funds from a user specified by the terminal device to a predetermined account; Means for determining whether the contract conditions are satisfied based on the determination data received from the terminal device; Means for moving the funds from the predetermined account to each distribution destination according to the fund distribution setting at the time of task success when the contract conditions are satisfied during the period, and moving the funds from the predetermined account to each distribution destination according to the fund distribution setting at the time of task failure when the contract conditions are not satisfied during the period A server device comprising: A challenge support system comprising:

13. The terminal device includes a first terminal device including at least the first means, and a second terminal device including at least the second means. The first means further transmits information of a person who determines whether contract conditions are satisfied to the server device. The second terminal device transmits the determination data together with information associated with the information of the person who makes the determination. The challenge support system according to claim 12.

14. Means for receiving, from a first terminal device, contract conditions including conditions for achieving a task and a period for challenging the task, the amount of funds deposited for the task, a fund allocation setting upon successful completion of the task, and a fund allocation setting upon failure of the task, and storing them in a storage unit. Means for confirming the deposit of the funds into a predetermined account from the user specified by the first terminal device. Means for receiving, from a second terminal device, determination data used to determine whether the contract conditions are satisfied. Means for determining whether the contract conditions are satisfied based on the determination data. Means for moving the funds from the predetermined account to each distribution destination according to the fund allocation setting upon successful completion of the task if the contract conditions are satisfied during the period, and moving the funds from the predetermined account to each distribution destination according to the fund allocation setting upon failure of the task if the contract conditions are not satisfied during the period. An information processing apparatus comprising the above.

15. The fund allocation setting upon failure of the task includes a setting for allocating all or part of the forfeited funds, which are all or part of the funds, to a user different from the user who failed the task. The challenge support system according to any one of Claims 1 to 6.

16. The user different from the user who failed the task is a user who succeeded in the task among the users who entered the task. The challenge support system according to Claim 15.

17. The forfeited funds are equally distributed to the users who succeeded in the task. The challenge support system according to Claim 16.

18. The fund allocation setting upon failure of the task includes a setting for allocating all or part of the funds to the operator of the operator server. The challenge support system according to any one of Claims 1 to 6.

19. First means for transmitting to a server device the period for challenging a task and the amount of funds deposited by a user for the task. Second means for transmitting to the server device determination data used to determine whether conditions for achieving a task are satisfied during the period. A terminal device comprising the above. Means for receiving the period and the amount of funds from the terminal device and storing them in a storage unit communicably connected to the server device. means for determining whether or not conditions for achieving the task are satisfied during the period based on the determination data received from the terminal device; means for confiscating the funds from the user when it is determined that the conditions for achieving the task are not satisfied during the period; A server device comprising: A challenge support system comprising:

20. The terminal device includes a first terminal device including at least the first means and a second terminal device including at least the second means, The first means further transmits to the server device information of a person who determines whether or not conditions for achieving the task are satisfied during the period, The second terminal device transmits the determination data together with information associated with the information of the person who makes the determination, The challenge support system according to claim 18.

21. means for receiving from a first terminal device a period for challenging a task and an amount of funds deposited by a user for the task and storing them in a storage unit; means for receiving from a second terminal device determination data used for determining whether or not conditions for achieving the task are satisfied during the period; means for determining whether or not conditions for achieving the task are satisfied during the period based on the determination data; means for confiscating the funds from the user when it is determined that the conditions for achieving the task are not satisfied during the period; An information processing apparatus comprising:

Images