WO2020233236A1 - Verification method and device of consumable certificates applied to block chain - Google Patents

Abstract

A verification method and device of consumable certificates applied to a block chain. The method comprises: a verification party obtains a certificate provided by a user and used for verification (201), the certificate recording validated verification records; the verification party obtains a verification registration of the certificate from the block chain (202), the verification registration recording a first Hash value, wherein the first Hash value is generated according to all valid verification records after the certificate is verified last time; the verification party generates a second Hash value according to each validated verification record in the certificate (203); and when confirming that the first Hash value and the second Hash value are consistent, the verification party determines that the certificate can be used for verification (204).

Description

Method and device for verifying consumable certificate applied to blockchain

Cross references to related applications

This application requires the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910427763.7, and the application name is "A method and device for validating a consumable certificate applied to the blockchain" on May 22, 2019. The entire content is incorporated into this application by reference.

Technical field

The embodiments of the present invention relate to the field of Fintech, and in particular, to a method and device for verifying a consumable certificate applied to a blockchain (Blockchain).

Background technique

With the development of computer technology, more and more technologies are applied in the financial field. The traditional financial industry is gradually changing to Finteh. Blockchain technology is no exception, but due to the security of the financial industry , Real-time requirements, but also higher requirements for technology.

Traditional consumable credential solutions require a centralized server, and there are often moral criticisms of "changing rules after issuing coupons". Blockchain is a way for all people to participate in bookkeeping, which has the characteristics of decentralization and trustlessness. The most important thing about blockchain is to solve the problem of intermediary credit. In the past, it was difficult for two people who did not know and trust each other to achieve collaboration, and it was necessary to rely on a third party. For example, payment behavior, any kind of transfer in the past, must have an institution such as a bank or Alipay. However, through blockchain technology, Bitcoin is the first time that human beings can complete mutual trust transfer behavior without any intermediary institutions. This is a major breakthrough in the blockchain, and the blockchain is becoming more and more important. Get people's attention.

In the process of using the blockchain, the distributed verification of consumable vouchers (such as coupons, prescriptions, and tickets) is a hot spot in the blockchain industry. However, there are still many problems in the current verification process that make verification difficult.

Summary of the invention

The present invention provides a method and device for verifying a consumable certificate applied to a blockchain to solve the problem of untrustworthy and low security of the verification request of the certificate in the prior art.

The embodiment of the present invention provides a method for verifying a consumable certificate applied to a blockchain, including:

The verifier obtains the certificate provided by the user for verification; the certificate records each valid verification record;

The verification party obtains the verification registration of the certificate from the blockchain, and the verification registration records the first hash value; the first hash value is the last time the certificate was verified Generated based on all valid verification records;

The verification party generates a second Hash value according to the effective verification records in the certificate;

When the verification party confirms that the first Hash value is consistent with the second Hash value, it determines that the certificate can be used for verification.

In a possible implementation manner, the verification record further includes a verification signature for signing the first Hash value by the verification party last verification;

When the verification party confirms that the first Hash value is consistent with the second Hash value, determining that the voucher can be used for verification includes:

The verification party obtains the verification record of the last verification from the certificate;

The verification party verifies the verification signature according to the verification institution information in the verification record of the previous verification;

When the verification party confirms that the first Hash value is consistent with the second Hash value and the verification of the verification signature is passed, the verification party determines that the certificate can be used for verification.

A possible implementation manner, after the verification party determines that the voucher can be used for verification, the method further includes:

The verification returns a lock request for the certificate to the user; the lock request is used by the user to generate a lock signature and upload the lock signature to the blockchain; the lock signature is used to indicate The blockchain sets the lock state in the verification registration to a locked state and records the lock signature in the verification registration;

The verification party receives a lock success response sent by the user; the lock success response is used to trigger the verification party to perform verification.

In a possible implementation manner, after the verification party receives the lock success response sent by the user, the method further includes:

After the verification party verifies that the lock signature is legal, generate a verification party record corresponding to the verification request;

The verification party sends the verification party record to the user;

The verification party obtains the user-side record returned by the user;

The verification party determines the verification record corresponding to the verification request according to the verification party record and the user record;

The verification party generates a third Hash value according to each verification record in the voucher and the verification record corresponding to the verification request;

The verification party updates the first Hash value in the verification registration of the certificate in the blockchain to the third Hash value.

A possible implementation manner, the method further includes:

The verification party changes the writing status of the certificate to unlocked, and writes the locked signature to the blockchain;

The verification returns a successful response to the user.

In a possible implementation manner, before the verification party updates the first Hash value on the blockchain to the third Hash value, the method further includes:

The verification party queries the writing status of the certificate on the blockchain;

If it is determined that the writing status is unlocked, return a relocking instruction to the user, delete the second verification record in the voucher, and return to the user.

In a possible implementation, before the verification party obtains the verification registration of the certificate from the blockchain, the method further includes:

The verification party obtains the verification request of the certificate sent by the user; the verification request of the certificate includes the attribute signature of the certificate and the number of verifications;

The verification party determines the remaining available times of the voucher according to the voucher;

The verification party verifies whether the verification times of the verification request is less than or equal to the remaining available times of the certificate; the verification party obtains the public key of the certificate issuer from the blockchain, and verifies the Whether the attribute signature of the certificate is legal.

A possible implementation manner, the method further includes:

The verification value sends the verification value of the verification request of the certificate to the user; the verification value is used by the verification party to generate a verification record of the verification request and verify the verification value for the user The verification record generated by the verification party.

The embodiment of the present invention provides a verification device for a consumable certificate applied to a blockchain, including:

The transceiver unit is used to obtain the certificate provided by the user for verification; the certificate records each valid verification record; obtain the verification registration of the certificate from the blockchain, the verification registration A first hash value is recorded in, the first hash value is generated based on all valid verification records after the last verification of the voucher;

The processing unit is configured to generate a second Hash value according to each valid verification record in the voucher; when it is confirmed that the first Hash value is consistent with the second Hash value, it is determined that the voucher can be used for verification pin.

In a possible implementation manner, the verification record further includes a verification signature used by the verification party to sign the first Hash value in the last verification; the processing unit is configured to: Obtain the verification record of the last verification; verify the verification signature according to the verification institution information in the verification record of the last verification; verify the first Hash value and the second Hash When the values are consistent and the verification of the verification signature is passed, it is determined that the certificate can be used for verification.

In a possible implementation manner, the transceiver unit is further configured to: return a lock request for the credential to the user; the lock request is used for the user to generate a lock signature and upload the lock signature to the user. The blockchain; the lock signature is used to instruct the blockchain to set the lock state in the verification registration to the locked state and record the lock signature in the verification registration; receive the user's sending The lock successful response; the lock successful response is used to trigger the verification party to write off.

In a possible implementation manner, the transceiver unit is further configured to: send the verification party record to the user; obtain the user-side record returned by the user;

The processing unit is further configured to: after verifying that the lock signature is legal, generate a verification party record corresponding to the verification request; and determine the verification request corresponding to the verification request based on the verification party record and the user record The verification record; the verification record corresponding to the verification request and each valid verification record in the voucher generates a third Hash value; the verification of the voucher in the blockchain is updated The first Hash value in the registration is the third Hash value.

In a possible implementation manner, the processing unit is further configured to: modify the writing status of the certificate to unlock, and write the lock signature to the blockchain; and return a successful verification response to the user .

In a possible implementation manner, the processing unit is configured to: query the writing status of the voucher on the blockchain; if it is determined that the writing status is unlocked, return an instruction to relock to the user , And after deleting the second verification record in the voucher, return to the user.

In a possible implementation manner, the transceiver unit is configured to: obtain a verification request for the voucher sent by the user; the verification request for the voucher includes the attribute signature of the voucher and the number of verifications;

The processing unit is configured to verify whether the number of times of verification of the verification request is less than or equal to the available times of the certificate; the verification party obtains the public key of the certificate issuer from the blockchain, and verifies After the attribute signature of the certificate is legal, the verification result of the verification request of the certificate is returned.

In a possible implementation manner, the processing unit is configured to: send the verification value of the verification request of the voucher to the user; the verification value is used by the verification party to generate the verification request And verify the verification record generated by the verification party for the user.

An embodiment of the present invention provides a computer storage medium, where the computer-readable storage medium includes a computer program, and when the computer program runs on a computer, the computer executes the method described in any one of the foregoing embodiments.

An embodiment of the present invention provides a computer program product containing instructions, which when the instructions run on a computer, cause the computer to execute the method described in any one of the foregoing embodiments.

The embodiment of the present invention provides a computer device, including:

At least one memory for storing program instructions;

At least one processor is configured to invoke program instructions stored in the memory, and execute the method according to any one of the foregoing embodiments according to the obtained program.

In the embodiment of the present invention, the verification party compares the hash value in the verification registration on the blockchain with the hash value generated after the verification record in the certificate is serialized to verify whether the verification record of the expendable certificate has been tampered with Over. It only needs to be on the chain when it is written off, and no private data is exposed on the blockchain, which improves the efficiency of verification.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings may be obtained from these drawings without creative labor.

Figure 1a is a schematic diagram of a system architecture provided by an embodiment of the present invention;

Figure 1b is a schematic diagram of another system architecture provided by an embodiment of the present invention;

FIG. 2 is a schematic flowchart of a method for expendable credentials provided by an embodiment of the present invention;

3 is a schematic structural diagram of a consumable credential device provided by an embodiment of the present invention;

Figure 4 is a schematic structural diagram of a computer device provided by an embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. . Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

Verifier: This role is used to describe the organization that has the authority to verify the certificate. Other institutions may apply for a verification certificate from the verification party.

Issuer: This role is used to describe an organization that has the authority to generate certificates and issue them to users.

User: This role can obtain the certificate sent by the issuer, and can apply to the verifier for verification of the certificate.

Blockchain: All participants have the ability to read and write to the blockchain. Among them, the participants can be the verification party, issuer, and user who have a blockchain account.

Block: used to record data collections and status results divided according to certain conditions, which are formed after each node reaches a consensus. In the embodiment of the present invention, the data to be recorded is mainly data or user data The history update information after the change. Specifically, blocks can be divided by time. For example, a block is generated every 10 seconds (s), then this block is to record all the data in these 10s, or a block is generated every day, then this The block is to record all the data during the day; or, the block can also be divided according to the number of received data or history update information, for example, after receiving a specified number of data or history update information, a Block, then this block is used to record the specified amount of data update information that has been received. Of course, the embodiment of the present invention does not limit the specific division method of the block. A block includes a block header and a block body. Among them, the block header includes the previous block address (Prev-block), the previous block address can be stored in the block header in the form of the previous block hash code (pre-Hash), and the previous block The direction of the address connects all the blocks in series to form a blockchain. The block body is used to store specific data, such as data in the embodiment of the present invention.

Blockchain (blockchain): or distributed data recording ledger, is a chained data structure in which data storage blocks are sequentially connected in a certain order. The blocks are connected in sequence to form a blockchain.

Node: Refers to the computing equipment that participates in the process of data recording or verification in the blockchain network. For example, computers, mobile phones, mining machines, desktops, or servers that have computing capabilities can all be used as nodes in the blockchain network.

In addition, the term "and/or" in this article is only an association relationship describing associated objects, which means that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, and both A and B exist. There are three cases of B alone. In addition, the character "/" in this text, unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.

In order to facilitate the understanding of the technical solutions of the embodiments of the present invention, the principle of the blockchain is introduced below.

In blockchain technology, any device in the network can be used as a node of the blockchain and can participate in the recording and storage of the blockchain. Based on the consensus mechanism between nodes, the entire block is jointly maintained through competitive computing. chain. Since any node can have a complete copy of the data of the blockchain, any node fails, and the remaining nodes can still work normally, so the reliability of the blockchain-based storage method is high.

In addition, because the blockchain technology center uses many nodes to jointly maintain the entire blockchain, each node can have the same authority, so there is no centralized equipment or management organization. All data information in the blockchain is open and transparent, and the modification of its own data by a single node or even multiple nodes cannot affect the data of other nodes unless it can control more than half of the nodes in the entire blockchain network to modify. However, this method is too difficult, and each block in the blockchain is associated with two blocks before and after. If you want to tamper with the data of a block, you need to tamper with multiple blocks related to it. Data is more difficult, so the data stored based on the blockchain is immutable.

Hash value: An algorithm that generates a hash map value for a certain string, such as sha3.

Consumable certificate: It can be an electronic certificate, the number of times is limited, it will be consumed every time it is written off, and it will become invalid when used up. Common consumable vouchers can be prescriptions, coupons, tickets, etc. Traditional consumable credential solutions require a centralized server, and there are often moral criticisms of "changing rules after issuing coupons". In this regard, the verification party can put the certificate generated Hash value deposit certificate on the blockchain for publicity. Figure 1a exemplarily shows a schematic diagram of a system architecture to which an embodiment of the present invention is applicable. As shown in Figure 1a, the system architecture to which an embodiment of the present invention is applicable includes a user 101, a verification party 102, an issuer 103, and a blockchain Network 104. Among them, the certificate issuer 103 is used to issue consumable certificates to users. Certificate holder (user 101): As the holder, the user can consume the certificate by presenting the certificate to the verifier. The credential verification party can be a role such as a merchant. This role can verify the credentials provided by the user and provide services to the user. User 101 sends a certificate verification request to the verification party; the verification party is connected to the blockchain network and sends the data that needs to be chained to the blockchain network; the user is connected to the blockchain network to verify the response returned by the verification party data. The nodes in the blockchain network can be accounting nodes or ordinary nodes.

Each participating institution, such as the verification party, issuer, and user, uses the agreed asymmetric encryption algorithm, such as ECDSA to generate its own public-private key pair; store the private key in its own private database, and then upload the public key to the chain. As shown in Figure 1b, institution A publishes its public key A to the blockchain, and institution B publishes its public key B to the blockchain. For the verification of existing certificates, the consumable certificate needs to be abstracted into a certificate Token on the blockchain, and then the entire life cycle of the issuance of the certificate and the verification of the certificate are on the chain. However, this approach is very inefficient: merchants may send millions of coupons every day, and their full tokenization will put a huge burden on the blockchain.

Based on the foregoing problems, embodiments of the present invention provide a consumable credential method applied to a blockchain, including:

Step 1. The certificate issuer generates a certificate for the user and sends the certificate to the user.

In a specific embodiment, the check value may be a character string of variable length. A possible implementation is that the format of a consumable voucher can be represented by a json string, and its attribute items can include the following fields, as shown in Table 1:

Key	Value
Issuer	Issuer chain address
Issuance time and validity period	Issuance time and validity period
ID	UUID string
receiver	Recipient's on-chain address
content	Business data determined by the issuer
Maximum available times	Maximum number of times the voucher can be used
signature	Signature generated by the issuer
Write-off record set	A collection of multiple voucher write-off records, the creation time is empty

Table 1

Among them, the business data determined by the issuer itself can be "full 50-25", "-yuan movie", "prescription" and other data, which are not limited here. The signature generated by the issuer may be the original text generated by the issuer based on the attribute information in the certificate, for example, it may be the original text based on other content that does not include the verification record. In the specific implementation process, the issuer can use its private key to serialize all the attribute items of the certificate to generate a signature. The verification agency or user can verify the signature value through the public key published by the issuer on the blockchain. The recipient can be the user, that is, after the issuer has generated the voucher, the voucher is sent to the user, or it can be sent to the user through a third party, which is not limited here.

In a possible implementation, the write-off record set can be another json string nested in the json of the expendable certificate, which is empty when the certificate is created. After the certificate has a verification record, the verification record set may include multiple verification records. The format of each verification record can be serialized, that is, the content of a table is converted into a series according to the content of a table. String format. As shown in Table 2, it includes the following fields:

Key	Value
Write-off time	Write-off time
Write-off agency	Chain address of verification agency
Remaining usage	The remaining number of uses after the verification
Check value	Write off random value
Verify user signature	User-generated signature
Signature of verification agency	Signature generated by verification agency

Table 2

It should be noted that each verification record needs to be signed by the user and the verification agency. This is to ensure that both parties use digital signatures to confirm the legal use of the certificate. The verification user signature may be a signature generated by the user based on the verification record as the original text, and the verification agency signature may be a signature generated by the verification agency using the verification record as the original text. Specifically, the user signature that can be verified may be a signature generated by the user based on his own private key, the verification time, the verification organization, the remaining times, and the verification value of the original text. In a possible implementation manner, the check value is used by the verification party to generate a verification record of the verification request and verify the verification record generated by the verification party for the user. The check value can be a string of unspecified length, which is used as one of the input parameters of the digital signature algorithm. When the user or the verification party verifies the signature corresponding to the verification record, the verification value needs to be provided at the same time. This provides the digital signature with the ability to resist replay attacks, so that the signature can be correctly verified only when the verification value is exchanged between the designated user and the verification party.

Step 2: The user sends a verification request of the voucher to the verification party.

In a specific implementation process, the verification request of the voucher includes the voucher and the number of verifications.

In the specific implementation process, it may include: the verification party verifies whether the number of verifications of the verification request is less than or equal to the remaining available times of the voucher according to the certificate; The number of cancellations and the maximum available number of times in the certificate and the last written verification record, confirm the remaining available times of the certificate, and determine that the verifier obtains the public key of the certificate issuer from the blockchain To verify whether the attribute signature of the certificate is legal.

As shown in FIG. 2, an embodiment of the present invention provides a method for verifying a consumable certificate applied to a blockchain, including:

Step 201: The verifier obtains the certificate provided by the user for verification; the certificate records each valid verification record;

Step 202: The verification party obtains the verification registration of the certificate from the blockchain, and the verification registration records the first hash value; the first hash value is the last verification of the certificate Later generated based on all valid verification records;

In order to prevent users from tampering with the verification record of the certificate or directly deleting its content, the verification record of each certificate needs to be stored on the chain. In a possible implementation, the verification and cancellation registration of the certificate can be established for each certificate. In the specific implementation process, it can be stored through a serialized field. As shown in Table 3, the verification and registration of the voucher includes the first Hash value.

Key	Value
ID	UUID string, same as credential ID
Write-off record Hash	The Hash value of the serialized string of the verification record of the certificate
Hash signature of verification record	The signature generated by the last verification party of the certificate

table 3

In order to enhance the verification effect, in a possible implementation manner, the verification record further includes a verification signature for the verification party that was previously verified to sign the first Hash value. The verification signature may be a signature generated based on the Hash value and the verification value of the verification record generated by the last-level verification party.

Step 203: The verification party generates a second Hash value according to the effective verification records in the certificate;

Step 204: When confirming that the first Hash value is consistent with the second Hash value, the verification party determines that the certificate can be used for verification.

In the embodiment of the present invention, the certificate only needs to be chained when the certificate is verified, and only the latest state of the certificate, the hash value and the signature of the verification record are stored on the chain, which effectively guarantees the efficiency and safety of certificate verification.

The verification party verifies whether the verification record of the certificate has been tampered with. One possible implementation method includes:

The verification party obtains the verification record of the last verification from the certificate;

The verification party verifies the verification signature according to the verification institution information in the verification record of the previous verification;

When the verification party confirms that the first Hash value is consistent with the second Hash value and the verification of the verification signature is passed, the verification party determines that the certificate can be used for verification.

In the specific implementation process, the verification party will compare the Hash in the verification registration on the chain with the hash value generated after the verification record of the certificate is serialized. If the verification record is not empty and the first Hash value is consistent with the second Hash value, then further, obtain the public key of the last verification party from the chain, and use the first Hash value as the original text to verify whether the verification signature is legitimate. If either of the two is illegal, return failure.

Further, the verification party can verify the content of the certificate and the legality of the signature. A possible implementation is to obtain the issuer's public key from the chain according to the address of the certificate issuer, and then use all the attributes of the certificate and the serialized string as the original text to verify whether the signature is legal. If it is not legal, return failure.

Further, in order to further verify the legality of the certificate, the verification party enters according to whether the verification record set in the provided certificate is empty:

If the set of verification records is not empty, for each verification record in the certificate, obtain the verification agency public key and the user public key from the blockchain, and then verify whether the verification agency signature and verification user signature are legal . If any signature in any one of the verification records is illegal, return failure. Otherwise, go to the next step.

If the set of verification records is empty, it is determined that the certificate has not been verified, and there is no verification registration of the certificate on the blockchain. At this time, add a record of the verification and registration of the certificate in the verification and verification on the chain and fill in the ID of the certificate or the ID of the verification and registration generated for the certificate.

In order to avoid the successful consumption of a voucher at multiple merchants at the same time, that is, double spending. In the embodiment of the present invention, a smart contract can be used to perform transactional locks on verification to ensure that neither the holder of the certificate nor the verification party is likely to conduct a double-spending attack.

In order to avoid double spending, a possible implementation method, after the verification party determines that the certificate can be used for verification, further includes:

The verification returns a lock request for the certificate to the user; the lock request is used by the user to generate a lock signature and upload the lock signature to the blockchain; the lock signature is used to indicate The blockchain sets the lock state in the verification registration to a locked state and records the lock signature in the verification registration;

In order to avoid double spending and improve the security of verification, the verification value of the verification request of the credential may be sent to the user while sending the lock request; the verification value may be used by the user according to the verification The value generates a lock signature to uniquely identify this verification, so that the verification party can trigger the verification process after obtaining the lock success response sent by the user.

The verification party receives a lock success response sent by the user; the lock success response is used to trigger the verification party to perform verification.

Specifically, the user uses the Hash and check value in the verification and registration as the original text, and generates the lock signature with his own private key. The user modifies the corresponding entry of the certificate in the verification registration, sets the lock status to Y, and attaches the lock signature.

In combination with the above-mentioned embodiment, the lock status and the lock signature can be stored in the verification registration of the certificate. In the specific implementation process, serialized fields can be used for storage, as shown in Table 4:

Key	Value
ID	UUID string
Write-off record Hash	The Hash value of the serialized string of the verification record of the certificate

Hash signature of verification record	The signature generated by the last verification party of the certificate
Locked state	Y/N
Lock signature	User-generated signature

Table 4

In the specific implementation process, the verification party is in the blockchain to check whether the certificate is being registered in a locked state. If the credential is currently locked, it will also return a failure.

A possible implementation can include:

Step 1: After the verification party verifies that the lock signature is legal, a record of the verification party corresponding to the verification request is generated;

In the specific implementation process, the user informs the verification party that the lock process has been completed and the verification can be started; the verification party finds the attribute item of the corresponding voucher ID from the voucher status table and the verification value generated corresponding to the verification request , Obtain the user's public key from the chain, check whether the certificate has been correctly locked, and whether the signature is legal. If it is not locked or the signature is invalid, it returns a failure.

The verifier generates a record of the verifier based on the verification record set of the certificate. The record of the verifier includes the remaining number of times, the address of the verification institution, the verification time, and the verification value.

Further, the verifier can also write the signature of the verification agency in the verifier record. Specifically, the verification time, the address of the verification agency, the remaining number of times, and the verification value can be used as the original text together with its own private key. Generate a signature and fill it in the "Signature of Verification Agency" item recorded by the verification party.

Step 2: The verification party sends the record of the verification party to the user;

Specifically, the verification party sends the verification record to the user, asking the user to confirm the implementation of the verification party record and sign.

Step 3: The verification party obtains the user record returned by the user;

Specifically, the user obtains the public key of the verification agency from the chain to verify whether the verification agency signature is legal. If it is illegal or if there is an error in the verification content, the verification agency is required to regenerate the verification party record. Otherwise, the user approves the signature of the verification agency and generates a signature with its own private key, and fills it in the "Verification of User Signature" item in the verification record. The original text of the signature can be the same original text as the signature of the verification agency, or a different original text, which is not limited here.

Step 4: The verification party determines the verification record corresponding to the verification request according to the verification party record and the user side record;

The verification party obtains the user's public key from the chain, verifies whether the verification user's signature is legal, and fails if it is not. Otherwise, it means that a complete write-off record has been generated.

Specifically, the verification party updates the verification record set of the certificate, adds a verification record, and fills in the verification party record and the user record. Can include: verification time, verification agency address, remaining times, verification value, verification agency signature, verification user signature. Of course, the update of the set of write-off records can also be updated at the second step, and the reviewer does not need to separately generate the record of the write-off party, and only needs to verify and send the updated certificate to the user.

Step 5. The verification party generates a third Hash value according to the verification records of each verification in the certificate and the verification records corresponding to the verification request;

Step 6. The verification party updates the first Hash value in the verification registration of the certificate in the blockchain to the third Hash value.

In the specific implementation process, the verification party serializes all verification records to generate a Hash, and then writes the Hash into the “value of the entry” of the entry corresponding to the certificate ID in the verification registration on the chain. At the same time, use the Hash value as the original text, use your own private key to generate a signature, and write it into the "Into the verification signature item" of the verification registration corresponding entry.

A possible implementation manner, the method further includes:

The verification party modifies the writing status of the certificate to unlock, and writes the lock signature into the blockchain; the verification party returns a successful verification response to the user.

At this time, the verification party can modify the locked status in the verification registration to N and delete the locked signature. The lock state can also be modified by the user in this step, which is not limited here. The verification response to the user that the verification is successful may also include providing the user with a business service corresponding to the credential.

In a possible implementation manner, before the verification party updates the first Hash value on the blockchain to the third Hash value, the method further includes:

The verification party queries the writing status of the certificate on the blockchain;

If it is determined that the writing status is unlocked, return a relocking instruction to the user, delete the second verification record in the voucher, and return to the user.

If the verification party finds that the lock status is no longer Y, it means that the user may be trying to double-spend the credential. The verification party can immediately terminate the verification process and request the user to enter the credential lock process again.

It should be noted that the verification party can also use the blockchain with permissions to ensure that the unlocked state can only be modified by the verification party, further avoiding the possibility of double spending and improving the security of verification.

In the embodiment of the present invention, all certificates need to be chained when they are verified, and only the latest state of the certificate, the Hash and signature of the verification record are stored on the chain; even if a certificate is used multiple times, only one chain is required Record; the entire verification process only requires a maximum of four blockchain write operations. In addition, the verification process can effectively prevent double-spending attacks by either the user or the verification party, effectively ensuring the efficiency and security of credential verification.

Based on the same inventive concept, as shown in FIG. 3, an embodiment of the present invention provides a verification device for a consumable certificate applied to a blockchain, including:

The transceiving unit 301 is used to obtain a certificate provided by the user for verification; the certificate records each valid verification record; obtains the verification registration of the certificate from the blockchain, and the verification A first hash value is recorded in the registration; the first hash value is generated based on all valid verification records after the last verification of the voucher;

The processing unit 302 is configured to generate a second Hash value according to each valid verification record in the voucher; when it is confirmed that the first Hash value is consistent with the second Hash value, it is determined that the voucher can be used Write off.

In a possible implementation manner, the verification record further includes a verification signature for the verification party that was previously verified to sign the first Hash value; the processing unit 302 is configured to: Obtain the verification record of the last verification; verify the verification signature according to the verification institution information in the verification record of the previous verification; confirm the first Hash value and the second When the Hash value is consistent and the verification of the verification signature is passed, it is determined that the certificate can be used for verification.

In a possible implementation manner, the transceiver unit 301 is further configured to: return a lock request for the credential to the user; the lock request is used for the user to generate a lock signature and upload the lock signature to The blockchain; the lock signature is used to instruct the blockchain to set the lock state in the verification registration to the locked state and record the lock signature in the verification registration; receive the user The sent lock success response; the lock success response is used to trigger the verification party to perform verification.

In a possible implementation manner, the transceiver unit is further configured to: send the verification party record to the user; obtain the user-side record returned by the user;

The processing unit is further configured to: after verifying that the lock signature is legal, generate a verification party record corresponding to the verification request; and determine the verification request corresponding to the verification request based on the verification party record and the user record The verification record; the verification record corresponding to the verification request and each valid verification record in the voucher generates a third Hash value; the verification of the voucher in the blockchain is updated The first Hash value in the registration is the third Hash value.

In a possible implementation manner, the processing unit is further configured to: modify the writing status of the certificate to unlock, and write the lock signature to the blockchain; and return a successful verification response to the user .

In a possible implementation manner, the processing unit is configured to: query the writing status of the voucher on the blockchain; if it is determined that the writing status is unlocked, return an instruction to relock to the user , And after deleting the second verification record in the voucher, return to the user.

In a possible implementation manner, the transceiver unit is configured to: obtain a verification request for the voucher sent by the user; the verification request for the voucher includes the attribute signature of the voucher and the number of verifications;

The processing unit is configured to verify whether the number of times of verification of the verification request is less than or equal to the available times of the certificate; the verification party obtains the public key of the certificate issuer from the blockchain, and verifies After the attribute signature of the certificate is legal, the verification result of the verification request of the certificate is returned.

In a possible implementation manner, the processing unit is configured to: if it is determined that the verification result is passed, send a check value of the verification request of the voucher to the user; the check value is used for all The verification party generates a verification record of the verification request and verifies the verification record generated by the verification party for the user.

Referring to FIG. 4, based on the same technical concept, an embodiment of the present invention also provides a computer device for executing a method of a user or a verification party in any embodiment of the present invention, and may include a memory 1001 and a processor 1002.

The memory 1001 is used to store a computer program executed by the processor 1002. The memory 1001 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required for at least one function, and the like; the data storage area may store data created according to the use of a computer device. The processor 1002 may be a central processing unit (central processing unit, CPU), or a digital processing unit or the like. The embodiment of the present invention does not limit the specific connection medium between the foregoing memory 1001 and the processor 1002. In the embodiment of the present invention, in FIG. 4, the memory 1001 and the processor 1002 are connected through a bus 1003, and the bus 1003 is represented by a thick line in FIG. 4. The connection mode between other components is only for schematic illustration, not Limited. The bus 1003 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used to represent in FIG. 4, but it does not mean that there is only one bus or one type of bus.

The memory 1001 may be a volatile memory (volatile memory), such as a random-access memory (random-access memory, RAM); the memory 1001 may also be a non-volatile memory (non-volatile memory), such as a read-only memory, flash memory Flash memory, hard disk drive (HDD) or solid-state drive (SSD), or memory 1001 can be used to carry or store desired program codes in the form of instructions or data structures and can be used by Any other medium accessed by the computer, but not limited to this. The memory 1001 may be a combination of the above-mentioned memories.

The processor 1002 is configured to execute the block chain-based consumable voucher method provided by the embodiment of the present invention when calling the computer program stored in the memory 1001.

An embodiment of the present invention also provides a computer storage medium that stores computer executable instructions required to execute the foregoing processor, and contains a program used to execute the foregoing processor.

In some possible implementations, all aspects of the blockchain-based consumable credential method provided by the present invention can also be implemented in the form of a program product, which includes program code, when the program product runs on a computer device At the time, the program code is used to make the computer device execute the steps in the block chain-based consumable voucher method provided according to various exemplary implementations of the present invention described above in this specification. For example, the computer device can execute The embodiment of the present invention provides a method for verifying a consumable certificate based on a blockchain.

The program product can use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electric, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

The program product based on the block chain-based consumable credential method provided in the embodiment of the present invention can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can run on a computing device. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, device, or device.

The readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.

The program code contained on the readable medium can be transmitted by any suitable medium, including, but not limited to, wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

The program code used to perform the operations of the present invention can be written in any combination of one or more programming languages. The programming languages include object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural styles. Programming language-such as "C" language or similar programming language. The program code can be executed entirely on the user's computing device, partly on the user's device, executed as an independent software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on. In the case of remote computing devices, the remote computing device can be connected to the user's computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (for example, using Internet services) Provider to connect via the Internet).

It should be noted that although several units or subunits of the device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present invention, the features and functions of two or more units described above may be embodied in one unit. Conversely, the features and functions of a unit described above can be further divided into multiple units to be embodied.

In addition, although the operations of the method of the present invention are described in a specific order in the drawings, this does not require or imply that these operations must be performed in the specific order, or that all the operations shown must be performed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

The present invention is described with reference to flowcharts and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Although the preferred embodiments of the present invention have been described, those skilled in the art can make additional changes and modifications to these embodiments once they learn the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present invention.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. In this way, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims (12)

1. A method for verifying consumable certificates applied to blockchain, which is characterized in that it includes:

   The verifier obtains the certificate provided by the user for verification; the certificate records each valid verification record;

   The verification party obtains the verification registration of the certificate from the blockchain, and the verification registration records the first hash value; the first hash value is the last time the certificate was verified Generated based on all valid verification records;

   The verification party generates a second Hash value according to the effective verification records in the certificate;

   When the verification party confirms that the first Hash value is consistent with the second Hash value, it determines that the certificate can be used for verification.
2. The method according to claim 1, wherein the verification record further includes a verification signature of the first Hash value signed by the verification party last verification;

   When the verification party confirms that the first Hash value is consistent with the second Hash value, determining that the voucher can be used for verification includes:

   The verification party obtains the verification record of the last verification from the certificate;

   The verification party verifies the verification signature according to the verification institution information in the verification record of the previous verification;

   When the verification party confirms that the first Hash value is consistent with the second Hash value and the verification of the verification signature is passed, the verification party determines that the certificate can be used for verification.
3. The method according to claim 1, wherein after the verification party determines that the certificate can be used for verification, the method further comprises:

   The verification returns a lock request for the certificate to the user; the lock request is used by the user to generate a lock signature and upload the lock signature to the blockchain; the lock signature is used to indicate The blockchain sets the lock state in the verification registration to a locked state and records the lock signature in the verification registration;

   The verification party receives a lock success response sent by the user; the lock success response is used to trigger the verification party to perform verification.
4. The method according to claim 1, wherein after the verification party receives the lock success response sent by the user, the method further comprises:

   After the verification party verifies that the lock signature is legal, generate a verification party record corresponding to the verification request;

   The verification party sends the verification party record to the user;

   The verification party obtains the user-side record returned by the user;

   The verification party determines the verification record corresponding to the verification request according to the verification party record and the user record;

   The verification party generates a third Hash value according to each verification record in the voucher and the verification record corresponding to the verification request;

   The verification party updates the first Hash value in the verification registration of the certificate in the blockchain to the third Hash value.
5. The method according to claim 4, wherein the method further comprises:

   The verification party changes the writing status of the certificate to unlocked, and writes the locked signature to the blockchain;

   The verification returns a successful response to the user.
6. The method according to claim 4, wherein before the verification party updates the first Hash value on the blockchain to the third Hash value, the method further comprises:

   The verification party queries the writing status of the certificate on the blockchain;

   If it is determined that the writing status is unlocked, return a relocking instruction to the user, delete the second verification record in the voucher, and return to the user.
7. The method according to claim 1, wherein before the verification party obtains the verification registration of the certificate from the blockchain, the method further comprises:

   The verification party obtains the verification request of the certificate sent by the user; the verification request of the certificate includes the attribute signature of the certificate and the number of verifications;

   The verification party determines the remaining available times of the voucher according to the voucher;

   The verification party verifies whether the number of verification times of the verification request is less than or equal to the remaining available times of the certificate;

   The verification party obtains the public key of the issuer of the certificate from the blockchain, and verifies whether the attribute signature of the certificate is legal.
8. 8. The method of claim 7, wherein the method further comprises:

   The verification value sends the verification value of the verification request of the certificate to the user; the verification value is used by the verification party to generate a verification record of the verification request and verify the verification value for the user The verification record generated by the verification party.
9. A device for verifying consumable certificates applied to blockchain, which is characterized in that it comprises:

   The transceiver unit is used to obtain the certificate provided by the user for verification; the certificate records each valid verification record; obtain the verification registration of the certificate from the blockchain, the verification registration A first hash value is recorded in, the first hash value is generated based on all valid verification records after the last verification of the voucher;

   The processing unit is configured to generate a second Hash value according to each valid verification record in the voucher; when it is confirmed that the first Hash value is consistent with the second Hash value, it is determined that the voucher can be used for verification pin.
10. A computer storage medium, wherein the computer readable storage medium includes a computer program, and when the computer program runs on a computer, the computer is caused to execute the method according to any one of claims 1 to 8.
11. A computer program product containing instructions, characterized in that, when the instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1 to 8.
12. A computer device, characterized in that it comprises:

    At least one memory for storing program instructions;

    At least one processor, configured to call program instructions stored in the memory, and execute the method according to any one of claims 1 to 8 according to the obtained program.

Images