Signature verification for a blockchain ledger

A computer-implemented system, comprising:

• one or more computers;
• and
• one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform operations comprising:
• sending, by a client and to a server, signature verification instructions for verifying multiple types of digital signatures, the signature verification instructions comprising third-party parameters, platform parameters, and time service certificate parameters, wherein each signature verification instruction comprises a verification object parameter and a hash value, wherein the verification object parameter comprises a third-party parameter, a platform parameter, or a time service certificate parameter, wherein the verification object parameter indicates a type of a to-be-verified object;
• receiving, by the server and from the client, a signature verification instruction, wherein the server is configured to store data by using a blockchain ledger;
• obtaining, by the server, the to-be-verified object based on the verification object parameter and the hash value, wherein the type of the to-be-verified object comprises a third-party digital signature, a server digital signature, or a time service certificate;
• wherein when the verification object parameter is the third-party parameter, the server determines that the type of the to-be-verified object is the third-party digital signature, and obtaining the to-be-verified object based on the hash value further comprises:
• determining, by the server, a data record or a data block corresponding to the hash value;
• sending the data record or the data block to a third party of the blockchain ledger for digital signing by the third party;
• and
• receiving encrypted data from the third party, wherein the encrypted data is obtained by the third party by digitally signing the data record or the data block;
• wherein when the verification object parameter is the platform parameter, the server determines that the type of the to-be-verified object is the server digital signature, and obtaining the to-be-verified object based on the hash value further comprises:
• determining, by the server, a data record or a data block corresponding to the hash value;
• and
• digitally signing, by the server, the data record or the data block to generate encrypted data that comprises the server digital signature;
• wherein when the verification object parameter is the time service certificate parameter, the server determines that the type of the to-be-verified object is the time service certificate, and obtaining the to-be-verified object based on the hash value further comprises:
• determining, by the server, a block height of a data block in which a data record corresponding to the hash value is located, or determining a block height of a data block corresponding to the hash value;
• and
• obtaining a time service certificate corresponding to the data block, wherein the time service certificate corresponds to a part of the blockchain ledger, wherein the time service certificate comprises a starting data block height, an ending data block height, a trusted timestamp, and a root hash of the part of the blockchain ledger, so as to determine a generation time of the part of the blockchain ledger, and wherein the time service certificate comprises a digital signature of a trusted time service authority;
• sending, by the server and to the client, the to-be-verified object and one or more of the following:
• the encrypted data from the third party, the encrypted data generated by the server, and the time service certificate;
• and
• verifying, by the client, the to-be-verified object to generate a verification result.

A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

• sending, by a client and to a server, signature verification instructions for verifying multiple types of digital signatures, the signature verification instructions comprising third-party parameters, platform parameters, and time service certificate parameters, wherein each signature verification instruction comprises a verification object parameter and a hash value, wherein the verification object parameter comprises a third-party parameter, a platform parameter, or a time service certificate parameter, wherein the verification object parameter indicates a type of a to-be-verified object;
• receiving, by the server and from the client, a signature verification instruction, wherein the server is configured to store data by using a blockchain ledger;
• obtaining, by the server, the to-be-verified object based on the verification object parameter and the hash value, wherein the type of the to-be-verified object comprises a third-party digital signature, a server digital signature, or a time service certificate;
• wherein when the verification object parameter is the third-party parameter, the server determines that the type of the to-be-verified object is the third-party digital signature, and obtaining the to-be-verified object based on the hash value further comprises:
• determining, by the server, a data record or a data block corresponding to the hash value;
• sending the data record or the data block to a third party of the blockchain ledger for digital signing by the third party;
• and
• receiving encrypted data from the third party, wherein the encrypted data is obtained by the third party by digitally signing the data record or the data block;
• wherein when the verification object parameter is the platform parameter, the server determines that the type of the to-be-verified object is the server digital signature, and obtaining the to-be-verified object based on the hash value further comprises:
• determining, by the server, a data record or a data block corresponding to the hash value;
• and
• digitally signing, by the server, the data record or the data block to generate encrypted data that comprises the server digital signature;
• wherein when the verification object parameter is the time service certificate parameter, the server determines that the type of the to-be-verified object is the time service certificate, and obtaining the to-be-verified object based on the hash value further comprises:
• determining, by the server, a block height of a data block in which a data record corresponding to the hash value is located, or determining a block height of a data block corresponding to the hash value;
• and
• obtaining a time service certificate corresponding to the data block, wherein the time service certificate corresponds to a part of the blockchain ledger, wherein the time service certificate comprises a starting data block height, an ending data block height, a trusted timestamp, and a root hash of the part of the blockchain ledger, so as to determine a generation time of the part of the blockchain ledger, and wherein the time service certificate comprises a digital signature of a trusted time service authority;
• sending, by the server and to the client, the to-be-verified object and one or more of the following:
• the encrypted data from the third party, the encrypted data generated by the server, and the time service certificate;
• and
• verifying, by the client, the to-be-verified object to generate a verification result.