WO2020143431A1

WO2020143431A1 - Bookkeeping method, mining pool server, terminal apparatus, mining node, and mining pool

Info

Publication number: WO2020143431A1
Application number: PCT/CN2019/127183
Authority: WO
Inventors: 程强
Original assignee: 深圳市红砖坊技术有限公司
Priority date: 2019-01-07
Filing date: 2019-12-20
Publication date: 2020-07-16
Also published as: CN109741039B; CN109741039A

Abstract

A bookkeeping method, a mining pool server, a terminal apparatus, a mining node, and a mining pool, pertaining to the technical field of blockchains. The bookkeeping method comprises: a mining pool server receiving and storing a hash value of a main body of a block header and a target difficulty value sent by a mining node; the mining pool server receiving a bookkeeping request sent by a terminal apparatus; the mining pool server sending the hash value of the main body of the block header and the target difficulty value to the terminal apparatus, such that a slave TEE determines whether an accumulated unused duration is greater than a lower accumulated unused duration threshold, and if so, signs bookkeeping right confirmation information; and the mining pool server receiving the bookkeeping right confirmation information sent by the terminal apparatus and a signature of the bookkeeping right confirmation information, and sending the two pieces of information to the mining node, such that the mining node generates a bookkeeping block and adds the bookkeeping block to a local blockchain. The method prevents waste of computational resources in slave TEEs, and reduces electrical energy consumption thereof.

Description

Accounting method, mining pool server, terminal equipment, mining node and mining pool

Cross-reference of related applications

This disclosure requires the priority of the Chinese patent application with the application number 2019100117501 and titled "Accounting Method, Mining Pool Server, Terminal Equipment, Mining Nodes and Mining Pool" submitted to the China Patent Office on January 07, 2019. The entire contents are incorporated by reference in this application.

Technical field

The present disclosure relates to the field of blockchain technology, and in particular, to an accounting method, mining pool server, terminal equipment, mining node, and mining pool.

Background technique

The existing blockchain generally uses a consensus algorithm to determine which miner node obtains the accounting right, and the miner node that obtains the accounting right can receive a pre-agreed reward (for example, digital currency). This process is called mining. Because mining can bring certain economic benefits, in some implementation schemes, the consensus calculation is stripped from the miner node, and many application specific integrated circuits (Application Specific Integrated Circuit, ASIC) miners connected by the remote provide consensus The calculated computing power forms a mining pool structure.

At present, the consensus algorithm used by each mining machine in the mining pool is mainly the Proof of Work (PoW) algorithm, which requires a large number of meaningless hash collision calculations during the competition of the accounting power of the mining machine , Leading to serious waste of computing resources and power consumption.

Summary of the invention

In view of this, embodiments of the present disclosure provide a billing method, mining pool server, terminal equipment, mining node, and mining pool, and adopt consensus based on accumulated unused time in the trusted execution environment of terminal equipment participating in mining Algorithms to save computing resources and reduce power consumption.

To achieve the above purpose, the embodiments of the present disclosure may be implemented in the following manner:

The bookkeeping method provided by an embodiment of the present disclosure can be applied to a blockchain system. The blockchain system includes at least one parallel chain, at least one parallel chain is built with at least one mining pool, and each mining pool includes a mining pool server and a A mining node on a parallel chain. The mining node uses a distributed data blockchain to store data. The method includes:

The mining pool server receives and stores the hash value of the main body of the block header of the pending accounting block sent by the mining node and the target difficulty of mining on the parallel chain where the mining node is located;

The mining pool server receives the accounting request sent by the terminal device;

The mining pool server sends the hash value and difficulty target value of the main part of the block header to the terminal device, so that the Slave Trusted Execution Environment (Slave TEE) configured by the terminal device determines whether its accumulated unused duration is greater than The cumulative unused lower limit duration calculated according to the difficulty target value, and signing the accounting right determination information when the cumulative unused duration is greater than the cumulative unused lower limit duration, wherein the accounting right determination information includes a hash of the main part of the block header Value and the address subject of the wallet account bound by Slave TEE;

The mining pool server receives the accounting right determination information and the signature of the accounting right determination information sent by the terminal device;

The mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node, so that the mining node generates an accounting block containing the address body of the wallet account and the signature of the accounting right determination information, and Add the accounting block to the local blockchain.

In the above method, the terminal equipment is connected to the mining pool to participate in mining. The Slave TEE configured in the terminal equipment acts as a miner. Slave TEE uses a consensus algorithm different from PoW when competing for billing rights: Slave TEE maintains a cumulative With the duration, the accumulated unused duration will accumulate with the passage of time. At the same time, Slave TEE also obtains the difficulty target value from the mining pool server, and calculates the cumulative unused minimum duration according to the difficulty target value. If the cumulative unused duration is greater than the cumulative unused duration With the lower limit time, the Slave TEE competition accounting right succeeds, otherwise the competition accounting right fails, and it can continue to participate in the next accounting right competition. The calculation amount involved in this consensus algorithm is much smaller than the PoW algorithm, which effectively avoids the waste of computing resources in the Slave TEE, reduces the power consumption of the Slave TEE, or enables the Slave TEE to adopt a low-cost, low-power hardware implementation, which is effective Save the consumption of electrical energy.

On the other hand, Slave TEE will also sign the information of the accounting right after the competition for the accounting right is successful, and send the accounting right determination information together with its signature to the mining pool server, and the mining pool server will further forward it to the mining Node, the mining node will finally save the signature in the newly generated accounting block, and broadcast the accounting right determination information and the newly generated accounting block on the parallel chain where it is located. Therefore, the mining pool server, mining nodes, and other nodes on the parallel chain can verify the authenticity of the bookkeeper based on the signature, and can also verify the bookkeeping rights to determine whether the content of the information has been tampered, which is conducive to improving the area. The security of the blockchain system. The accounting right determination information includes key information related to the competitive accounting right. The hash value of the main body of the block header can uniquely identify the pending accounting block, and the address body of the wallet account bound by Slave TEE indicates the identity of the bookkeeper , So they can be included in the accounting right determination information.

On the other hand, the blockchain system in the above method uses parallel chains to support the decentralization of each slave TEE on different parallel chains for mining, effectively avoiding the concentration of computing power and improving the security of the blockchain system.

On the other hand, mining by building a mining pool on a parallel chain has the following advantages over deploying miner nodes directly on the parallel chain:

First, the blockchain system usually requires a certain number of distributed full ledger nodes to ensure security. If the miner nodes deployed on the parallel chain all participate in the accounting, due to the large number of miner nodes, the entire network broadcast of the ledger data will be Occupying a lot of bandwidth leads to an increase in network burden, and too many full ledger nodes do not bring additional value; moreover, because many miner nodes are personal devices, their data transmission capabilities and network environment are more limited. One problem is more prominent; however, in the accounting method provided by the embodiments of the present disclosure, Slave TEE only competes for accounting rights, and does not directly account for it. Only mining nodes perform accounting (generating blocks), and mining nodes The number is much smaller than the number of Slave TEE. Even if the entire network broadcast data volume is not too large, at the same time, the mining pool can be deployed in the cloud, and its data transmission bandwidth can be guaranteed.

Second, as mentioned above, many of the miner nodes are personal devices, and most of the individuals involved in mining do not have or have little accounting requirements, but only hope to obtain economic benefits through mining. If they are forced to participate in accounting, Not only does it result in a poor user experience, but some personal devices have limited storage space (for example, mobile devices), which is not suitable for billing at all, which ultimately leads to the loss of users. At the same time, some users with large billing needs, such as enterprise users, are The mine is not interested. however. In the accounting method provided by the embodiments of the present disclosure, enterprise users can build a mining pool on the parallel chain to be responsible for accounting, and at the same time attract individual users to access the mining pool to help them mine. The operating status of the chain system.

Optionally, the parallel chain may include a routing node, at least one mining node of a mining pool, and at least one Simplified Payment Verification (SPV) node, a network connection between at least one parallel chain routing node, and SPV node binding The parallel chain corresponding to the address of the specified wallet account is the parallel chain where the SPV node is located, where:

In response to receiving the transaction request, the SPV node sends the received transaction request to the routing node of the parallel chain where the SPV node is located;

In response to the verification of the received transaction request, the routing node adds the received transaction request to the routing node's transaction request set, and broadcasts the received transaction request to the routing node's same-chain mining after signing Mining node; and synchronize the blockchain of the routing node with the mining node of the same chain to the local blockchain in real time;

In response to the verification of the signed transaction request received from the same link by the node, the mining node adds the in-chain transaction request of the mining node in the signed transaction request to the mining node's pending transaction request set; Process the transaction request set to generate the hash value of the main part of the block header;

The routing node also determines the unrecorded transaction requests that are confirmed and unrecorded in the transaction request set of the routing node; the determined unrecorded transaction requests are sent to the routing node of the target parallel chain, where the target parallel chain is determined The parallel chain corresponding to the address of the account number in the unrecorded transaction request; and in response to receiving the transaction request sent by the node on the different link, the received transaction request is signed and broadcast to the same-chain mining node of the routing node.

In these embodiments, the interconnection between the parallel chains is achieved by routing nodes, and the transactions between SPV nodes need to be completed by routing nodes, so that routing nodes can be used to effectively supervise digital currency transactions.

On the other hand, in the blockchain system, the transaction processing process is improved from the traditional single-chain serial method to the multi-chain concurrent method. With the increase of the number of parallel chains, the number of transactions per second of the blockchain system (Transactions Per Second, referred to as TPS) with it.

Optionally, the accounting right determination information may also include accumulated unused lower limit duration.

The accumulated unused minimum time limit can directly determine whether Slave TEE can obtain the accounting right, and also belongs to the key information related to the competitive accounting right, so it can also be included in the accounting right determination information.

Optionally, the signature of the accounting right determination information may be generated by the Slave TEE based on the saved first private key, and before the mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node, The method may also include:

The mining pool server determines that the signature of the accounting right determination information is a true signature according to the stored first public key matching the first private key.

According to the principle of asymmetric encryption, Slave TEE uses the saved first private key to determine the information signature of the accounting right. The mining pool server uses the saved first public key that matches the first private key to verify the signature. If the verification is successful, It is confirmed that the signature is indeed sent by the Slave TEE, which can prevent the attacker from forging the message.

Optionally, the mining pool may include multiple mining nodes, and different mining nodes are located on different parallel chains;

The mining pool server sends the hash value of the main body of the block header to the terminal device and the difficulty target value may include: the master trusted execution environment (Master Trusted Execution Environment, Master for short TEE) configured by the mining pool server determines the parallel associated with the terminal device Chain; the mining pool server sends the hash value and difficulty target value of the main part of the block header provided by the mining node on the parallel chain associated with the terminal device to the terminal device;

The mining pool server sending the accounting right determination information and the signature of the accounting right determination information to the mining node may include: the mining pool server sending the accounting right determination information and the signature of the accounting right determination information to the parallel chain associated with the terminal device On the mining node.

In these embodiments, the terminal device can only obtain the hash value and difficulty target value of the main part of the block header provided by the mining node on the parallel chain associated with it, so that the Slave TEE configured by the terminal device can only be used in the associated Mining on the parallel chain means that the computing power of the terminal equipment is distributed to different parallel chains to avoid 51% computing power attacks in the blockchain.

Optionally, the master TEE determines that the parallel chain associated with the terminal device may include:

The Master TEE calculates the chain ID of the parallel chain associated with the terminal device based on the virtual parallel chain ID of the wallet account address bound by the Slave TEE, the parallel chain ID mask of the terminal device, and the number of parallel chains included in the blockchain system, where, The virtual parallel chain identification is calculated based on the hardware identification of the slave TEE configured in the terminal device.

In these embodiments, the virtual parallel chain identification can be calculated based on the Slave TEE hardware identification, and the parallel chain identification mask and the number of parallel chains are stored in the Master TEE, so that any terminal equipment involved in mining is associated The parallel chain can be uniquely determined, which can ensure that the terminal equipment is distributed to different parallel chains for mining.

Optionally, the mining pool server sends the hash value of the main body of the block header and the target difficulty value to the terminal device, which may include:

Master TEE generates a first key based on the mining pool configuration information according to the first key generation algorithm, and encrypts the hash value of the main body of the block header according to the first key; the mining pool configuration information includes the chain identifier of the parallel chain associated with the terminal device ; Among them, Slave TEE can use the first key generation algorithm to generate the first key, and use the first key to decrypt the encrypted hash value of the main body of the block header;

The mining pool server sends the target difficulty value and the encrypted hash value of the main body of the block header to the terminal device.

In these embodiments, the hash value of the main body of the block header is symmetrically encrypted. The same first key generation algorithm is used in Master TEE and Slave TEE to calculate the first key. If the calculated first key In the same way, Slave TEE can be decrypted correctly, and Slave TEE can only sign the accounting right determination information if the hash value of the main part of the block header is decrypted correctly. The above mechanism ensures that Master TEE and Slave TEE must be used together. Once the two do not match, such as Slave TEE being forged, the encryption and decryption mechanism will not work properly.

Optionally, the first key is related to the chain ID of the parallel chain associated with the terminal device, which means that the chain ID calculated in Slave TEE must be consistent with the chain ID calculated in Master TEE before the Slave TEE can be obtained. The same first key as in Master TEE, or Slave TEE can only obtain and decrypt the block header sent by the mining node on the parallel chain (parallel chain associated with the terminal device where Slave TEE is located) corresponding to the chain ID The hash value of the main part, even if the hash value of the main part of the block header sent by the mining node on the other parallel chain is obtained, it cannot be decrypted correctly, thus limiting the Slave TEE to only be on a specific parallel chain Mining.

Optionally, the first key generation algorithm is proprietary to Master TEE and Slave TEE. The algorithm implementation is not disclosed outside Master TEE and Slave TEE. The first key generated by the first key generation algorithm is used in Master TEE And it is only used to encrypt the hash value of the body part of the block header, which is used in Slave TEE and only to decrypt the hash value of the encrypted body part of the block header.

In these embodiments, the encryption and decryption process of the hash value of the main part of the block header is one-way, that is, the master TEE is only responsible for encryption, and the first key is not used for decryption purposes, and the Slave TEE is only responsible for For decryption, the first key will not be used for encryption purposes, and the first key generation algorithm is not disclosed to the outside, ensuring that the first key will not be cracked.

Optionally, the mining pool server sends the hash value of the main body of the block header and the target difficulty value to the terminal device, including:

The mining pool server judges whether the time interval t1 between the terminal device and the last accounting time is greater than the cooling time t2. The cooling time t2 is k times the cumulative unused lower limit time, and k is a constant greater than 0 and less than 1;

If it is greater, the mining pool server sends the hash value of the main body of the block header and the target difficulty value to the terminal device.

In these embodiments, the mining pool server restricts the terminal device to obtain at least the cooling time interval after each successful accounting to obtain the accounting right again, to avoid the intentional accumulation of unused time in the slave TEE configuration of some terminal devices, and then Continuously obtain the right to keep accounts, in disguised form 51% hashing power attack. At the same time, by setting the cooling time limit, Slave TEE, which can configure more terminal equipment, has the opportunity to obtain accounting rights, which also reflects the fairness of mining to a certain extent.

Optionally, after the mining pool server determines whether the time interval t1 from the last accounting time is greater than the cooling time t2, the method may further include:

If the time interval t1 from the last accounting time is not greater than the cooling time t2, the mining pool server notifies the terminal device of the time interval t3 from which the next accounting request is initiated, and the time interval t3 from the time of the next accounting request is the cooling time The difference between t2 and the time interval t1 from the last accounting time.

If the mining pool server finds that the current accounting request sent by the terminal device does not meet the cooling time requirement, it can actively inform it to be idle for a period of time, and then send a new accounting request until the cooling time requirement is met, to avoid the terminal device continuously sending meaningless Accounting request (that is, it is impossible to obtain the accounting right), resulting in a waste of resources.

Optionally, the time interval t1 from the last accounting time can be calculated by the following formula:

Among them, Height2 is the height of the pending accounting block in the blockchain, and Height1 is the height of the block generated by the last accounting in the blockchain,

It is the preset constant of the blockchain system and is used to characterize the average block time of the blockchain system.

In some existing blockchain protocols, the time stamp in the block header can only roughly represent the accounting time. If the difference between the time stamps of the two blocks is used to estimate the accounting time interval, the accuracy and credibility may be Not high, because the timestamp of the pending accounting block does not necessarily equal the actual accounting time, but allows a deviation of several hours from the current network time, and is determined by the relevant mining node. It is not excluded that someone deliberately advances the accounting time Or postponed, and the difference in height between the two blocks in the blockchain is used to estimate the accounting time interval, which has higher accuracy and credibility, which makes the judgment of whether the accounting request meets the cooling time more reasonable.

Optionally, before the mining pool server receives the accounting request sent by the terminal device, the method may further include:

The mining pool server receives the registration request sent by the terminal device. The registration request carries the registration information, the user's real-name authentication result and the real-name authentication agency's signature of the real-name authentication result with the private key. The registration information includes the address of the wallet account bound by the Slave TEE;

The Master TEE configured by the mining pool server verifies the authenticity of the signature of the real-name authentication result based on the stored public key that matches the private key of the real-name certification authority;

If the signature of the real-name authentication result is a real signature, the mining pool server saves the registration information and sends a registration response to the terminal device.

Before using the terminal device to participate in mining, users need to go to a real-name certification agency for real-name certification, and obtain the certification result and signature returned by the real-name certification agency. Before participating in mining, the terminal device needs to register with the mining pool server and submit the authentication result and its signature to the mining pool server. The mining pool server can determine whether the authentication result is valid by verifying the authenticity of the signature of the authentication result.

The introduction of a real-name authentication mechanism makes it easy for users who misbehave in the mining process to be held accountable and meet regulatory requirements. At the same time, the publishers of Slave TEE can also prove themselves innocent, because the real-name authentication is controlled by a third-party real-name certification body, and the publisher cannot cheat in the mining process by forging many Slave TEE (for example, through software simulation). Because the actual identity of the user is limited, it is difficult for a large number of forged Slave TEE to pass the real-name authentication.

Optionally, the real-name authentication result includes an authentication code assigned by the real-name authentication organization, and the authentication code corresponds to the address of the wallet account bound to the Slave TEE, and is used to characterize that the user has passed the real-name authentication of the real-name authentication organization; the method may further include:

The mining pool server also receives the authentication code sent by the terminal device and sends the authentication code to the mining node, so that the mining node adds the authentication code to the accounting block;

The accounting right determination information also includes an authentication code.

The authentication code corresponds to the address of the wallet account bound to the Slave TEE, or it corresponds to the user. The authentication code can be used to check whether the user has been authenticated by the real-name authentication agency. Therefore, the authentication code is introduced into the accounting process. Help to improve the security of the accounting process.

The mining pool server receives the pool application sent by the terminal equipment;

The Master TEE configured by the mining pool server determines whether the capacity of the mining pool server is less than the capacity threshold;

If it is less, the mining pool server authorizes the terminal device to enter the pool according to the authorization information generated by the Master TEE to inform the terminal device that the accounting request sent to the mining pool server within the authorized use time after the authorization start time can be accepted by the mining pool server , Where the authorized use duration is the pre-configured data stored in the Master TEE configured by the mining pool server;

If it is greater, the mining pool server sends a message to notify the terminal device that it has not been authorized to enter the pool.

In these embodiments, each mining pool has a limit on the number of Slave TEEs allowed to be mined in the pool, thereby avoiding the situation where a small number of mining pools accumulate a large amount of computing power. Furthermore, each mining pool in the blockchain system can be operated by different operators, and the computing power that each operator can control is limited by the capacity of the mining pool, which can effectively suppress the centralization of mining pool computing power. trend.

Optionally, the capacity of the mining pool server less than the capacity threshold may include:

The authorization amount for pooling in the current authorization period is less than the first threshold; wherein, the authorization period and the first threshold are pre-configured data saved in the Master TEE configured by the mining pool server.

The mining pool server allows the slave TEE configured in the terminal device to enter the mining pool according to the authorization cycle. The number of pooled authorizations in each authorization cycle is limited to a certain amount, to avoid the concentration of terminal devices in a certain period of time to apply for pooling. The computing power is scattered as much as possible at the time level.

Optionally, the authorization information may include an authorization serial number and an authorization code, where the authorization serial number is assigned by the Master TEE, and the authorization code is used to verify that the Slave TEE configured in the terminal device is valid for the pooling authorization.

The mining pool server authorizes the terminal device to enter the pool according to the authorization information generated by the Master TEE, which may include:

The mining pool server sends the authorization serial number and authorization code to the terminal device, and stores the authorization serial number corresponding to the authorization related information, where the authorization related information refers to the information related to the authorized content;

Before the mining pool server sends the hash value of the main body of the block header and the target difficulty value to the terminal device, the method may further include:

The mining pool server queries the corresponding authorization association information according to the authorization serial number carried in the accounting request, and determines that the terminal pooling authorization is valid according to the authorization association information.

After the mining pool server authorizes the terminal device to enter the pool, the terminal device will obtain the pool access authorization code. Or, when the pool application is not approved by the mining pool server, the terminal device may wait for a period of time and apply to the pool server again. Slave TEE configured in the terminal device can further verify whether the authorization to enter the pool is valid according to the authorization code when competing for the accounting right to confirm whether it can obtain the accounting right. At the same time, after receiving the accounting request sent by the terminal device, the mining pool server , You can further confirm whether the Slave TEE should be allowed to compete for accounting rights based on the authorization association information. Through the above-mentioned double verification mechanism, the terminal device can participate in mining only within the authorized use time, and realize the control of the computing power of the pool aggregation.

Optionally, the mining pool server sends the authorization serial number and authorization code to the terminal device, which may include:

The Master TEE generates a second key according to the second key generation algorithm, and uses the second key to encrypt the authorization code;

The mining pool server sends the authorization serial number and the encrypted authorization code to the terminal device; the Slave TEE configured on the terminal device can use the second key generation algorithm to generate the second key, and use the second key to decrypt the encrypted authorization code .

In these embodiments, the authorization code is symmetrically encrypted. Master TEE and Slave TEE use the same second key generation algorithm to calculate the second key. If the calculated second keys are the same, the Slave TEE can Decrypt correctly, and Slave TEE can verify the authorization information contained in the authorization code only if the authorization code is correctly decrypted. The above mechanism ensures that Master TEE and Slave TEE must be used together. Once the two do not match, such as Slave TEE being forged, the encryption and decryption mechanism will not work properly.

Optionally, the second key generation algorithm is private to Master TEE and Slave TEE, the implementation of the second key generation algorithm is not disclosed outside Master TEE and Slave TEE, and the second key generated by the second key generation algorithm is at Master It is used in TEE and only for encrypting the authorization code, and in Slave TEE is used and only for decrypting the encrypted authorization code.

In these embodiments, the encryption and decryption process of the authorization code is one-way, that is, the Master TEE is only responsible for encryption, and the second key will not be used for decryption purposes, and the Slave TEE is only responsible for decryption, not the The second key is used for encryption purposes, and the second key generation algorithm is not disclosed to the outside, ensuring that the second key will not be cracked.

Optionally, after the mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node, the method may further include:

The mining pool server transfers the preset amount of mining pool rewards from the address of the pre-configured mining pool wallet account to the address of the wallet account bound to the slave TEE configured for the terminal device competing for the accounting right.

According to the blockchain agreement, after successful mining, users can get a certain amount of digital currency as a mining reward, and the mining pool reward is an additional digital currency issued by the mining pool operator to the user, which is not part of the mining reward. Its purpose is to attract more users to participate in mining and improve the operation of the mining pool.

An embodiment of the present disclosure also provides an accounting method, which is applied to a terminal device connected to a blockchain system. The blockchain system includes at least one parallel chain, and at least one mining pool is built on at least one parallel chain, each The mining pool includes a mining pool server and a mining node located on a parallel chain. The mining node uses a distributed data blockchain to store data. The method includes:

The terminal device sends an accounting request to the mining pool server;

The terminal device receives the hash value of the main body of the block header of the pending accounting block sent by the mining pool server and the difficulty target value of mining on the parallel chain;

The Slave TEE configured in the terminal device determines whether its accumulated unused duration is greater than the cumulative unused minimum duration calculated according to the difficulty target value, and signs the accounting right determination information when the cumulative unused duration is greater than the cumulative unused minimum duration. Among them, the accounting right determination information includes the hash value of the body part of the block header and the address body of the wallet account bound by the Slave TEE;

The terminal device sends the accounting right determination information and the signature of the accounting right determination information to the mining pool server.

Optionally, the Slave TEE signs the accounting right determination information, which may include:

Slave TEE signs the accounting right determination information according to the saved first private key, and the mining pool server and the mining node store the first public key matching the first private key.

Optionally, the mining pool includes multiple mining nodes, and different mining nodes are located on different parallel chains;

The terminal device receives the hash value of the main body of the block header of the pending accounting block sent by the mining pool server and the difficulty target value of mining on the parallel chain, including:

The terminal device receives the encrypted hash value and difficulty target value of the main body of the block header sent by the mining pool server, where the first key used for encryption is generated by the Master TEE configured by the mining pool server according to the first key generation algorithm;

Before Slave TEE signs the accounting right determination information, the method further includes:

Slave TEE generates a first key based on the mining pool configuration information based on the first key generation algorithm, and uses the first key to decrypt the hash value of the encrypted block header body, where the mining pool configuration information includes the The chain identifier of the parallel chain and the accounting right determination information include the hash value of the decrypted block header body.

Optionally, the configuration information of the mining pool further includes the number of times the parallel chain has been expanded and/or the pre-configured mining pool identifier of the mining pool.

The first key generation algorithm considers the number of times the parallel chain has been expanded when generating the first key. If the parallel chain has been expanded, the number of times the parallel chain saved in the Master TEE has been expanded has been updated, but the parallel chain saved in the Slave TEE has The number of expansions has not been updated, and Slave TEE will not be able to continue mining (because the hash value of the main part of the block header cannot be decrypted correctly), that is, after the parallel chain expansion and upgrade, if the Slave TEE configuration is not upgraded, the Slave TEE will not be allowed Continue to participate in mining, so that even if there is a concentration of computing power on a parallel chain before the upgrade, once the configuration of the Slave TEE is updated after the upgrade, the aggregated Slave TEE may be dispersed to the new parallel chain to mine, which is effective Eliminate the accumulation of computing power.

The first key generation algorithm considers the pool ID when generating the first key, which can restrict the Slave TEE to only mine in the specified pool, and cannot replace the pool at will (otherwise, the hash value of the main part of the block header cannot be decrypted correctly ), to avoid the accumulation of computing power.

In the first key generation algorithm, only one of the above two pieces of information may be considered, or both may be considered.

Optionally, the chain identifier of the parallel chain associated with the terminal device is composed of the virtual parallel chain identifier of Slave TEE according to the address of the wallet account bound by the Slave TEE, the parallel chain identifier mask of the terminal device, and the parallel chain included in the blockchain system. The number is calculated, and the virtual parallel chain logo is calculated based on the slave TEE hardware logo.

Optionally, before the terminal device sends an accounting request to the mining pool server, the method may further include:

The terminal device sends a registration request to the mining pool server. The registration request carries registration information, the user’s real-name authentication result, and the real-name authentication agency’s signature of the real-name authentication result with the private key. The registration information includes the address of the wallet account bound by the Slave TEE; The Master TEE configured by the pool server stores the public key matching the private key of the real-name certification authority;

The real-name authentication result includes the authentication code assigned by the real-name authentication organization. The authentication code corresponds to the address of the wallet account bound to the Slave TEE, and is used to characterize that the user has passed the real-name authentication of the real-name authentication organization;

The terminal device sends a pooling application to the mining pool server and obtains the pooling authorization of the mining pool server.

Optionally, the terminal device obtaining the pool access authorization of the mining pool server may include:

The terminal device receives the authorization serial number and encrypted authorization code sent by the mining pool server, where the authorization serial number is allocated by the Master TEE configured by the mining pool server, and the second key used for encryption is generated by the Master TEE according to the second key generation algorithm;

Slave TEE generates a second key according to the second key generation algorithm, and uses the second key to decrypt the encrypted authorization code;

Slave TEE determines that the authorization to enter the pool is valid according to the decrypted authorization code.

An embodiment of the present disclosure also provides an accounting method, which is applied to a blockchain system. The blockchain system includes at least one parallel chain, at least one parallel chain is built with at least one mining pool, and each mining pool includes a mining pool server. And the mining nodes located on the parallel chain. The mining nodes use distributed data blockchain to store data. Methods can include:

The mining node sends the hash value of the main body of the block header of the pending accounting block to the mining pool server and the difficulty target value of mining on the parallel chain;

The mining node receives the signature of the address body of the wallet account bound by the Slave TEE and the accounting right determination information generated by the Slave TEE sent by the mining pool server to the terminal device configured to access the mining pool server, where the accounting right determination information includes The hash value of the body part of the block header and the address body of the wallet account bound by Slave TEE;

The mining node generates a signed accounting block that contains the address body of the wallet account and the accounting right determination information, and adds the accounting block to the local blockchain.

Optionally, the accounting right determination information further includes a cumulative unused minimum duration and/or an authentication code assigned by a real-name certification body, where the cumulative unused minimum duration is calculated by Slave TEE according to the difficulty target value, and the authentication code is related to the Slave TEE The address of the bound wallet account corresponds to the real-name authentication of the user through the real-name authentication agency. The accounting block generated by the mining node also contains the cumulative unused minimum duration and/or authentication calculated according to the difficulty target value code.

Optionally, the signature of the accounting right determination information is generated by the Slave TEE based on the stored first private key. Before the mining node generates the accounting accounting block containing the address body of the wallet account and the signature of the accounting right determination information, the Methods can also include:

The mining node determines that the signature of the accounting right determination information is a real signature according to the stored first public key matching the first private key.

According to the principle of asymmetric encryption, Slave TEE uses the saved first private key to determine the information signature of the accounting right. The mining node uses the saved first public key that matches the first private key to verify the signature. If the verification is successful, It is confirmed that the signature is indeed sent by the Slave TEE, which can prevent the attacker from forging the message.

Optionally, before the mining node generates a signed accounting block containing the address body of the wallet account and the accounting right determination information, the method may further include:

The mining node queries the address subject of the wallet account to obtain the height of the block generated by the terminal device in the last bookkeeping in the blockchain;

The mining node determines the generation time of the pending accounting block and the block generated by the last accounting based on the height of the block generated by the last accounting in the blockchain and the height of the pending accounting block in the blockchain The time interval of the generation time;

The mining node determines that the judgment interval is greater than the cooling duration, where the cooling duration is k times the cumulative unused lower limit duration calculated based on the difficulty target value stored in the accounting block to be confirmed, and k is greater than 0 and less than 1. constant.

Before generating the accounting block, the mining node can also verify whether its accounting interval meets the cooling time requirement. If the requirement is met, the block will be generated and added to the local blockchain, otherwise It will not recognize the generated block, avoiding the same Slave TEE to continuously obtain the accounting right.

Optionally, after the mining node adds the accounting block to the local blockchain, the method may further include:

The mining node sends the height of the accounting block in the blockchain and the address body of the wallet account bound by the Slave TEE configuration of the terminal device competing for the accounting right to the mining pool server.

In these embodiments, the mining node sends the above information to the mining pool server for storage. When verifying whether the accounting request meets the cooling time requirement, the mining pool server can use the address body of the wallet account bound by Slave TEE to query each The height of the sub-accounted block in the blockchain, and then estimate the accounting interval to complete the verification.

Optionally, the method may further include:

The mining node queries the address body of the wallet account of the terminal device stored in the accounting block to be confirmed on the blockchain to obtain the height of the block generated by the terminal device in the last accounting in the blockchain, where The confirmed accounting block refers to the accounting block received by the mining node and broadcast by other mining nodes on the same chain;

The mining node determines the generation time of the accounting block to be confirmed and the last accounting based on the height of the block generated by the last accounting in the blockchain and the height of the accounting block to be confirmed in the blockchain The time interval of the generation time of the generated block;

The mining node judges whether the time interval is greater than the cooling time, and if it is greater than the cooling time, it will approve the accounting block to be confirmed, where the cooling time is the cumulative uncalculated value calculated based on the difficulty target value stored in the accounting block to be confirmed Using k times the lower limit time, k is a constant greater than 0 and less than 1.

Mining nodes will receive the accounting blocks to be confirmed broadcast by other mining nodes. The accounting blocks to be confirmed have been added to their local blockchain by other mining nodes, but have not been mined on the parallel chain. Approved by the mining node.

For the received accounting block to be confirmed, the mining node can verify whether the accounting interval meets the cooling time requirement. If the requirement is met, the block will be recognized and added to the local blockchain Medium, otherwise the block will not be recognized.

An embodiment of the present disclosure also provides a mining pool server. The mining pool server includes:

Memory, used to store computer instructions;

Communication interface, used to communicate with terminal equipment and mining nodes;

The mining pool server also includes Master TEE or Master TEE connected;

The mining pool server also includes a processor, which is connected to the memory, the communication interface, and the Master TEE. When the computer instructions in the memory are executed by the processor, the processor combines with the Master TEE to execute the above-mentioned mining pool applicable to the blockchain system The accounting method of the server.

An embodiment of the present disclosure also provides a terminal device. The terminal device includes:

Memory, used to store computer instructions;

Communication interface, used to communicate with the mining pool server;

Terminal equipment also includes Slave TEE or Slave TEE connected;

The terminal device also includes a processor, which is connected to the memory, the communication interface, and the Slave TEE. When the computer instructions in the memory are executed by the processor, the processor combined with the Slave TEE execution can be applied to the terminal device connected to the blockchain system. Accounting method.

An embodiment of the present disclosure also provides a mining node. The mining node includes:

Memory, used to store computer instructions;

Communication interface, used to communicate with the mining pool server;

The processor is connected to the memory and the communication interface. When the computer instructions in the memory are executed by the processor, the processor executes the above-mentioned accounting method applied to the mining node of the blockchain system.

An embodiment of the present disclosure also provides a mining pool, including: a mining pool server and a mining node located on a parallel chain of the blockchain system. The mining node uses a distributed data blockchain to store data. The blockchain system includes At least one parallel chain

Among them, the mining node is used to: send the hash value of the main body of the block header of the pending accounting block to the mining pool server and the difficulty target value of mining on the parallel chain;

The mining pool server is used to: receive and store the hash value and difficulty target value of the main part of the block header, and after receiving the accounting request sent by the terminal device, send the hash value and difficulty target of the main part of the block header to the terminal device Value, so that the Slave TEE configured by the terminal device determines whether its accumulated unused duration is greater than the cumulative unused minimum duration calculated according to the difficulty target value, and determines the accounting right when the accumulated unused duration is greater than the cumulative unused minimum duration Sign the information, where the accounting right determination information includes the hash value of the body part of the block header and the address body of the wallet account bound by Slave TEE; the signature of the accounting right determination information and the accounting right determination information sent by the receiving terminal device , And send the accounting right determination information and the signature of the accounting right determination information to the mining node;

Mining nodes are also used to: generate a billing block that contains the address body of the wallet account and the signature of the billing right determination information, and add the billing block to the local blockchain.

Optionally, the mining pool server can also be used to: before receiving the accounting request sent by the terminal device, receive the pooling application sent by the terminal device, and determine whether the capacity of the mining pool server is less than the Master TEE configured in the mining pool server Capacity threshold, if the capacity of the mining pool server is less than the capacity threshold, the terminal device is authorized to enter the pool according to the authorization information generated by the Master TEE to inform the terminal device of the accounting request sent to the mining pool server within the authorized use time after the authorization start time It can be accepted by the mining pool server. If the capacity of the mining pool server is greater than the capacity threshold, a message is sent to notify the terminal device that it has not been authorized to enter the pool. The authorized duration is the pre-configured data stored in the Master TEE configured by the mining pool server.

Optionally, the capacity of the mining pool server is less than the capacity threshold, which may include:

In order to make the above-mentioned objects, technical solutions and beneficial effects of the present disclosure more obvious and understandable, the embodiments are specifically described below, together with the accompanying drawings, for detailed description as follows.

BRIEF DESCRIPTION

In order to more clearly explain the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present disclosure, and therefore do not It should be regarded as a limitation on the scope. For those of ordinary skill in the art, without paying any creative labor, other related drawings can also be obtained based on these drawings.

FIG. 1(A) to FIG. 1(B) show a schematic structural diagram of a blockchain system that can be used in embodiments of the present application;

2 shows a schematic diagram of a workflow of a blockchain system provided by an embodiment of the present disclosure;

FIG. 3 shows a flowchart of a billing method provided by an embodiment of the present disclosure;

4(A) to 4(B) show a flowchart of another accounting method provided by an embodiment of the present disclosure;

5 shows a functional module diagram of a mining pool server provided by an embodiment of the present disclosure;

6 shows a functional block diagram of a terminal device provided by an embodiment of the present disclosure;

FIG. 7 shows a functional block diagram of a mining node provided by an embodiment of the present disclosure.

detailed description

The technical solutions in the embodiments of the present disclosure will be described clearly and completely in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, but not all the embodiments. The components of the embodiments of the present disclosure generally described and illustrated in the drawings herein can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present disclosure provided in the drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of the disclosure. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present disclosure.

It should be noted that similar reference numerals and letters indicate similar items in the following drawings, therefore, once an item is defined in one drawing, there is no need to further define and explain it in subsequent drawings. Meanwhile, in the description of the present disclosure, the terms "first", "second", etc. are only used to distinguish one entity or operation from another entity or operation, and cannot be understood as indicating or implying relative importance, or It cannot be understood as requiring or implying that there is any such actual relationship or order between these entities or operations. Moreover, the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also those not explicitly listed Or other elements that are inherent to this process, method, article, or equipment. Without more restrictions, the element defined by the sentence "include one..." does not exclude that there are other identical elements in the process, method, article or equipment that includes the element.

The accounting method provided by the embodiments of the present disclosure can be applied to a blockchain system. The blockchain system may include at least one parallel chain, and each parallel chain may include at least one mining node. Of course, other nodes can be included on the parallel chain, and the functions of the mining nodes can include mining and accounting. The so-called mining refers to the mining node competing with other nodes on the parallel chain where it is based on the blockchain's consensus algorithm for accounting rights. The so-called bookkeeping refers to: after the mining node competes for the bookkeeping rights, a new block is generated according to the transaction to be booked in the transaction buffer, and the new block is added to the block chain corresponding to the parallel chain where it is located Data (ledger). Moreover, the mining node will also synchronize the block data with other nodes on the parallel chain where it is located, that is, the mining node is also a full ledger node on the parallel chain where it is located. Except for mining nodes, other nodes on the parallel chain do not participate in mining, but can participate in bookkeeping.

As previously stated, the mining node is a full ledger node on the parallel chain, but the transaction data it stores is only the transaction data related to the parallel chain where it is located. Select a mining node from each parallel chain in the blockchain system. For example, if there are N (N ≥ 1) parallel chains, select a total of N mining nodes. The set of mining nodes formed is Called the ledger cluster. The ledger cluster stores all transaction data in the blockchain system, that is, it is used to maintain the entire network ledger, so as to provide functions such as query of the entire network transaction data. It should be pointed out that since each mining node is a full ledger node on the parallel chain, when forming a ledger cluster, it is enough to select one mining node on each parallel chain; of course, if it is due to reliability and other aspects For consideration, it is also feasible to select multiple mining nodes on the same parallel chain.

At least one mining pool can be built on at least one parallel chain of the blockchain system. Among them, each mining pool may include a mining pool server and a mining node on a parallel chain. The above-mentioned construction of a mining pool on at least one parallel chain means that the mining pool contains mining nodes on these parallel chains, so the mining pool can mine on these parallel chains and keep accounts for these parallel chains. Optionally, in some implementations, the mining pool may include a mining pool server and a ledger cluster, that is, the mining pool may mine and keep accounts on all parallel chains in the entire blockchain system.

In the mining pool, the mining function of the mining node can actually be performed by the miners connected to the mining pool. Miners are devices that can run consensus algorithms. After the miner accesses the mining pool server, the mining node can distribute the consensus calculation task to the miners through the mining pool server for actual execution. The miners compete for the accounting power. Of course, from the perspective of the mining node, it is still mining Mine nodes are competing for accounting rights. In addition to serving as a communication intermediary between mining nodes and miners, the mining pool server can also be used for pooling management of miners, that is, whether or not miners are allowed to access the mining pool, as well as functions for issuing mining pool rewards. Will be introduced in detail.

Optionally, in some implementations, the mining pool may also include a database for storing data involved in the mining process, such as registration information of miners, information related to billing sent by mining nodes, and so on. Such a database can be deployed on a mining pool server, or it can also be deployed on a separate database server, where the mining pool server can access the database server. For the sake of simplicity, it will be referred to as the database of the mining pool server.

In the embodiment of the present disclosure, the miner may refer to the SlaveTEE configured for the terminal device, and the so-called configuration may refer to that the terminal device is a carrier of the SlaveTEE. The communication between Slave TEE and external devices (such as mining pool server) can be completed by means of the application program on the terminal device. The above mentioned miner access to the mining pool server may refer to that the terminal device is connected to the mining pool server, and then Slave TEE is responsible for mining. The following briefly introduces the concept of Trusted Execution Environment (TEE):

TEE is an operating environment that coexists with a rich operating system (Rich OS, such as Android, etc.) on the terminal device, and provides security services to RichOS. TEE can have its own execution space. The software and hardware resources that TEE can access can be separated from RichOS. TEE provides a secure execution environment for trusted applications (TA), and also protects the resources of trusted applications and provides data confidentiality, integrity, and access rights. In order to ensure the root of trust of TEE itself, TEE is verified and isolated from Rich OS during the secure boot process. In TEE, each trusted application is independent of each other, and cannot access each other without authorization.

TEE can be used, but not limited to the following two methods:

(1) With the help of specific CPU chips, such as Intel SGX, ARM Trust Zone, etc., provide a security protection capability to construct a trusted execution environment. In order to ensure the security strength, you can also add trusted hardware support at the bottom of the trusted execution environment, such as using a secure chip that conforms to the Trusted Platform Module (TPM) standard, or using a trusted cryptographic module (Trusted Cryptography Module) , Referred to as TCM) standard security chip.

(2) Adopt encryption lock (commonly known as dongle) to achieve a trusted execution environment. Common dongles are often packaged as a Universal Serial Bus (USB) device. The dongles provide both file storage and support for running customized programs. With the dongle, it is not necessary to limit the device type of the device, as long as the device has a USB interface, which reduces the requirements on the device.

If you want to use the functions of TEE outside TEE, or obtain the data stored in TEE, you must implement it by calling the external interface provided by TEE, such as Application Programming Interface (API).

In the embodiments of the present disclosure, there may be two types of TEE that may be involved. One type is the TEE of the terminal equipment configuration, called Slave TEE, which is mainly used to participate in the competition for billing rights. As a miner, Slave TEE is bound to the address of the wallet account used for mining and is used to receive mining revenue. The other type is the Master TEE configured by the mining pool server, which is mainly used to support the capacity control of the mining pool and to disperse the computing power of the Slave TEE and other functions. The functions of the two types of TEE are different, but they can be implemented with the same hardware structure. The specific functions of the two types of TEE will be further elaborated later. It should be pointed out that in the following description, if it refers to the functions completed by the terminal equipment or the mining pool server, unless otherwise specified, it refers to the functions completed in its Rich OS; if it is in the TEE of the terminal equipment or the mining pool server configuration The completed functions will generally specify the functions completed in Slave TEE or Master TEE.

FIG. 1(A) to FIG. 1(B) show a schematic structural diagram of a blockchain system 100 that can be used in an embodiment of the present application. Referring to FIG. 1(A), the blockchain system 100 may include parallel chains 101, 102, 103 and

networks

104, 105.

The parallel chain 101 may include: a routing node 1011; a

mining node

1012, 1014, 1015, 1016, 1018; an

SPV node

1013, 1017; and a network 1019. The network 1019 may be used as a medium for providing communication links between the routing node 1011, the

mining nodes

1012, 1014, 1015, 1016, 1018, and the

SPV nodes

1013, 1017. The network 1019 may include various connection types, such as wired, wireless communication links, or fiber optic cables, and so on. The

mining nodes

1012, 1014, 1015, 1016, and 1018 of the parallel chain 101 may use a distributed data blockchain to store data. The

SPV nodes

1013 and 1017 of the parallel chain 101 may be bound to the address of the wallet account. The parallel chain corresponding to the address of the wallet account bound to the

SPV nodes

1013 and 1017 is the parallel chain 101, that is, the parallel chain where the

SPV nodes

1013 and 1017 are located.

The parallel chain 102 may include: a routing node 1021; a

mining node

1022, 1023, 1025, 1026; an SPV node 1024; and a network 1027. The network 1027 may be used as a medium for providing communication links between the routing node 1021, the

mining nodes

1022, 1023, 1025, 1026, and the SPV node 1024. The network 1027 may include various connection types, such as wired, wireless communication links, or fiber optic cables, and so on. The

mining nodes

1022, 1023, 1025, and 1026 of the parallel chain 102 can use a distributed data blockchain to store data. The SPV node 1024 of the parallel chain 102 may be bound with the address of the wallet account. The parallel chain corresponding to the address of the wallet account bound by the SPV node 1024 is the parallel chain 102, that is, the parallel chain where the SPV node 1024 is located.

The parallel chain 103 may include: a routing node 1031; mining nodes 1032, 1033, 1035, 1036;

SPV nodes

1034, 1037; and a network 1038. The network 1038 may be used as a medium for providing communication links between the routing node 1031, the mining nodes 1032, 1033, 1035, 1036, and the

SPV nodes

1034, 1037. The network 1038 may include various connection types, such as wired, wireless communication links, or fiber optic cables, and so on. The mining nodes 1032, 1033, 1035, and 1036 of the parallel chain 103 can use a distributed data blockchain to store data. The

SPV nodes

1034 and 1037 of the parallel chain 103 may be bound to the address of the wallet account, and the parallel chain corresponding to the address of the wallet account bound to the

SPV nodes

1034 and 1037 is the parallel chain 103.

The user can use the

SPV nodes

1013 and 1017 to interact with the routing node 1011 through the network 1019 to receive or send messages and so on. The user can also use the SPV node 1024 to interact with the routing node 1021 through the network 1027 to receive or send messages, etc. The user can also use the

SPV nodes

1034, 1037 to interact with the routing node 1031 through the network 1038 to receive or send messages, etc.

Various communication client applications can be installed on the SPV node, such as simplified payment verification applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc. Users can use the simplified payment verification application installed on the SPV node to implement operations such as digital currency management, transfer, collection, check balance, and transaction records.

The SPV node can be hardware or software. When the SPV node is hardware, it can be a smart phone, a tablet computer, a notebook computer, a desktop computer, and other electronic devices. When the SPV node is software, it can be installed in the electronic devices listed above. The SPV node can be implemented in multiple software or software modules (for example to provide simplified payment verification services), or it can be implemented in a single software or software module. There is no specific limit here.

The routing node can be hardware or software. When the routing node is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the routing node is software, the routing node may be implemented as multiple software or software modules (for example, to provide routing services), or may be implemented as a single software or software module. There is no specific limit here.

The mining node can be hardware or software. When the mining node is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the mining node is software, it can be implemented as multiple software or software modules (for example, to provide mining and billing services), or as a single software or software module. There is no specific limit here.

Referring to FIG. 1(B), the blockchain system 100 may further include a mining pool 110 and a mining pool 120.

The mining pool 110 may include a mining pool server 1101 and a ledger cluster 1102. The ledger cluster 1102 may include a mining node 1012 on the parallel chain 101, a mining node 1022 on the parallel chain 102, and a mining node 1032 on the parallel chain 103. The network 1106 is used as a medium for providing a communication link between the mining pool server 1101 and the ledger cluster 1102. The network 1106 may include various connection types, such as wired, wireless communication links, or fiber optic cables, and so on. The terminal devices 1103, 1104, and 1105 can access the mining pool server to participate in mining (Slave TEE not shown). The network 1107 is used as a medium for providing communication links between the mining pool server 1101 and the terminal devices 1103, 1104, and 1105. The network 1107 may include various connection types, such as wired, wireless communication links, or fiber optic cables.

The mining pool 120 may include a mining pool server 1201 and a ledger cluster 1202. The ledger cluster 1202 may include a mining node 1014 on the parallel chain 101, a mining node 1023 on the parallel chain 102, and a mining node 1033 on the parallel chain 103. The network 1206 is used to provide a communication link medium between the mining pool server 1201 and the ledger cluster 1202. The network 1206 may include various connection types, such as wired, wireless communication links, or fiber optic cables. The terminal devices 1203, 1204, 1205 can be connected to the mining pool server to participate in mining (Slave TEE not shown). The network 1207 may be used as a medium for providing communication links between the mine pool server 1201 and the terminal devices 1203, 1204, 1205. The network 1207 may include various connection types, such as wired, wireless communication links, or fiber optic cables.

The mining pool server can be hardware or software. When the mining pool server is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the mining pool server is software, it can be implemented as multiple software or software modules (for example, to control the access of terminal devices), or as a single software or software module. There is no specific limit here.

The terminal device may be a mobile phone, a desktop computer, a tablet computer, a personal digital assistant, a smart wearable device, a smart vehicle-mounted device, a router, a set-top box, an embedded device, and other electronic devices. Various communication client applications can be installed on the terminal device, such as mining applications, wallet applications, web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc. Users can use the mining application installed on the terminal device to participate in mining and obtain mining income.

It can be understood that the number of parallel chains in FIG. 1(A) and FIG. 1(B) is only schematic. According to the implementation requirements, there can be any number of parallel chains. In particular, when the number of parallel chains is 1, the parallel chain degenerates into a single chain, and cross-chain transactions will not be involved at this time. The number of routing nodes, mining nodes, networks, and SPV nodes in each parallel chain is also only schematic. According to the implementation needs, there can be any number of routing nodes, mining nodes, networks and SPV nodes. The number of mining pools built on the parallel chain is also only schematic. According to the implementation needs, any number of mining pools can be built (requiring support from mining nodes). The number of terminal devices connected to the mining pool is also only schematic, and the number of terminal devices depends on the number of actual users of the mining pool.

Regarding the working process of the blockchain system shown in FIG. 1(A) and FIG. 1(B), taking the steps in FIG. 2 as an example, a brief description is as follows:

Step S201: In response to receiving the transaction request, the SPV node sends the received transaction request to the routing node of the parallel chain where the SPV node is located.

As mentioned earlier, simplified payment verification applications can be installed in SPV nodes. Users can use the simplified payment verification application in the SPV node to submit transaction requests. Here, the transaction request is a transfer request, that is, the digital currency in the address of the wallet account bound to the SPV node is transferred to the address of another wallet account. In this way, the SPV node can send the above transaction request to the routing node of the parallel chain where the SPV node is responsive to receiving the above transaction request. Each SPV node can be bound with an account address. In some implementations, a wallet application can be used to generate and bind a wallet account address for the SPV node.

The parallel chain corresponding to the address of the wallet account bound to each SPV node is the parallel chain where the SPV node is located. During specific implementation, various implementations may be used to correspond the address of the wallet account bound to the SPV node to one of the parallel chains included in the blockchain system. For example, a parallel chain can be randomly selected from the parallel chains included in the blockchain system as the parallel chain corresponding to the address of the wallet account bound to the SPV node.

Step S202: In response to the verification of the received transaction request, the routing node adds the received transaction request to the routing node's transaction request set, and broadcasts the received transaction request to the route after signing Nodes of the same chain mining node.

The routing node may verify the received transaction request in response to receiving the transaction request sent by the SPV node in step S201. If the verification is passed, the received transaction request can be added to the routing node's transaction request set, and the received transaction request can be signed and broadcast to the same-chain mining nodes of the routing node.

The routing node checking the received transaction request may include, but is not limited to, verifying the validity of the transaction request. Among them, the legality verification may include, but not limited to, verify whether the address of the transfer-out wallet account in the transaction request has an unspent transaction output (Unspent Transaction Output, UTXO) record, and the balance of the address of the transfer-out wallet account in the transaction request Whether this transaction request is supported, whether the address of the transfer-out wallet account in the transaction request is the address of the wallet account in the blacklist of addresses of the transfer-out wallet account stored in the routing node, and whether the address of the transfer-in wallet account in the transaction request is It is the address of the wallet account in the blacklist of addresses transferred to the wallet account stored in the routing node and so on. During specific implementation, the verification of the transaction request may also include other verifications.

Each transaction request verified by the routing node is stored in the transaction request set of the routing node. The routing node may sign the received transaction request by using the routing node's private key to sign the received transaction request. The same-chain mining node of a routing node is a mining node that belongs to the same parallel chain as the routing node. For example, in FIG. 1(A), the

mining nodes

1012, 1014, 1015, 1016, and 1018 are the same-chain mining nodes of the routing node 1011.

In specific implementation, since each parallel chain can be implemented based on a peer-to-peer (Peer-to-Peer, P2P), the routing node broadcasts the received transaction request to the same-chain mining node of the routing node after signing , May be to sign the received transaction request and broadcast it to the neighboring same-chain mining node of the routing node, and then the neighboring same-chain mining node of the routing node will broadcast the signed transaction request to the respective Adjacent mining nodes.

It should be noted that the routing node can add the received transaction request to the routing node's transaction request set before verifying the transaction request received from the SPV node, and then add the received The transaction request is signed and broadcasted to the same-chain mining nodes of the routing node, or the routing node can first verify the transaction request received from the SPV node, and then the received transaction request After being signed, it is broadcasted to the same-chain mining nodes of the routing node, and then the received transaction request is added to the routing node's transaction request set, which is not specifically limited in this application.

Step S203: the routing node synchronizes the blockchain of the same mining node of the routing node to the local blockchain in real time.

The routing node will not perform mining and accounting operations, but the routing node synchronously saves the blockchain data (ledger) of the parallel chain where the routing node is located. It should be noted that the routing node may perform step S203 at any time, and is not limited to performing step S203 after performing step S202.

Step S204: In response to the verification of the signed transaction request received from the same link by the node, the mining node adds the in-chain transaction request of the mining node in the signed transaction request to the pending transaction of the mining node Request collection.

The mining node can respond to receiving the post-signed transaction request from the same link by the node: first, verify the received post-signed transaction request; second, if the verification is passed, the mining node can send the signed transaction request The in-chain transaction request of the mining node is added to the set of pending transaction requests of the mining node.

The verification of the received signed transaction request by the mining node may include: using the same link of the mining node and the node's public key to verify the received signed transaction request by the node's public key. The received signed transaction request is checked for legality. If the legality check is passed, it can be determined that the mined node verifies the received signed transaction request.

In the embodiment of the present disclosure, the transaction request may include a billing request and a billing request. For example, the transaction request D is to transfer X digital currencies in the address A of the wallet account to the address B of the wallet account. Then, the transaction request D may include an accounting request D1 and an accounting request D2, where the accounting request D1 is to reduce the digital currency in the address A of the wallet account by X, and the accounting request D2 is to convert the digital currency in the address B of the wallet account Increase X.

The in-chain transaction request of the mining node in the post-signed transaction request can include the following two situations: In the first case, the parallel chain corresponding to the address of the transferred-out wallet account and the address of the transferred-in wallet account in the signed transaction request are both Is the parallel chain where the mining node is located, then the sign-out transaction request and the account entry request in the transaction request after signing are both in-chain transaction requests of the mining node; in the second case, the transfer-out wallet account in the transaction request after signing The parallel chain corresponding to the address of is the parallel chain where the mining node is located, and the parallel chain corresponding to the address transferred to the wallet account in the transaction request after signing is not the parallel chain where the mining node is located. The accounting request is the in-chain transaction request of the mining node, and the account entry request in the signed transaction request is not the in-chain transaction request of the mining node.

Each mining node can save the set of pending transaction requests of the mining node in the buffer. Each mining node belonging to the same parallel chain can compete for the accounting rights of the parallel chain where the mining node is located according to a preset consensus mechanism. If a mining node competes for the accounting rights of the parallel chain where the mining node is located, the pending transaction request in the set of pending transaction requests stored locally by the mining node can be used to form a new block, and the formed The new block is added to the local blockchain (ledger) of the mining node.

As mentioned before, in the embodiment of the present disclosure, due to the adoption of the mining pool structure, the task of competing for accounting rights on the mining nodes is actually distributed to the miners connected to the mining pool through the mining pool server to complete the mining. The main work of the node is to be responsible for accounting after the success of the miner's competition for accounting rights. Of course, from the perspective of the mining node, it is still the mining node that is mining and accounting. Regarding how the mining pool works, we will introduce it further in the following article. For now, we only focus on the functions provided by the mining nodes.

Step S205: The routing node determines an unaccounted transaction request that is confirmed to have been accounted and unaccounted in the transaction request set of the routing node.

In addition to recording transaction requests in the local transaction request set, the routing node can also update and record the current processing status corresponding to each transaction request in the local transaction request set in real time.

According to step S203, since the routing node synchronously stores the blockchain data of the parallel chain where the routing node is located, the routing node can first query the local transaction request set for the corresponding unprocessed transaction whose current processing status is not yet accounted for Request, and then based on the locally synchronized blockchain data to determine whether each unbilled transaction request has been confirmed to be billed. For example, the routing node can determine whether there are six or more blocks after the block corresponding to the account request in the transaction request in the blockchain data stored locally, and if so, it can confirm the transaction Request confirmation that it has been posted. If it is determined that the unrecorded transaction request confirms that it has been accounted for, it can be determined that the transaction request is an unrecorded transaction request that confirms that it has been posted and is not accounted for.

Step S206: The routing node sends the determined unaccounted transaction request to the routing node of the target parallel chain.

The routing node may send the unrecorded transaction request determined in step S205 to the routing node of the target parallel chain. Wherein, the above target parallel chain is the parallel chain corresponding to the address of the account of the account of the credited wallet in the determined unaccounted transaction request. For example, for the unaccounted transaction request D: transfer X digital currencies from the address A of the wallet account to the address B of the wallet account, where the address A of the wallet account corresponds to the parallel chain 101 and the address B of the wallet account corresponds to the parallel chain 102 Then, corresponding to step S206, the routing node of the parallel chain 101 may send the unaccounted transaction request D to the routing node of the parallel chain 102.

Step S207: In response to receiving the transaction request sent by the node on the different link, the routing node signs the received transaction request and broadcasts it to the same-chain mining node of the routing node.

A different link of a routing node refers to a routing node in a parallel chain that is different from the parallel chain where the routing node is located. If the routing node receives a transaction request sent by a node with a different link, it indicates that the above-mentioned different link has sent a different link to the routing node. The non-accounted transaction confirmed by the node in the transaction request set of the node is confirmed and unaccounted request. Then, the routing node can sign the received transaction request and broadcast it to the same-chain mining node of the routing node. Here, the routing node may sign the transaction request by the routing node using the routing node's private key to sign.

For example, for an unaccounted transaction request D: transfer X digital currencies from the address A of the wallet account to the address B of the wallet account, where the address A of the wallet account corresponds to the parallel chain 101 and the address B of the wallet account corresponds to the parallel chain 102 Then, corresponding to step S206, the routing node of the parallel chain 101 may send the unaccounted transaction request D to the routing node of the parallel chain 102. Corresponding to step S207, it may be that the routing node of the parallel chain 102 broadcasts the unrecorded transaction request D and broadcasts it to the mining node in the parallel chain 102. Therefore, the mining node of the parallel chain 102 can perform step S204. If a node with the same link, that is, a routing node of the parallel chain 102, receives the signed transaction request D, the mining node of the parallel chain 102 first receives the The signed transaction request D is verified. If the verification is passed, the in-chain transaction request of the mining node in the signed transaction request is added to the set of pending transaction requests of the mining node. Among them, the intra-chain transaction request of the mining node of the parallel chain 102 in the transaction request D is to increase the address B of the wallet account by X digital currencies.

It should be noted that the above steps are only examples to illustrate the working principle of the blockchain system. In specific implementation, the execution order of steps S201 to S207 can be rearranged and combined in various ways, and this application does not Be specific.

In the blockchain systems shown in Figures 1(A) to 1(B), the transaction processing process is improved from the traditional single-chain serial mode to the multi-chain concurrent mode. As the number of parallel chains increases, the blockchain The number of transactions per second (Transactions Per Second, TPS for short) of the system has also increased, improving the problem of low throughput of traditional blockchains and the difficulty of large-scale commercial applications. At the same time, transactions between SPV nodes need to be completed through routing nodes, so that routing nodes can be used to effectively supervise digital currency transactions, which improves the difficulty of traditional blockchain supervision due to its decentralized characteristics . It can be understood that FIGS. 1(A) to 1(B) show only a specific exemplary architectural manner of the blockchain system, but it is not the only architectural manner, for example, in some implementations The SPV node may not be included in the parallel chain, so the illustrated blockchain system should not be regarded as a limitation on the protection scope of the present disclosure.

In addition, in the present disclosure, the blockchain system performs mining by forming a mining pool on the mining node of the parallel chain. Compared with the way in which the miner node directly mines on the parallel chain, it has at least the following advantages.

Blockchain systems usually require a certain number of distributed full ledger nodes to ensure security. If the miner nodes on the parallel chain are responsible for accounting, due to the large number of miner nodes, the entire network broadcast of ledger data will occupy a large amount of bandwidth. In terms of high-throughput parallel chains, the amount of data that needs to be synchronized is large, and the network burden is further increased. Too many full-ledger nodes do not bring additional value; moreover, support for the transmission of large amounts of synchronized data to the miner node equipment Both performance and network bandwidth have high requirements. However, in practice, especially on the public chain, miner nodes are mostly personal devices, and their performance is limited and distributed in different network environments. This requirement is difficult to meet. In addition, most individuals who participate in mining do not have or have very little accounting needs, but only hope to obtain economic benefits through mining. If they are forced to participate in accounting, it may lead to the loss of users.

In the blockchain system provided by the embodiments of the present disclosure, due to the use of the mining pool, the slave TEE as a miner only competes for the accounting right, and does not directly account for it. Only the mining node performs accounting, and the mining node The number of is much smaller than the number of Slave TEE, so the amount of data that needs to be synchronized between mining nodes will not be too large. In some implementations, the mining pool can be deployed in the cloud, the performance of the mining pool server and mining nodes, and the bandwidth of the network transmission can be guaranteed, and data synchronization will not cause a serious burden on the network. At the same time, because Slave TEE does not participate in accounting, there is no need to synchronize the data of the blockchain. Therefore, the performance of the terminal equipment and the network environment will not become the performance bottleneck of the blockchain system.

Mining pools can be operated by users who have a large amount of accounting requirements. For example, enterprise users may have a large amount of accounting requirements after the funds are chained. Enterprise users are usually not interested in mining revenue, but to achieve accounting requirements, you can Attract individual users to access the mining pool to help them mine. Individual users can obtain mining revenue without accounting, and naturally are willing to join the mining pool. Both types of users take their own needs, which is conducive to improving the block The operating status of the chain system. Multiple mining pools can be built on the blockchain system. Different companies can build their own mining pools and share the entire blockchain system. At the same time, it is also convenient to disperse the mining power into different mining pools and avoid computing power. Concentration affects the security of the blockchain system. Further, in some implementations, all mining nodes on the parallel chain are included in a mining pool. There are no mining nodes on the parallel chain that are free of the mining pool. Users can only participate in mining through the mining pool. In the mine, the terminal equipment is controlled by the mining pool server to prevent the attacker from gathering computing power.

In addition, the blockchain system in the embodiment of the present disclosure uses a parallel chain instead of an ordinary single chain, supports the decentralization of each slave TEE on different parallel chains for mining, and effectively avoids the concentration of computing power. Decentralized, I will introduce the possible implementation methods in detail later.

FIG. 3 shows a flowchart of a billing method provided by an embodiment of the present disclosure. Figure 3 describes a process of accounting rights competition. Referring to FIG. 3, the accounting method may include:

Step S301: The mining node sends the hash value of the main body of the block header of the pending accounting block to the mining pool server and the difficulty target value of mining on the parallel chain.

During the operation of the blockchain system, the transaction buffer of the mining node holds the transaction to be booked. The pending bookkeeping block refers to the new block determined according to the transaction to be booked before the mining starts. , The block body of the block has been determined, which contains pending transactions.

The block header of the pending accounting block can be divided into two parts, including the main part and additional parts. Before starting mining, the main part has also been determined. For example, in some implementations, the main part of the block header may include the version number of the block, the block header of the previous block in the block chain. The hope value, the chain identifier of the parallel chain (such as the parallel chain number), the root of the Merkle tree constructed from the transactions in the block body, the timestamp indicating the generation time of the block, mining on the parallel chain The target value of difficulty, etc., where the parallel chain refers to the parallel chain where the mining node that generated the block is located. It can be understood that, according to actual needs, the main part of the block header may also include more or fewer fields, for example, in some implementations, in order to superimpose the PoW consensus mechanism and the consensus mechanism adopted in the embodiments of the present disclosure In order to improve the security of the blockchain system, the main part of the block header may also contain the random number (Nonce) to be used in the PoW algorithm.

The additional part of the pending accounting block can only be determined after the mining is completed. Specifically, the Slave TEE competing for the accounting right is returned to the mining node through the mining pool server. After the mining node obtains the additional part, it can be completed. Block header. The additional part of the block header includes at least the signature of the accounting right determination information and the address body of the wallet account bound by the Slave TEE competing for the accounting right of the block, the specific meaning of which will be described later. Understandably, the additional part of the block header may also include other information, such as an authentication code, which will be described later.

According to the body part of the block header, the hash value of the body part of the block header can be calculated, and the hash value can uniquely identify the pending accounting block. The difficulty target value represents the difficulty of mining on the parallel chain (the greater the difficulty of mining, the longer the average mining time per mining). The difficulty target value is maintained and updated by the mining node. When the difficulty target value is not updated, the same parallel chain The difficulty target values of the mining nodes on the same moment are the same. In some implementations, the difficulty target value is updated by the following formula:

New difficulty target value = current difficulty target value * (actual time of current cycle/expected time of one cycle)

The period here refers to the update period of the difficulty target value. For example, it can be set that each mining node generates 1008 blocks as a period. Assuming that a block is expected to be generated every 5 minutes, the expected time of one cycle is 5040 (1008*5) minutes, and the actual time of the current cycle can be obtained statistically during the process of generating blocks. At the beginning, you can set a difficulty target value in a certain mining environment as the initial difficulty target value, and then update the difficulty target value according to the above formula.

Understandably, in some implementations, the hash value of the main body of the block header can also be replaced with some other information that can uniquely identify the block, such as the area of the previous block in the blockchain The hash value of the block header, or a string formed by splicing the fields of the main body of the block header, etc. The advantages of using the hash value of the main part of the block header are: first, the hash value is shorter, which can reduce the amount of data that needs to be transmitted; second, the hash value of the main part of the block header is only at the beginning of the assembly of the pending accounting area It can only be determined at the time of the block, and it cannot be determined before this, so each Slave TEE cannot start the competition of computing power in advance when the main part of the block header has not been determined Will be used to generate signatures), so that the hash value of the main part of the block header is used to identify the pending accounting block is conducive to improving the fairness in the process of competing accounting rights.

After a round of computing power competition has ended, when a new pending accounting block is to be mined, the mining node sends the hash value of the main body of the block header and the difficulty target value to the mining pool server, that is, step S301 is executed. In the mining process of pending bookkeeping blocks (no Slave TEE has yet competed for bookkeeping rights), the difficulty target value remains unchanged, but there may be new pending bookkeeping transactions included in the pending bookkeeping block In the body, this will cause the value of some fields in the body of the block header to change, such as the timestamp and the root of the Merkel tree, which in turn will cause the hash value of the body of the block header to change. The server needs to send the hash value of the new block header body to the mining pool server. In some implementations, the mining node checks whether the hash value and difficulty target value of the hash value of the main body of the block header need to be sent to the mining pool server every preset time period (such as half a minute, one minute, etc.) . According to the above, when it is detected that a new block has been mined or a new transaction is included in the pending accounting block, the corresponding data is sent.

If the blockchain system is implemented using the architecture shown in FIG. 1(A) to FIG. 1(B), step S301 can be performed after step S204 in FIG. 2 and the set of pending transaction requests mentioned in step S204 Is the transaction to be recorded.

Step S302: The mining pool server stores the hash value of the main body of the block header and the difficulty target value sent by the mining node.

The hash value and difficulty target value of the main part of the block header can be stored in the database of the mining pool server, of course, it can also be stored in memory or other locations, which is not limited. The hash value and difficulty target value of the main body of the block header sent by the mining nodes on different parallel chains can be stored separately, so that they can be distinguished during subsequent use.

Step S303: The terminal device sends an accounting request to the mining pool server.

Before step S303 starts to be executed, the terminal device has been connected to the mining pool server and can participate in mining. The accounting request is used to indicate to the mining pool server that the slave TEE of the terminal device configuration wishes to participate in the competition for accounting rights. In some implementations, the terminal device sends an accounting request every other time, which can be fixed or configured by the user in the mining application installed on the terminal device, for example, the time interval for initiating the request is configured as Sometime within 1 to 60 minutes. In some implementations, the time interval at which the terminal device sends the accounting request may also be affected by the success of the Slave TEE competition accounting. For example, after the accounting competition is successful, it may be idle for a period of time to temporarily not participate in the competition accounting, or, in After the accounting competition fails, it then participates in the accounting competition.

Step S304: the mining pool server sends the hash value of the main body of the block header and the difficulty target value to the terminal device.

After receiving the accounting request, the mining pool server returns the hash value and difficulty target value of the main body of the block header required for competitive accounting to the terminal device, where the hash value and difficulty target value of the main body of the block header are the steps Obtained in S302.

When there are multiple parallel chains in the blockchain system, Slave TEE can only compete for the accounting rights on one of the parallel chains at a time, and the hash value of the main body of the block header sent by the mining node on the parallel chain and the The difficulty target value is sent to the terminal device. As for how to determine on which parallel chain Slave TEE should mine, different implementation methods can be adopted. For example, it is not limited on which parallel chain Slave TEE mines, and a parallel chain is randomly selected as its mining parallel chain, for example, Limit Slave TEE to only mine on a particular parallel chain, etc.

Step S305: The Slave TEE configured in the terminal device determines whether its accumulated unused duration is greater than the accumulated unused lower limit duration calculated according to the difficulty target value.

A clock can be set in Slave TEE, which is independent of the clock on the terminal device, and the clock can only be accessed by the program (TA) inside Slave TEE, and cannot be accessed by programs other than Slave TEE (such as the program on the terminal device) Visited.

When the Slave TEE is manufactured, the initial value of the accumulated unused time can be configured. During the Slave TEE competition accounting right, the elapsed/elapsed time from the start of the competition accounting right to the current time of the clock set in the Slave TEE Will add up to the accumulated unused time.

The specific accumulation method is not limited. For example, the process of continuously running in the Slave TEE (or background thread) can control the change of the accumulated unused time. For another example, each time the accounting right is competed, the accumulated unused time needs to be obtained first, and the time elapsed/elapsed from the start of the competition accounting right to the current time of the clock set in the Slave TEE is determined before acquiring, and then The determined duration is added to the accumulated unused duration. In the latter method, the Slave TEE is simply powered up without competing for billing rights, and the current accumulated unused time will not be accumulated.

The cumulative unused lower limit duration is calculated according to the difficulty target value, for example, in some implementations, it can be calculated by the following formula:

Cumulative unused lower limit duration = M/difficulty target value

Among them, M is a preset constant, which can be saved in Slave TEE. The cumulative unused lower limit duration can characterize the approximate time interval between each Salve TEE obtaining the accounting right twice under the specified difficulty target value. Therefore, if Slave TEE judges that the current accumulated unused time exceeds the accumulated unused lower limit time, then Slave TEE can determine that it has obtained the accounting right. If the accounting right is obtained, step S306 is executed. If the accounting right is not obtained, it can continue to participate in the next round of accounting right competition. It should be pointed out that Slave TEE can obtain the accounting right, which does not mean that Slave TEE can successfully account, and there may be other verification steps in the subsequent steps, which leads to Slave TEE accounting failure, so the acquisition of accounting right here should be understood as pure From the perspective of the consensus algorithm, the accounting power can be obtained.

After obtaining the accounting right, Slave TEE updates the accumulated unused minimum duration to the difference between the current accumulated unused duration and the accumulated unused minimum duration. That is, the competition for the accounting right will cause the accumulated unused time to consume the accumulated unused lower limit time, thereby ensuring the fair competition of the Slave TEE in the mining pool.

It should be noted that after step S304, the terminal device first receives the difficulty target value and the hash value of the body part of the block header, and then passes the two pieces of information to the Slave TEE (respectively for step S305 and step S306), and passes The way of information can be to call the external interface provided by Slave TEE, using the difficulty target value and the hash value of the main part of the block header as the calling parameters. The function of this interface externally is the function of competing for accounting rights (step S305 and step S306) .

According to the above explanation, it is not difficult to see that the above consensus algorithm is very different from the PoW algorithm. There is no need to perform meaningless hash collision calculations. In Slave TEE, only the cumulative unused duration needs to be maintained and the cumulative unused duration and the cumulative A simple comparison of the lower limit time is not used, and the calculation amount involved is much smaller than the PoW algorithm, which effectively avoids the waste of computing resources in the Slave TEE, reduces the power consumption of the Slave TEE, and effectively saves the power consumption. In other words, Slave TEE can be implemented with low-cost, low-power hardware, which further reduces the threshold of equipment required for mining and helps the mining pool attract more users to participate in mining. Further, most of the time, such as the interval between competing billing rights, Slave TEE's computing resources are idle, so they can even be used to perform other tasks.

It should be pointed out that, in the explanation of the embodiments of the present disclosure, the computing power of the Slave TEE is often mentioned, but its meaning is different from the computing power of the miner when the PoW consensus algorithm is adopted, and does not represent the computing power. Of course, the computing power of Slave TEE also characterizes the ability to compete for accounting power. From this point of view, it also has similarities with the definition of computing power in the prior art, so this statement is used.

Step S306: Slave TEE signs the accounting right determination information.

The accounting right determination information includes key information related to the competitive accounting right. In the embodiment of the present disclosure, the accounting right determination information includes at least the hash value of the body part of the block header of the pending accounting block and the address body of the wallet account bound by the Slave TEE. In different implementation manners, the accounting right determination information may further include the cumulative unused lower limit duration mentioned in step S305, the random number mentioned in step S301, an authentication code to be mentioned later, and so on.

Among them, Slave TEE is bound to the address of the wallet account for receiving mining revenue. The address of the wallet account is unique in the blockchain system where Slave TEE is located. The address of the wallet account includes at least the address body of the wallet account, and in some implementations may optionally include additional parts. Slave TEE can generate a wallet account address in response to an account address generation request sent by a terminal device, and the address of each wallet account corresponds uniquely to each Slave TEE, that is, it has a binding relationship. For example, after the terminal device is configured with Salve TEE, the user can make an account address generation operation in the wallet application installed on the terminal device, the terminal device responds to the operation and generates the above account address generation request, and then generates a wallet account in Slave TEE address.

The method of generating the address body of the wallet account may use the method of generating the address of the wallet account in the existing blockchain, that is, the meaning of the address body of the wallet account in the embodiment of the present disclosure and the address of the wallet account in the prior art The meaning is the same. The additional part of the address of the wallet account may include, but is not limited to, Slave TEE's virtual parallel chain identifier, the type of the wallet account, and other information. The virtual parallel chain identifier will be described in detail later. Even if the additional part of the address of the wallet account is not considered, the address body of the wallet account can uniquely identify the Slave TEE, so the address body of the wallet account indicates the identity of the bookkeeper, and is also one of the key information in the process of competing bookkeeping rights .

In some implementations, the signature of the accounting right determination information may be asymmetrically encrypted. For example, the first private key may be saved in the Slave TEE in advance, and the first private key may be used to encrypt the accounting right determination information to generate a signature of the accounting right determination information. Any node in the blockchain system that holds the first public key that matches the first private key (such as a mining pool server, mining node, etc.) can use the first public key to verify the authenticity of the signature.

Step S307: The terminal device sends the accounting right determination information and the signature of the accounting right determination information to the mining pool server.

Step S308: The mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node.

In some implementations, the mining pool server may directly perform step S308 without processing the accounting right determination information and the signature of the accounting right determination information. In other implementation manners, the mining pool server may verify the result of competing for the accounting right according to the accounting right determination information and the signature of the accounting right determination information. For example, when the accounting right determination information is signed with the first private key, the mining pool server can save the first public key and use the first public key to verify the authenticity of the signature. If the signature verification succeeds, it indicates that the signature is indeed generated by the Slave TEE , Which can prove that the accounting right determination information received by the mining pool server is indeed sent by Slave TEE, and then step S308 can be executed. If the signature verification fails, it indicates that the accounting right determination information received by the mining pool server is not sent by Slave TEE , May be forged by the attacker, so step S308 and subsequent steps are not performed to prevent the attacker from obtaining accounting rights.

Furthermore, the mining pool server can also verify the accounting rights to determine whether the content of the information has been tampered with to improve the security of the blockchain system and avoid information forgery. For example, the mining pool server can verify whether the hash value of the locally stored block header body part is consistent with the hash value of the block header body part in the accounting right determination information, so as to determine whether Slave TEE used forged Pending accounting block. For another example, the mining pool server can convert a cumulative unused lower limit duration according to the locally saved difficulty target value, and verify whether the converted cumulative unused lower limit duration is consistent with the cumulative unused lower limit duration in the accounting right determination information, In order to determine whether Slave TEE used the forged difficulty target value when accounting. According to the verification result, if the accounting right determination information has not been tampered with, step S308 is continued, otherwise step S308 and subsequent steps are not executed.

As mentioned earlier in step S304, when the blockchain system has multiple parallel chains, Slave TEE can only compete for the accounting rights on one of the parallel chains at a time, so the mining pool server sends to the mining node in step S308 The signature of the accounting right determination information and the accounting right determination information should also be the signature of the accounting right determination information and the accounting right determination information sent to the mining node on the parallel chain where Slave TEE competes for the accounting right, or That is to say, if the hash value and difficulty target value of the main body of the block header used in the Slave TEE competition for the accounting right are originally from which mining node, then after the competition to the accounting right, the accounting right determination information and the accounting right are determined The signature of the information should also be sent back to the mining node.

Step S309: The mining node generates an accounting block and adds the accounting block to the local blockchain.

As mentioned in step S301, the additional part of the block header of the pending accounting block includes at least the signature of the accounting right determination information and the address body of the wallet account bound by the Slave TEE competing for the accounting right of the block, and The content of the competition cannot be determined before the success of the accounting right. The accounting right determination information contains these two contents, so at this time, the mining node can already form a complete block header, and the block body is also determined, so it can generate a complete block, which may be called the accounting area Piece. After the mining node has assembled the accounting block, it is added to the tail of its local blockchain.

In some implementations, the mining node may directly perform step S309 without processing the accounting right determination information and the signature of the accounting right determination information. In other implementations, the mining node may verify the result of competing for the accounting right based on the accounting right determination information and the signature of the accounting right determination information. For example, in the case where the accounting right determination information is signed using the first private key, the mining node may save the first public key and use the first public key to verify the authenticity of the signature. If the signature verification is successful, step S309 is executed. If the signature verification fails, step S309 and subsequent steps are not executed.

Further, the mining node can also verify the accounting rights to determine whether the content of the information has been tampered with to improve the security of the blockchain system and avoid information forgery. For example, the mining node can verify whether the hash value of the locally stored block header body part is consistent with the hash value of the block header body part in the accounting right determination information, so as to determine whether Slave TEE used forged Pending accounting block. For another example, the mining node may convert a cumulative unused lower limit duration according to the locally saved difficulty target value, and verify whether the converted cumulative unused lower limit duration is consistent with the cumulative unused lower limit duration in the accounting right determination information, thereby Determine whether Slave TEE uses the forged difficulty target value when accounting. According to the verification result, if the accounting right determination information has not been tampered with, step S309 is continued, otherwise step S309 and subsequent steps are not executed.

After the mining node adds the accounting block to the local blockchain, it will also broadcast the newly generated block on the parallel chain where the mining node is located, so that the block is synchronized to other on the parallel chain In the node's ledger, the specific broadcast method can be similar to the existing blockchain, and will not be elaborated in detail. In some implementations, the mining node also broadcasts the accounting right determination information and the signature of the accounting right determination information to other nodes on the parallel chain that need to be accounted for, and these nodes can verify after receiving the information Whether the content of the information is consistent with the accounting block to be confirmed in the local blockchain. If they are consistent, the accounting block is recognized as a legal block, otherwise the accounting block is not approved to avoid the generation of The block was forged.

For example, the accounting block B1 is generated by the mining node M1, and the mining node M1 broadcasts it to the mining node M2 of the same chain, and the mining node M2 adds the block B1 to the tail of its local blockchain, waiting It is further confirmed that for mining node M2, block B1 is the accounting block to be confirmed. Of course, there may be multiple accounting blocks to be confirmed at the end of the blockchain of mining node M2, for example B2, B3, etc.

Take the mining node M2 as an example to illustrate how the accounting node on the parallel chain can verify the legitimacy of the block based on the accounting right determination information and the signature of the accounting right determination information. First, the first public key may be stored on M2 to verify the authenticity of the signature of the accounting right determination information. Secondly, M2 can combine the hash value of the main body of the block header in the accounting right determination information, the address body of the wallet account, the accumulated unused minimum duration (corresponding to the difficulty target value) and other content with its local blockchain. The corresponding information items in the block header of the confirmed accounting block are compared to verify whether they are consistent. For example, calculate the hash value of the main body of the block header of blocks B1, B2, and B3, and verify whether the hash value of the main body of the block header in the accounting right determination information is consistent with the calculated three hash values. It is consistent with the calculated hash value of block B2, and it is further verified whether the other pieces of information in the block header of block B2 are consistent with the corresponding information items in the accounting right determination information. If the block B2 passes all the verification steps, the mining node M2 can determine that the block B2 is a legal block.

In addition, since the block header of the accounting block contains the signature of the accounting right determination information, at any time after the block is generated, the holder of the public key can verify the authenticity of the signature to confirm the area Whether the block is generated by legal SlaveTEE equipment through mining.

According to the basic principles of the blockchain, for the blockchain system, one of the core problems to be solved is to prevent the attacker from intentionally concentrating the computing power and creating a 51% computing power attack. The embodiments of the present disclosure provide several measures to avoid the accumulation of computing power in the blockchain system. 4(A) to 4(B) show a flowchart of another accounting method provided by an embodiment of the present disclosure. 4(A) and 4(B), the method includes:

Step S401: The terminal device sends a registration request to the mining pool server.

Slave TEE is configured on a certain terminal device, and Slave TEE has been bound to the address of the wallet account used in mining. Now the user wants to access a mining pool through the terminal device to participate in mining. In some implementations, the terminal device can directly start mining, such as step S303. In some other implementations, the user needs to register on the mining pool server first, and only after the registration is successful can mining be performed, so that the mining pool server can control the miners. During registration, the user sends a registration request to the mining pool server through the terminal device, and the registration request can be actively initiated by the user in the mining application installed on the terminal device.

The registration request carries registration information. The registration information includes at least the address of the wallet account bound to the Slave TEE, and may also include user attribute information, such as a user name, password, and user personal information.

In the implementation of some mining pools, you can also require that all users participating in mining in the mining pool must go through a real-name certification authority, that is, the user's real identity information must be bound to the Slave TEE.

The real-name certification authority may be a third-party authority that has no direct interest in users and mining pools, for example, some national regulatory authorities. The real-name authentication can be handled by the user to the real-name authentication agency, for example, the user visits the website of the real-name authentication agency through a web browser application installed on the mobile phone (a type of terminal device), and fills in his mobile phone number (the user’s real identity information) One), the address of the wallet account and the mobile phone verification code bound to the Slave TEE. The mobile phone verification code can be obtained from the real-name certification body after the user fills out the mobile phone number. The verification code will be sent to the mobile phone as a message, and the user will Fill it in, the user submits all the information after filling in all the information, and the real-name certification body verifies and stores the information submitted by the user on the server side. If the authentication is passed, the authentication result is returned to the mobile phone, and the mobile phone saves the authentication result locally. It can be understood that the specific method of real-name authentication is not limited in the embodiments of the present disclosure, and the above is only one of them.

The real-name authentication result may be a message with a specific format. The real-name authentication result includes at least an authentication code, and may also include, but is not limited to, one or more information items in the authentication ID, user real-name ID, and device ID. The following is a brief introduction:

The certification mark is used to characterize the identity of the real-name certification body.

The user real name identification is used to characterize the user's real identity information, such as the user's mobile phone, ID card number, bank card number, driving license number, etc. The content of the user real name identification may be submitted by the user when performing real name authentication.

The device identifier is used to characterize the slave TEE participating in the authentication, for example, it can be the address (or address body) of the wallet account bound to the slave TEE, the hardware identifier of the slave TEE, etc., where the hardware identifier of the slave TEE is used to uniquely mark a certain The identity of the Slave TEE can be determined and solidified in the Slave TEE when Salve TEE is manufactured. The content of the device identification may be submitted by the user during real-name authentication.

The authentication code is used to indicate that the user has passed the authentication of the real-name authentication agency, and the authentication code has a corresponding relationship with the user. In the process of real-name authentication, the user's real identity information is bound to the Slave TEE, and the user can be marked either by the user's real-name ID or by the device ID, so the authentication code and the user's real-name ID and device ID There is also a corresponding relationship. In some implementations, the authentication code may be implemented as a random integer generated by the real-name certification authority, and stored on the server of the real-name certification authority in association with the user real-name identification and/or device identification.

The person or device that obtains the above-mentioned authentication result can go to the real-name authentication agency to verify whether the user has passed the real-name authentication. For example, first parse out which real-name certification body made the certification result according to the certification mark, and then visit a query URL provided by the real-name certification body, submit the user real-name identification and authentication code, or submit the device identification and authentication code, namely You can get the results of the real-name certification body feedback, and indicate whether the user has passed the real-name authentication.

Further, in order to ensure the authenticity of the certification result, the real-name certification authority can use its private key to sign the certification result, return the certification result and the signature of the certification result to the terminal device, and the device with the public key of the real-name certification authority can verify the The authenticity of the signature.

For the real-name authentication mechanism, the registration request sent by the terminal device to the mining pool server may also include the authentication result and the signature of the authentication result.

Step S402: The mining pool server verifies whether the registration request is valid.

The mining pool server judges whether the received registration information is legal, for example, whether the format is correct, etc. If it is legal, step S403 is executed, and if it is illegal, step S404 is executed to notify the terminal device that the registration has failed, so that the user can take corresponding measures, for example Re-register.

If the implementation of the mining pool requires verification of whether the mining user has passed the real-name authentication, the mining pool server will also receive the authentication result sent by the terminal device and the signature of the authentication result. The public key that matches the private key of the real-name certification authority can be stored on the mining pool server, so that the authenticity of the signature can be verified. If the verification is successful, step S403 is executed; if the verification fails, step S404 is executed to notify the terminal device that the registration has failed.

In addition, in some implementations, the mining pool server can also go to the real-name certification authority to verify whether the user has actually passed the real-name authentication according to the authentication result, to avoid tampering with the authentication result. The possible verification method has been illustrated in step S401. Repeat again. If the verification is successful, step S403 is executed; if the verification fails, step S404 is executed to notify the terminal device that the registration has failed.

Step S403: The mining pool server saves the registration information.

The registration information can be saved in the database of the mining pool server. In some implementations, the main part of the address of the wallet account bound by Slave TEE and the virtual parallel chain identifier (additional part of the address of the wallet account) can be divided into two fields to save and add these two fields in the database Index for quick query.

Step S404: the mining pool server sends a registration response to the terminal device.

The registration response may include the status of successful registration, failed registration, etc., to inform the user of the registration result.

Step S405: The terminal device sends the pool application to the mining pool server.

After successful registration, the user has been registered as a user of the mining pool. In some implementations, the terminal device can directly start mining, such as step S303. In other implementations, the user needs to be authorized by the mining pool server to start mining.

The inventor's long-term research and practice found that in the existing blockchain using PoW consensus, out of the pursuit of economic benefits, the trend of centralization of mining pools is inevitable. The so-called centralization refers to the large number of ASIC miners from the remote Access to miner nodes to participate in mining leads to the accumulation of computing power in the mining pool. Once the computing power on the large mining pool is used by the attacker, it may lead to a 51% computing power attack. In the embodiment of the present disclosure, although the PoW consensus algorithm is replaced by a new consensus algorithm, the essence of the algorithm is still the competitive accounting right. If the number of Slave TEE participating in mining in each mining pool is not limited, it is still possible There is a problem that a large number of mining pools gather a lot of computing power.

The purpose of the mining pool server authorization is precisely to control the number of slave TEEs participating in mining in the mining pool and avoid the trend of centralized mining pools. Once the centralization of the mining pool can be avoided, the advantages brought by the mining pool structure are significant. It has been explained in the previous introduction to the structure of the parallel chain system, including reducing the network burden of the blockchain system, making enterprise users with accounting needs Complementary advantages with individual users who have mining needs, etc.

In order to obtain the authorization of the mining pool server, the terminal device first sends the pool application to the mining pool server to inform the mining pool server that it wants to participate in mining. The pooling application can carry information related to mining, including but not limited to the mine pool identification, application time, the public key of the address of the slave TEE-bound wallet account configured on the terminal device, and the wallet account of the Slave TEE-bound wallet account Information such as the virtual parallel chain ID in the address. Among them, the mining pool logo is used to uniquely identify a mining pool in the blockchain system. This logo is open to the public and can be obtained by anyone. For example, if a user wants to mine in a mining pool, he can obtain the mining pool ID of the mining pool in advance, and then enter it into the mining application installed on the terminal device. The public key of the address of the wallet account has a unique correspondence with the main part of the address of the wallet account. The former can be used to derive the latter according to the determined rules. Therefore, obtaining the public key is equivalent to obtaining the address body of the wallet account. At the same time, the public key of the address of the wallet account can be used to verify the signature made by the corresponding private key, so its scope of application is wider than the address of the pure wallet account. In some implementations, the terminal device generates an application for pooling by calling the interface provided by Slave TEE. The mining pool ID is passed to Slave TEE as the calling parameter. The remaining three items of information can be given by the application in Slave TEE. To ensure the authenticity of the pooling application, the Slave TEE can store the second private key, and use the second private key to sign the above four items of information, and the signature is also carried in the pooling application.

Step S406: The mining pool server verifies whether the pool entry application is valid.

The mining pool server judges whether the received pooling application is legal. If it is legal, step S407 is executed. If it is not legal, step S411 can be executed to inform the terminal device that the pooling application failed, so that the user can take corresponding measures, such as re-applying .

If the pool entry application includes the four items of information and signature mentioned in step S405, step S406 may be implemented in the following manner:

First, verify that the mine pool ID is the same as the mine pool ID of the mine pool where it is located. In the mining pool server, the mining pool logo can be saved in its configured Master TEE and cannot be modified at will. If it is verified that the mine pool ID is the same as the mine pool ID of the mine pool where it is located, continue to perform the next steps, otherwise it is determined that the application for pool entry is invalid. After verifying that the mine pool ID is the same as the mine pool ID of the mine pool where you are, use the second public key saved by the mine pool server to match the second private key to verify the authenticity of the signature in the pool application. If the verification passes, continue Perform the following steps, otherwise it is determined that the pool application is invalid. After the authenticity of the signature in the pool application is verified, the wallet account’s address body is derived from the wallet account’s public key. Since the registration information is saved in step S403, the registration information can be queried from the previously saved registration information If the address body of the wallet account is not queried, it indicates that the user who applied for pooling has not registered at all, and it is determined that the application for pooling is invalid; or although the address body of the wallet account is queried, the virtual parallel chain of the address of the corresponding wallet account If the ID is inconsistent with the ID of the virtual parallel chain carried in the pooling application, the pooling application is also determined to be invalid; if the user applying for pooling is registered and the sequence number of the virtual parallel chain saved is correct according to the query result, the pooling application is valid. It can be understood that, in specific implementation, the sequence of the above several verification steps may also adopt a different sequence from the above listed.

Step S407: the master TEE configured by the mining pool server determines whether the capacity of the mining pool server is less than the capacity threshold.

The capacity threshold of the mining pool server refers to the maximum number of Slave TEE allowed by the mining pool server at a certain moment or a certain period of time, and the capacity refers to the mining pool server at a certain moment or a certain period of time The number of Slave TEEs that have been allowed to be mined in the pool. If the capacity is less than the capacity threshold, you can continue to perform step S408 to authorize the Slave TEE of the terminal device configuration that submitted the pool application to participate in mining, otherwise you can perform step S411 to notify the terminal device that the current mining pool is full and suspend the authorization so that the terminal device Take appropriate measures, such as waiting a while and trying again. Through mining pool capacity control, it can effectively avoid the trend of centralized mining pools, improve the security of the blockchain system, and increase the practical value of the mining pool structure.

Regarding the capacity threshold, different definitions can be adopted in different implementations. For example, in one implementation, the authorized use time T1 of each Slave TEE can be limited, that is, after each Slave TEE is authorized, it can only participate in mining within T1 time (from the authorization start time) After the expiration, you must re-apply for pooling (also does not exclude some implementations of automatic renewal for a period of time), otherwise, after a long period of time, there may be more and more terminal devices connected to the mining pool, resulting in Force gathering, specifically how to limit Slave TEE can only participate in mining during T1 time will be explained in detail later. The capacity threshold is defined as the maximum number N2 of slave TEE allowed to be mined by the mining server during the T1 time.

In the above implementation, the mining pool server can take the following measures to control its capacity not to exceed the capacity threshold:

The mining pool server performs pooling authorization according to a fixed authorization period T2 (T2<T1), and controls the number of pooling authorizations in each authorization period to be less than the first threshold N1, that is, N1 is the maximum number of slaves that can be authorized in an authorization period quantity. When the mining pool server receives a new pooling application, it can judge whether the new pooling application can be authorized by comparing the pooling authorization amount and N1 in the current authorization period. If it can, continue to step S408, and Add 1 to the pool authorization amount in the current authorization period. If it is not possible, step S411 can be executed to inform the terminal device that the mining pool is full in the current authorization period and the authorization is suspended so that the terminal device can take corresponding measures, for example, in the next authorization Try again during the cycle.

Among them, N1, N2, T1, T2 satisfy the relationship: N2 = (T1/T2) * N1, that is, by controlling the amount of pooling authorization in each T2 time, the total amount of pooling authorization in T1 time is controlled At the same time, the way of pooling authorization according to the authorization cycle is helpful to avoid the situation that terminal equipment is concentrated in a certain period of time to apply for pooling, and the computing power of the device is dispersed as much as possible at the time level.

The above T1, T2 and N1 can be pre-configured in the Master TEE. In some implementations, the application in Master TEE can set N1 to meet the rental requirements of Master TEE equipment. For example, resetting N1 to 0 every other year (lease period) will cause the mining pool server to be unable to continue to be authorized. The manager of the mining pool server must renew the lease with the Master TEE publisher.

Step S408: The Master TEE generates authorization information.

After the verification in step S407 is passed, the Master TEE can organize the message content of the authorization response (used in step S411). The content is authorization information, and the authorization information includes at least an authorization code and an authorization serial number. In some implementations, the authorization information may further include the authorized use duration (ie, T1 in step S407). The authorization information can be used to inform the terminal device that its configured slave has been authorized and can start mining.

Among them, the authorization code may include, but is not limited to, the mining pool ID of the mining pool server, the authorization serial number, the application time, the authorized use duration, the address body of the wallet account bound by the authorized Slave TEE, and other information. The authorization serial number can be assigned by the Master TEE to mark each authorization differently, for example, it can be implemented as an integer that increases with the number of authorizations. According to step S405, the application time and the address subject of the authorized Slave TEE-bound wallet account can be included in the pooling application sent by the terminal device (the address subject of the wallet account is deduced from the public key of the address of the wallet account).

Step S409: The Master TEE generates a second key according to the second key generation algorithm, and uses the second key to encrypt the authorization code.

In some implementations, after performing step S408, step S410 may be directly executed. In other implementations, after performing step S408, step S409 may be further executed to encrypt the authorization code before performing step S410.

The encryption process of the authorization code can be implemented in the Master TEE. The Master TEE provides the calling interface, and the clear text authorization code is passed in as a parameter to return the encrypted authorization code after the call. The authorization code uses the second key generated by the second key generation algorithm for symmetric encryption. The second key generation algorithm is not limited here. For example, a preset word string can be stored in the Master TEE, the second key generation algorithm can be a certain hash algorithm, and the hash value can be calculated as the second key according to the preset word string. The above word string is only in TEE Used in the environment, will not leak to the outside. Symmetric encryption algorithm is not limited, for example, AES algorithm, DES algorithm, 3DES algorithm, SM4 algorithm, etc.

Further, the second key generation algorithm can be implemented to be owned by Master TEE, that is, the algorithm implementation is not disclosed outside the TEE environment, and the second key generated by the algorithm is used in Master TEE and only used for encryption The authorization code is not used for other purposes including decryption authorization code, that is, the second key is used unidirectionally in the Master TEE. In the specific implementation, the Master TEE can only provide an interface for encrypting the authorization code, and does not provide an interface for decrypting the authorization code (or the interface is not implemented at all).

The significance of encrypting the authorization code will be explained later when decrypting the authorization code.

In some implementations, steps S407, S408, and S409 can be continuously executed in Master TEE. The execution of these three steps cannot be interrupted or interfered with by programs other than Master TEE, so that external programs cannot change the dependent parameters of intermediate steps. This can ensure that the capacity control is completely determined by the Master TEE, and the program in the mining pool server cannot simulate or fake the capacity control process as a whole. For example, Master TEE can provide an interface for authorization. The mining server is responsible for calling after the verification in step S406, and steps S407, S408, and S409 are implemented in the interface.

Step S410: the mining pool server saves the authorization serial number and authorization related information;

The authorization serial number is generated by the Master TEE in step S408. Since the authorization serial number is ultimately sent by the mining pool server to the terminal device (in step S411), the mining pool server can obtain the authorization serial number. The mining pool server stores the authorization sequence number and authorization related information in correspondence. The authorization-related information refers to information related to the authorization content, which may include, but is not limited to, the start time of authorization, the duration of authorized use, the address body of the wallet account bound by the authorized Slave TEE, and other information. Among them, the authorization start time can be taken into the application time of the pool application. Considering that there may be many users participating in mining, the authorization associated information will occupy a lot of storage space. Therefore, in the specific implementation, the authorization serial number and authorization associated information may be stored in the database of the mining pool server. In addition, if the mining pool server is down for some reason, it can also read the authorization related information from the database after the restart, restore the authorization record, and continue to provide mining services, which is conducive to improving system stability.

Step S411: The mining pool server sends an authorization response to the terminal device.

The authorization response includes both the response to authorization success and the response to authorization failure. Among them, the response to the authorization failure may be that the pool entry application fails verification or the mining pool is full, etc., which has been mentioned in the previous step description. The successful authorization response includes information such as the authorization code, authorization serial number, and authorization duration generated in step S408. In some implementations, if step S409 is performed to encrypt the authorization code, step S411 should include the encrypted authorization code.

Step S412: The mining node sends the hash value of the main body of the block header of the pending accounting block to the mining pool server and the difficulty target value of mining on the parallel chain.

Step S412 is similar to step S301 and will not be repeated.

Step S413: The Master TEE generates a first key according to the first key generation algorithm, and uses the first key to encrypt the hash value of the body part of the block header.

In some implementations, step S414 can be directly executed after step S412. In other implementation manners, after step S412 is performed, step S413 may be first performed to encrypt the hash value of the body part of the block header of the accounting block to be determined, and then step S414 may be executed. In some other implementations, after step S412 is performed, step S414 may also be performed first, and in step S419, before the hash value of the body part of the block header is sent to the terminal device, step S413 may be performed to encrypt it.

The encryption process of the hash value of the main part of the block header is implemented in the Master TEE. The Master TEE provides a calling interface, and the hash value of the main body of the block header in clear text is passed as a parameter to return the encrypted hash value of the main body of the block header after the call is completed. The hash value of the body part of the block header is symmetrically encrypted using the first key generated by the first key generation algorithm. The first key generation algorithm is not limited here. For example, it may be a hash algorithm that calculates a hash value as the first key according to the configuration information of the mining pool.

For example, the first key generation algorithm can be implemented as follows: the content of the mining pool configuration information is spliced into a string, and a preset string that is not disclosed to the public is added at the end of it, and the hash value of the generated string is calculated, Then use the hash value as the first key.

The configuration information of the mining pool may include the chain identifier of the parallel chain. The parallel chain identifier is used to uniquely mark each parallel chain in the blockchain system. For example, the chain identifier of the parallel chain may be implemented using an integer serial number. The parallel chain here refers to the parallel chain where the mining node that sends the hash value of the main part of the block header is located. The mining pool server can pre-store the chain ID of the parallel chain corresponding to each mining node in the mining pool. Therefore, when encrypting the hash value of the main part of the block header, Master TEE obtains the chain ID of the corresponding parallel chain as described above. A key for encryption.

In some implementations, the mining pool configuration information further includes at least one of the number of times the parallel chain has been expanded and the mining pool identifier of the mining pool. Among them, the mining pool logo where the mining pool server is located is pre-configured in Master TEE, which has been introduced before. The parallel chains in the blockchain system provided by the embodiments of the present disclosure support capacity expansion, that is, the number of parallel chains in the system can be expanded when the traffic volume is large (new nodes are added to the newly generated parallel chains). For simplicity, only the expansion method of doubling the number of parallel chains is introduced, but it should not be understood that the blockchain system can only adopt this expansion method. The so-called multiplication and expansion refers to the number of parallel chains doubled each time the capacity is expanded. Each time the capacity is expanded, the number of expansions is incremented by 1. For example, the blockchain system initially has 1 parallel chain, and the number of times it has been expanded is 0; then after one expansion, 1 parallel chain is expanded into 2 parallel chains, and the number of times that it has been expanded is 1, and then passes Once the capacity is expanded, the two parallel chains are expanded into four parallel chains, and the number of times the capacity has been expanded is 2, and so on. In some implementations, an upper limit can also be set for the number of times the capacity is expanded according to the size of the system that can be supported, such as 16, that is, the blockchain system supports up to 65536 parallel chains. The number of times the parallel chain has been expanded can also be saved in the Master TEE and updated when the blockchain system is expanded.

In some implementations, if the real-name authentication mechanism is introduced in the blockchain system, when calculating the first key using the first key generation algorithm, in addition to considering the pool configuration information, the authentication obtained during real-name authentication can also be used The code also serves as one of the sources of the first key, and the authentication code is included in the registration request sent by the terminal device to the mining pool server in step S401.

The symmetric encryption algorithm that encrypts the hash value of the main part of the block header is not limited, and may be, for example, the AES algorithm, DES algorithm, 3DES algorithm, SM4 algorithm, and so on.

Further, the first key generation algorithm can be implemented to be privately owned by Master TEE, that is, the algorithm implementation is not disclosed outside the TEE environment, and the first key generated by the algorithm is used in Master TEE and only used for encryption The hash value of the body part of the block header is not used for other purposes including decrypting the hash value of the body part of the block header, that is, the first key is used unidirectionally in the Master TEE. In specific implementation, Master TEE can only provide an interface for encrypting the hash value of the main body of the block header, and does not provide an interface for decrypting the hash value of the main body of the block header (or the interface is not implemented at all).

The meaning of the hash value of the main body of the encrypted block header will be described later when decrypting the hash value of the main body of the block header.

Step S414: The mining pool server stores the hash value of the main body of the block header and the target difficulty value.

Similar to step S302, the explanation will not be repeated.

Step S415: The terminal device sends an accounting request to the mining pool server.

After obtaining the authorization of the mining pool server, the terminal device may send an accounting request to the mining pool server, indicating that the slave TEE configured by the terminal device wishes to participate in the competition for accounting rights. The billing request may include, but is not limited to, information such as mine pool identification, authorization serial number, and current time. Among them, the mining pool identifier and the mining pool identifier carried in the pooling application previously sent by the terminal device are the same, and the authorization serial number is obtained by the terminal device in step S411.

In some implementations, the terminal device generates a billing request by calling the Slave TEE interface, where the mining pool ID and authorization serial number are passed into the Slave TEE as calling parameters, and the current time can be given by the clock in the Slave TEE. To ensure the authenticity of the accounting request, the Slave TEE can store the third private key, and use the third private key to sign the above three items of information. The signature can also be carried in the accounting request. The third private key and the aforementioned second private key may be the same or different.

Step S416: The mining pool server verifies whether the accounting request is valid.

The mining pool server can determine whether the received accounting request is legal. If it is legal, step S417 is executed. If it is not legal, the terminal device can be notified that the accounting request failed, and the terminal device can initiate the request next time.

If the accounting request includes the three items of information mentioned in step S415 and the signature, step S416 may be implemented in the following manner:

First, the mining pool server verifies that the mining pool ID is the same as the mining pool ID of the mining pool where it is located. In the mining pool server, the mining pool logo can be saved in its configured Master TEE and cannot be modified at will. If the mine pool identifier is the same as the mine pool identifier of the mine pool where it is located, continue to perform the next steps, otherwise it is determined that the accounting request is invalid. After verifying that the mine pool ID is the same as the mine pool ID of the mine pool where it is located, use the third public key saved by the mine pool server to match the third private key to verify the authenticity of the signature in the accounting request. If the verification is passed, continue Perform the next steps, otherwise it is determined that the accounting request is invalid. After the verification of the authenticity of the signature in the billing request is passed, the authorization associated information is queried according to the authorization serial number. The authorization serial number and the authorization associated information have been stored on the mining pool server correspondingly in step S410. If the authorization information does not exist in the stored information , Indicating that the terminal device has not been authorized at all, and it is determined that the billing request is invalid, otherwise the subsequent steps are continued. As mentioned in step S410, the authorization association information may include, but is not limited to, the start time of authorization, the duration of authorization use, the address body of the wallet account bound by the authorized Slave TEE, and other information. The mining pool server can also verify whether the authorization of the Slave TEE has expired, that is, whether the interval between the authorization start time and the current time carried in the billing request exceeds the authorized use time, if the authorized use time is exceeded, it indicates that the authorization has expired, Slave TEE has no right to continue accounting, and the accounting request is determined to be invalid, otherwise it will continue to perform the next steps. It can be understood that, in specific implementation, the sequence of the above several verification steps may also adopt a different sequence from the above listed.

Step S417: The Master TEE determines the parallel chain associated with the terminal device.

In some implementations, Slave TEE can mine on any parallel chain, and each mining can also be on a different parallel chain. This article is not limited to this. In other implementations, in order to avoid SlaveTEE's computing power being concentrated on certain parallel chains, a 51% computing power attack is created, and terminal devices are restricted to only obtain block headers provided by mining nodes on their associated parallel chains. The hash value and difficulty target value of the main part, so that the Slave TEE configured by the terminal device can only be mined on the associated parallel chain, that is, the computing power of the Slave TEE is dispersed. It should be pointed out that the term “parallel chain associated with terminal equipment” refers to the parallel chain associated with the slave TEE configuration of the terminal equipment. If some terminal equipment is configured with multiple slave TEEs, these slave TEEs can be associated with different parallel chains. Of course, for simplicity, this article generally takes the case where the terminal device is configured with only one slave TEE as an example, but this should not be considered as a limitation on the protection scope of the present disclosure.

In some implementations, the Master TEE can calculate the parallel associated with the terminal device based on the virtual parallel chain identifier of the wallet account address bound by the Slave TEE, the parallel chain identifier mask of the terminal device, and the number of parallel chains included in the blockchain system The chain ID of the chain is to determine the parallel chain associated with the terminal device.

Among them, the virtual parallel chain identifier is calculated according to the hardware identifier of the slave TEE configured in the terminal device, and the hardware identifier of the slave TEE has been introduced in step S401. In some implementations, the virtual parallel chain identifier VCN can be calculated as follows:

VCN＝UID&UidMask

Among them, & means bitwise AND operation, UID is the hardware identifier of Slave TEE, which can be realized as a multi-byte value, UidMask is a virtual parallel chain identification mask, which is a constant stored in Slave TEE. For example, if VCN is implemented as 2 bytes, UidMask is also 2 bytes, and the value of UidMask is not limited, for example, it can be 0xFFFF, 0xFFEE (hexadecimal number), and so on. When Slave TEE generates the address of the bound wallet account, the virtual parallel chain identification of the additional part can be calculated based on the above formula, and the generation method of the main part can use the existing blockchain to generate the address of the wallet account method.

Based on the virtual parallel chain ID, the parallel chain ID mask, and the number of parallel chains included in the blockchain system, it can be inferred on which parallel chain Slave TEE mines, that is, the parallel chain associated with the terminal device. In some implementations, the chain identifier MCN of the parallel chain associated with the terminal device can be calculated as follows:

MCN=(VCN^MiningMask)&(N-1)

Among them, ^ means XOR operation, & means bitwise AND operation, VCN means virtual parallel chain identifier, MiningMask means parallel chain identifier mask, and N means the number of parallel chains. MiningMask can be stored in the Master TEE. When the blockchain system is expanded or the mining application installed on the terminal device is upgraded, the value of MingMask may be adjusted. Its purpose is mainly to prevent attackers from deliberately acquiring Slave TEE with a specific VCN. The MCN calculated by these Slave TEE devices is the same, so that mining power can be aggregated on a specific parallel chain. If MiningMask is regularly updated, the attacker's acquisition behavior will become meaningless. N can also be stored in the Master TEE, and its value is updated in the blockchain system capacity updater.

After the expansion of the parallel chain, the number of parallel chains will change, and the parallel chain logo will also change accordingly. However, the virtual parallel chain logo is unchanged, so after the system is expanded, Slave TEE can quickly use the virtual parallel chain logo Re-determining a parallel chain logo, and then switching to the parallel chain corresponding to the parallel chain logo to mine, that is to achieve the distribution of computing power to the new parallel chain, which is also one of the important meanings of setting the virtual parallel chain logo.

It can be understood that the Master TEE can also adopt other methods to determine the parallel chain associated with the terminal device, which is not limited to the above method.

Step S418: The mining pool server verifies whether the billing request meets the cooling time requirement.

In some implementations, Slave TEE can immediately participate in the next round of accounting rights competition after obtaining the accounting rights, without restrictions; in other implementations, Slave TEE will take the initiative to rest for a period of time after acquiring accounting rights If you do not participate in the accounting right, you will participate in the accounting right again after this time. The period during which the Slave TEE rests is called the cooling time. The cooling time can be taken as k times the accumulated unused lower limit time (k is greater than 0 and Constant less than 1), where the cumulative unused lower limit duration is calculated according to the current difficulty target value, which has been explained previously.

In one implementation, the Slave TEE has built-in applications to determine whether it should rest. During the Slave TEE break, even if the terminal device calls the interface for the competitive accounting right provided by the external device, the Slave TEE does not respond to the call or return The prompt message informs the terminal device that it is still in the cooling period. In another implementation, the mining application installed in the terminal device records the time of the last successful accounting, and determines whether the time interval between the current time and the last successful accounting exceeds the cooling time, if not, then It will not mobilize the interface provided by Slave TEE for the external accounting right, otherwise it can be called.

In addition, on the side of the mining pool server, you can also verify whether the accounting request meets the cooling time requirement. It should be pointed out that the judgment process on the mining pool server and Slave TEE's own active rest are independent of each other, even if Slave TEE does not take the initiative to rest after competing for the accounting rights (including cases of deliberate cheating or otherwise not having this function), the mine The pool server can still block the billing request by executing step S418 to force the Slave TEE to fail to obtain the billing right again within the cooling time period after obtaining the billing right.

Specifically, the mining pool server can determine whether the time interval t1 between the Slave TEE and the last billing time configured by the terminal device is greater than the cooling time t2, and t2 is k times the cumulative unused lower limit time (k is greater than 0 and less than 1) Constant), where the cumulative unused lower limit duration is calculated according to the difficulty target value. Since the blockchain system may include multiple parallel chains, the difficulty target value on each parallel chain may not be the same, so for the slave TEE to be verified, the cumulative unused value should be calculated according to the difficulty target value on the parallel chain that it mines Lower limit duration. If the judgment result is greater than, it indicates that the Slave TEE has passed the cooling period, and the billing can be performed again, and the subsequent steps are continued, otherwise the billing request is rejected, and the hash value of the main body of the block header and the target difficulty value are not returned to the terminal device . Or, in some implementations, if the judgment result is negative, the mining pool server may also notify the terminal device of the time interval t3 from which the next billing request is initiated, where t3 may be t2-t1, that is, the terminal device is not allowed to initiate New accounting request, until the time interval between Slave TEE and the last accounting exceeds the cooling time, to avoid the terminal device continuously sending meaningless (that is, impossible to obtain accounting rights) accounting request, resulting in waste of resources.

Through the above verification, the mining pool server can prevent the attacker from intentionally hoarding the accumulated unused time in the Slave TEE configured by the terminal device through some means, and then release the computing power in the short term, so as to continuously obtain the accounting power, and make 51% calculation in disguise Attack, because all slaves participating in mining TEE can not avoid the cooling time limit. At the same time, by setting the cooling time limit, Slave TEE, which can configure more terminal equipment, has the opportunity to obtain accounting rights, which also reflects the fairness of mining to a certain extent.

Slave TEE time interval from the last accounting time is the current accounting time minus the last accounting time, where the current accounting time is the time indicated by the time stamp in the block header of the pending accounting block, the last time The accounting time is the time indicated by the timestamp in the block header of the block generated during the last accounting. Although the mining pool server can obtain these two times from the mining node, according to the existing blockchain protocol, the area The timestamp in the block header can only roughly represent the accounting time (if it does not exceed 2 hours of the current network time is acceptable), the accounting time interval calculated directly by this method has a large error. On the other hand, the timestamp is The mining node decides that it is not ruled out that someone deliberately advances or delays the billing time. These factors may cause the verification accuracy and credibility in step S418 to be low.

Therefore, in some implementations, the following formula can be used to estimate the above accounting time interval:

It is the preset constant of the blockchain system, which is used to characterize the average block generation time of the blockchain system (the average time to generate a block), where the height of a block in the blockchain refers to its There are a total of blocks connected to the blockchain before. For the genesis block, there is no block before it, so its height is 0. The difference in block height is used to estimate the accounting time interval between the two blocks, with higher accuracy and credibility.

In specific implementation, the height of the block can be actively requested by the mining pool server to the mining node on the parallel chain where the Slave TEE mining is located, and the mining node can query and obtain it from the blockchain data stored in it. Alternatively, the mining node on the parallel chain where Slave TEE mining is located can also add the accounting block to the local blockchain, and after the accounting block is finally confirmed, place the accounting block in its The main body of the local blockchain that competes with the accounting right Slave TEE wallet account address is actively sent to the mining pool server. The mining pool server can save these data in the database and need to estimate the accounting time interval. At the time, according to the address subject of the wallet account bound by the current Slave TEE, go to the database to obtain the height of the block generated in the last accounting in the blockchain, and the pending accounting block has not been recorded when step S418 is executed In the blockchain, but if it is added to the blockchain, it must be at the end of the blockchain, so its height in the blockchain is known, and it can get the most recent block sent by the mining node. Height (the latest confirmed block in the current blockchain), this height is used as the height of the pending accounting block in the blockchain.

As an optional solution, the mining node may also send the confirmed block generation time (that is, the timestamp in the block header) to the mining pool server, and the block generation time may serve as an auxiliary judgment. For example, the mining pool operator provides several Slave TEEs that act as stabilizers on each parallel chain. These Slave TEEs only compete with other Slave TEEs for a long time (for example, several times the average block time). Participate in the accounting right only when accounting rights, and is not limited by the cooling time, to avoid too long accounting interval of individual blocks. Among them, the mining pool server sends the generation time of the block in the blockchain to the terminal device equipped with Slave TEE as the stabilizer. The mining application installed on the terminal device is confirmed according to the current time and the latest one in the blockchain The difference in the generation time of the block can determine whether to allow Slave TEE as the stabilizer to compete for the accounting right.

The inventor has discovered in long-term practice that in a few cases, for example, there are not many terminal devices involved in mining, and most terminal devices are offline due to network failures and other reasons. Only a few terminal devices are still mining. It may cause the block in the blockchain to stop growing, because all the terminal equipment configured Slave TEE can not meet the requirement of using the height difference to estimate the cooling time, that is, for all the terminal equipment configured Slave TEE that is still online, Height2Height1 no longer changes, and the estimated t1 is never greater than t2. To solve this problem, in some implementations, the mining pool server can add a verification rule. If the difficulty target value saved by the mining pool server is greater than a certain preset value (such as half of the maximum difficulty target value), it is also regarded as To meet the requirements of cooling time, continue to perform the next steps. The difficulty target value greater than the preset value indicates that the current mining difficulty on the parallel chain is too small (according to the calculation formula of the cumulative unused minimum duration, the greater the difficulty target value, the smaller the mining difficulty, and the smaller the mining difficulty means the parallel chain The number of Slave on the TEE is very small.) If the condition is met, it means that the block of the blockchain has stopped growing on the parallel chain corresponding to the difficulty target value. The Slave TEE should be allowed to keep the account so that the block can be added normally. Correspondingly, a judgment can be added to the Slave TEE if the cumulative unused duration in the Slave TEE has exceeded the preset multiple of the cumulative unused minimum duration (eg 2 times), and the difficulty target value used to calculate the cumulative unused minimum duration is greater than A certain preset value (such as half of the maximum difficulty target value) is also considered to meet the cooling time requirement, and Slave TEE will not continue to rest. The above judgment is performed in the Slave TEE and the outside world cannot interfere or forge its judgment process, so it is true and credible.

Further, if a Slave TEE participates in mining for the first time, or has just changed to a parallel chain mining (because of the expansion of the blockchain system or the adjustment of the parallel chain logo mask), because the mining pool server is only in the current parallel mining of Slave TEE The data associated with the chain is queried for the height of the block generated in the last successful bookkeeping in the blockchain, so the corresponding data cannot be queried, so it is also considered to have met the cooling time requirement.

Step S419: The mining pool server sends the hash value and difficulty target value of the block header body part of the parallel chain associated with it to the terminal device.

In step S417, the parallel chain associated with the terminal device has been determined, so in step S419, the hash value and the difficulty target value of the body part of the block header of its associated parallel chain can be sent to the terminal device.

Step S420: Slave TEE determines whether its accumulated unused duration is greater than the accumulated unused lower limit duration calculated according to the difficulty target value.

Step S420 is similar to step S305 and will not be described repeatedly. In some implementations, Slave TEE determines whether it can obtain accounting rights. In addition to determining whether the cumulative unused duration exceeds the cumulative unused minimum duration, it also determines whether the cumulative unused duration falls within an integer multiple of the cooling duration. Only if both judgments are the same, can you confirm that you have obtained the accounting right, otherwise the competition for accounting right will fail. For example, if the cumulative unused lower limit duration is 2 days, and k is 0.5, the cooling duration is 1 day, and the integer multiple of the cooling duration is 1 day, 2 days, 3 days, and so on. An integer multiple of the cooling duration is defined as an integer multiple of the cooling duration plus a fault tolerance deviation time (for example, 20 minutes). Under this definition, the integer multiple of the cooling duration is 1 day to 1 day and 20 minutes, and 2 days to 2 Days and 20 minutes, 3 days to 3 days and 20 minutes, etc. In a possible scenario, after the attacker controls a certain number of Slave TEEs, let these Slave TEEs concentrate on certain specific time points to compete for accounting power, so that the computing power is concentrated in time, and 51% computing power is disguised. The significance of the attack to increase the above judgment is to force the time points at which Slave TEE competes for accounting power to be dispersed in time, to avoid concentration of computing power, and to ensure the security of the blockchain system.

Step S421: Slave TEE generates a second key according to the second key generation algorithm, and uses the second key to decrypt the authorization code.

In step S422, the authorization code obtained from the mining pool server is used, and the authorization code is carried in the authorization response in step S411. If step S410 is performed to encrypt the authorization code before, step S421 needs to be performed to decrypt the authorization code before step S422 is performed, otherwise step S421 does not need to be performed.

The decryption process of the authorization code is implemented in Slave TEE. Slave TEE provides a calling interface. The encrypted authorization code is passed in as a parameter, and the plain text authorization code is returned after the call. The authorization code uses the second key generated by the second key generation algorithm for symmetric decryption. The second key generation algorithm should be the same as that used in the Master TEE in step S410 to ensure that the generated second key is also in the Master TEE The same, for example, referring to the example of step S410, the same preset character string as in Master TEE can also be saved in Slave TEE, and the same second key generation algorithm in Slave TEE and Master TEE is also based on this string Generate the second key. This string is only used in the TEE environment and will not be leaked to the outside. After obtaining the second key, the symmetric decryption algorithm in Slave TEE should also be consistent with the symmetric encryption algorithm used in Master TEE in step S410.

Further, similar to step S410, the second key generation algorithm can also be implemented as private by Slave TEE (master private by TEE in step S410), that is, the algorithm implementation is not disclosed outside the TEE environment, and the second secret generated by the algorithm The key is used in the Slave TEE and is only used to decrypt the authorization code, not for other purposes including the encrypted authorization code, that is, the second key is used unidirectionally in the Slave TEE. In specific implementation, the Slave TEE It is possible to provide only an interface for decrypting the authorization code, and an interface for not encrypting the authorization code (or not to implement the interface at all).

The encryption and decryption mechanisms in steps S410 and S421 ensure that Master TEE and Slave TEE must be used together. Once there is a mismatch between the two, such as Slave TEE is forged, the encryption and decryption mechanism will not work properly, so that Slave TEE cannot decrypt. And use the authorization code. Moreover, since the second key is used unidirectionally in Master TEE and Slave TEE, it is ensured that the second key will not be cracked by an attacker.

Step S422: Slave TEE uses the authorization code to verify whether the authorization is valid.

As mentioned in step S408, the authorization code may include, but is not limited to, mine pool identification, authorization serial number, application time, authorized use duration, authorized Slave TEE wallet account address body and other information. Therefore, in step S422, the information can be used to verify whether the authorization is still valid at this time. For example, Slave TEE can verify whether the address body of the wallet account carried in the authorization code is consistent with the one saved by itself. (The condition for accumulating unused duration in S420 has been met), otherwise continue to the subsequent steps. For another example, Slave TEE verifies whether the obtained authorization has expired, that is, whether the interval between the application time when sending the pooling application and the current time exceeds the authorized use time, if the authorized use time is exceeded, it indicates that the authorization has expired, Slave TEE It has no right to continue accounting, and it is determined that the competition for accounting rights has failed (although the condition of accumulating unused duration in S420 has been met), otherwise the subsequent steps are continued. As mentioned in step S305, the Slave TEE competition billing right can be invoked by the terminal device through the interface provided by the terminal device. Therefore, it can be determined that the failure of the competition billing right can be prematurely terminated by calling the interface. It can be understood that, in specific implementation, the sequence of the above verification steps may also be different from the sequence listed above.

It should be pointed out that although the authorization code already contains the authorization serial number and the duration of authorization, the authorization response sent by the mining pool server in step S411 contains the authorization serial number and the authorization duration in addition to the authorization code. The reason is that the authorization code is in a ciphertext state, and it is encrypted in step S410 until it is decrypted in step S421. Before that, the information in the authorization code cannot be obtained. In addition, the information passed in the authorization code is The decryption process can ensure that it is not forged. Therefore, the other two messages can be sent separately in clear text. Among them, the authorization serial number is used in step S415, and the authorized use time can be fed back to the mining application, for example, displayed on the application interface, so that the user knows how long he has been authorized, and for example, the mining application You can also determine whether the authorization of the current device is about to end according to the duration of the authorization. When the authorization is about to end, the mining application can automatically initiate the pooling application described in step S405 (for example, call the interface provided by SlaveTEE to generate the pooling application ). It can be understood that, in some implementations, the terminal device may also be implemented without using the authorized use duration. In these implementations, the mining pool server does not need to send the clear authorization use duration during authorization.

Step S423: Slave TEE generates a first key according to the first key generation algorithm, and uses the first key to decrypt the hash value of the encrypted block header body part.

In step S424, the Slave TEE uses the hash value of the main body of the block header obtained from the mining pool server, and the hash value is obtained in step S419. If step S413 is performed to encrypt the hash value of the body part of the block header before, step S423 needs to be performed to decrypt the hash value of the body part of the block header before step S424 is performed, otherwise step S423 is not necessary.

The decryption process of the hash value of the main body of the block header is implemented in Slave TEE. The Slave TEE provides a calling interface. The hash value of the encrypted main body of the block header is passed as a parameter. After the call, the plain text of the main body of the block header is returned. Hash value. The hash value of the body part of the block header is symmetrically decrypted using the first key generated by the first key generation algorithm. The first key generation algorithm should be the same as that used in the Master TEE in step S413 to ensure the generated first secret The key is also the same as in Master TEE.

The algorithm calculates the first key based on the mining pool configuration information. Among them, the mining pool configuration information includes the chain identifier of the parallel chain. The parallel chain here refers to the parallel chain associated with the terminal device. The parallel chain identifier can be obtained through the virtual parallel chain identifier of the wallet account address bound by Slave TEE and the terminal device’s The parallel chain identification mask and the number of parallel chains included in the blockchain system should be calculated in the same way as in step S417. Among them, the virtual parallel chain ID, the parallel chain ID mask, and the number of parallel chains can be saved in the Slave TEE. If the Master Chain TEE updates the parallel chain ID mask and the number of parallel chains, the Slave TEE should also be updated synchronously.

It should be pointed out that although in step S413, the chain identifier of the parallel chain is not calculated by the above three items of information, but since the sent in step S419 is the main part of the block header on the parallel chain corresponding to the parallel chain number calculated in step S417 The hash value of, which can be equivalent to the parallel chain used in the calculation of the first key, is also calculated using the method in step S417, that is, the same algorithm used in decryption.

If the mining pool configuration information at the time of encryption also includes information items such as the number of times the parallel chain has been expanded, the mining pool identifier, and the authentication code, the same information item should also be included in the mining pool configuration information used at the time of decryption. Among them, the mine pool logo is pre-configured in the Slave TEE, which has been introduced before. The number of times the parallel chain has been expanded has been introduced in step S413, and is not described in detail. The number of times the parallel chain has been expanded can be saved in the Slave TEE. If the number of times the parallel chain has been expanded is updated in the Master TEE, the Slave TEE should also be updated synchronously. . The authentication code is already obtained and stored in the Slave TEE when the terminal device performs real-name authentication.

After obtaining the first key, the symmetric decryption algorithm in Slave TEE should also be consistent with the symmetric encryption algorithm used in Master TEE in step S413.

Further, similar to step S413, the first key generation algorithm can also be implemented as private by Slave TEE (master private by TEE in step S413), that is, the algorithm implementation is not disclosed outside the TEE environment, and the first secret generated by the algorithm The key is used in Slave TEE and is only used to decrypt the hash value of the body part of the block header. It is not used for other purposes including the hash value of the body part of the encrypted block header. That is, the first key is in the Slave TEE It is used unidirectionally. In specific implementation, Slave TEE can only provide an interface for decrypting the hash value of the main body of the block header, and does not provide an interface for encrypting the hash value of the main body of the block header (or the interface is not implemented at all).

The encryption and decryption mechanisms in steps S413 and S423 ensure that Master TEE and Slave TEE must be used together. Once the two do not match, for example, Slave TEE is forged, the encryption and decryption mechanism will not work properly, so that Slave TEE cannot decrypt. And use the hash value of the main part of the block header, or even if it can be decrypted, the correct hash value of the main part of the block header cannot be obtained (it can be checked in the subsequent steps, causing the accounting to fail). Moreover, since the use of the first key in Master TEE and Slave TEE is unidirectional, it ensures that the first key will not be cracked by an attacker.

Further, the calculation of the first key is related to the chain ID of the parallel chain associated with the terminal device, which means that the chain ID calculated in the Slave TEE must be consistent with the chain ID calculated in the Master TEE before the Slave TEE can Obtain the same first key as in Master TEE, or Slave TEE can only obtain and decrypt the hash value of the main body of the block header sent by the mining node on the parallel chain corresponding to the chain ID, even if other The hash value of the main body of the block header sent by the mining node on the parallel chain cannot be decrypted correctly, which limits the slave TEE to only mine on the parallel chain associated with the terminal device. According to the calculation method of the chain ID of the parallel chain, the parallel chain ID mask and the number of parallel chains in each Slave TEE are the same. Only the virtual parallel chain ID is different. The virtual parallel chain ID is calculated according to the slave TEE hardware ID, as long as The hardware identification does not have a specific tendency, which can ensure that the Slave TEE in the mining pool is approximately evenly distributed to different parallel chains in the blockchain system.

Further, for the implementation of the first key generation algorithm considering the number of times the parallel chain has been expanded when generating the first key, if the parallel chain is expanded, the number of times the parallel chain has been expanded and the number of parallel chains stored in the Master TEE (Used when calculating the chain ID of the parallel chain) has been updated, but the number of times the parallel chain saved in the Slave TEE has been expanded or the number of parallel chains has not been updated, Slave TEE will not be able to continue mining on the original parallel chain (because Correctly decrypt the hash value of the main part of the block header), that is, after the expansion and upgrade of the parallel chain, if the configuration of the Slave TEE is not upgraded, the Slave TEE will not be allowed to continue to participate in mining, so that even on a parallel chain before the upgrade There has been a gathering of computing power. Once the configuration of the Slave TEE is updated after the upgrade, the aggregated Slave TEE may be distributed to the new parallel chain to mine, thereby effectively eliminating the gathering of computing power.

Further, for the first key generation algorithm to consider the implementation of the mining pool identification when generating the first key, it can restrict the Slave TEE to only mine under the specified mining pool, and cannot replace the mining pool at will (otherwise the decryption area cannot be decrypted correctly The hash value of the main part of the block header) to avoid the accumulation of computing power.

Further, for the first key generation algorithm to consider the implementation of the authentication code when generating the first key, since the accounting nodes on the parallel chain can use the authentication code to go to the real-name certification authority to query whether the user who obtained the accounting right has passed Real-name authentication (see the description below for the specific method), so it can avoid that the pool operator allows some users without real-name authentication (there is no authentication code in their Slave TEE) to use their terminal equipment to participate in mining, ensuring the fairness of the mining process Sex.

Further, step S423 and step S424 can be executed continuously in Slave TEE, and cannot be interrupted or interfered with by programs other than Slave TEE, because the hash value of the main body of the block header obtained by decryption will be used as the accounting right determination information. One part is signed, and the two steps are closely tied to ensure that the hash value of the main body of the block header in clear text is only used to generate the signature of the accounting right determination information, and is not used for other purposes, to avoid being forged. On the other hand, since the signature of the accounting right determination information needs to use the first private key saved by Slave TEE, step S423 also ensures that no one can use the first without decrypting the hash value of the body part of the block header. The private key, or the first private key, can only be used in this scenario without being abused, ensuring that the signature will not be forged.

According to the previous explanation, in order to support the encryption and decryption mechanism of the hash value of the main part of the block header. The Master TEE can save several information such as the number of parallel chains, the number of times the parallel chain has been expanded, the mining pool ID, and the parallel chain ID mask. Among them, the first three pieces of information are configured when the Master TEE is issued, and the first two pieces of information can be changed by trusted authorized operations when the parallel chain is expanded. Master TEE also provides external interfaces to expand the capacity of the blockchain system or the parallel chain When the identification mask is updated, the mining pool server calls this interface to update the number of parallel chains, the number of times the parallel chain has been expanded, and one or more items of information in the parallel chain identification mask.

Slave TEE can save several information such as the number of parallel chains, the number of times the parallel chain has been expanded, mining pool identification, parallel chain identification mask, and virtual parallel chain identification. Among them, the first two pieces of information are configured when Slave TEE is issued, and can be changed by trusted authorization operation when the parallel chain is expanded, the mining pool ID is entered by the user, and the virtual parallel chain ID is generated when the address of the wallet account is generated Calculated according to Slave TEE's hardware identification. Slave TEE also provides an external interface. When the blockchain system is expanded or the parallel chain identification mask is updated, the terminal device invokes this interface to update one of the number of parallel chains, the number of times the parallel chain has been expanded, and the parallel chain identification mask. Item or items.

In order to ensure that the command to change the configuration information in TEE (including Master TEE and Slave TEE) is trusted, in some implementations, a signature needs to be passed in as a parameter when calling the configuration update interface. This signature uses the blockchain The private key saved by the system administrator is generated, and the matching public key is saved in the TEE environment to verify the authenticity of the signature. If the verification is passed, the configuration information is updated. When the capacity of the blockchain system is expanded or the identity mask of the parallel chain is updated, the administrator broadcasts a configuration update instruction in the system (for example, a broadcast message is sent through a routing node on the parallel chain). This instruction will be used by the mining pool server and terminal equipment. Receive and finally call the interface provided by TEE to complete the configuration update. The configuration update instructions have a strict execution sequence (for example, the number of times the parallel chain has been expanded must be accumulated by 1 each time), so the mining nodes and mining pool servers can save each received instruction in their own databases. Once the Master TEE or Slave TEE missed one or more configuration update instructions due to being offline for some reason. After it is re-launched, it will execute the missed instructions in sequence according to the records in the database without generating errors in the order of instruction execution.

In some implementations, the number of times of expansion can be used as the value of the version number field in the main part of the block header, that is, the version number field not only reflects the change of the software version in the blockchain system, but also reflects the expansion in the blockchain system. Configuration changes to simplify version management.

Step S424: Slave TEE signs the accounting right determination information.

The similar parts of step S424 and step S306 will not be repeated. If the mining pool uses the real-name authentication mechanism mentioned in step S401, an authentication code field may be added to the block header of the pending accounting block to fill in the authentication code in the authentication result obtained by the user. Therefore, each block in the blockchain contains the address body of the wallet account bound by the Slave TEE that obtained the accounting right of the block and the corresponding authentication code. According to the explanation in step S401, the nodes on the parallel chain You can use the real-name certification authority to verify whether the user has actually passed the real-name certification based on the two pieces of information recorded in the block header.

Specifically, after obtaining the authentication result, the terminal device may save the authentication code in the authentication result to the Slave TEE. For example, call the external interface provided by Slave TEE, and use the authentication result and the signature of the authentication result as the calling parameters. The public key of the real-name certification authority is stored in Slave TEE, and the signature is verified first. If it passes, the authentication code is stored in Slave TEE. Slave TEE includes the authentication code when signing the accounting right determination information, that is, the authentication code is also used as part of the accounting right determination information. After the accounting right determination information is finally received by the mining node, the mining node saves the authentication code in the block header of the accounting block.

Taking a mining node on a parallel chain as an example, when verifying whether a user has undergone real-name authentication, the mining node needs to know which real-name organization the user authenticates. Since the authentication code does not contain this information, it is implemented in some implementations. In the method, the information is pre-configured in the mining node, and the mining node can verify it at the query URL provided by the real-name certification authority according to the pre-configured information.

In some other implementations, the authentication code can be extended to include the authentication identifier in the authentication result into the authentication code. This extension may be implemented at the end of the real-name certification authority. For example, the authentication code returned by the real-name certification authority already contains the authentication identifier, and no separate authentication identifier will be returned. Or, the real-name certification body still returns the certification mark and the original certification code, but Slave TEE merges the original certification code and certification mark into the extended certification code when saving the certification code, for example, the original certification code is 4 characters Section, the authentication mark is 1 byte, the extended authentication code is 5 bytes, and the extended authentication code is used in the subsequent steps. Since the extended authentication code contains the authentication mark, the mining node can determine the information of the real-name certification body based on the authentication code only when verifying whether the user has undergone real-name authentication, and visit the corresponding real-name certification body to complete the verification, thereby realizing In the blockchain system, it supports terminal equipment certified by multiple real-name certification agencies to participate in mining. It should be pointed out that the extended authentication code mentioned above includes the authentication mark, which means the part of the authentication mark that describes the identity of the real-name certification body, and does not necessarily include all the contents of the authentication mark.

After the introduction of the real-name authentication mechanism, once the mining pool server, mining node or other nodes in the blockchain system discover that a user participating in mining has misconduct, such as the tampering of data in the terminal equipment used by it, it is very It is easy to query the user's true identity information based on the authentication code, and hold him accountable to meet the regulatory needs of the blockchain system's regulatory department.

On the other hand, the real-name authentication mechanism can also make the publishers of Slave TEE self-certified, because the real-name authentication is controlled by a third-party real-name authentication institution, and the publisher cannot forge many Slave TEEs (for example, through software simulation). Abnormal computing power is obtained during the mining process, because the actual identity of the user is limited (for example, it is difficult for the user to have a large number of real mobile phone numbers), and it is difficult for a large number of fake Slave TEE to pass the real-name authentication.

Further, steps S420, S421, S421, S423, and S424 can also be executed continuously in Slave TEE, and cannot be interrupted or interfered with by programs other than Slave TEE, which ensures that the results of the previous steps in these steps cannot be forged in order to use Make input for subsequent operations.

Step S425: The terminal device sends the accounting right determination information and the signature of the accounting right determination information to the mining pool server.

Step S426: The mining pool server verifies whether the accounting right determination information is valid.

The content that the mining pool server can verify includes whether the signature of the accounting right determination information is authentic and whether the accounting right determination information has been tampered with. The content that has been explained in step S308 will not be repeated. If the authentication code is included in the accounting right determination information, the mining pool server can also verify whether the authentication code is consistent with the locally saved one. If they are consistent, the verification code is passed, and if they are inconsistent, the authentication code in the accounting right determination information has been tampered with .

Step S427: the mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node.

When there are multiple parallel chains in the blockchain system, the mining pool server sends the accounting right determination information to the mining node on the parallel chain where the Slave TEE competing for the accounting right is located.

Step S428: The mining node verifies whether the accounting right determines that the information is valid.

The content that the mining node can verify includes whether the signature of the accounting right determination information is authentic and whether the accounting right determination information has been tampered with. The content that has been explained in step S309 will not be repeated. If the accounting right determination information contains an authentication code, the mining node can also verify whether the user has been authenticated by real name.

Step S429: verify whether the pending accounting block meets the cooling time requirement.

If the cooling time requirement is met, step S430 is executed to generate an accounting block; otherwise, an accounting block is not generated, and the accounting fails this time.

The judgment method is similar to that in step S418, which is simply repeated here. For details, refer to step S418:

First, the mining node queries the address subject of the wallet account in the information for determining the accounting rights to obtain the height of the block generated by the terminal device in the last accounting in the blockchain. In order to speed up the query progress, in some implementations, the mining node can separately save the height of each block in the blockchain and the address body of the wallet account in the block header to the mining node's database.

Secondly, the mining node determines the generation time of the pending accounting block and the last accounting generation based on the height of the block generated by the last accounting in the blockchain and the height of the pending accounting block in the blockchain The time interval of the generation time of the block. The specific estimation formula can refer to step S418.

Finally, the mining node determines that the judgment time interval is greater than the cooling time. If it is greater, it determines that the pending accounting block meets the cooling time requirement, otherwise it does not meet the cooling time requirement. The cooling duration is k times the cumulative unused minimum duration calculated according to the difficulty target value saved by the mining node, and k is a constant greater than 0 and less than 1.

Similar to step S418, in some implementations, the mining node may add a verification rule. If the difficulty target value in the block header of the pending accounting block is greater than a certain preset value (such as half of the maximum difficulty target value), then It is also considered to meet the requirement of cooling time, and the cooling time is not estimated according to the height of the block.

Similar to step S418, if a Slave TEE participates in mining for the first time, or has just changed to a parallel chain mining (because of the expansion of the blockchain system or the adjustment of the parallel chain identification mask), because the mining nodes on the new parallel chain are only new The ledger on the parallel chain of the account cannot find the record of the mining before the Slave TEE in the ledger, so it cannot obtain the height of the block generated in the last successful bookkeeping in the blockchain, so it is also considered To meet the cooling time requirements.

Step S430: The mining node generates an accounting block and adds the accounting block to the local blockchain.

The content that has been explained in step S309 will not be repeated. If the accounting block contains an authentication code, the accounting nodes (such as other mining nodes, etc.) on the parallel chain can also verify whether the user has been authenticated by real name, as described in step S424.

In addition, in some implementations, the mining node can also verify whether the accounting behavior of the block for the accounting block broadcast from other mining nodes to be confirmed meets the cooling time, and then determine whether to approve the area Piece. It should be pointed out that the judgment process on the mining node and Slave TEE's own active rest and the judgment process on the mining pool server are independent of each other, even if the slave TEE and the mining pool server do not implement the functions related to the cooling time, the mining node This judgment can still be made independently.

First, the mining node queries the address body of the wallet account of the terminal device saved in the accounting block to be confirmed in the local blockchain to obtain the block of the terminal device's last accounting in the blockchain. height. In order to speed up the query progress, in some implementations, the mining node can separately save the height of each block in the blockchain and the address body of the wallet account in the block header to the mining node's database.

Secondly, the mining node determines the generation time of the accounting block to be confirmed and the last time according to the height of the block generated by the last accounting in the blockchain and the height of the accounting block to be confirmed in the blockchain The time interval of the generation time of the block generated by accounting. The specific estimation formula can refer to step S418.

Finally, the mining node judges whether the time interval is greater than the preset cooling duration. If it is greater than the cooling duration, it will approve the accounting block to be confirmed and add it to the local blockchain for further confirmation, otherwise it will not be approved This block can be discarded directly. The cooling duration is k times the cumulative unused lower limit duration calculated according to the difficulty target value stored in the accounting block to be confirmed, and k is a constant greater than 0 and less than 1.

Similar to step S418, in some implementations, the mining node may add a verification rule, if the difficulty target value in the block header of the accounting block to be confirmed is greater than a certain preset value (such as half of the maximum difficulty target value) ), it is also considered to meet the cooling time requirement, and the cooling time is not estimated according to the height of the block.

Similar to step S418, if a Slave TEE participates in mining for the first time when the accounting block to be confirmed is generated, or has just changed to a parallel chain mining (because of the expansion of the blockchain system or the adjustment of the parallel chain identification mask), Since the mining nodes on the new parallel chain only have the ledger on the new parallel chain, the mining records before the Slave TEE cannot be found in the ledger, so it is impossible to obtain the area generated when the last bookkeeping was successful. The height of the block in the blockchain, so it is also considered to have met the cooling time requirement.

Step S431: The mining pool server transfers the mining pool reward from the address of the mining pool wallet account to the address of the wallet account bound to the Slave TEE competing for the accounting right.

The distribution of mining pool rewards can also be implemented as a script of a smart contract, which triggers the smart contract after the Slave TEE competition billing rights are successful, to realize the distribution of mining pool rewards. It should be pointed out that although the users competing for the billing rights are not necessarily the users who successfully book the bills in the end, the mining pool operators are still considering the operation and can still issue mining pool rewards to them.

The mining pool reward and the mining reward may be the same digital currency, or may not be the same digital currency. The former can be issued and maintained by the mining pool operator himself. The address of the wallet account bound to the Slave TEE is known to the mining pool server, and the address of the mining pool wallet account can be managed by the Master TEE. Each transfer transaction rewarded by the mining pool can be signed using the private key in the Master TEE To ensure the security of transactions.

In addition, it should also be pointed out that the parallel chain that issues mining rewards to Slave TEE is not necessarily the parallel chain where Slave TEE mines.

It can be understood that steps S401 to S431 may also be executed in an order different from the above, and the order of the steps above is only an implementation manner provided by the embodiments of the present disclosure, and should not be considered as limiting the protection scope of the present disclosure.

The above-mentioned embodiments are briefly summarized as, the mining task is distributed to the slave TEE configured in the terminal device through the mining pool server, and the computing power competition is realized in the slave TEE through the accumulation of duration. However, in practice, such a scheme is not excluded: allowing a single TEE to be directly linked to a mining node under a parallel chain for mining without relying on the mining pool server. If the TEE wins the competition based on the accumulated unused time, the accounting right determination information is also signed, and the terminal equipment sends the accounting right determination information and its signature to the mining node, which is generated by the mining node The accounting block and the accounting are completed. Its function is similar to the Slave TEE described above. The single TEE can also determine that it can only perform mining on a certain parallel chain mining node according to the rules introduced previously.

It can be understood that the TEE directly linked to the mining node for mining and the Slave TEE mentioned in the above are different in implementation, and are not the same product. For example, in some implementations, the Slave TEE in the foregoing may use the first key to decrypt the hash value of the body part of the block header (encrypted by the Master TEE), while in this scenario, the TEE can directly pass the zone The plain text of the hash value of the body of the block header. Of course, the implementation of TEE in this scenario has many similarities with the Slave TEE in the previous article. You can refer to the previous article for explanation, which will not be repeated here.

An embodiment of the present disclosure also provides a mining pool server, as shown in FIG. 5. 5, the mining pool server 500 includes:

Memory 504, used to store computer instructions;

Communication interface 506, used to communicate with terminal equipment and mining nodes;

Master TEE508 or Master TEE508 connected;

The processor 502 is connected to the memory 504, the communication interface 506, and the Master TEE 508 through one or more buses 510, wherein when the computer instructions in the memory 504 are executed by the processor, the processor 502 combines with the Master TEE 508 to execute the embodiments of the present disclosure The provided accounting method corresponds to the steps of the mining pool server and Master TEE.

Among them, the memory 504 includes one or more, which may be, but not limited to, random access memory (Random Access Memory, RAM for short), read only memory (Read Memory Only, ROM for short), programmable read only memory (Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The processor 502 and other possible components may access the memory 504, read and/or write data therein.

The processor 502 includes one or more, which may be an integrated circuit chip with signal processing capabilities. The foregoing processor 502 may be a general-purpose processor, including a central processing unit (CPU), a micro controller unit (MCU), a network processor (NP), or other conventional processing It can also be a dedicated processor, including digital signal processor (Digital Signal Processor, referred to as DSP), application-specific integrated circuit (Application Specific Integrated Circuits, referred to as ASIC), field programmable gate array (Field Programmable Gate Array, referred to as FPGA) Or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

The communication interface 506 includes one or more. The communication interface 506 may be a computer network interface, such as an Ethernet interface, or a mobile communication network interface, such as an interface of a 3G, 4G, or 5G network, or may be other data receiving and sending functions. interface.

Master TEE 508 has been introduced in the previous article and will not be repeated again.

The implementation principle and technical effects of the mining pool server 500 provided by the embodiments of the present disclosure have been introduced in the foregoing method embodiments. For a brief description, for the parts not mentioned in the device embodiment, please refer to the corresponding content in the method embodiments .

An embodiment of the present disclosure also provides a terminal device, as shown in FIG. 6. 6, the terminal device 600 includes:

Memory 604, used to store computer instructions;

Communication interface 606, used to communicate with the mining pool server;

Slave TEE 608 or Slave TEE 608 connected;

The processor 602 is connected to the memory 604, the communication interface 606, and the slave TEE 608 through one or more buses 610, wherein when the computer instructions in the memory 604 are executed by the processor 602, the processor 602 performs the present disclosure in conjunction with the slave TEE 608 The accounting method provided in the embodiment corresponds to the steps of the terminal device and the slave TEE.

The implementation method of the memory 604, the communication interface 606, and the processor 602 may adopt a similar implementation method as that of the memory 504, the communication interface 506, and the processor 502, and will not be described repeatedly. Slave TEE 608 has been introduced in the previous article and will not be repeated again.

The implementation principles and technical effects of the terminal device 600 provided by the embodiments of the present disclosure have been introduced in the foregoing method embodiments. For a brief description, for the parts not mentioned in the device embodiments, refer to the corresponding contents in the method embodiments.

An embodiment of the present disclosure also provides a mining node, as shown in FIG. 7. Referring to FIG. 7, the mining node 700 includes:

Memory 704, used to store computer instructions;

Communication interface 706, used to communicate with the mining pool server;

The processor 702 is connected to the memory 704 and the communication interface 706 through the bus 710. When the computer instructions in the memory 704 are executed by the processor 702, the processor 702 performs the accounting method provided in the embodiment of the present disclosure corresponding to mining. Node steps.

The implementation methods of the memory 704, the communication interface 706, and the processor 702 may adopt similar implementation methods as those of the memory 504, the communication interface 506, and the processor 502, and will not be described repeatedly.

The implementation principles and technical effects of the mining node 700 provided by the embodiments of the present disclosure have been introduced in the foregoing method embodiments. For a brief description, for the parts not mentioned in the device embodiments, please refer to the corresponding content in the method embodiments .

It should be noted that the embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments refer to each other. can. For the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method embodiment.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may also be implemented in other ways. The device embodiments described above are only schematic. For example, the flowcharts and block diagrams in the drawings show possible implementation architectures, functions, and functions of devices, methods, and computer program products according to multiple embodiments of the present disclosure. operating. In this regard, each block in the flowchart or block diagram may represent a module, program segment, or part of code that contains one or more of the Executable instructions. It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two consecutive blocks can actually be executed substantially in parallel, and sometimes they can also be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and/or flowcharts, and combinations of blocks in the block diagrams and/or flowcharts, can be implemented with dedicated hardware-based systems that perform specified functions or actions Or, it can be realized by a combination of dedicated hardware and computer instructions.

In addition, the functional modules in the embodiments of the present disclosure may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.

If the function is implemented in the form of a software function module and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present disclosure essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a storage medium, including several The instructions are used to cause the computer device to perform all or part of the steps of the methods described in various embodiments of the present disclosure. The foregoing computer devices include: personal computers, servers, mobile devices, smart wearable devices, network devices, virtual devices, and other devices that have the ability to execute program code. The foregoing storage media include: U disk, mobile hard disk, read-only memory, Random access memory, magnetic disks, magnetic tapes, or optical disks can store program codes.

The above are only specific implementations of the present disclosure, but the scope of protection of the present disclosure is not limited to this, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present disclosure. It should be covered by the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Industrial applicability

The accounting method, mining pool server, terminal equipment, mining node and mining pool provided by the embodiments of the present disclosure adopt a consensus algorithm based on accumulated unused time in the trusted execution environment of the terminal equipment participating in mining to save calculation Resources and reduce power consumption. In particular, the terminal equipment is connected to the mining pool to participate in mining. The Slave TEE configured in the terminal equipment acts as a miner. Slave TEE uses a consensus algorithm different from PoW when competing for billing rights: Slave TEE maintains a cumulative unused time internally , The accumulated unused time will accumulate with the passage of time, meanwhile, Slave TEE also obtains the difficulty target value from the mining pool server, and calculates the accumulated unused minimum duration according to the difficulty target value, if the accumulated unused duration is greater than the accumulated unused lower limit Duration, then the Slave TEE competition accounting right is successful, otherwise the competition accounting right fails, you can continue to participate in the next accounting right competition. The calculation amount involved in the consensus algorithm is not as mechanically consuming as the PoW algorithm based on hash collision, so it is more energy-saving and environmentally friendly, which helps to improve the overall social benefits.

In addition, Slave TEE will also sign the information of the accounting right after the competition for the accounting right is successful, and send the accounting right determination information together with its signature to the mining pool server, which will further forward it to the mining node. The mining node finally saves the signature in the newly generated accounting block, and broadcasts the accounting right determination information and the newly generated accounting block on the parallel chain where it is located. Therefore, the mining pool server, mining nodes, and other nodes on the parallel chain can verify the authenticity of the bookkeeper based on the signature, and can also verify the bookkeeping rights to determine whether the content of the information has been tampered, which is conducive to improving the area. The security of the blockchain system. The accounting right determination information includes key information related to the competitive accounting right. The hash value of the main body of the block header can uniquely identify the pending accounting block, and the address body of the wallet account bound by Slave TEE indicates the identity of the bookkeeper , So they can be included in the accounting right determination information.

In addition, in the present disclosure, the blockchain system uses a parallel chain, thereby supporting the dispersion of each slave TEE on different parallel chains for mining, effectively avoiding the concentration of computing power, and improving the security of the blockchain system.

Claims

An accounting method, which is applied to a blockchain system, the blockchain system includes at least one parallel chain, at least one mining pool is built on the at least one parallel chain, and each mining pool includes a mining pool A server and a mining node located on the parallel chain. The mining node uses a distributed data blockchain to store data. The method includes:

The mining pool server receives and stores the hash value of the body part of the block header of the pending accounting block sent by the mining node and the difficulty target value of mining on the parallel chain where the mining node is located;

The mining pool server receives the accounting request sent by the terminal device;

The mining pool server sends the hash value of the main body of the block header and the difficulty target value to the terminal device, so that the terminal device configures itself to accumulate unused duration from the trusted execution environment Slave TEE Is greater than the cumulative unused lower limit duration calculated according to the difficulty target value, and signing the accounting right determination information when the cumulative unused duration is greater than the cumulative unused lower limit duration, wherein the accounting right The determination information includes the hash value of the body part of the block header and the address body of the wallet account bound by the Slave TEE;

The mining pool server receives the accounting right determination information and the signature of the accounting right determination information sent by the terminal device;

The mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node, so that the mining node generates an address body including the wallet account and the The accounting right determines the signed accounting block of the information and adds the accounting block to the local blockchain.
The method according to claim 1, wherein the parallel chain includes a routing node, at least one mining node of a mining pool and at least one simplified payment verification SPV node, and a network between the routing nodes of the at least one parallel chain Connection, the parallel chain corresponding to the address of the wallet account bound by the SPV node is the parallel chain where the SPV node is located, where:

In response to receiving the transaction request, the SPV node sends the received transaction request to the routing node of the parallel chain where the SPV node is located;

In response to the verification of the received transaction request, the routing node adds the received transaction request to the transaction request set of the routing node, and broadcasts the received transaction request to the transaction after signing The same-chain mining node of the routing node; and the real-time synchronization of the same-chain mining node's blockchain of the routing node to the local blockchain;

In response to the verification of the post-signed transaction request received by the node from the same link, the mining node adds the in-chain transaction request of the mining node in the post-signed transaction request to the pending processing of the mining node A transaction request set; generating a hash value of the body part of the block header according to the pending transaction request set;

The routing node also: determines the unrecorded transaction request that is confirmed to be accounted and unrecorded in the transaction request set of the routing node; sends the determined unrecorded transaction request to the routing node of the target parallel chain, wherein, the The target parallel chain is the parallel chain corresponding to the account number of the account that is determined in the unrecorded transaction request; and in response to receiving the transaction request sent by the node on the different link, the received transaction request is signed and broadcast to the route The same chain mining node of the node.
The method according to claim 1 or 2, wherein the accounting right determination information further includes the cumulative unused lower limit duration.
The method according to claim 1 or 2, wherein the signature of the accounting right determination information is generated by the Slave TEE based on the saved first private key, and the accounting right is stored in the mining pool server Before the determination information and the signature of the accounting right determination information are sent to the mining node, the method further includes:

The mining pool server determines that the signature of the accounting right determination information is a true signature according to the stored first public key matching the first private key.
The method according to claim 1 or 2, wherein the mining pool includes multiple mining nodes, and different mining nodes are located on different parallel chains;

The mining pool server sends the hash value of the body part of the block header and the difficulty target value to the terminal device, including: the master trusted execution environment Master TEE configured by the mining pool server determines with the terminal device An associated parallel chain; the mining pool server sends to the terminal device the hash value of the body of the block header provided by the mining node on the parallel chain associated with the terminal device and the difficulty target value ;

The mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node, including: the mining pool server sends the accounting right determination information and the accounting right The signature of the account right determination information is sent to the mining node on the parallel chain associated with the terminal device.
The method according to claim 5, wherein the Master TEE determining the parallel chain associated with the terminal device includes:

The Master TEE calculates the terminal device based on the virtual parallel chain identifier of the address of the wallet account bound to the Slave TEE, the parallel chain identifier mask of the terminal device, and the number of parallel chains included in the blockchain system The chain identifier of the associated parallel chain, wherein the virtual parallel chain identifier is calculated and obtained according to the hardware identifier of the slave TEE configured by the terminal device.
The method according to claim 5, wherein the mining pool server sending the hash value of the body part of the block header and the difficulty target value to the terminal device includes:

The Master TEE generates a first key based on the mining pool configuration information according to the first key generation algorithm, and encrypts the hash value of the body part of the block header according to the first key; the mining pool configuration information includes a terminal The chain identifier of the parallel chain associated with the device; wherein the Slave TEE can use the first key generation algorithm to generate the first key, and use the first key to decrypt the encrypted block header body Partial hash value;

The mining pool server sends the difficulty target value and the encrypted hash value of the main body of the block header to the terminal device.
The method according to claim 7, wherein the first key generation algorithm is private to the Master TEE and the Slave TEE, and the implementation of the first key generation algorithm is not at the Master TEE and Outside of the Slave TEE, the first key generated by the first key generation algorithm is used in the Master TEE and is only used to encrypt the hash value of the body part of the block header, Used in the Slave TEE and only used to decrypt the encrypted hash value of the body part of the block header.
The method according to claim 1 or 2, wherein the mining pool server sending the hash value of the body part of the block header and the difficulty target value to the terminal device includes:

The mining pool server judges whether the time interval (t1) from the last accounting time of the terminal device is greater than the cooling time (t2), the cooling time (t2) is k times the accumulated unused lower limit time, and k is greater than A constant of 0 and less than 1;

If it is greater, the mining pool server sends the hash value of the body part of the block header and the difficulty target value to the terminal device.
The method according to claim 9, wherein after the mining pool server determines whether the time interval (t1) from the last accounting time is greater than the cooling time (t2), the method further comprises :

If the time interval (t1) from the last accounting time is not greater than the cooling time (t2), the mining pool server notifies the terminal device of the time interval (t3) from which the next accounting request is initiated, The time interval (t3) from which the next billing request is initiated is the difference between the cooling duration (t2) and the time interval (t1) from the last billing time.
The method according to claim 9, wherein the time interval (t1) from the last accounting time is calculated by the following formula:

Where Height2 is the height of the pending accounting block in the blockchain, Height1 is the height of the block generated by the last accounting in the blockchain, and t is the height of the blockchain system A preset constant is used to characterize the average block generation time of the blockchain system.
The method according to claim 1 or 2, wherein before the mining pool server receives the accounting request sent by the terminal device, the method further comprises:

The mining pool server receives a registration request sent by the terminal device, where the registration request carries registration information, a user’s real-name authentication result, and a real-name authentication agency’s signature of the real-name authentication result with a private key. The registration information includes The address of the wallet account bound to the Slave TEE;

The Master TEE configured by the mining pool server verifies the authenticity of the signature of the real-name authentication result according to the stored public key that matches the private key of the real-name certification authority;

If the signature of the real-name authentication result is a real signature, the mining pool server saves the registration information and sends a registration response to the terminal device.
The method according to claim 12, wherein the real-name authentication result includes an authentication code assigned by the real-name authentication institution, the authentication code corresponding to the address of the wallet account bound to the Slave TEE, used for Characterizing that the user has passed the real-name authentication of the real-name authentication institution;

The method also includes:

The mining pool server also receives the authentication code sent by the terminal device, and sends the authentication code to the mining node, so that the mining node adds the authentication code to the accounting Block

The accounting right determination information also includes the authentication code.
The method according to claim 1 or 2, wherein before the mining pool server receives the accounting request sent by the terminal device, the method further comprises:

The mining pool server receives the pooling application sent by the terminal device;

The Master TEE configured by the mining pool server determines whether the capacity of the mining pool server is less than the capacity threshold;

If it is less, the mining pool server authorizes the terminal device to enter the pool according to the authorization information generated by the Master TEE to inform the terminal device to send to the mining pool server within the authorized use time after the authorization start time The accounting request of can be accepted by the mining pool server, wherein the authorized use duration is pre-configured data stored in the Master TEE configured by the mining pool server;

If it is greater, the mining pool server sends a message to notify the terminal device that it has not been authorized for pooling.
The method according to claim 14, wherein the capacity of the mining pool server is less than the capacity threshold, including:

The authorization amount for pooling in the current authorization period is less than the first threshold; wherein, the authorization period and the first threshold are the pre-configured data saved in the Master TEE configured by the mining pool server.
The method according to claim 14, wherein the authorization information includes an authorization serial number and an authorization code, wherein the authorization serial number is allocated by the Master TEE, and the authorization code is used to configure the terminal device Slave TEE verifies that the pooling authorization is valid,

The mining pool server authorizes the terminal device to enter the pool according to the authorization information generated by the Master TEE, including:

The mining pool server sends the authorization serial number and the authorization code to the terminal device, and stores the authorization serial number in correspondence with authorization related information, where the authorization related information refers to information related to authorized content;

Before the mining pool server sends the hash value of the body part of the block header and the target difficulty value to the terminal device, the method further includes:

The mining pool server queries the corresponding authorization association information according to the authorization serial number carried in the billing request, and determines that the pooling authorization of the terminal device is valid according to the authorization association information.
The method according to claim 16, wherein the mining pool server sending the authorization serial number and authorization code to the terminal device includes:

The Master TEE generates a second key according to a second key generation algorithm, and uses the second key to encrypt the authorization code;

The mining pool server sends the authorization serial number and the encrypted authorization code to the terminal device; wherein, the slave TEE configured in the terminal device can generate the second password using the second key generation algorithm Key and use the second key to decrypt the encrypted authorization code.
The method according to claim 17, wherein the second key generation algorithm is private to the Master TEE and the Slave TEE, and the second key generation algorithm is not implemented at the Master TEE and the Outside the Slave TEE, the second key generated by the second key generation algorithm is used in the Master TEE and is only used to encrypt the authorization code, and is used in the Slave TEE Used and only used to decrypt the encrypted authorization code.
The method according to claim 1 or 2, wherein after the mining pool server sends the accounting right determination information and the signature of the accounting right determination information to the mining node, the The method also includes:

The mining pool server transfers a preset amount of mining pool rewards from the address of the pre-configured mining pool wallet account to the address of the wallet account bound by the Slave TEE configured for the terminal device competing for billing rights.
An accounting method, characterized in that it is applied to a terminal device connected to a blockchain system, the blockchain system includes at least one parallel chain, at least one mining pool is built on the at least one parallel chain, each Each mining pool includes a mining pool server and a mining node located on the parallel chain. The mining node uses a distributed data blockchain to store data. The method includes:

The terminal device sends an accounting request to the mining pool server;

The terminal device receives the hash value of the body part of the block header of the pending accounting block sent by the mining pool server and the target difficulty value of mining on the parallel chain;

The Slave TEE configured in the terminal device determines whether its accumulated unused duration is greater than the cumulative unused minimum duration calculated according to the difficulty target value, and checks if the cumulative unused duration is greater than the cumulative unused minimum duration Signing of the accounting right determination information, wherein the accounting right determination information includes the hash value of the body part of the block header and the address body of the wallet account bound by the Slave TEE;

The terminal device sends the accounting right determination information and the signature of the accounting right determination information to the mining pool server.
The method according to claim 20, wherein the Slave TEE signs the accounting right determination information, including:

The Slave TEE signs the accounting right determination information according to the saved first private key, and the mining pool server and the mining node store a first public key that matches the first private key.
The method according to claim 20, wherein the mining pool includes multiple mining nodes, and different mining nodes are located on different parallel chains;

The terminal device receives the hash value of the main body of the block header of the pending accounting block sent by the mining pool server and the target difficulty value of mining on the parallel chain, including:

The terminal device receives the encrypted hash value of the main body of the block header and the difficulty target value sent by the mining pool server, where the first key used for encryption is a master configured by the mining pool server TEE is generated according to the first key generation algorithm;

Before the Slave TEE signs the accounting right determination information, the method further includes:

The Slave TEE generates the first key based on the mining pool configuration information according to the first key generation algorithm, and uses the first key to decrypt the encrypted hash value of the body part of the block header, where The mining pool configuration information includes the chain identifier of the parallel chain associated with the terminal device, and the accounting right determination information includes the decrypted hash value of the main body of the block header.
The method according to claim 22, wherein the mining pool configuration information further includes the number of times the parallel chain has been expanded and/or a pre-configured mining pool identifier of the mining pool.
The method according to claim 22, wherein the chain identifier of the parallel chain associated with the terminal device is the virtual parallel chain identifier of the slave TEE according to the address of the wallet account bound by the slave TEE, the terminal The parallel chain identification mask of the device and the number of parallel chains included in the blockchain system are calculated and obtained, wherein the virtual parallel chain identification is calculated and obtained according to the slave TEE hardware identification.
The method according to claim 20, wherein before the terminal device sends an accounting request to the mining pool server, the method further comprises:

The terminal device sends a registration request to the mining pool server. The registration request carries registration information, the user’s real-name authentication result, and the real-name authentication agency’s signature of the real-name authentication result with a private key. The registration information includes all The address of the wallet account bound to the Slave TEE; the Master TEE configured by the mining pool server stores a public key that matches the private key of the real-name certification authority;

The real-name authentication result includes an authentication code assigned by the real-name authentication organization, and the authentication code corresponds to the address of the wallet account bound to the Slave TEE, and is used to characterize that the user has passed the real-name authentication of the real-name authentication organization ;

The accounting right determination information also includes the authentication code.
The method according to claim 20, wherein before the terminal device sends an accounting request to the mining pool server, the method further comprises:

The terminal device sends a pooling application to the mining pool server, and obtains the pooling authorization of the mining pool server.
The method according to claim 26, wherein the terminal device obtaining the pool access authorization of the mining pool server includes:

The terminal device receives the authorization serial number and the encrypted authorization code sent by the mining pool server, wherein the authorization serial number is allocated by the Master TEE configured by the mining pool server and the second key used for encryption is allocated by the Master TEE Generated according to the second key generation algorithm;

Before the Slave TEE signs the accounting right determination information, the method further includes:

The Slave TEE generates the second key according to the second key generation algorithm, and decrypts the encrypted authorization code using the second key;

The Slave TEE determines that the authorization to enter the pool is valid according to the decrypted authorization code.
An accounting method, which is applied to a blockchain system, the blockchain system includes at least one parallel chain, at least one mining pool is built on the at least one parallel chain, and each mining pool includes a mining pool A server and a mining node located on the parallel chain. The mining node uses a distributed data blockchain to store data. The method includes:

The mining node sends the hash value of the body part of the block header of the pending accounting block to the mining pool server and the difficulty target value of mining on the parallel chain;

The mining node receives the address body of the wallet account bound by the Slave TEE configured by the terminal device connected to the mining pool server sent by the mining pool server and the signature of the accounting right determination information generated by the Slave TEE, Wherein, the accounting right determination information includes the hash value of the body part of the block header and the address body of the wallet account bound by the Slave TEE;

The mining node generates a signed accounting block that includes the address body of the wallet account and the accounting right determination information, and adds the accounting block to the local blockchain.
The method according to claim 28, wherein the accounting right determination information further includes a cumulative unused lower limit duration and/or an authentication code assigned by a real-name certification authority, wherein the cumulative unused lower limit duration is the The Slave TEE is calculated according to the difficulty target value, and the authentication code corresponds to the address of the wallet account bound to the Slave TEE, and is used to characterize that the user has passed the real-name authentication of the real-name authentication institution. The mining node The generated accounting block further includes the accumulated unused lower limit duration calculated according to the difficulty target value and/or the authentication code.
The method according to claim 28, wherein the signature of the accounting right determination information is generated by the Slave TEE based on the saved first private key, and an address including the wallet account is generated at the mining node Before the subject and the signed accounting block of the accounting right determination information, the method further includes:

The mining node determines that the signature of the accounting right determination information is a true signature according to the stored first public key matching the first private key.
The method according to claim 28, wherein before the mining node generates a signed accounting block containing the address body of the wallet account and the accounting right determination information, the method further comprises :

The mining node queries the address body of the wallet account to obtain the height of the block generated by the terminal device in the last bookkeeping in the blockchain;

The mining node determines the pending accounting block according to the height of the block generated by the last accounting in the blockchain and the height of the pending accounting block in the blockchain The time interval between the generation time of the block and the generation time of the block generated by the previous accounting;

The mining node determines that the time interval is greater than the cooling duration, where the cooling duration is k times the cumulative unused lower duration calculated according to the difficulty target value, and k is a constant greater than 0 and less than 1.
The method according to claim 28, wherein after the mining node adds the accounting block to the local blockchain, the method further comprises:

The mining node sends the height of the accounting block in the blockchain, the address body of the wallet account bound by the Slave TEE configured for the terminal device competing for the accounting right to the mining pool server.
The method of claim 28, further comprising:

The mining node queries and obtains the block generated by the terminal device's last accounting in the blockchain according to the address body of the wallet account of the terminal device saved in the accounting block of the blockchain to be confirmed Height, where the accounting block to be confirmed refers to the accounting block received by the mining node and broadcast by the same-chain mining node;

The mining node determines the to-be-confirmed according to the height of the block generated by the last accounting in the blockchain and the height of the to-be-confirmed accounting block in the blockchain The time interval between the generation time of the accounting block and the generation time of the block generated by the previous accounting;

The mining node judges whether the time interval is greater than the cooling duration, and if it is greater than the cooling duration, the accounting block to be confirmed is approved, wherein the cooling duration is based on the accounting area to be confirmed The cumulative unused lower limit duration calculated by the difficulty target value stored in the block is k times, and k is a constant greater than 0 and less than 1.
A mining pool server, characterized in that the mining pool server includes:

Memory, used to store computer instructions;

Communication interface, used to communicate with terminal equipment and the mining node;

The mining pool server also includes a Master TEE or the Master TEE is connected;

The mining pool server further includes a processor connected to the memory, the communication interface, and the Master TEE, wherein the computer instructions are executed by the processor, and the processor executes as follows in conjunction with the Master TEE The method of any one of claims 1-19.
A terminal device, characterized in that the terminal device includes:

Memory, used to store computer instructions;

Communication interface, used to communicate with the mining pool server;

The terminal device further includes a Slave TEE or a Slave TEE is connected;

The terminal device further includes a processor, which is connected to the memory, the communication interface, and the Slave TEE, wherein the computer instructions are executed by the processor, and the processor executes the rights in combination with the Slave TEE. The method according to any one of claims 21 to 29.
A mining node, characterized in that the mining node includes:

Memory, used to store computer instructions;

Communication interface, used to communicate with the mining pool server;

A processor is connected to the memory and the communication interface, wherein the computer instructions are executed by the processor, and the processor executes the method according to any one of claims 28-33.
A mining pool is characterized by comprising: a mining pool server and a mining node located on a parallel chain of a blockchain system, the mining node adopts a distributed data blockchain to store data, and the blockchain system Including at least one parallel chain;

Wherein, the mining node is used to: send the hash value of the main body of the block header of the pending accounting block to the mining pool server and the difficulty target value of mining on the parallel chain;

The mining pool server is used to: receive and store the hash value of the main part of the block header and the difficulty target value, and after receiving the accounting request sent by the terminal device, send the area to the terminal device The hash value of the main body of the block header and the difficulty target value, so that the Slave TEE configured by the terminal device determines whether its accumulated unused duration is greater than the cumulative unused lower limit duration calculated according to the difficulty target value, and Sign the accounting right determination information when the accumulated unused duration is greater than the cumulative unused lower limit duration, where the accounting right determination information includes the hash value of the body part of the block header and the Slave TEE binding The main body of the address of the designated wallet account; receiving the signature of the accounting right determination information and the accounting right determination information sent by the terminal device, and sending the accounting right determination information and the accounting right determination information Is sent to the mining node;

The mining node is also used to: generate an accounting block that contains the address body of the wallet account and the signature of the accounting right determination information, and add the accounting block to the local blockchain .
The mining pool according to claim 37, wherein the mining pool server is further configured to: before receiving the accounting request sent by the terminal device, receive the pooling application sent by the terminal device, and In the Master TEE configured by the mining pool server, determine whether the capacity of the mining pool server is less than the capacity threshold, and if the capacity of the mining pool server is less than the capacity threshold, generate authorization information to the terminal device according to the Master TEE Perform pooling authorization to inform the terminal device that the accounting request sent to the mining pool server within the authorized usage time period after the authorization start time can be accepted by the mining pool server if the mining pool server has a capacity If it is greater than the capacity threshold, a message is sent to notify the terminal device that it has not been authorized to enter the pool, where the authorized duration is pre-configured data stored in the Master TEE configured by the mining pool server.
The mining pool according to claim 38, wherein the capacity of the mining pool server is less than the capacity threshold, including:

The authorization amount for pooling in the current authorization period is less than the first threshold; wherein, the authorization period and the first threshold are pre-configured data saved in the Master TEE configured by the mining pool server.