Centralized certificate method based on blockchain pre-set contract

Abstract

The present invention provides a centralized certificate method based on a blockchain pre-set contract, including certificate issuance, certificate verification and certificate status change, wherein the certificate issuance is completed by a CA center, and the certificate verification and certificate status change are completed through a blockchain pre-set contract. The present invention uses different methods for different certificate processes, the issuance process is centralized and automatically completed, the status change is automatically carried out through a smart contract and blockchain consensus, and is transmitted to all nodes, which has the decentralized and trustworthy characteristics of blockchain while ensuring efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of blockchain centralized digital certificates, and in particular to a centralized certificate method based on a preset contract. Background Art

[0002] The traditional centralized certificate method is to establish a chain to verify the certificate information. The certificate verification is traced back to the root certificate through the chain. The certificate chain is composed of sub-certificates issued by the CA, which are used to transmit the certificate public key information and signing information. Although centralized certificates are easy to issue and revoke, there are third-party trusted service providers who have the ability to tamper with certificate-related records, and there is a risk of single point failure of the service.

[0003] In view of this, blockchain decentralized certificates have emerged. However, the issuance of a completely blockchain decentralized certificate requires consensus operations such as consultation and voting of multiple nodes or even all nodes. The issuance of certificates takes a long time, and may even fail to issue certificates because some nodes are slow to participate in consultation and voting.

[0004] The above contents are only used to assist in understanding the technical solution of the present invention and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The purpose of the present invention is to solve the above problems and provide a centralized certificate method based on a preset contract.

[0006] In order to achieve the above object, the technical solution of the present invention is as follows:

[0007] A centralized certificate method based on a blockchain preset contract includes certificate issuance, certificate verification and certificate status change, wherein the certificate issuance is completed by a CA center, and the certificate verification and certificate status change are completed through a blockchain preset contract.

[0008] The certificate issuance process includes the following:

[0009] S11. The CA center generates a root certificate by self-signing, and writes the root certificate public key of the CA center into the configuration file of the 0th block of the chain;

[0010] S12. Before the node is started, the node sends the node information to the CA center, and the CA center signs and generates a node sub-certificate. Then, the node downloads the sub-certificate from the CA center and starts the node.

[0011] Furthermore, the present invention sets a "sub-certificate status record" in the block.

[0012] Furthermore, the certificate verification includes the following process:

[0013] S21. During operation, the node regularly queries the "sub-certificate status record", self-checks to confirm its own status, and runs its own node according to the self-check status;

[0014] S22. If a communication request is received from another node, the root certificate public key is obtained from the configuration file of block 0, and the sub-certificate of the other node is verified to be signed by the CA center;

[0015] S23. Verify the validity period of the other node's sub-certificate;

[0016] S24. Query the "sub-certificate status record" to determine the status of the other party's node sub-certificate.

[0017] Furthermore, the certificate status change includes the following steps:

[0018] S31. Limit the genesis node and only grant the genesis node the authority to trigger the smart contract to change the status of the sub-certificate;

[0019] S32. The genesis node triggers the smart contract of state change;

[0020] S33. The contract is executed, the status record of the corresponding sub-certificate is changed, the change result is fed back, and the execution record and the final status of the sub-certificate are uploaded to the chain.

[0021] In addition, the present invention also provides a centralized certificate system based on a blockchain pre-set contract, including a CA center, wherein the root certificate public key of the CA center is written into the 0th block of the chain.

[0022] Furthermore, the system also includes a genesis node, which is granted authority to trigger a smart contract and change the status of a sub-certificate.

[0023] Furthermore, the system also sets a genesis node information module in the block to specify the genesis node and change the genesis node through a smart contract.

[0024] Furthermore, the system also sets a "sub-certificate status record" module in the block to record the status and change record information of the sub-certificate.

[0025] In addition, the present invention also provides a centralized certificate device based on a blockchain preset contract, including: a memory, a processor, and a centralized certificate program based on a blockchain preset contract stored in the memory and executable on the processor, wherein the centralized certificate program based on a blockchain preset contract is configured with a centralized certificate method based on a blockchain preset contract.

[0026] The present invention also provides a storage medium, on which a centralized certificate program based on a blockchain preset contract is stored. When the centralized certificate program based on a blockchain preset contract is executed, a centralized certificate method based on a blockchain preset contract is implemented.

[0027] By adopting the above technical solution, the present invention uses different methods to handle different certificate processes. The issuance process is centralized and automatically completed. The status change is automatically carried out through smart contracts and blockchain consensus and transmitted to all nodes. While ensuring efficiency, it has the decentralized and trustworthy characteristics of blockchain. Therefore, compared with the existing solutions, the certificate status is traceable and verifiable, there is no single point of failure, and it is more reliable and efficient.

[0028] In addition, each node of the present invention obtains the root certificate public key in the configuration file of the 0th block to verify the sub-certificate. There is no need to obtain the root certificate through the certificate chain, nor to install the root certificate for each machine, which simplifies the certificate verification process and saves resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1 It is a flow chart of certificate verification of the present invention. DETAILED DESCRIPTION

[0030] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not intended to limit the present invention.

[0031] Embodiment 1: A centralized certificate system based on a blockchain pre-set contract, including a CA center.

[0032] The certificate signed by the CA center with its own private key is the root certificate and is trusted by all nodes.

[0033] The root certificate public key of the CA center will form a configuration file with some other chain configuration information and be written into the 0th block of the chain.

[0034] like Figure 1 As shown in the figure, before the node is deployed, the node provides the CA center with node information such as the node unit name, blockchain identity number (chainID), configuration file hash (Hash), node public key, etc. After receiving the node information, the CA center signs it with its own private key to generate the node sub-certificate. Before the node is started, the corresponding node sub-certificate will be downloaded from the CA center to successfully start the node.

[0035] If the certificate is issued on the chain, it is necessary to broadcast consensus, which will seriously affect the efficiency of issuing certificates. Therefore, the node of the present invention directly downloads the sub-certificate from the CA center instead of issuing it through on-chain operations.

[0036] The present invention sets a "sub-certificate status record" module in the block to record the current status of each sub-certificate, such as "valid", "revoke", "freeze", "thaw", etc. Since the issuance of sub-certificates does not go through the chain operation, all sub-certificates, as long as the status information is not queried in the "sub-certificate status record", are defaulted to the status of "valid".

[0037] During operation, the node will self-check every short period of time (such as 1 second) to confirm whether its own node sub-certificate is "revoked". If the node's own sub-certificate has been "revoked" or "frozen", the node will stop running immediately.

[0038] If the node's own sub-certificate status is "valid", the root certificate public key is read from the configuration file, and the signature of the received sub-certificate is verified by the root certificate public key. If the signature verification fails, communication with the other node is refused; if the signature verification passes, it can be indicated that the certificate information is indeed signed by the CA center, and the subsequent steps can be continued.

[0039] Continue to verify the validity period of the sub-certificate signature to ensure that the sub-certificate has not expired; finally, query the "sub-certificate status record" to verify whether the trusted sub-certificate of the other node has been "revoked". If it has been "revoked", refuse to communicate with the other node. If the status of the other sub-certificate is "valid", you can communicate with the other party.

[0040] The present invention also defines a genesis node for changing the status of a sub-certificate. The genesis node is specified by setting a genesis node information module in the block. The initially specified genesis node is specified in the genesis node information module of the 0th block, and can be changed during the operation of the chain through a smart contract. To prevent misoperation or confusion of the sub-certificate status due to multi-node operation, the present invention only grants permission to the genesis node, triggering a smart contract to change the status of the sub-certificate. Through the execution of the smart contract, the sub-certificate status change information is stored in the sub-certificate status record and uploaded to the chain.

[0041] In the existing centralized certificate solution, the generation and status changes of certificates are all determined by centralized services. Although issuance and revocation are convenient, there are third-party trusted service providers who have the ability to tamper with certificate-related records, and there is a risk of single point failure of the service. In addition, the verification of certificates also requires the endorsement of centralized services, which is inefficient.

[0042] Or certificate generation and status changes are all simply performed using blockchain smart contracts, thus solving the single point failure problem of the original solution, but all processes must go through node voting, which is inefficient. This solution uses a preset smart contract, and uses different methods to handle different certificate processes. The issuance process is centralized and automatically completed, and the status change automatically passes the blockchain consensus and is transmitted to all nodes, which ensures efficiency while having the decentralized and trustworthy characteristics of blockchain. Therefore, compared with existing solutions, the certificate status is traceable and verifiable, there is no single point failure, and it is more reliable and efficient.

[0043] It should be noted that the system described above is merely illustrative and does not limit the scope of protection of the present invention. In practical applications, technicians in this field can select part or all of them according to actual needs to achieve the purpose of the invention, and no limitation is made here.

[0044] Embodiment 2: In addition, the embodiment of the present invention also proposes a centralized certificate method based on a blockchain pre-set contract, including certificate issuance, certificate verification and certificate status change.

[0045] The certificate issuance process includes the following:

[0046] S11. The CA center generates a root certificate by self-signing, and writes the root certificate public key of the CA center into the configuration file of the 0th block of the chain;

[0047] S12. Before the node is started, the node sends the node information to the CA center, and the CA center signs and generates a node sub-certificate. Then, the node downloads the sub-certificate from the CA center and starts the node.

[0048] The present invention also sets a "sub-certificate status record" in the block.

[0049] The certificate verification includes the following process:

[0050] S21. During operation, the node regularly queries the "sub-certificate status record", self-checks to confirm its own status, and runs its own node according to the self-check status;

[0051] S22. If a communication request is received from another node, the root certificate public key is obtained from the configuration file of block 0, and the sub-certificate of the other node is verified to be signed by the CA center;

[0052] S23. Verify the validity period of the other node's sub-certificate;

[0053] S24. Query the "sub-certificate status record" to determine the status of the other party's node.

[0054] The certificate status change includes the following steps:

[0055] S31. Limit the genesis node and only grant the genesis node the authority to trigger the smart contract to change the status of the sub-certificate;

[0056] S32. The genesis node triggers the smart contract of state change;

[0057] S33. The contract is executed, the status record of the corresponding sub-certificate is changed, the change result is fed back, and the execution record and the final status of the sub-certificate are uploaded to the chain.

[0058] In addition, this embodiment is only a basic description of the centralized certificate method based on the blockchain pre-set contract of the present invention. For technical details not fully described in this embodiment, please refer to the method provided in any embodiment of the present invention, and will not be repeated here.

[0059] Embodiment 3: Those skilled in the art can clearly understand that the systems and methods of the above embodiments can be implemented by means of software plus a necessary general hardware platform, or by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as a read-only memory (ROM) / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, a computer, a node packaging device, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0060] Therefore, the present invention also provides a centralized certificate device based on a blockchain preset contract, comprising: a memory, a processor, and a centralized certificate program based on a blockchain preset contract stored in the memory and executable on the processor, wherein the centralized certificate program based on a blockchain preset contract is configured with a centralized certificate method based on a blockchain preset contract.

[0061] In addition, the present invention also provides a storage medium, on which a centralized certificate program based on a blockchain preset contract is stored.

[0062] Because, in reality, when deploying equipment or programs, the operation of a program can be to implement all steps, or it can be to implement only one step, and all steps can be implemented through the cooperation of multiple programs.

[0063] Therefore, when the centralized certificate program based on the blockchain preset contract is executed, it realizes all or some processes in the centralized certificate method based on the blockchain preset contract.

[0064] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are included in the patent protection scope of the present invention.

Claims

1. A centralized certificate method based on blockchain pre-set contracts, including certificate issuance, certificate verification and certificate status change, characterized in that: The certificate issuance is completed by the CA center, and the certificate status change is completed through the blockchain preset contract; The certificate issuance process includes the following: S11. The CA center generates a root certificate by self-signing, and writes the root certificate public key of the CA center into the configuration file of the 0th block of the chain; S12. Before the node is started, the node sends the node information to the CA center, and the CA center signs and generates a node sub-certificate. Then, the node downloads the sub-certificate from the CA center and starts the node.

2. The centralized certificate method based on blockchain pre-set contract according to claim 1 is characterized in that: Set "Sub-certificate status record" in the block.

3. The centralized certificate method based on blockchain pre-set contract according to claim 2 is characterized in that: Certificate verification includes the following process: S21. During operation, the node periodically queries the "sub-certificate status record", self-checks to confirm its own status, and runs its own node according to the self-check status; S22. If a communication request is received from another node, the root certificate public key is obtained from the configuration file of block 0, and the sub-certificate of the other node is verified to be signed by the CA center; S23. Verify the validity period of the other node's sub-certificate; S24. Query the "sub-certificate status record" to determine the status of the other node's sub-certificate.

4. The centralized certificate method based on blockchain pre-set contract according to claim 2 is characterized in that: The certificate status change includes the following steps: S31. Limit the genesis node and only grant the genesis node the authority to trigger the smart contract to change the status of the sub-certificate; S32. The genesis node triggers the smart contract of state change; S33. The contract is executed, the status record of the corresponding sub-certificate is changed, the change result is fed back, and the execution record and the final status of the sub-certificate are uploaded to the chain.

5. A centralized certificate system based on blockchain pre-set contracts, characterized by: Including genesis nodes, which are granted permissions to trigger smart contracts and change the status of sub-certificates; The system also sets a genesis node information module in the block to specify the genesis node and change the genesis node through a smart contract; The certificate issuance is completed by the CA center, and the certificate status change is completed through the blockchain preset contract; The root certificate public key of the CA center is written into the 0th block of the blockchain; Before the node is started, the node sends the node information to the CA center, and the CA center signs and generates a node sub-certificate. Then, the node downloads the sub-certificate from the CA center and starts the node.

6. The centralized certificate system based on blockchain pre-set contract according to claim 5 is characterized in that: The system also sets up a "sub-certificate status record" module in the block to record the status and change record information of the sub-certificate.

7. A centralized certificate device based on a blockchain pre-set contract, characterized in that: The invention comprises a memory, a processor and a centralized certificate program based on a blockchain preset contract which is stored in the memory and can be run on the processor. The centralized certificate program based on a blockchain preset contract is configured to implement the centralized certificate method based on a blockchain preset contract as described in any one of claims 1 to 4.

8. A storage medium, characterized in that The storage medium stores a centralized certificate program based on a blockchain preset contract. When the centralized certificate program based on a blockchain preset contract is executed, it implements the centralized certificate method based on a blockchain preset contract as described in any one of claims 1 to 4.

Images