JP7079539B1 - Information processing methods, information processing equipment and programs - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing method or the like capable of lending and operating a hash rate held by a hash rate holder. SOLUTION: The information processing method according to one aspect obtains loan information regarding a hash rate loan held by a hash rate holder from a user, and operates the hash rate from the user who has received the loan of the hash rate. It is characterized in that it acquires consignment information regarding consignment and causes a computer to execute a process of determining a mining reward obtained by mining based on the hash rate for which operation is consigned as a reward for the user. [Selection diagram] Fig. 1

Description

The present invention relates to an information processing method, an information processing device and a program.

In recent years, virtual currencies (cryptographic assets) have become widespread. Patent Document 1 discloses a mining system that determines the type of virtual currency to be mined by a mining machine based on the rate of the virtual currency, the difficulty of mining, and the hash rate.

Japanese Unexamined Patent Publication No. 2020-126518

However, the invention according to Patent Document 1 has a problem that the hash rate held by the hash rate holder cannot be lent and operated.

One aspect is to provide an information processing method or the like capable of lending and operating the hash rate held by the hash rate holder.

The information processing method according to one aspect obtains loan information regarding the lending of the hash rate held by the hash rate holder from the user, and consignment information regarding the operation consignment of the hash rate from the user who has received the loan of the hash rate. Is obtained, and the computer is made to execute a process of determining the mining reward obtained by the mining based on the hash rate entrusted to the operation as a reward for the user.

In one aspect, it is possible to lend and manage hash rates held by hash rate holders.

It is explanatory drawing which shows the outline of the hash rate operation system. It is a block diagram which shows the configuration example of a server. It is explanatory drawing which shows an example of the record layout of a hash rate DB and a user DB. It is explanatory drawing which shows an example of the record layout of the loan management DB and the operation management DB. It is explanatory drawing which shows an example of the record layout of a consignment management DB and a mining pool DB. It is a block diagram which shows the configuration example of the node of a blockchain. It is a block diagram which shows the configuration example of a user terminal. It is explanatory drawing explaining the process of determining the mining reward for a user. It is explanatory drawing which shows an example of the lending screen of a hash rate. It is explanatory drawing which shows an example of the selection screen of a mining pool. It is a flowchart which shows the processing procedure at the time of determining the mining reward for a user. It is a flowchart which shows the processing procedure at the time of determining the mining reward for a user. It is a flowchart which shows the process procedure of the subroutine of the process of acquiring loan information. It is a flowchart which shows the process procedure of the subroutine of the process of acquiring consignment information. It is a flowchart which shows the processing procedure of the subroutine of the selection processing of a mining pool. It is explanatory drawing which shows an example of the record layout of the loan management DB and the operation management DB in Embodiment 2. It is explanatory drawing explaining the process which distributes a mining reward to a plurality of users. It is a flowchart which shows the processing procedure at the time of allocating the mining reward to each user.

Hereinafter, the present invention will be described in detail with reference to the drawings showing the embodiments thereof.

(Embodiment 1)
The first embodiment relates to a mode in which a hash rate held by a hash rate holder is lent to a user, and a mining reward obtained by operating the hash rate is distributed to the user. Hash rate is the computational power in mining, that is, the mining speed. It is a numerical value that indicates how much hash (fixed length data obtained by converting a certain data) can be generated within a certain range and a certain time, so the more hash is generated, the newer it is. The probability of being able to mine a large block increases. Hash rate holders are providers that provide cloud mining.

FIG. 1 is an explanatory diagram showing an outline of a hash rate operation system. The system of this embodiment includes an information processing device 1, a blockchain system 2, and an information processing terminal 3, and each device transmits / receives information via a network N such as the Internet.

The information processing device 1 is an information processing device that processes, stores, and transmits / receives various information. The information processing device 1 is, for example, a server device, a personal computer, a general-purpose tablet PC (personal computer), or the like. In the present embodiment, the information processing device 1 is assumed to be a server device, and is referred to as a server 1 in the following for the sake of brevity.

The blockchain system 2 is a distributed ledger technology or a distributed network. The blockchain system 2 is composed of a plurality of nodes 21 that execute consensus processing. Each of the nodes 21 keeps a copy of the blockchain data through the execution of the consensus process. The blockchain system 2 generates a unit of data called a block at regular time intervals and stores the data by connecting them like a chain. Each of the nodes 21 mines based on the hash rate.

The blockchain system 2 is autonomously managed by using a peer-to-peer network and a distributed time stamp server. Since the data is stored in a chain, once the data in the block is stored, it is difficult to retroactively change the data. The blockchain system 2 may be a public type, a private type, or a consortium type. The unit of data may be individual transactions instead of blocks. In addition to the chain shape, the data may be stored in a stored format such as a directed acyclic graph. In the following, for the sake of brevity, the blockchain system 2 will be read as the blockchain 2.

The information processing terminal 3 is a terminal device that acquires loan information related to hash rate lending and consignment information related to the operation consignment of the hash rate, and receives and displays mining rewards obtained by mining based on the hash rate. be. The information processing terminal 3 is, for example, a smartphone, a mobile phone, a wearable device such as an Apple Watch (registered trademark), a tablet, an information processing device such as a personal computer terminal. In the following, for the sake of brevity, the information processing terminal 3 will be read as the user terminal 3.

The server 1 according to the present embodiment acquires the loan information regarding the loan of the hash rate held by the hash rate holder from the user terminal 3 of the user. The server 1 acquires the consignment information regarding the operation consignment of the hash rate from the user terminal 3 of the user. The server 1 determines the mining reward obtained by the mining based on the hash rate entrusted to the operation as the reward for the user.

FIG. 2 is a block diagram showing a configuration example of the server 1. The server 1 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, a reading unit 16, and a large-capacity storage unit 17. Each configuration is connected by bus B.

The control unit 11 includes arithmetic processing units such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit), and reads out a control program 1P (program product) stored in the storage unit 12. By executing it, various information processing, control processing, etc. related to the server 1 are performed. Further, the control program 1P includes a program that executes processes such as generation / execution of smart contracts such as Ethereum's Geth (Go-Ethereum) and Mist Wallet, virtual currency transfer, account creation, and mining. Although the control unit 11 is described as a single processor in FIG. 2, it may be a multiprocessor.

The storage unit 12 includes memory elements such as a RAM (Random Access Memory) and a ROM (Read Only Memory), and stores the control program 1P or data required for the control unit 11 to execute processing. Further, the storage unit 12 temporarily stores data and the like necessary for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing processing related to communication, and transmits / receives information to / from the node 21 of the blockchain 2 or the user terminal 3 or the like via the network N.

The input unit 14 is an input device such as a mouse, a keyboard, a touch panel, or a button, and outputs the received operation information to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL (electroluminescence) display, or the like, and displays various information according to the instructions of the control unit 11.

The reading unit 16 reads a portable storage medium 1a including a CD (Compact Disc) -ROM or a DVD (Digital Versatile Disc) -ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 16 and store it in the large-capacity storage unit 17. Further, the control unit 11 may download the control program 1P from another computer via the network N or the like and store it in the large-capacity storage unit 17. Furthermore, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

The large-capacity storage unit 17 includes a recording medium such as an HDD (Hard disk drive) or SSD (Solid State Drive). The large-capacity storage unit 17 includes a hash rate DB (database: database) 171, a user DB 172, a loan management DB 173, an operation management DB 174, a consignment management DB 175, and a mining pool DB 176.

The hash rate DB 171 stores information about the hash rate. The user DB 172 stores information about the user. The loan management DB 173 stores loan information related to hash rate lending. The operation management DB 174 stores operation management information related to the operation of the hash rate. The consignment management DB 175 stores the consignment information regarding the operation consignment of the hash rate. The mining pool DB 176 stores a plurality of mining pool candidates.

In this embodiment, the storage unit 12 and the large-capacity storage unit 17 may be configured as an integrated storage device. Further, the large-capacity storage unit 17 may be composed of a plurality of storage devices. Furthermore, the large-capacity storage unit 17 may be an external storage device connected to the server 1.

The server 1 may execute various information processing and control processing by a single computer, or may be distributed and executed by a plurality of computers. Further, the server 1 may be realized by a plurality of virtual machines provided in one server, or may be realized by using a cloud server.

FIG. 3 is an explanatory diagram showing an example of the record layout of the hash rate DB 171 and the user DB 172.
The hash rate DB 171 includes a holder ID column, a name column, a provision quantity column, a provision period column, and a status column. The holder ID column stores the ID of the uniquely identified hash rate holder in order to identify each hash rate holder. The name column remembers the name of the hash rate holder. The hash rate holder of the present embodiment is a lender who lends the hash rate held to the user (borrower). The offer quantity column stores the quantity for which the hash rate can be lent. The offer period column stores the period during which the hash rate can be lent. The status column stores the lending status of the hash rate. The loan status includes, for example, "accepting", "lending", "waiting for cancellation", and the like.

The user DB 172 includes a user ID column, a name column, and a password column. The user ID column stores the ID of a uniquely identified user in order to identify each user. The name column stores the user's name. The password string stores the password used for the authentication process such as login. The user of the present embodiment is a borrower who receives a loan of the hash rate held by the hash rate holder (lender).

FIG. 4 is an explanatory diagram showing an example of the record layout of the loan management DB 173 and the operation management DB 174.
The loan management DB 173 includes a loan ID column, a holder ID column, a user ID column, a provision quantity column, a loan date and time column, a provision period column, and a loan fee column. The loan ID column stores the ID of the loan information uniquely specified in order to identify each loan information. The holder ID column stores the holder ID that identifies the hash rate holder (lender).

The user ID column stores a user ID that identifies a user (borrower) who has received a hash rate loan. The offer quantity column stores the offer quantity (loan quantity) of the hash rate. The loan date / time column stores information on the date and time when the hash rate was lent. The offer period column stores the offer period (loan period) of the hash rate. The loan fee column stores the loan fee (rental fee) paid by the user to the hash rate holder.

The operation management DB 174 has an operation ID column, a loan ID column, a holder ID column, a user ID column, a consignment ID column, a pool ID column, an operation start date and time column, an operation period column, a reward amount column, an operation fee column, and an allocation amount column. And the distribution date and time column is included. The operation ID column stores the operation ID of the operation information uniquely specified in order to identify each operation information. The loan ID column stores the loan ID that specifies the loan information of the hash rate. The holder ID column stores the holder ID that identifies the hash rate holder. The user ID column stores a user ID that identifies a user.

The consignment ID column stores the consignment ID that specifies the operation consignment of the hash rate. The pool ID column stores the pool ID that identifies the mining pool. The operation start date / time column stores the date / time information when the operation of the hash rate is started. The operation period column stores the operation period of the hash rate. The reward amount column stores the mining reward amount obtained by mining based on the hash rate. The management fee column stores the management fee related to the operation of the hash rate. The allocation amount column stores the mining reward amount allocated to the user. The distribution date / time column stores the date / time information in which the mining reward is distributed to the users.

FIG. 5 is an explanatory diagram showing an example of the record layout of the consignment management DB 175 and the mining pool DB 176.

The consignment management DB 175 includes a consignment ID column, a consignment source column, a consignment destination column, a consignment period column, a provision quantity column, a provision period column, and a consignment content column. The consignment ID column stores the ID of the consignment information uniquely specified in order to identify each consignment information. The consignment source column stores the consignment source information (for example, the consignment source ID or the consignment source name) of the operation consignment. The outsourcer column stores the outsourcer information (for example, outsourcer ID or outsourcer name) of the operation outsourcing. In this embodiment, the consignor is a user, and the consignee is a sponsor or system operator who operates the hash rate.

The consignment period column stores the consignment period of operation consignment. The offer quantity column stores the offer quantity of the hash rate. The offer period column stores the offer period of the hash rate. The consignment content column stores the content of the operation consignment or the terms of use at the time of use within the period. An electronic file (for example, a PDF (Portable Document Format) file) in which the consignment information is described may be stored in the consignment content column.

The mining pool DB 176 stores information about the mining pool. The mining pool is a mechanism for mining in cooperation with multiple miners (miners). By using the mining pool, it is possible to secure the computing power that can compete with large-scale businesses and stabilize the mining reward by sharing the mining power by the participating miners.

The mining pool DB176 includes a pool ID column and a pool name column. The pool ID column stores the pool ID of the mining pool that is uniquely identified in order to identify each mining pool. The pool name column stores the name of the mining pool.

The storage form of each DB described above is an example, and other storage forms may be used as long as the relationship between the data is maintained.

FIG. 6 is a block diagram showing a configuration example of the node 21 of the block chain 2. The node 21 of the block chain 2 includes a control unit 211, a storage unit 212, a communication unit 213, a reception unit 214, an output unit 215, a block generation unit 216, a block verification unit 217, and a block sharing unit 218. Each configuration is connected by bus B.

The control unit 211 autonomously and decentrally cooperates with the control unit of another node 21 (terminal), and always holds the latest blockchain (ledger: copy of blockchain data) in the storage unit 212. The storage unit 212 stores a blockchain (ledger) including transactions broadcast to a distributed network, information required for verification processing of information in the block, and the like.

The communication unit 213 is a communication module for performing processing related to communication. The reception unit 214 receives information to be recorded in the distributed network, which is a blockchain managed by the blockchain 2, from an external node. The output unit 215 outputs the blockchain information held by itself in response to a request from the external node.

The block generation unit 216 generates a block to be added to the block chain based on the information received by the reception unit 214. The block generation unit 216 generates a block including information based on the previous block and information received by the reception unit 214. Further, the block generation unit 216 searches for, for example, a nonce as a predetermined consensus process for a block generated by itself or a block generated by a node 21 of another block chain via a block sharing unit 218 described later. After performing processing or processing to add a signature, add a block to the blockchain (ledger) managed by itself. The block generated by the block generation unit 216 is finally added to the block chain 2 by a plurality of nodes 21 performing a predetermined consensus process.

When adding a block to the block chain held by the block verification unit 217, the block verification unit 217 verifies the information in the block. Normally, the block to be added is the block whose rule is satisfied earliest in the node 21 group including its own node, but the rule is actually set in consideration of the case where a malicious node 21 is included. May be verified whether is satisfied.

The block sharing unit 218 exchanges information between the nodes 21 belonging to the block chain 2. More specifically, the block sharing unit 218 transmits the information received by the reception unit 214, the block generated by the block generation unit 216, the block received from the other node 21, and the like to the other node 21 as appropriate. As a result, all the nodes 21 share this information and the latest blockchain 2 as much as possible.

The configuration of FIG. 6 is merely an example, and the node 21 of the blockchain can execute a predetermined consensus process for sharing and managing the blockchain 2 which is difficult to be tampered with by a plurality of nodes, and is external. The specific configuration is not limited as long as the node can add information to the distributed network and refer to the information recorded in the distributed network in response to a request from the node.

The server 1 may be a node 21 of the blockchain 2.

FIG. 7 is a block diagram showing a configuration example of the user terminal 3. The user terminal 3 includes a control unit 31, a storage unit 32, a communication unit 33, an input unit 34, and a display unit 35. Each configuration is connected by bus B.

The control unit 31 includes an arithmetic processing unit such as a CPU and an MPU, and by reading and executing a control program 3P (program product) stored in the storage unit 32, various information processing, control processing, etc. related to the user terminal 3 are performed. I do. Further, the control program 3P includes a program that executes processes such as generation / execution of smart contracts such as Ethereum's Geth and Mist Wallet, remittance of virtual currency, account creation, and mining. Although the control unit 31 is described as a single processor in FIG. 7, it may be a multiprocessor.

The storage unit 32 includes memory elements such as RAM and ROM, and stores the control program 3P or data required for the control unit 31 to execute the process. Further, the storage unit 32 temporarily stores data and the like necessary for the control unit 31 to execute the arithmetic processing. The communication unit 33 is a communication module for performing processing related to communication, and transmits / receives information to / from the server 1 or the like via the network N. The input unit 34 may be a keyboard, a mouse, or a touch panel integrated with the display unit 35. The display unit 35 is a liquid crystal display, an organic EL display, or the like, and displays various information according to the instructions of the control unit 31.

FIG. 8 is an explanatory diagram illustrating a process of determining a mining reward for a user. The user terminal 3 acquires loan information regarding the loan of the hash rate held by the hash rate holder. For example, the user terminal 3 may accept input of loan information by the user. The loan information includes, for example, a holder ID, a user ID, a hash rate provided quantity, a loan date and time, a provision period, a loan fee, and the like.

The user terminal 3 acquires the consignment information regarding the operation consignment of the hash rate. For example, the user terminal 3 may accept input of consignment information by the user. Alternatively, the user terminal 3 may read the entrusted information from the electronic file in which the entrusted information is described. The electronic file may be, for example, a PDF file, a text file, a Word (registered trademark) file, or the like. The outsourced information includes outsourcer information (for example, user ID), outsourcee information (for example, ID of a sponsor or system operator who operates the hash rate), outsourcing period, hash rate provision quantity, and provision period. Or it includes the contents of the consignment.

The user terminal 3 accepts a user's selection of a mining pool from a plurality of mining pool candidates. Specifically, the user terminal 3 sends a request for acquisition of a plurality of mining pool candidates to the server 1. The server 1 receives the acquisition request transmitted from the user terminal 3.

The server 1 acquires a plurality of mining pool candidates from the mining pool DB 176 in response to the received acquisition request. The server 1 transmits the acquired plurality of mining pool candidates to the user terminal 3. The user terminal 3 receives a plurality of mining pool candidates transmitted from the server 1 and displays them on the screen. The user terminal 3 accepts the user's selection of a mining pool from the plurality of displayed mining pool candidates.

The user terminal 3 transmits the acquired loan information and consignment information, and the pool ID of the mining pool selected by the user to the server 1. The server 1 receives the loan information, the consignment information, and the pool ID transmitted from the user terminal 3. The server 1 stores the received loan information in the loan management DB 173. Specifically, the server 1 allocates a loan ID to the received loan information, and associates the allocated loan ID with the holder ID, user ID, provision quantity, loan date and time, provision period, and loan fee. It is stored in the loan management DB 173 as a record.

The server 1 stores the received consignment information in the consignment management DB 175. Specifically, the server 1 allocates a consignment ID to the received consignment information, associates it with the allocated consignment ID, and associates it with the consignment source ID, consignment destination ID, consignment period, hash rate provision quantity, provision period, and The contents of the consignment are stored in the consignment management DB 175 as one record.

The server 1 stores the operation management information of the hash rate in the operation management DB 174. Specifically, the server 1 allocates an operation ID, associates it with the allocated operation ID, and associates the assigned operation ID with the hash rate loan ID, owner ID, user ID, consignment ID, selected mining pool pool ID, and operation start. The date and time and the operation period are stored in the operation management DB 174 as one record.

Server 1 provides the hash rate to the selected mining pool. Specifically, the server 1 transmits transaction data (for example, a loan ID and a wallet address for receiving a mining reward) to any node 21 of the blockchain 2 corresponding to the selected mining pool. The wallet address is a mathematically derived account number based on the public key cryptography used in the blockchain 2. The node 21 of the blockchain 2 receives the transaction data transmitted from the server 1. The node 21 generates a block including at least the pre-block management information created based on the received transaction data and the blockchain information managed by the node 21.

Then, each node 21 of the blockchain 2 executes a process according to a predetermined consensus algorithm. For example, when the blockchain technology related to Bitcoin (registered trademark) is applied to this system, nodes 21, nodes 21, nodes 21 ... execute arithmetic processing called POW (Proof of Work) to update blockchain 2. Determine the node 21 to be used. POW is a (mining) operation process for searching for a certain correct answer value from a hash value stored in advance in the block immediately before the newly generated block.

When a new block is generated, the node 21 generates a hash value stored in the block immediately before the block and a hash value obtained by hashing the transaction data, and stores the hash value in the latest block. When generating the latest block, each node 21 solves a search problem of searching for a correct answer value (a nonce value in the Bitcoin example) from the hash value included in the previous block.

The probability of finding the correct answer value in one calculation process is low, and when blockchain technology related to virtual currencies such as Bitcoin is applied, it takes about 10 minutes on average. Each node 21 simultaneously executes the arithmetic processing of the search problem and searches for the correct answer value. Then, the node 21 that finds the correct answer value earliest is given the authority to generate the latest block. When an unauthorized person tries to rewrite the data of the blockchain, it is necessary to generate a block at a speed higher than the arithmetic processing speed of all the well-meaning verifiers (node 21), and it is extremely difficult to actually perform the illegal rewriting. It has become.

If the search is successful, the node 21 generates the latest block storing the verified transaction data, and notifies the other nodes 21, 21, 21 ... Of the data related to the block. In this case, as described above, the node 21 generates a hash value from the hash value and transaction data stored in the previous block, stores the hash value in a new block, and notifies each node 21. ..

Since the hash value stored in the new block includes the hash value of the previous block, each block constituting the block chain is associated in chronological order. The other nodes 21, 21, 21 ... Store the transaction data in the storage unit 212 after confirming the validity of the data of the notified block. As a result, the data related to the same blockchain is duplicated and stored in the storage unit 212 of each node 21, 21, 21 ...

The administrator (minor) of the node 21 that succeeds in the search is given a mining reward that succeeds in the search. That is, the administrator of the node 21 that succeeds in the search is paid the fee for each transaction stored in the block. As a result, the administrator is given a mining reward (incentive) for investing a computational resource called a node 21.

In the above, POW is used as a method for determining the update authority of the blockchain, but the present embodiment is not limited to this, and for example, POI (Proof of Importance), POS (Proof of Stake), etc. are used. You may use it. Further, although the system to which the Bitcoin technique is applied has been described above, the present embodiment is not limited to this. For example, in addition to Bitcoin, blockchain technology related to Ethereum, Hyperledger Fabric, etc. may be applied.

If the mining pool selected by the user is successfully mined, the mining pool administrator is first given a successful mining reward for the search. Next, the manager of the mining pool is given a mining reward based on the degree of contribution (for example, operating time, etc.) that is the arithmetic processing capacity of each node 21 (participant of the mining pool) of the mining pool. The allocation amount to be allocated to each node 21 is calculated. The manager of the mining pool allocates the calculated allocation amount to each node 21.

When the node 21 to be allocated is the node 21 that produces the hash rate entrusted with the operation, the node 21 is the allocation amount allocated by the manager of the mining pool (obtained by mining based on the hash rate). Mining reward) is sent to the wallet address that receives the mining reward. The server 1 receives the mining reward transmitted from the node 21 via the wallet address.

The server 1 calculates the management fee related to the operation of the hash rate according to a predetermined standard. For example, the management fee may be calculated by multiplying the mining reward amount by a predetermined ratio (for example, 1%). The management fee may be a fixed amount. The server 1 deducts the calculated management fee from the mining reward amount, and determines the mining reward amount after deduction as the reward amount for the user.

The server 1 stores the mining reward amount, the management fee, the reward amount (allocation amount) for the user, and the allocation date and time when the reward amount is allocated to the user in the operation management DB 174 in association with the operation ID of the hash rate. The server 1 transmits the determined mining reward amount to the user terminal 3 in virtual currency or legal currency. The user terminal 3 receives the mining reward amount transmitted from the server 1 and displays it on the screen.

FIG. 9 is an explanatory diagram showing an example of a hash rate loan screen. The loan screen includes an annual yield display field 11a, a hash rate display field 11b, and a loan button 11c. The annual yield display column 11a is a display column for displaying the annual yield of the mining reward obtained by mining based on the hash rate. The hash rate display field 11b is a display field for displaying information regarding the hash rate. The loan button 11c is a button for lending a hash rate.

The server 1 acquires information about the hash rate held by each hash rate holder from the hash rate DB 171 of the large-capacity storage unit 17. Information about the hash rate includes the holder ID, the quantity of the hash rate provided, the period and status of provision (“accepting”, “renting”, “waiting for cancellation”, etc.). The server 1 calculates the static annual yield based on the acquired quantity of each hash rate provided. Static annual yield is the expected benefit of using hashrate-based mining. For example, the server 1 may calculate (predict) the static annual yield based on the past actual value at the hash rate.

Further, the server 1 calculates the loan fee (purchase price) of each hash rate based on the provided quantity and the provision period of each hash rate acquired. For example, if the daily loan fee is 1.1466 USDT for a hash rate with a supply quantity of 300 MH / s, the server 1 has a loan fee of 113.51 USDT for the hash rate during the 99-day offer period. Is calculated. USDT (tether) is a peg currency operated by Tether Limited, and is also called stablecoin. The loan fee may be paid in other types of cryptographic assets such as Bitcoin or Ethereum, or in legal currency.

The server 1 transmits to the user terminal 3 the provided quantity and the provision period of each acquired hash rate, the static annual yield based on the calculated hash rates, and the loan fee of each calculated hash rate. The user terminal 3 receives the provided quantity, the provided period, the static annual yield, and the loan fee of each hash rate transmitted from the server 1 and displays them on the screen. As shown in the figure, the static annual yield is displayed in the annual yield display column 11a, and the provided quantity of the hash rate, the provision period (expiration date), and the loan fee (purchase price) are displayed in the hash rate display column 11b.

The user terminal 3 sets the title of the loan button 11c (character string displayed on the loan button 11c) corresponding to each hash rate based on the state of each acquired hash rate. Specifically, when the hash rate state is "accepting", the user terminal 3 sets the title of the loan button 11c to "rent" and puts the loan button 11c in an operable active state. Set. When the state of the hash rate is "renting", the user terminal 3 sets the title of the lending button 11c to "sold out" and sets the lending button 11c to an inoperable inactive (inactive) state. When the state of the hash rate is "waiting for cancellation", the user terminal 3 sets the title of the loan button 11c to "waiting for cancellation" and sets the loan button 11c to an inoperable inactive state.

When the user terminal 3 accepts the touch (click) operation of the loan button 11c whose title is "rent", the user terminal 3 transitions to the payment screen (not shown). The user terminal 3 performs payment processing for the loan of the corresponding hash rate, for example, through a payment system or platform. After performing the settlement process, the user terminal 3 transmits the holder ID, the provided quantity of the hash rate, the provision period, the loan date and time, and the loan fee to the server 1 in association with the user ID.

The server 1 receives the user ID, the holder ID, the provided quantity of the hash rate, the provision period, the loan date and time, and the loan fee transmitted from the user terminal 3. The server 1 allocates a loan ID, associates it with the allocated loan ID, and stores the received user ID, holder ID, hash rate provision quantity, provision period, loan date and time, and loan fee as one record in the loan management DB 173. do.

FIG. 10 is an explanatory diagram showing an example of a mining pool selection screen. The selection screen includes a loan information display field 12a, a mining pool selection field 12b, and a decision button 12c. The loan information display column 12a is a display column for displaying loan information related to hash rate lending. The mining pool selection column 12b is a column for accepting the selection of the mining pool. The decision button 12c is a button for determining the selected mining pool.

The user terminal 3 transmits a request for acquiring a plurality of mining pool candidates to the server 1 in association with the user ID. The server 1 receives the user ID and the acquisition request transmitted from the user terminal 3. Based on the user ID, the server 1 acquires the loan information (loan ID, holder ID, user ID, provision quantity, etc.) of the hash rate lent to the user by the hash rate holder from the loan management DB 173. The server 1 acquires the pool IDs and pool names of a plurality of mining pool candidates from the mining pool DB 176 in response to the received acquisition request.

The server 1 transmits the acquired hash rate loan information, pool IDs and pool names of a plurality of mining pool candidates to the user terminal 3. The user terminal 3 receives the hash rate loan information transmitted from the server 1 and the pool IDs and pool names of a plurality of mining pool candidates and displays them on the screen. As shown in the figure, loan information including a loan ID, a holder ID, a user ID, and a provided quantity is displayed in the loan information display field 12a, and pool names of a plurality of mining pool candidates are displayed in the mining pool selection field 12b. ..

When the user terminal 3 accepts the selection operation of the mining pool selection field 12b, the user terminal 3 acquires the pool ID of the mining pool selected by the user. When the user terminal 3 receives the touch operation of the decision button 12c, the user terminal 3 associates the acquired pool ID of the mining pool with the loan ID and transmits the pool ID to the server 1. The server 1 associates the pool ID transmitted from the user terminal 3 with the loan ID and stores it in the operation management DB 174.

In the present embodiment, the mining pool selection process is performed on the user terminal 3 side, but the present invention is not limited to this. For example, the information processing terminal of the sponsor or the system operator may accept the selection of the mining pool by the sponsor or the system operator and transmit the received pool ID of the mining pool to the server 1. Alternatively, the server 1 may directly accept the selection of the mining pool by the sponsor, the system operator, or the like.

11 and 12 are flowcharts showing a processing procedure for determining a mining reward for a user. The control unit 31 of the user terminal 3 accepts the input of login information by the input unit 34 (step S301). The login information includes a user ID as user identification information, authentication information for user authentication (for example, a password), and the like. The control unit 31 performs a login process based on the received login information (step S302).

For example, the control unit 31 transmits the received login information (user ID and password) to the server 1 by the communication unit 33. The control unit 11 of the server 1 compares the login information transmitted from the user terminal 3 with the login information stored in the user DB 172 of the large-capacity storage unit 17. The control unit 11 transmits the comparison result to the user terminal 3 as a result of the login process. The control unit 31 of the user terminal 3 receives the result of the login process transmitted from the server 1 by the communication unit 33.

The control unit 31 determines whether or not the login was successful based on the result of the login process (step S303). When the control unit 31 determines that the login has failed (NO in step S303), the control unit 31 displays an error message including the login failure on the display unit 35, and ends the process. When it is determined that the login is successful (YES in step S303), the control unit 31 executes a subroutine of the process of acquiring the loan information regarding the hash rate loan (step S304). The loan information includes, for example, a holder ID, a user ID, a quantity provided, a date and time of loan, a period of provision, and the like.

The control unit 31 executes a subroutine of processing for acquiring the consignment information regarding the operation consignment of the hash rate (step S305). The consignment information includes the consignor ID (for example, user ID) of the operation consignment, the consignee ID (for example, the ID of the sponsor or system operator who operates the hash rate), the consignment period, the quantity of the hash rate provided, and the provision period. Or it includes the contents of the consignment. The control unit 31 executes a subroutine for selecting a mining pool (step S306). The subroutines for the loan information acquisition process, the consignment information acquisition process, and the mining pool selection process will be described later.

The control unit 31 transmits the acquired loan information, the consignment information, and the pool ID of the selected mining pool to the server 1 by the communication unit 33 (step S307). The control unit 11 of the server 1 receives the loan information, the consignment information, and the pool ID transmitted from the user terminal 3 by the communication unit 13 (step S101).

The control unit 11 stores the received loan information in the loan management DB 173 of the large-capacity storage unit 17 (step S102). Specifically, the server 1 allocates a loan ID to the received loan information, and associates the allocated loan ID with the holder ID, user ID, provision quantity, loan date and time, provision period, and loan fee. It is stored in the loan management DB 173 as a record.

The control unit 11 stores the received consignment information in the consignment management DB 175 of the large-capacity storage unit 17 (step S103). Specifically, the control unit 11 allocates a consignment ID to the received consignment information, associates it with the allocated consignment ID, and associates it with the consignment source ID, consignment destination ID, consignment period, hash rate provision quantity, and provision period. And the contents of the consignment are stored in the consignment management DB 175 as one record.

The control unit 11 stores the operation management information of the hash rate in the operation management DB 174 of the large-capacity storage unit 17 (step S104). Specifically, the control unit 11 allocates an operation ID, associates it with the allocated operation ID, and associates the assigned operation ID with the hash rate loan ID, owner ID, user ID, consignment ID, selected mining pool pool ID, and operation start. The date and time and the operation period are stored in the operation management DB 174 as one record.

The control unit 11 creates transaction data including a holder ID, a user ID, a loan ID, a hash rate provision quantity, a provision period, a wallet address for receiving a mining reward, and the like (step S105). The control unit 11 transmits the created transaction data to any node 21 of the blockchain 2 corresponding to the selected mining pool by the communication unit 13 (step S106).

The control unit 211 of the node 21 of the blockchain 2 receives the transaction data transmitted from the server 1 by the communication unit 213 (step S201). The control unit 211 of the node 21 records the received transaction data in the storage unit 212 (step S202). The control unit 211 of the node 21 performs mining processing (step S203).

If the mining is successful in the mining pool selected by the user, the control unit 211 of the node 21 acquires the mining reward amount to be distributed to the node 21 (step S204). Specifically, if the mining is successful, the manager of the mining pool is given a mining reward for the successful search. The manager of the mining pool calculates the allocation amount to be distributed to each node 21 from the given mining reward based on the degree of contribution that becomes the arithmetic processing capacity of each node 21 of the mining pool. The manager of the mining pool allocates the calculated allocation amount to each node 21. The process of allocating the mining reward to each node 21 may be executed by a smart contract. When the node 21 that succeeds in the search is the node 21 that produces the hash rate for which the operation is outsourced, the mining reward obtained by mining based on the hash rate may be directly given to the node 21.

The control unit 211 of the node 21 sends the acquired mining reward amount to the wallet address for receiving the mining reward to the server 1 via the communication unit 213 (step S205). The control unit 11 of the server 1 receives the mining reward amount transmitted from the node 21 via the wallet address by the communication unit 13 (step S107). The control unit 11 calculates the management fee related to the operation of the hash rate according to a predetermined standard (step S108). For example, the control unit 11 may calculate the management fee by multiplying the mining reward amount by a predetermined ratio (for example, 1%).

The control unit 11 deducts the calculated management fee from the mining reward amount, and calculates the mining reward amount after deduction as the reward amount for the user (step S109). The control unit 11 stores a large amount of reward information including the mining reward amount, the management fee, the reward amount (allocation amount) for the user, and the distribution date and time when the reward amount is distributed to the user in association with the operation ID of the hash rate. It is stored in the operation management DB 174 of 17 (step S110).

The control unit 11 transmits the reward amount to the user to the user terminal 3 by the communication unit 13 (step S111). The process of allocating the mining reward to the users may be executed by the smart contract. The control unit 31 of the user terminal 3 receives the reward amount for the user transmitted from the server 1 by the communication unit 33 (step S308). The control unit 31 displays the reward amount for the received user on the display unit 35 (step S309), and ends the process.

According to the present embodiment, it is possible to distribute the mining reward obtained by mining based on the hash rate to the user who has been entrusted with the operation of the hash rate.

FIG. 13 is a flowchart showing a processing procedure of a subroutine of processing for acquiring loan information. The control unit 31 of the user terminal 3 acquires a license condition including a usage condition of the hash rate from the storage unit 32 on the hash rate operation system (platform) (step S01). The license conditions may be stored in the storage unit 12 or the large-capacity storage unit 17 of the server 1. The control unit 31 displays the acquired license conditions on the display unit 35 (step S02).

The control unit 31 accepts the input of the license of the hash rate operation system by the user by the input unit 34 (step S03). The control unit 31 displays the hash rate lending screen (FIG. 9) on the display unit 35 (step S04). The control unit 31 accepts the user's selection of the hash rate to be lent by the input unit 34 through the hash rate lending screen (step S05).

The control unit 31 displays a loan fee payment screen (not shown) on the display unit 35 (step S06). When the user's payment instruction is received on the loan fee payment screen, the control unit 31 processes the loan fee payment, for example, through a payment system or platform (step S07). The control unit 31 determines whether or not the loan fee has been successfully paid (step S08).

When the control unit 31 determines that the payment of the loan fee has failed (NO in step S08), the control unit 31 displays an error message including the failure to pay the loan fee on the display unit 35 (step S09). The control unit 31 ends the subroutine of the loan information acquisition process and returns. When the control unit 31 determines that the payment of the loan fee is successful (YES in step S08), the control unit 31 acquires the received loan information (holder ID, user ID, supply quantity, loan date / time, provision period, loan fee, etc.). (Step S10). The control unit 31 ends the subroutine of the loan information acquisition process and returns.

FIG. 14 is a flowchart showing a processing procedure of a subroutine of processing for acquiring consignment information. The control unit 31 of the user terminal 3 displays an operation consignment screen (not shown) on the display unit 35 (step S21). The control unit 31 inputs the user's permission to reuse the hash rate usage right (consignment of operation of the hash rate usage right) to the hash rate licensed by the hash rate holder to the user through the operation consignment screen. Accepted by the input unit 34 (step S22).

The control unit 31 receives input of consignment information including the consignment source ID, consignee ID, consignment period, hash rate provision quantity, provision period or consignment content, etc. by the input unit 34 (step S23). The control unit 31 ends the subroutine of the entrustment information acquisition process and returns.

FIG. 15 is a flowchart showing a processing procedure of a subroutine for selecting a mining pool. The control unit 31 of the user terminal 3 acquires the pool IDs and pool names of the candidates of the plurality of mining pools from the mining pool DB 176 of the large-capacity storage unit 17 of the server 1 (step S31). The control unit 31 displays the acquired pool names of a plurality of mining pool candidates on the mining pool selection screen (FIG. 10) via the display unit 35 (step S32).

The control unit 31 accepts the user's selection of a mining pool from the plurality of mining pool candidates by the input unit 34 (step S33). The control unit 31 acquires the pool ID of the mining pool selected by the user (step S34). The control unit 31 ends the subroutine of the mining pool selection process and returns.

According to this embodiment, it is possible to accept the selection of a mining pool from a plurality of mining pool candidates.

According to the present embodiment, it is possible to determine the loan fee of the hash rate based on the provision quantity and the provision period of the hash rate.

According to this embodiment, it is possible to calculate the management fee related to the operation of the hash rate according to a predetermined standard.

(Embodiment 2)
In the second embodiment, a hash rate commissioned by a plurality of users is provided to the mining pool, and a mining reward obtained by mining based on the hash rate is distributed according to the loan information of the hash rate of each user. Regarding morphology. The description of the contents overlapping with the first embodiment will be omitted.

FIG. 16 is an explanatory diagram showing an example of the record layout of the loan management DB 173 and the operation management DB 174 in the second embodiment. The description of the contents overlapping with FIG. 4 will be omitted.
The loan management DB 173 and the operation management DB 174 include a sub-lending ID column. The sub-lending ID column stores a sub-lending ID that specifies the hash rate lending information for each user.

FIG. 17 is an explanatory diagram illustrating a process of allocating a mining reward to a plurality of users. A hash rate owned by the same hash rate holder can be lent to a plurality of users (for example, user A, user B, and user C). When the server 1 provides the mining pool with a hash rate commissioned by a plurality of users, the server 1 acquires a mining reward obtained by mining based on the hash rate.

The server 1 calculates the management fee related to the operation of the hash rate according to a predetermined standard, and deducts the calculated management fee from the mining fee. The server 1 calculates the distribution amount to each user from the deducted mining reward according to the loan information of the hash rate of each user. The server 1 transmits the calculated allocation amount to the user terminal 3 of each user.

For example, each user terminal 3 of user A, user B, and user C has a hash rate loan information (holder ID, user ID, hash rate loan ID, sub-rental ID, provision quantity, loan date and time, provision period, etc.). , And the consignment information (consignment source ID, consignee ID, consignment period or consignment content, etc.) of the hash rate is acquired. Each user terminal 3 transmits the acquired loan information and consignment information to the server 1.

The server 1 receives the loan information and the consignment information transmitted from each user terminal 3. The server 1 stores the received loan information in the loan management DB 173, and stores the received consignment information in the consignment management DB 175. After that, the server 1 processes the selection of the mining pool, the storage of the operation management information, the transmission of the transaction data, the receipt of the mining reward amount obtained by the mining based on the hash rate, and the like, as in the process of the first embodiment. I do.

When the server 1 receives the mining reward amount obtained by mining based on the hash rate, the server 1 calculates the management fee related to the operation of the hash rate according to a predetermined standard. Since the calculation process of the management fee is the same as that of the first embodiment, the description thereof will be omitted. The server 1 deducts the calculated management fee from the mining reward amount.

The server 1 calculates the mining reward amount (allocation amount) to be distributed to each user from the deducted mining reward according to the loan information of the hash rate of each user. Specifically, the server 1 acquires the provision quantity of the hash rate lent to each user by the hash rate holder from the loan management DB 173 based on the loan ID and the sub-lending ID of the hash rate.

As shown, the hash rate holder has a "100TH / s" hash rate. The hash rate holder lends user A a "50 TH / s" hash rate, user B a "30 TH / s" hash rate, and user C a "20 TH / s" hash rate. .. The server 1 calculates the distribution amount to each user from the mining reward after deduction based on the ratio between the acquired quantity of the hash rate provided by each user and the total amount of loans of the hash rate.

The server 1 stores the mining reward amount, the management fee, the allocation amount to the user, and the allocation date and time for each user in the operation management DB 174 in association with the operation ID, the loan ID, and the sub-rental ID of the hash rate. The server 1 transmits the calculated allocation amount to each user to the user terminal 3 of each user. Each user terminal 3 receives the distribution amount transmitted from the server 1 and displays it on the screen.

FIG. 18 is a flowchart showing a processing procedure when allocating a mining reward to each user. The control unit 11 of the server 1 receives the mining reward amount transmitted from the node 21 of the blockchain 2 by the communication unit 13 (step S121). The control unit 11 calculates, for example, a management fee related to the operation of the hash rate by multiplying the mining reward amount by a predetermined ratio (for example, 1%) (step S122). The control unit 11 deducts the calculated management fee from the received mining reward amount (step S123).

The control unit 11 obtains the loan information of each user from the loan management DB 173 of the large-capacity storage unit 17 based on the loan ID and the sub loan ID of the hash rate and the user IDs of the plurality of users who have received the loan of the hash rate. Acquire (step S124). The acquired loan information includes the quantity provided of the hash rate and the like. The control unit 11 calculates the distribution amount to each user from the deducted mining reward based on the ratio between the acquired quantity of the hash rate provided by each user and the total amount of loans of the hash rate (step S125). ..

The control unit 11 manages the operation of the large-capacity storage unit 17 by associating the operation ID, the loan ID, and the sub-rental ID of the hash rate with the mining reward amount, the operation fee, the distribution amount to the user, and the distribution date and time for each user. Store in DB 174 (step S126). The control unit 11 transmits the calculated allocation amount to each user to the user terminal 3 of each user by the communication unit 13 (step S127). The control unit 31 of each user terminal 3 receives the distribution amount transmitted from the server 1 by the communication unit 33 (step S321). The control unit 31 of each user terminal 3 displays the received allocation amount on the display unit 35 (step S322), and ends the process.

According to the present embodiment, when a hash rate commissioned by a plurality of users is provided to the mining pool, the mining reward obtained by mining based on the hash rate can be distributed to each user.

The embodiments disclosed this time should be considered to be exemplary in all respects and not restrictive. The scope of the present invention is indicated by the scope of claims, not the above-mentioned meaning, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

1 Information processing device (server)
11 Control unit 12 Storage unit 13 Communication unit 14 Input unit 15 Display unit 16 Reading unit 17 Large-capacity storage unit 171 Hash rate DB
172 User DB
173 Lending management DB
174 Operation management DB
175 Consignment management DB
176 Mining pool DB
1a Portable storage medium 1b Semiconductor memory 1P control program 2 Blockchain system (blockchain)
21 Node 211 Control unit 212 Storage unit 213 Communication unit 214 Reception unit 215 Output unit 216 Block generation unit 217 Block verification unit 218 Block sharing unit 3 Information processing terminal (user terminal)
31 Control unit 32 Storage unit 33 Communication unit 34 Input unit 35 Display unit 3P control program

Claims (8)

Obtain loan information about the hash rate loan held by the hash rate holder from the user,
Obtaining consignment information regarding the operation consignment of the hash rate from the user who has received the loan of the hash rate,
An information processing method in which a computer executes a process of determining a mining reward obtained by mining based on the hash rate entrusted as a reward to the user. Output multiple mining pool candidates selectably,
The information processing method according to claim 1, wherein the user accepts a selection of a mining pool from a plurality of output mining pool candidates. The information processing method according to claim 1 or 2, wherein the hash rate is provided to the selected mining pool. The management fee related to the operation of the hash rate is calculated according to a predetermined standard, and
The calculated management fee is deducted from the mining fee,
The information processing method according to any one of claims 1 to 3, wherein the mining reward after deduction is determined as a reward for the user. The loan information includes the quantity and period of provision of the hash rate.
Obtain the provision quantity and provision period of the hash rate,
The information processing method according to any one of claims 1 to 4, wherein the loan fee of the hash rate is determined based on the acquired supply quantity and provision period. Providing the hash rate commissioned by multiple users to the mining pool,
The management fee related to the operation of the hash rate is calculated according to a predetermined standard, and
The calculated management fee is deducted from the mining fee,
The information processing method according to any one of claims 1 to 5, wherein the mining reward after deduction is distributed to each user according to the loan information of the hash rate of each user. The first acquisition unit that acquires loan information related to the loan of the hash rate held by the hash rate holder from the user,
A second acquisition unit that acquires consignment information regarding the operation consignment of the hash rate from the user who has received the loan of the hash rate, and
An information processing device including a determination unit that determines a mining reward obtained by mining based on the hash rate commissioned for operation as a reward for the user. Obtain loan information about the hash rate loan held by the hash rate holder from the user,
Obtaining consignment information regarding the operation consignment of the hash rate from the user who has received the loan of the hash rate,
A program that causes a computer to execute a process of determining a mining reward obtained by mining based on the hash rate commissioned as a reward for the user.

Images