Tampering verification system and method for financial institution certificates based on blockchain

Patent metadata

Field	Value
Publication number	US-11005666-B2
Application number	US-201816050840-A
Country	US
Kind code	B2
Filing date	Jul 31, 2018
Priority date	Feb 22, 2016
Publication date	May 11, 2021
Grant date	May 11, 2021

Abstract

A tampering verification system and method for financial institution certificates are based on blockchain and verify whether one of the financial institution certificates has been tampered with by comparing the contents of the financial institution certificate at the point of first being generated by a financial institution and at the point of client issue.

First claim

What is claimed is:

1. A system for verifying whether a certificate of a financial institution (FI) is forged or not based on a blockchain, comprising:
an FI terminal configured to (i) transmit a recording request for an authentication of a certificate under a condition that the certificate is generated, (ii) store a specific transaction ID transmitted in response to the recording request, and (iii) transmit the certificate and the specific transaction ID in response to receipt of a download request for the certificate;
an authentication-managing server configured to respond to the recording request transmitted from the FI terminal by executing processes of (I) generating specific node hash information for registration by using the certificate and client identification information, (II) storing the specific node hash information for registration in a certificate database (DB), (III) under a condition that an anchoring condition is met, instructing a hashing engine of the authentication-managing server to retrieve, from the certificate DB, pieces of node hash information included in a specific Merkle tree having the specific node hash information for registration, (IV) generating specific root hash information for registration by using the specific Merkle tree, (V) instructing a transaction-processing engine of the authentication-managing server to generate (v-i) specific transaction information wherein the specific transaction information includes the specific root hash information for registration and (v-ii) the specific transaction ID to be used as a key value for searching for the specific transaction information, (VI) transmitting the specific transaction ID to the FI terminal, and (VII) transmitting, for the authentication, the specific transaction information to blockchain nodes;
the blockchain nodes, wherein the blockchain nodes are configured to store, in the blockchain, the specific transaction information transmitted from the authentication-managing server, wherein the blockchain nodes authenticate a cryptocurrency transfer through verification of transaction information for cryptocurrency transfer in response to the transaction information for cryptocurrency transfer being received, and wherein the blockchain nodes are also configured to store the transaction information for cryptocurrency transfer by referring to a result of authenticating the cryptocurrency transfer; and
a client device configured to transmit the download request to the FI terminal, and to transmit the certificate and the specific transaction ID, received from the FI terminal in response to the download request, to the authentication-managing server at a time of a verification request for verifying whether the certificate is forged or not;
wherein the authentication-managing server is further configured to perform (VIII) a pair-wise match of node hash information generated from a hash of the transmitted certificate, the transmitted specific transaction ID, and the transmitted client identification information with previous node hash information registered in the blockchain nodes, (IX) generating verification-related information which represents whether the node hash information generated from the hash is identical to the previous node hash information, and (X) allowing the verification-related information to be transmitted to the client device.

2. The system of claim 1 , wherein the anchoring condition includes at least one of (i) a numeric condition of determining whether the specific Merkle tree includes a predetermined quantity of said pieces of node hash information, the predetermined quantity being expressed as a predetermined cardinal number, and (ii) a temporal condition of determining whether a predetermined amount of time has elapsed since a last anchoring condition was met.

3. The system of claim 1 , wherein, under a condition that the anchoring condition is met, the authentication-managing server is configured to retrieve from a verification DB all of previous transaction IDs that have been stored, and transmit each of the previous transaction IDs to the blockchain nodes,
wherein the blockchain nodes are configured to extract pieces of previous root hash information for registration included in pieces of previous transaction information, wherein the pieces of previous transaction information are retrieved from a blockchain ledger by referring to each of the previous transaction IDs transmitted from the authentication-managing server, and wherein the blockchain nodes are configured to transmit the pieces of previous root hash information for registration to the authentication-managing server, and
wherein the authentication-managing server is configured to (i) receive the pieces of previous root hash information for registration transmitted from the blockchain nodes, (ii) instruct the hashing engine of the authentication-managing server to group pieces of previous node hash information for registration into a plurality of sets whose size is determined by the anchoring condition, wherein the pieces of previous node hash information for registration have been stored in the certificate DB, so that the authentication-managing server thereby generates pieces of previous root hash information for comparison by hashing the pieces of previous node hash information for registration included in each of said plurality of sets, (iii) pair each of the pieces of the previous root hash information for registration and each of the pieces of previous root hash information for comparison according to generated sequences of each of the pieces of the previous root hash information for registration and each of the pieces of the previous root hash information for comparison, and (iv) confirm that said each of the pieces of previous root hash information for registration is identical pair-wise to said each of the pieces of previous root hash information for comparison, to thereby complete a verification of whether the certificate stored in the authentication-managing server is forged or not.

4. The system of claim 1 , wherein, at the process of (V), the authentication-managing server is configured to instruct the transaction-processing engine to insert the specific root hash information for registration in an Operation Code RETURN area of the specific transaction information, and wherein the Operation Code RETURN represents that its transaction information is not a monetary transaction related to a cryptocurrency payment.

5. The system of claim 4 , wherein the blockchain nodes, under a condition that the Operation Code RETURN area of specific transaction information that was transmitted from the transaction-processing engine is determined to have the specific root hash information for registration, allow the specific transaction information to be stored in a blockchain ledger.

6. The system of claim 1 , wherein generating the verification-related information includes processes of:
the authentication-managing server, under a condition that the certificate and the specific transaction ID are received, transmitting the specific transaction ID to the blockchain nodes to thereby request a transmission of the specific transaction information;
the blockchain nodes retrieving the specific transaction information from a blockchain ledger by referring to the specific transaction ID, and transmitting the specific transaction information to the authentication-managing server; and
the authentication-managing server (i) instructing the hashing engine of the authentication-managing server to generate specific node hash information for comparison by hashing a data group comprised of the client identification information and the certificate transmitted from the client device, (ii) comparing (ii-1) the specific node hash information for registration included in t

Assignees

• Coinplug Inc

Inventors

• Uhr Joon Sun
• Hong Jay Wu
• Song Joo Han

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• H04L63/12

  Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32) · CPC title

• H04L63/1483

  service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12) · CPC title

• H04L2209/56

  Financial cryptography, e.g. electronic payment or e-cash · CPC title

• G06Q20/38215

  Use of certificates or encrypted proofs of transaction rights · CPC title