WO2017146333A1 - 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 - Google Patents
블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 Download PDFInfo
- Publication number
- WO2017146333A1 WO2017146333A1 PCT/KR2016/011288 KR2016011288W WO2017146333A1 WO 2017146333 A1 WO2017146333 A1 WO 2017146333A1 KR 2016011288 W KR2016011288 W KR 2016011288W WO 2017146333 A1 WO2017146333 A1 WO 2017146333A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- certificate
- information
- hash
- customer
- transaction
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
- H04L9/3268—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
- G06Q20/38215—Use of certificates or encrypted proofs of transaction rights
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1441—Countermeasures against malicious traffic
- H04L63/1483—Countermeasures against malicious traffic service impersonation, e.g. phishing, pharming or web spoofing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
- H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
- H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3263—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements
- H04L9/3265—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements using certificate chains, trees or paths; Hierarchical trust model
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q2220/00—Business processing using cryptography
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
Definitions
- the present invention provides a non-validated watermark by means of verifying forgery against the contents at the time of initial generation of the certificate provided to the customer at the financial institution and the contents issued at the request of the customer in the future. Regardless of whether the forgery of the certificate issued by the financial institution can be verified accurately, it also significantly reduces the cost when registering the customer's certificate based on the blockchain, and registers the customer certificate based on the blockchain.
- the system administrator bundles and compresses the transaction information by the preset value and registers the compressed certificate information of the customer. This minimizes network overload and stores it at financial institutions.
- Forgery verification of financial institutions based on the blockchain that can quickly monitor the forgery of customers under control by malicious acts such as hacking by verifying the forgery of managed clients at predetermined intervals. System and method.
- a conventional certificate issuing system includes information receiving means for receiving issuance application certificate information including predetermined customer information and certificate type and use from a terminal, and a predetermined ledger (or Information extracting means for extracting at least one piece of certificate configuration information corresponding to the customer information and issuance application certificate information from a database), and generating an electronic document for generating a certificate electronic document including the certificate configuration information and storing it in an electronic document repository. Means and a certificate issuing means for transmitting and issuing the certificate electronic document stored in the electronic document storage to a certificate destination terminal.
- the customer can receive the certificate in real time when the desired certificate is requested through the receiving terminal even at a remote location without directly visiting the financial institution.
- the conventional certificate issuing system has a problem that can not provide the seal of the person in charge, such as seal, iron stamp or stamp that is a means of checking forgery of the issued certificate.
- a document issuing and authentication system using a conventional watermarking technology is issued by inserting a watermark into a certificate issued online, and the institution or company which has requested the submission of the certificate is applied to the certificate using a watermark extraction algorithm.
- An authentication system based on a watermarking technology is provided to authenticate the integrity and legitimacy of a certificate through extraction of an embedded watermark.
- the document issuing and authentication system using the conventional watermarking technology detects the forgery of the certificate only through the insertion of the watermark inserted in the certificate. If a watermark is inserted into the certificate, it is recognized as a normal certificate that is not forged, and thus there is a problem that a complete forgery detection system cannot be operated.
- the forgery verification system and method for a financial institution-certified document that is based on the conventional blockchain is based on the contents of the first generation of the certificate provided to the customer at the financial institution and when it is issued at the request of the customer in the future.
- the means for verifying forgery and forgery it provides a feature to verify whether a forgery of a certificate issued by a financial institution is accurate regardless of an unvalidated watermark.
- the system and method for forgery verification of financial institution's certification documents based on the conventional blockchain is initially required to store and manage customer's certification information on the blockchain holding server. You have to pay.
- the issuance cost is 0.0001 bitcoin
- 0.0001 bitcoin is a low cost of about 46 won in Korean Won, but it registers the customer's certificate information on the blockchain holding server for storage management. Since it is a cost each time, there is a problem that the registration cost also increases proportionally as the number of certificate information of the customer increases.
- system and method for forgery verification certificate for financial institutions based on the conventional blockchain is more than 100,000 blockchain holding server so that forgery of the customer's certificate information stored and managed in the blockchain holding server is not possible when hacking occurs.
- the propagation of transaction information including the certificate information of the customer is promised by the communication protocol, and when the transaction information occurs, one node (here referred to as a blockchain holding server) is propagated to eight nodes designated. All blockchains equipped with an electronic wallet with a blockchain necessary to perform Bitcoin payments through pyramid propagation are repeatedly propagated to each of the eight designated nodes for each of the eight nodes receiving the transaction information for the Bitcoin payment. It is completed by propagating to the holding server.
- Patent Document 1 Korean Patent Office Publication No. 10-2009-0000740 (published date: January 08, 2009)
- Patent Document 2 Korean Patent Office Publication No. 10-2003-0020675 (published date: March 10, 2003)
- Patent Document 3 Korean Patent Application Publication No. 10-2015-0086457 (Application Date: June 18, 2015)
- the present invention is to solve the problems of the prior art, the object of the present invention is to provide the contents at the time of the first generation of the certificate provided to the customer in the financial institution and when issued at the request of the customer in the future In addition, through the means of verifying forgery and alteration, it is possible to accurately verify whether or not forgery of a certificate issued by a financial institution regardless of an unvalidated watermark, and also when registering a client's certificate based on blockchain. To provide a system and method for forgery verification forgery of financial institutions based on blockchain that drastically reduces costs.
- Another object of the present invention is to compress the transaction information including the customer's certificate information during the blockchain-based customer certificate registration process in the blockchain holding server, the system administrator binds and compresses as much as a predetermined value and then compressed the customer
- the present invention provides a system and method for verifying and forgery forgery of a financial institution based on a blockchain that minimizes traffic overload by minimizing traffic generation through means of registering certificate information.
- a forgery verification system for financial institutions based on the blockchain of the present invention is generated when generating the certificate information for providing the customer, which is a certificate provided to the customer in the financial institution.
- the certificate is processed into the certificate node hash information, and stored in the certificate registration information DB.
- the hash processing engine is operated to correspond to the number of route hash generation sections set in the certificate registration information DB. Extract the certificate certificate node hash information, and process the extracted certificate certificate node hash information into a certificate certificate root hash information having a Merkle tree structure, and operate the transaction processing engine to include the certificate certificate root hash information for registration.
- An authentication management server for transmitting the certificate certificate ID information to the financial institution terminal and transmitting the certificate certificate information for record authentication;
- the electronic wallet with a blockchain that authenticates the bitcoin payment by verifying the transmitted transaction information for the bitcoin payment and records the transaction information for the bitcoin payment according to the authentication is mounted.
- a client terminal for requesting verification of forgery of the forgery certificate information provided by the customer; and the authentication management server is based on the forwarder certificate information for the customer provision, the transaction certificate ID information and the customer identification information. It is determined whether the corresponding certificate information is forged, generates a customer request certificate verification information for guiding whether or not the certificate information for providing the customer is forged according to the determination, and controls it to be transmitted to the customer terminal.
- the authentication management server extracts all certificate authentication transaction ID information accumulated in the certificate forgery monitoring information DB when the certificate node hash information reaches a predetermined route hash generation section, and extracts each extracted certificate certificate information.
- the certificate transaction ID information is transmitted to the blockchain holding server, and the blockchain holding server matches each transmitted certificate transaction ID information with the blockchain provided in the electronic wallet and includes it in each matching certificate transaction information. Extracts the registered certificate certificate root hash information, and transmits each extracted certificate certificate registration route hash information to the authentication management server, and the certificate management server transmits each certificate certificate registration root certificate transmitted. Receive the city information, operate the hash processing engine, and set the number of certificate certificate node hash information accumulated and stored in the certificate registration information database.
- Root hash information of each certificate and each preparation certificate root hash information are prepared in the order of creation, and each registration certificate route hash information and each preparation certificate root solution are compared in the order of generation. Compute the hash value of the time information and check whether the calculated hash values are the same from the first generation order to the last generation order, and forgery or falsification of the certificate information provided by the customer stored and managed by the authentication management server. Performs the function of verifying
- the block chain holding server sends the certificate certificate ID information among the transmitted information. Request to transmit the certificate transaction information to the certificate management server, and transmit the certificate transaction information matching the certificate certificate ID to the blockchain from the electronic wallet of the blockchain holding server to the authentication management server.
- the authentication management server by operating a hash processing engine hashing the customer provided certificate information and customer identification information from the information transmitted from the customer terminal to process the processing certificate certificate hash hash information for preparation, and the blockchain
- the process of verifying whether the forgery of the issuance document is issued by the financial institution using the forgery verification system for the financial institution based on the blockchain of the present invention is provided by the financial institution terminal.
- the authentication management server storing the sent set of provision information for the customer and the identification information of the customer in the certificate registration information DB and hashing the certificate information and customer identification information for the customer provision by operating a hash processing engine.
- the authentication management server by operating a transaction processing engine to generate certificate certificate transaction information including the certificate certificate root hash information for registration and certificate certificate transaction information used as a key value to retrieve the certificate certificate transaction information, Transmitting certificate information transaction information among the generated information to blockchain holding servers;
- At the blockchain holding servers recording the transmitted certificate authentication transaction information on a blockchain to perform record authentication; Transmitting, at the transaction processing engine of the authentication management server, the certificate certificate ID information to the financial institution terminal; Storing and managing, at the financial institution terminal, the transmitted certificate certificate transaction ID information; Requesting, from the customer terminal, the download of the certificate information for providing the customer to the financial institution terminal; Transmitting, at the financial institution terminal, the requested certificate provision information for customer providing and the certificate transaction ID information corresponding to the corresponding client provision certificate information to the client terminal;
- the customer terminal the transmission of the provided customer certificate information and certificate certificate transaction ID information and the customer identification information for identifying the
- the present invention provides a non-validated watermark by means of verifying forgery against the contents at the time of initial generation of the certificate provided to the customer at the financial institution and the contents issued at the request of the customer in the future. Regardless of whether the forgery of the certificate issued by the financial institution can be verified accurately, it also has the effect of dramatically reducing the cost when registering the certificate of the customer based on the blockchain.
- the present invention after registering the transaction information including the certificate information of the customer in the blockchain-based customer certificate registration process to the blockchain holding server, the system administrator binds and compresses as much as a predetermined value and then the compressed customer's By minimizing the generation of traffic through the means for registering the certificate information, there is also an effect to minimize network overload.
- the present invention has the effect that can quickly monitor the forgery of the customer's certificate by a malicious act such as hacking by verifying whether the forgery of the customer is stored and managed by the financial institution at a predetermined cycle.
- FIG. 1 is an overall configuration diagram showing a forgery verification system for financial institution-certified documents based on the blockchain of the present invention
- FIG. 2 is a block diagram showing a terminal of a financial institution in the forgery verification system for financial institution-certified documents based on the blockchain of the present invention
- Figure 3 is a block diagram showing the authentication management server of the forgery verification system for financial institutions certified documents based on the blockchain of the present invention
- 4 to 6 is a flow chart showing a process of verifying whether the forgery of the certificate issued by the financial institution using the forgery verification system for financial institutions based on the blockchain of the present invention
- FIG. 7 is a block diagram showing a terminal of a financial institution according to another embodiment of a forgery verification system for financial institution-certified documents based on the blockchain of the present invention
- FIGS. 8 to 10 are flowcharts illustrating a process of verifying whether a forgery of forgery is in accordance with another embodiment of the forgery verification system for financial institutions based on the blockchain of the present invention.
- FIG. 1 is an overall configuration showing a forgery verification system for financial institutions certified documents based on the blockchain of the present invention
- Figure 2 is a financial institution terminal of the forgery verification system for financial institutions based on the blockchain of the present invention
- Figure 3 is a block diagram showing the authentication management server of the forgery verification system for financial institutions-certified documents forgery based on the blockchain of the present invention
- Figures 4 to 6 are based on the blockchain of the present invention.
- This is a flow chart showing the process of verifying whether the forgery of the documents issued by the financial institution is forged using the forgery verification system.
- the forgery verification system for financial institutions based on the blockchain of the present invention is largely financial institution terminal 100, authentication management server 200, blockchain holding server 300 and customer terminal It consists of 400.
- the financial institution terminal 100 is a terminal operated by a bank, a trust company, an insurance company, a securities company, etc., which is an institution that raises funds from deposits and loans them to companies or individuals, or invests in securities, and provides them to customers.
- generating the certificate information for customer provision which is the certificate for providing the certificate
- request recording verification of the generated certificate information for the customer provision storing the certificate transaction ID information transmitted by the record certification request, and providing the certificate for the customer provision
- the download of the request is requested to perform the function of transmitting the request for providing the certificate certificate provided by the customer and the corresponding certificate transaction ID information corresponding thereto.
- the financial institution terminal 100 is stored in the DB unit 110.
- the stored DB unit 110 is a certificate provided by the financial institution to the customer provided by the customer certificate information, the customer certificate information list for providing the customer identification information for identifying the customer DB (111) and
- the transaction identifier list information DB 112 stores the certificate transaction ID information used as a key value for retrieving the certificate certificate information.
- the blockchain holding server 300 is a device forming a bitcoin network that performs bitcoin payment through authentication and recording of the bitcoin payment when the bitcoin payment.
- Bitcoin is a digital currency that can be paid for in kind created by Satoshi Nakamoto in 2009, and has no structure for issuing and managing currency. Instead, Bitcoin's transactions are made through a peer-to-peer network (P2P) based distributed database, which performs transactions based on public key cryptography.
- P2P peer-to-peer network
- Bitcoin having a payment method can be used without information such as a card number or expiration date and CCV number required for credit card payment, and there is an advantage in using a low fee.
- Bitcoin is stored in an electronic wallet, which is a file, and each electronic wallet is given a unique address (public address), and trading of Bitcoin is performed based on the address.
- a bitcoin user subscribes to a bitcoin exchange (eg, www.coinplug.com) and charges KRW corresponding to the won while opening an electronic wallet.
- a bitcoin exchange eg, www.coinplug.com
- the blockchain holding server 300 may be a server operated by the bitcoin exchange side as one member.
- an electronic wallet having a blockchain must be mounted on each blockchain holding server 300, and a bitcoin payment generated in accordance with general bitcoin payment on a blockchain by an electronic wallet of the blockchain holding server 300.
- the bitcoin payment is authenticated by verifying the received transaction information of the bitcoin, and the transaction information for the bitcoin payment is recorded according to the authentication, and the blockchain holding server of the next stage designated ( 300 to propagate transaction information for Bitcoin payment.
- the propagation of the transaction information for Bitcoin payment is promised by the communication protocol, and when the occurrence of the transaction information for Bitcoin payment, one node (here referred to as a blockchain holding server) is propagated to eight nodes designated. All blockchains equipped with an electronic wallet with a blockchain necessary to perform Bitcoin payments through pyramid propagation are repeatedly propagated to each of the eight designated nodes for each of the eight nodes receiving the transaction information for the Bitcoin payment. By propagating to the holding server 300, it is completed.
- the blockchain holding server 300 is equipped with an electronic wallet having a blockchain, a server (or terminal) operated by a miner for mining Bitcoin, or a user terminal for bitcoin payment (for example, PC Or smartphone) can also be made up of one member.
- payments based on an electronic wallet equipped with a blockchain include Litecoin, Dark Coin, Namecoin, and Ceramic Coin. And ripple, etc., which may also be used as a substitute for performing a function such as bitcoin in the forgery verification of a certificate of a financial institution.
- the certificate transaction information including certificate certificate node hash information generated by hashing the certificate information for customer provision and the customer identification information, which is the certificate certificate provided to the customer by the financial institution, can also be recorded.
- the electronic wallet of each blockchain holding server 300 is a general bit. It is handled and propagated as private information rather than coin settlement, and the certificate transaction information is recorded in the OP return area, which is used as an important configuration for determining the prevention of forgery and alteration of digital content.
- OP Code Operaation Code Return
- the information in which the message inserted in the OP return area is recorded is a bitcoin transaction. It plays a role of guiding to recognize that it is used as information to inform that it is arbitrary data value rather than information.
- the certification management server 200 hashes the certificate for providing the customer and the customer identification information identifying the corresponding customer by processing the record certificate request from the financial institution terminal 100 and processes the certificate certificate into the hash certificate information. Accumulated and stored in the certificate registration information DB 211, when the cumulative stored number of certificate node node hash information reaches a predetermined route hash generation section, the hash processing engine 220 is operated to relate to certificate registration. Extract the number corresponding to the predetermined route hash generation section from the information DB 211, and process the extracted certificate certificate node hash information into the certificate certificate root hash information for registration composed of the Merkle tree structure, and the transaction.
- the authentication management server 200 is provided with a DB unit 210 in addition to the hash processing engine 220 and the transaction processing engine 230 mentioned above.
- the DB unit 210 is a storage medium in which information necessary for performing authentication of a customer certificate for authentication is stored, and includes a certificate registration information DB 211 and a certificate forgery monitoring related information DB 212. .
- the certificate registration registration information DB 211 stores a certificate for providing a customer, customer identification information for identifying a corresponding customer, certificate certificate node hash information accumulated and certificate certificate route hash information for registration, and the like.
- the certificate authentication forgery monitoring related information DB 212 stores cumulative certificate transaction information and certificate certificate ID information.
- the transaction processing engine 230 is operated by the authentication management server 200, the OP node (Operation Code RETURN) area that guides the certificate node hash information to be treated as private information rather than transaction settlement of Bitcoin Insert and generate certificate transaction information, and control it to be stored in the certificate forgery monitoring information DB (212), and generates certificate transaction ID information used as a key value for retrieving certificate transaction information, and also
- the certificate certificate forgery monitoring related information is stored in the DB (212), the certificate transaction ID information of the generated information is transmitted to the financial institution terminal 100, the certificate transaction information is block chain holding server 300 for record authentication It performs a function to control the holding server 300.
- the authentication management server 200 may also be equipped with an electronic wallet when performing the function of trading bitcoin.
- the authentication management server 200 does not first transmit to the blockchain holding server 300 for record authentication, and if the certificate transaction information is entered into the electronic wallet held by the authentication management server 200, the authentication management server 200 The electronic wallet reads the certificate transaction information and skips the process of authenticating the bitcoin payment upon recognizing that the information is inserted into the OP return area, and immediately passes the certificate node hash information to the blockchain. The information is recorded and transmitted to the next blockchain holding servers 300 that are known to propagate to all blockchain holding servers 300 in the state of performing recording authentication.
- the block chain holding server 300 transmits the certificate certificate ID information among the transmitted information. Certificate of the certificate information recorded in the other blockchain holding server 300 by matching the certificate ID information directly to the blockchain of the electronic wallet mounted on the authentication management server 200 without having to transmit to The same value as the node hash information value can be obtained.
- the route hash generation section is a section in which the system administrator binds the transaction information including the certificate information of the customer in the blockchain-based customer certificate registration process to the blockchain holding server and binds the preset number by a predetermined number. By transaction processing the certificate information of the customer compressed by the set number, it minimizes the occurrence of traffic, thereby reducing the network overload.
- the number of route hash generation sections may be specified by calculating various cases, such as the number of preset certificate node hash information or the number of certificate certificate node hash information accumulated and stored for a predetermined time.
- the authentication management server 200 determines whether the corresponding certificate information is forgery based on the customer certificate information, the certificate transaction ID information and customer identification information provided from the customer terminal 400 to be described later, and It performs the function of generating the verification information for the customer request certificate that guides whether the forgery certificate information for the customer is forged according to the judgment.
- the authentication management server 200 if the customer certificate providing certificate information and the certificate transaction ID information provided from the customer terminal 400 to be described later, the certificate transaction ID information of the transmitted information to the blockchain holding server ( 300 to request the transmission of the certificate transaction information.
- the blockchain holding server 300 may be operated in advance of the blockchain holding server 300 in advance.
- the electronic wallet of the blockchain holding server 300 transmits the matching certificate transaction information to the authentication management server 200 by matching the certificate transaction ID information to the blockchain.
- the authentication management server 200 operates the hash processing engine 210 and hashes the certificate information for providing the customer and the customer identification information among the information transmitted from the customer terminal 400 to process the certificate certificate node hash information for preparation. And calculating the hash certificate value of the certificate verification verification included in the certificate certificate transaction information transmitted from the blockchain holding server 300 and the prepared certificate node hash information value, respectively. Generate verification information for the customer request certificate.
- the authentication management server 200 verifies whether the forgery of the customer is stored and managed by the financial institution at a predetermined cycle to monitor whether the forgery of the customer is forged by malicious behavior such as hacking. Can be.
- the authentication management server 200 extracts all the certificate transaction ID information accumulated in the certificate forgery monitoring information DB (212) when the certificate node hash information reaches the predetermined route hash generation section, The extracted respective certificate authentication transaction ID information is transmitted to the blockchain holding server 300.
- the blockchain holding server 300 matches each transmitted certificate transaction ID information with the blockchain provided in the electronic wallet, and extracts the certificate certificate root hash information for registration included in each matching certificate transaction information. Then, the extracted each certificate certificate registration root hash information is transmitted to the authentication management server (200).
- the authentication management server 200 receives each transmitted certificate certificate root hash information, and operates the hash processing engine 220 to accumulate and store certificate certificate node hash information stored in the certificate registration information DB 211. The number of times is divided into the number corresponding to the predetermined route hash generation section, hashed for each number corresponding to the predetermined route hash generation section, and processed into the respective certificate certification route hash information.
- Each registration certificate route hash information and each preparation certificate route hash information are bilaterally generated in the order of creation, and each registration certificate certificate hash hash information and the respective contrasts are created in the order of creation.
- the hash value of the certification certificate root hash information is calculated, and whether the calculated hash values are the same from the first generation order to the last generation order is stored and managed by the authentication management server 200. Which verifies whether the forgery of the certificate information for the customer offer.
- the authentication management server 200 if the forgery is caused through the verification to provide the financial institution that the forgery was caused to notify that the forgery occurred in the certificate of the customer has been provided to respond quickly.
- the client terminal 400 requests the financial institution terminal 100 to download the certificate information for customer provision, and the certificate information and certificate transaction for the customer provision transmitted from the financial institution terminal 100 by the download request.
- ID information is relayed to the authentication management server 200 to request verification of forgery of the certificate information for providing the customer, and display the customer request certificate verification information transmitted from the authentication management server 200 so that the customer can view it. It is a terminal member.
- the financial institution official operating the financial institution terminal 100 each time the customer certificate information for customer provision, which is a certificate provided to the customer through the financial institution terminal 100 is generated, the certificate information list for customer provision DB In addition to storing in the 111 and the generated customer certificate information for providing the customer and customer identification information identifying the customer to the authentication management server 200 to request the record authentication of the certificate information for customer provided (S110). .
- the authentication management server 200 stores the sent certificate provision information and customer identification information provided in the certificate registration registration information DB 211 as well as operating the hash processing engine 210 to provide the certificate information for the customer provision. And hashing the customer identification information to process the certificate node hash information, and accumulate and store it in the certificate registration information DB 211 (S120).
- the authentication management server 200 checks whether the cumulative stored certificate node hash information reaches a preset route hash generation section (S130), and keeps checking until it reaches the route hash generation section. When the root hash generation section is reached, two tasks are performed.
- the certificate management server 200 stores the certificate certificate of the customer managed by the financial institution by malicious actions such as hacking.
- the certificate authentication forgery monitoring related information DB (212) is extracted all the certificate transaction ID information accumulated and stored in each, the extracted certificate transaction ID information of each extracted certificate transaction blockchain holding server
- the processor 300 transmits to S300.
- the blockchain holding server 300 matches each transmitted certificate transaction ID information with the blockchain provided in the electronic wallet, and extracts the certificate certificate root hash information for registration included in each matching certificate transaction information. (S132).
- the blockchain holding server 300 transmits each certificate registration root hash information to the authentication management server 200 (S133).
- the authentication management server 200 receives each transmitted certificate certificate root hash information, and operates the hash processing engine 220 to accumulate and store certificate certificate node hash information stored in the certificate registration information DB 211. The number of times is divided into the number corresponding to the predetermined route hash generation section, and each process is hashed for each number corresponding to the predetermined route hash generation section, and processed into the respective certificate certification route hash information (S134). )do.
- the hash processing engine 220 of the authentication management server 200 bilaterally prepares each registration certificate route hash information and each preparation certificate route hash information in the generation order, and in the generation order. Compute the hash value of each registered certificate root hash information and each prepared certificate root hash information and check whether the calculated hash values are the same from the first generation order to the last generation order. By doing so, it verifies whether the forgery of the certificate information for providing the customer that is stored and managed in the authentication management server (200) (S135).
- the authentication management server 200 when the cumulative stored certificate node hash information reaches a predetermined route hash generation section, and additionally operates a hash processing engine 220 to operate the certificate registration information DB (211).
- the number of times corresponding to the predetermined route hash generation section is extracted, and the extracted certificate certificate node hash information is processed into registration certificate certificate root hash information having a Merkle tree structure (S140).
- the authentication management server 200 operates the transaction processing engine 230 to verify certificate transaction information including certificate certificate root hash information for registration and certificate certificate transaction ID used as a key value to retrieve the certificate certificate transaction information. Generates information and transmits the certificate information transaction information among the generated information to the blockchain holding server 300 (S150).
- the blockchain holding server 300 records the transmitted certificate authentication information on the blockchain to perform record authentication (S160).
- the transaction processing engine 230 of the authentication management server 200 transmits the certificate certificate ID information to the financial institution terminal 100 (S170).
- the financial institution terminal 100 stores and manages the transmitted certificate certificate ID information in the certificate forgery monitoring related information DB 212 (S180).
- the customer terminal 400 requests the download of the certificate information for providing the customer to the financial institution terminal 100 (S190).
- the financial institution terminal 100 transmits the requested certificate provision information for the customer provided and the certificate transaction ID information corresponding to the corresponding certificate provision for the customer provided to the customer terminal 400 (S200).
- the customer terminal 400 relays the transmitted customer certificate information and the certificate transaction ID information and the customer identification information identifying the corresponding customer to the authentication management server 200 to relay the customer certificate information forgery or not. Request verification according to (S210).
- the authentication management server 200 determines whether the corresponding certificate information is forgery based on the transmitted certificate information, certificate certificate ID, and customer identification information transmitted, and the certificate information for customer provided according to the determination.
- the customer request certificate verification information for guiding whether the forgery is generated and transmitted to the customer terminal 400 (S220).
- the authentication management server 200 transmits the certificate information and the certificate transaction ID information for providing the customer, the certificate transaction ID information of the transmitted information to the blockchain holding server 300, the certificate transaction information Request transmission of (S221).
- the electronic wallet of the blockchain holding server 300 transmits matching certificate certificate information to the authentication management server 200 by matching the transmitted certificate certificate ID information to the blockchain (S222).
- the authentication management server 200 operates the hash processing engine 210 and hashes the certificate information for providing the customer and the customer identification information among the information transmitted from the customer terminal 400 to process the certificate certificate node hash information for preparation. And calculating the hash certificate value of the certificate certificate verification and the certificate node hash information value for the contrast included in the certificate certificate transaction information transmitted from the blockchain holding server 300, and notifying whether the hash values of both are the same. Complete by generating the customer request verification certificate verification information (S223).
- the customer terminal 400 can be used to properly receive the financial documents by viewing the transmitted customer request certificate verification information (S230) to check whether the forgery.
- the forgery verification system of a financial institution-certified document forgery verification based on the blockchain of the present invention is provided because the confidential information for various customer-provided certificate information issued by the financial institution is transmitted to the authentication management server 200 to check whether the forgery is forged. Is exposed to the risk of spillage.
- the forgery verification system for financial institution-certified documents based on the blockchain of the present invention may provide another embodiment.
- FIG. 7 is a block diagram showing a terminal of a financial institution according to another embodiment of a forgery verification system for financial institution-certified documents based on the blockchain of the present invention
- FIGS. 8 to 10 are based on the blockchain of the present invention.
- the financial institution forgery forgery verification system according to another embodiment of the present invention is a flow chart showing the process of verifying the forgery of forgery.
- the financial institution terminal 100 the authentication management server 200, the blockchain holding server 300 and the customer terminal 400, which is the technical configuration according to the above-mentioned basic embodiment, the same, but the internal configuration and operation relationship There is some difference, there is no difference from the technical configuration according to the above-mentioned basic embodiment, and the same reference numerals of the technical configuration to perform the same operating relationship by using the same reference numerals, the description of the present invention according to another embodiment Will be mentioned clearly.
- the financial institution terminal 100 is equipped with a hash processing engine 120 to perform a forgery process without transmitting the certificate information for providing the customer to the authentication management server 200.
- the financial institution terminal 100 operates the hash processing engine 120 when the financial institution generates the certificate information for providing the customer, which is the certificate provided to the customer, the certificate information for the customer provided and the corresponding customer. Hashing the customer identification information identifying the data processing to the certificate certificate node hash information, requesting the record authentication of the processed certificate certificate node hash information, the certificate certificate transaction ID information transmitted by the record authentication request When the request for downloading of the certificate information for the customer provided is downloaded, the certificate information for the customer provided and the certificate transaction ID information is transmitted, and if the download of the certificate information for the customer provided from the customer terminal 400 is requested Performs the function of transmitting the provided customer certificate information and certificate certificate ID information to the customer terminal (400).
- the customer terminal 400 is equipped with a hash processing engine, and the financial institution terminal 100 provides the certificate information for the customer provided by the financial institution terminal 100 and requests for downloading the certificate information for the customer provided to the financial institution terminal 100.
- the hash processing engine is operated to hash the certificate information provided for the customer and the customer identification information identifying the corresponding customer to process into the certificate certificate node hash information for preparation, and to prepare the processed contrast. It performs the function of transmitting the certificate node hash information and certificate certificate ID information to the authentication management server (200).
- the authentication management server 200 determines whether the corresponding certificate information is forgery based on the prepared certificate certificate node hash information and the certificate transaction ID information transmitted, and the certificate for providing the customer according to the determination The difference is that the control unit to generate the customer request certificate verification information for guiding whether the information is forged or transmitted to the customer terminal (400).
- a forgery verification process of a financial institution-certified document based on the blockchain of the present invention is as follows.
- the hash processing engine 120 is operated to identify the customer certificate information and the customer for identifying the customer.
- the information is hashed and processed into a certificate certificate node hash information, and the processed certificate certificate node hash information is transmitted to the authentication management server 200 to request verification of recording of certificate information for customer provision (S310). .
- the authentication management server 200 accumulates and stores the transmitted certificate certificate hash information in the certificate registration information DB 211 (S320).
- the authentication management server 200 checks whether the cumulative stored certificate node hash information has reached the preset route hash generation section (S330), and continues until it reaches the route hash generation section. When the root hash generation section is reached, two tasks are performed.
- the authentication management server 200 extracts all the certificate transaction ID information accumulated in the certificate forgery monitoring information DB (212) when the certificate node hash information reaches the predetermined route hash generation section, Each extracted certificate certificate ID information is transmitted to the blockchain holding server 300 (S331).
- the blockchain holding server 300 matches each transmitted certificate transaction ID information with the blockchain provided in the electronic wallet, and extracts the certificate certificate root hash information for registration included in each matching certificate transaction information. (S332), and extracts each extracted certificate certificate route hash information to the authentication management server 200 (S333).
- the authentication management server 200 receives each transmitted certificate certificate root hash information, and operates the hash processing engine 220 to accumulate and store certificate certificate node hash information stored in the certificate registration information DB 211. The number of times is divided into the number corresponding to the predetermined route hash generation section, and each process is hashed for each number corresponding to the predetermined route hash generation section, and processed into each certificate certificate route hash information (S334). )do.
- the hash processing engine 220 of the authentication management server 200 bilaterally prepares each registration certificate route hash information and each preparation certificate route hash information in the generation order, and in the generation order. Compute the hash value of each registered certificate root hash information and each prepared certificate root hash information and check whether the calculated hash values are the same from the first generation order to the last generation order. By verifying whether the forgery of the certificate information for customer provided that is stored and managed in the authentication management server (200) (S335).
- the authentication management server 200 operates the hash processing engine 220 in the certificate registration related information DB 211.
- the number of times corresponding to the predetermined route hash generation section is extracted, and the extracted certificate certificate node hash information is processed into registration certificate certificate root hash information having a Merkle tree structure (S340).
- the authentication management server 200 operates the transaction processing engine 230 to verify certificate transaction information including certificate certificate root hash information for registration and certificate certificate transaction IDs used as key values to retrieve the certificate certificate transaction information. Generates information, and transmits the certificate certificate information of the generated information to the blockchain holding server 300 (S350).
- the blockchain holding server 300 records the transmitted certificate authentication transaction information on the blockchain to perform record authentication (S360).
- the transaction processing engine 230 of the authentication management server 200 transmits the certificate certificate ID information to the financial institution terminal 100 (S370).
- the financial institution terminal 100 stores and manages the transmitted certificate certificate ID information (S380).
- the customer terminal 400 requests the download of the certificate information for providing the customer to the financial institution terminal 100 (S390).
- the financial institution terminal 100 transmits the certificate request ID information corresponding to the download request provided by the customer and the certificate certificate ID information corresponding to the customer certificate information provided to the customer terminal 400 (S400).
- the customer terminal 400 hashes the certificate information for customer provision and the customer identification information for identifying the corresponding client among the certificate information for the customer provision and the certificate transaction ID information transmitted by operating the hash processing engine. Process by hash information, and transmit the processed proof certificate node hash information and proof certificate transaction ID information to the certificate management server 200 to verify whether or not forgery of the certificate information for customer provision. Request (S410).
- the authentication management server 200 determines whether the corresponding certificate information is forged based on the prepared certificate certificate node hash information and the certificate transaction ID information transmitted, and forgery of the certificate information for providing the customer according to the determination. Generates the customer request certificate verification information to guide whether or not to transmit to the customer terminal 400 (S420).
- the authentication management server 200 transmits the certificate certificate ID information among the transmitted information to the blockchain holding server 300, thereby verifying the certificate certificate. Request transmission of information (S421).
- the electronic wallet of the blockchain holding server 300 transmits the matching certificate transaction information to the authentication management server 200 by matching the certificate certificate ID information to the blockchain (S422).
- the authentication management server 200 operates the hash processing engine 210, the index hash value for verifying the certificate included in the certificate transaction information transmitted from the blockchain holding server 300, and the certificate certificate node hash information value for contrasting. Are respectively calculated to generate customer request certificate verification information for guiding whether the hash values of both are the same (S423).
- the customer terminal 400 reads the transmitted customer request certificate verification information (S430).
- transaction propagation guide engine 300 blockchain holding server
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Computer Hardware Design (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Storage Device Security (AREA)
Abstract
Description
Claims (24)
- 금융기관에서 고객에게 제공되어지는 제증명서인 고객제공용 제증명서 정보 생성 시 그 생성된 고객제공용 제증명서 정보의 기록 인증을 요청하고, 그 기록 인증 요청에 의해 전송되는 제증명서 트랜잭션 ID정보를 저장하며, 상기 고객제공용 제증명서 정보의 다운로드가 요청되면 상기 고객제공용 제증명서 정보 및 상기 제증명서 트랜잭션 ID정보를 전송하는 금융기관단말(100)과;상기 금융기관단말(100)의 기록 인증 요청에 의해 상기 고객제공용 제증명서 및 해당 고객을 식별하는 고객식별정보를 해싱하여 제증명서 노드해시정보로 가공처리하고, 이를 제증명서 등록관련정보DB(211)에 누적저장하되, 그 누적저장되는 제증명서 노드해시정보의 개수가 기설정된 루트해시 생성구간에 도달되면, 해시처리엔진(220)을 운영하여 상기 제증명서 등록관련정보DB(211)에서 기설정된 루트해시 생성구간에 해당하는 개수만큼 추출하고, 그 추출된 제증명서 노드해시정보들이 머클트리 구조로 이루어진 등록용 제증명서 루트해시정보로 가공처리하며, 트랜잭션처리엔진(230)을 운영하여 상기 등록용 제증명서 루트해시정보를 포함하는 제증명서 트랜잭션정보 및 그 제증명서 트랜잭션정보를 검색하는데 키값으로 이용되는 제증명서 트랜잭션 ID정보를 생성하고, 상기 제증명서 트랜잭션 ID정보는 상기 금융기관단말(100)로 전송하며, 상기 제증명서 트랜잭션정보는 기록인증을 위해 전송하는 인증관리서버(200)와;비트코인 결제용 트랜잭션정보가 전송 시 그 전송된 비트코인 결제용 트랜잭션정보를 검증을 통해 비트코인 결제를 인증하고, 그 인증에 따라 비트코인 결제용 트랜잭션정보가 기록되는 블록체인을 갖는 전자지갑이 탑재된 것으로, 상기 인증관리서버(200)로부터 전송되는 제증명서 트랜잭션정보를 상기 블록체인에 기록하는 블록체인 보유서버(300)들과;상기 금융기관단말(100)로 고객제공용 제증명서 정보의 다운로드를 요청하고, 그 다운로드 요청에 의해 상기 금융기관단말(100)로부터 전송되는 상기 고객제공용 제증명서 정보 및 상기 제증명서 트랜잭션 ID정보를 상기 인증관리서버(200)로 중계전송하여 상기 고객제공용 제증명서 정보의 위변조 여부의 검증을 요청하는 고객단말(400);로 이루어지고,상기 인증관리서버(200)는 상기 전송되는 고객제공용 제증명서 정보, 제증명서 트랜잭션 ID정보 및 고객식별정보를 토대로 해당 제증명서 정보가 위변조 되었는지의 여부를 판단하고, 그 판단에 따른 고객제공용 제증명서 정보의 위변조 여부를 안내하는 고객요청 제증명서 검증정보를 생성하고, 이를 상기 고객단말(400)로 전송되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제1항에 있어서,상기 루트해시 생성구간은 기설정된 제증명서 노드해시정보의 개수이거나 또는 기설정된 시간동안 누적저장되는 제증명서 노드해시정보의 개수인 것을 특징으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제1항에 있어서,상기 인증관리서버(200)는 상기 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달되면 상기 제증명서 위변조 감시관련정보 DB(212)에 누적저장된 제증명서 트랜잭션 ID정보를 모두 추출하고, 그 추출된 각각의 제증명서 트랜잭션 ID정보를 블록체인 보유서버(300)로 전송하며,상기 블록체인 보유서버(300)는 전송된 각각의 제증명서 트랜잭션 ID정보를 전자지갑에 구비된 블록체인과 매칭하여, 매칭되는 각각의 제증명서 트랜잭션정보에 포함된 등록용 제증명서 루트해시정보를 추출하고, 그 추출된 각각의 등록용 제증명서 루트해시정보를 상기 인증관리서버(200)로 전송하며,상기 인증관리서버(200)는 전송된 각각의 등록용 제증명서 루트해시정보를 전송받고, 해시처리엔진(220)을 운영하여 제증명서 등록관련정보DB(211)에 누적저장된 제증명서 노드해시정보의 개수를 기설정된 루트해시 생성구간에 해당하는 개수로 구분하고, 그 구분된 기설정된 루트해시 생성구간에 해당하는 개수마다 해싱하여 각각의 대비용 제증명서 루트해시정보로 가공처리하며, 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보를 생성순번대로 양자대비하고, 생성순번대로 양자대비되는 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보의 해시값을 연산하여 첫 번째 생성순번부터 마지막 생성순번까지 그 연산된 양쪽의 해시값이 동일한지 여부를 확인하여, 상기 인증관리서버(200)에서 저장관리되고 있는 고객제공용 제증명서 정보의 위변조 여부를 검증하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제1항에 있어서,상기 인증관리서버(200)의 트랜잭션처리엔진(230)은 상기 등록용 제증명서 루트해시정보를 상기 제증명서 트랜잭션정보 중 비트코인의 거래 결제가 아닌 사적인 정보로서 취급되도록 안내하는 OP리턴(Operation Code RETURN) 영역에 삽입하여 전송되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제4항에 있어서,상기 각 블록체인 보유서버(300)에 탑재된 전자지갑은, 상기 전송된 제증명서 트랜잭션정보를 판독하여 OP리턴 영역에 정보가 삽입된 것을 인지하면, 비트코인 결제를 인증하는 과정을 생략하고, 바로 상기 블록체인에 기록되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제1항에 있어서,상기 고객요청 제증명서 검증정보의 생성과정은,상기 인증관리서버(200)에서, 상기 고객제공용 제증명서 정보 및 제증명서 트랜잭션 ID정보가 전송되면, 전송된 정보 중 제증명서 트랜잭션 ID정보를 상기 블록체인 보유서버(300)에게 전송하여, 제증명서 트랜잭션정보의 전송을 요청하고,상기 블록체인 보유서버(300)의 전자지갑에서, 상기 제증명서 트랜잭션 ID정보를 블록체인에 매칭하여 매칭되는 제증명서 트랜잭션정보를 상기 인증관리서버(200)로 전송하며,상기 인증관리서버(200)에서, 해시처리엔진(210)을 운영하여 상기 고객단말(400)로부터 전송된 정보 중 고객제공용 제증명서 정보 및 고객식별정보를 해싱하여 대비용 제증명서 노드해시정보로 가공처리하고, 상기 블록체인 보유서버(300)로부터 전송된 제증명서 트랜잭션정보에 포함된 제증명서 검증용 인덱스 해시값과 상기 대비용 제증명서 노드해시정보값을 각각 연산하여, 양쪽의 해시값의 동일여부를 안내하는 고객요청 제증명서 검증정보로 생성되는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 금융기관단말(100)에서, 고객에게 제공되어지는 제증명서인 고객제공용 제증명서 정보 생성 시 그 생성된 고객제공용 제증명서 정보 및 해당 고객을 식별하는 고객식별정보를 인증관리서버(200)로 전송하여 고객제공용 제증명서 정보의 기록 인증을 요청하는 단계(S110)와;상기 인증관리서버(200)에서, 전송된 한 조의 고객제공용 제증명서 정보 및 고객식별정보를 제증명서 등록관련정보 DB(211)에 저장함과 아울러 해시처리엔진(210)을 운영하여 상기 고객제공용 제증명서 정보 및 고객식별정보를 해싱하여 제증명서 노드해시정보로 가공처리하고, 이를 제증명서 등록관련정보DB(211)에 누적저장하는 단계(S120)와;상기 인증관리서버(200)에서, 상기 누적저장되는 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달됐는지 확인하는 단계(S130)와;상기 인증관리서버(200)에서, 상기 누적저장되는 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달되면, 해시처리엔진(220)을 운영하여 상기 제증명서 등록관련정보DB(211)에서 기설정된 루트해시 생성구간에 해당하는 개수만큼 추출하고, 그 추출된 제증명서 노드해시정보들을 머클트리 구조로 이루어진 등록용 제증명서 루트해시정보로 가공처리하는 단계(S140)와;상기 인증관리서버(200)에서, 트랜잭션처리엔진(230)을 운영하여 상기 등록용 제증명서 루트해시정보를 포함하는 제증명서 트랜잭션정보 및 그 제증명서 트랜잭션정보를 검색하는데 키값으로 이용되는 제증명서 트랜잭션 ID정보를 생성하고, 상기 생성된 정보 중 제증명서 트랜잭션정보를 블록체인 보유서버(300)들로 전송하는 단계(S150)와;상기 블록체인 보유서버(300)들에서, 상기 전송되는 제증명서 트랜잭션정보를 블록체인에 기록하여 기록 인증을 수행하는 단계(S160)와;상기 인증관리서버(200)의 트랜잭션처리엔진(230)에서, 상기 제증명서 트랜잭션 ID정보를 상기 금융기관단말(100)로 전송하는 단계(S170)와;상기 금융기관단말(100)에서, 상기 전송되는 제증명서 트랜잭션 ID정보를 저장관리하는 단계(S180)와;고객단말(400)에서, 상기 금융기관단말(100)로 고객제공용 제증명서 정보의 다운로드를 요청하는 단계(S190)와;상기 금융기관단말(100)에서, 그 다운로드 요청된 고객제공용 제증명서 정보 및 해당 고객제공용 제증명서 정보 에 대응되는 제증명서 트랜잭션 ID정보를 고객단말(400)로 전송하는 단계(S200)와;상기 고객단말(400)에서, 상기 전송되는 고객제공용 제증명서 정보 및 제증명서 트랜잭션 ID정보와 해당 고객임을 식별하는 고객식별정보를 상기 인증관리서버(200)로 중계전송하여 상기 고객제공용 제증명서 정보의 위변조 여부에 따른 검증을 요청하는 단계(S210)와;상기 인증관리서버(200)에서, 상기 전송되는 고객제공용 제증명서 정보, 제증명서 트랜잭션 ID정보 및 고객식별정보를 토대로 해당 제증명서 정보가 위변조 되었는지의 여부를 판단하고, 그 판단에 따른 고객제공용 제증명서 정보의 위변조 여부를 안내하는 고객요청 제증명서 검증정보를 생성하여 상기 고객단말(400)로 전송하는 단계(S220)와;상기 고객단말(400)에서, 상기 전송된 고객요청 제증명서 검증정보를 열람하는 단계(S230);로 이루어진 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제7항에 있어서,상기 루트해시 생성구간은 기설정된 제증명서 노드해시정보의 개수이거나 또는 기설정된 시간동안 누적저장되는 제증명서 노드해시정보의 개수인 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제7항에 있어서,상기 인증관리서버(200)에서, 상기 누적저장되는 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달됐는지 확인하는 S130단계에 있어서,상기 인증관리서버(200)에서, 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달된 경우 제증명서 위변조 감시관련정보 DB(212)에 누적저장된 제증명서 트랜잭션 ID정보를 모두 추출하고, 그 추출된 각각의 제증명서 트랜잭션 ID정보를 블록체인 보유서버(300)로 전송하는 단계(S131)와;상기 블록체인 보유서버(300)에서 전송된 각각의 제증명서 트랜잭션 ID정보를 전자지갑에 구비된 블록체인과 매칭하여, 매칭되는 각각의 제증명서 트랜잭션정보에 포함된 등록용 제증명서 루트해시정보를 추출하는 단계(S132)와;상기 블록체인 보유서버(300)에서 각각의 등록용 제증명서 루트해시정보를 상기 인증관리서버(200)로 전송하는 단계(S133)와;상기 인증관리서버(200)에서, 전송된 각각의 등록용 제증명서 루트해시정보를 전송받고, 해시처리엔진(220)을 운영하여 제증명서 등록관련정보DB(211)에 누적저장된 제증명서 노드해시정보의 개수를 기설정된 루트해시 생성구간에 해당하는 개수로 구분하고, 그 구분된 기설정된 루트해시 생성구간에 해당하는 개수마다 해싱하여 각각의 대비용 제증명서 루트해시정보로 가공처리하는 단계(S134)와;상기 인증관리서버(200)의 해시처리엔진(220)에서, 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보를 생성순번대로 양자대비하고, 생성순번대로 양자대비되는 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보의 해시값을 연산하여 첫 번째 생성순번부터 마지막 생성순번까지 그 연산된 양쪽의 해시값이 동일한지 여부를 확인하여, 상기 인증관리서버(200)에서 저장관리되고 있는 고객제공용 제증명서 정보의 위변조 여부를 검증하는 단계(S135);를 포함하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제7항에 있어서,상기 인증관리서버(200)에서, 트랜잭션처리엔진(230)을 운영하여 상기 등록용 제증명서 루트해시정보를 포함하는 제증명서 트랜잭션정보 및 그 제증명서 트랜잭션정보를 검색하는데 키값으로 이용되는 제증명서 트랜잭션 ID정보를 생성하고, 상기 생성된 정보 중 제증명서 트랜잭션정보를 블록체인 보유서버(300)들로 전송하는 S150단계에 있어서,상기 트랜잭션처리엔진(230)은, 상기 등록용 제증명서 루트해시정보를 상기 제증명서 트랜잭션정보 중 비트코인의 거래 결제가 아닌 사적인 정보로서 취급되도록 안내하는 OP리턴(Operation Code RETURN) 영역에 삽입하여 전송되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제10항에 있어서,상기 블록체인 보유서버(300)들에서, 상기 전송되는 제증명서 트랜잭션정보를 블록체인에 기록하여 기록 인증을 수행하는 S160단계에 있어서,상기 각 블록체인 보유서버(300)에 탑재된 전자지갑은, 상기 전송된 제증명서 트랜잭션정보를 판독하여 OP리턴 영역에 정보가 삽입된 것을 인지하면, 비트코인 결제를 인증하는 과정을 생략하고, 바로 상기 블록체인에 기록되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제7항에 있어서,상기 인증관리서버(200)에서, 상기 전송되는 고객제공용 제증명서 정보, 제증명서 트랜잭션 ID정보 및 고객식별정보를 토대로 해당 제증명서 정보가 위변조 되었는지의 여부를 판단하고, 그 판단에 따른 고객제공용 제증명서 정보의 위변조 여부를 안내하는 고객요청 제증명서 검증정보를 생성하여 상기 고객단말(400)로 전송하는 S220단계에 있어서,상기 고객요청 제증명서 검증정보 생성과정은,상기 인증관리서버(200)에서, 상기 고객제공용 제증명서 정보 및 제증명서 트랜잭션 ID정보가 전송되면, 전송된 정보 중 제증명서 트랜잭션 ID정보를 상기 블록체인 보유서버(300)에게 전송하여, 제증명서 트랜잭션정보의 전송을 요청하는 단계(S221)와;상기 블록체인 보유서버(300)의 전자지갑에서 상기 제증명서 트랜잭션 ID정보를 블록체인에 매칭하여 매칭되는 제증명서 트랜잭션정보를 상기 인증관리서버(200)로 전송하는 단계(S222)와;상기 인증관리서버(200)에서, 해시처리엔진(210)을 운영하여 상기 고객단말(400)로부터 전송된 정보 중 고객제공용 제증명서 정보 및 고객식별정보를 해싱하여 대비용 제증명서 노드해시정보로 가공처리하고, 상기 블록체인 보유서버(300)로부터 전송된 제증명서 트랜잭션정보에 포함된 제증명서 검증용 인덱스 해시값과 상기 대비용 제증명서 노드해시정보값을 각각 연산하여, 양쪽의 해시값의 동일여부를 안내하는 고객요청 제증명서 검증정보를 생성하는 단계(S223);로 이루어진 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 금융기관에서, 고객에게 제공되어지는 제증명서인 고객제공용 제증명서 정보가 생성되면, 해시처리엔진(120)을 운영하여 상기 고객제공용 제증명서 정보 및 해당 고객을 식별하는 고객식별정보를 해싱하여 제증명서 노드해시정보로 가공처리하고, 그 가공처리된 제증명서 노드해시정보의 기록 인증을 요청하며, 그 기록 인증 요청에 의해 전송되는 제증명서 트랜잭션 ID정보를 저장하고, 상기 고객제공용 제증명서 정보의 다운로드가 요청되면 상기 고객제공용 제증명서 정보 및 상기 제증명서 트랜잭션 ID정보를 전송하는 금융기관단말(100)과;상기 금융기관단말(100)의 기록 인증 요청에 의해 제증명서 노드해시정보를 제증명서 등록관련정보DB(211)에 누적저장하되, 그 누적저장되는 제증명서 노드해시정보의 개수가 기설정된 루트해시 생성구간에 도달되면, 해시처리엔진(220)을 운영하여 상기 제증명서 등록관련정보DB(211)에서 기설정된 루트해시 생성구간에 해당하는 개수만큼 추출하고, 그 추출된 제증명서 노드해시정보들이 머클트리 구조로 이루어진 등록용 제증명서 루트해시정보로 가공처리하며, 트랜잭션처리엔진(230)을 운영하여 상기 등록용 제증명서 루트해시정보를 포함하는 제증명서 트랜잭션정보 및 그 제증명서 트랜잭션정보를 검색하는데 키값으로 이용되는 제증명서 트랜잭션 ID정보를 생성하고, 상기 제증명서 트랜잭션 ID정보는 상기 금융기관단말(100)로 전송하며, 상기 제증명서 트랜잭션정보는 기록인증을 위해 전송하는 인증관리서버(200)와;비트코인 결제용 트랜잭션정보가 전송 시 그 전송된 비트코인 결제용 트랜잭션정보를 검증을 통해 비트코인 결제를 인증하고, 그 인증에 따라 비트코인 결제용 트랜잭션정보가 기록되는 블록체인을 갖는 전자지갑이 탑재된 것으로, 상기 인증관리서버(200)로부터 전송되는 제증명서 트랜잭션정보를 상기 블록체인에 기록하는 블록체인 보유서버(300)들과;상기 금융기관단말(100)로 고객제공용 제증명서 정보의 다운로드를 요청하여 상기 고객제공용 제증명서 정보 및 상기 제증명서 트랜잭션 ID정보를 전송받고, 해시처리엔진을 운영하여 상기 고객제공용 제증명서 정보와 해당 고객을 식별하는 고객식별정보를 해싱하여 대비용 제증명서 노드해시정보로 가공처리하고, 그 가공처리된 대비용 제증명서 노드해시정보와 상기 제증명서 트랜잭션 ID정보를 상기 인증관리서버(200)로 전송하여 상기 고객제공용 제증명서 정보의 위변조 여부에 따른 검증을 요청하는 고객단말(400);로 이루어지고,상기 인증관리서버(200)는 상기 전송되는 대비용 제증명서 노드해시정보 및 제증명서 트랜잭션 ID정보를 토대로 해당 제증명서 정보가 위변조 되었는지의 여부를 판단하고, 그 판단에 따른 고객제공용 제증명서 정보의 위변조 여부를 안내하는 고객요청 제증명서 검증정보를 생성하여 상기 고객단말(400)로 전송되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제13항에 있어서,상기 루트해시 생성구간은 기설정된 제증명서 노드해시정보의 개수이거나 또는 기설정된 시간동안 누적저장되는 제증명서 노드해시정보의 개수인 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제13항에 있어서,상기 인증관리서버(200)는 상기 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달되면, 제증명서 위변조 감시관련정보 DB(212)에 누적저장된 제증명서 트랜잭션 ID정보를 모두 추출하고, 그 추출된 각각의 제증명서 트랜잭션 ID정보를 블록체인 보유서버(300)로 전송하고,상기 블록체인 보유서버(300)는 전송된 각각의 제증명서 트랜잭션 ID정보를 전자지갑에 구비된 블록체인과 매칭하여, 매칭되는 각각의 제증명서 트랜잭션정보에 포함된 등록용 제증명서 루트해시정보를 상기 인증관리서버(200)로 전송하며,상기 인증관리서버(200)는 전송된 각각의 등록용 제증명서 루트해시정보를 전송받고, 해시처리엔진(220)을 운영하여 제증명서 등록관련정보DB(211)에 누적저장된 제증명서 노드해시정보의 개수를 기설정된 루트해시 생성구간에 해당하는 개수로 구분하고, 그 구분된 기설정된 루트해시 생성구간에 해당하는 개수마다 해싱하여 각각의 대비용 제증명서 루트해시정보로 가공처리하며, 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보를 생성순번대로 양자대비하고, 생성순번대로 양자대비되는 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보의 해시값을 연산하여 첫 번째 생성순번부터 마지막 생성순번까지 그 연산된 양쪽의 해시값이 동일한지 여부를 확인하여, 상기 인증관리서버(200)에서 저장관리되고 있는 고객제공용 제증명서 정보의 위변조 여부를 검증하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제13항에 있어서,상기 인증관리서버(200)의 트랜잭션처리엔진(230)은 상기 등록용 제증명서 루트해시정보를 상기 제증명서 트랜잭션정보 중 비트코인의 거래 결제가 아닌 사적인 정보로서 취급되도록 안내하는 OP리턴(Operation Code RETURN) 영역에 삽입하여 전송되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제16항에 있어서,상기 각 블록체인 보유서버(300)에 탑재된 전자지갑은, 상기 전송된 제증명서 트랜잭션정보를 판독하여 OP리턴 영역에 정보가 삽입된 것을 인지하면, 비트코인 결제를 인증하는 과정을 생략하고, 바로 상기 블록체인에 기록되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 제13항에 있어서,상기 고객요청 제증명서 검증정보 생성과정은,상기 인증관리서버(200)에서, 상기 대비용 제증명서 노드해시정보 및 제증명서 트랜잭션 ID정보가 전송되면, 전송된 정보 중 제증명서 트랜잭션 ID정보를 상기 블록체인 보유서버(300)에게 전송하여, 제증명서 트랜잭션정보의 전송을 요청하고,상기 블록체인 보유서버(300)의 전자지갑에서 상기 제증명서 트랜잭션 ID정보를 블록체인에 매칭하여 매칭되는 제증명서 트랜잭션정보를 상기 인증관리서버(200)로 전송하며,상기 인증관리서버(200)에서, 해시처리엔진(210)을 운영하여 상기 블록체인 보유서버(300)로부터 전송된 제증명서 트랜잭션정보에 포함된 제증명서 검증용 인덱스 해시값과 상기 대비용 제증명서 노드해시정보값을 각각 연산하여, 양쪽의 해시값의 동일여부를 안내하는 고객요청 제증명서 검증정보로 생성되는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템.
- 금융기관단말(100)에서, 고객에게 제공되어지는 제증명서인 고객제공용 제증명서 정보가 생성되면, 해시처리엔진(120)을 운영하여 상기 고객제공용 제증명서 정보 및 해당 고객을 식별하는 고객식별정보를 해싱하여 제증명서 노드해시정보로 가공처리하고, 그 가공처리된 제증명서 노드해시정보를 인증관리서버(200)로 전송하여 고객제공용 제증명서 정보의 기록 인증을 요청하는 단계(S310)와;상기 인증관리서버(200)에서, 전송된 제증명서 노드해시정보를 제증명서 등록관련정보 DB(211)에 누적저장하는 단계(S320)와;상기 인증관리서버(200)에서, 상기 누적저장되는 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달됐는지 확인하는 단계(S330)와;상기 인증관리서버(200)에서, 상기 누적저장되는 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달되면, 해시처리엔진(220)을 운영하여 상기 제증명서 등록관련정보DB(211)에서 기설정된 루트해시 생성구간에 해당하는 개수만큼 추출하고, 그 추출된 제증명서 노드해시정보들을 머클트리 구조로 이루어진 등록용 제증명서 루트해시정보로 가공처리하는 단계(S340)와;상기 인증관리서버(200)에서, 트랜잭션처리엔진(230)을 운영하여 상기 등록용 제증명서 루트해시정보를 포함하는 제증명서 트랜잭션정보 및 그 제증명서 트랜잭션정보를 검색하는데 키값으로 이용되는 제증명서 트랜잭션 ID정보를 생성하고, 상기 생성된 정보 중 제증명서 트랜잭션정보를 블록체인 보유서버(300)들로 전송하는 단계(S350)와;상기 블록체인 보유서버(300)들에서, 상기 전송되는 제증명서 트랜잭션정보를 블록체인에 기록하여 기록 인증을 수행하는 단계(S360)와;상기 인증관리서버(200)의 트랜잭션처리엔진(230)에서, 상기 제증명서 트랜잭션 ID정보를 상기 금융기관단말(100)로 전송하는 단계(S370)와;상기 금융기관단말(100)에서, 상기 전송되는 제증명서 트랜잭션 ID정보를 저장관리하는 단계(S380)와;고객단말(400)에서, 상기 금융기관단말(100)로 고객제공용 제증명서 정보의 다운로드를 요청하는 단계(S390)와;상기 금융기관단말(100)에서, 그 다운로드 요청된 고객제공용 제증명서 정보 및 해당 고객제공용 제증명서 정보 에 대응되는 제증명서 트랜잭션 ID정보를 고객단말(400)로 전송하는 단계(S400)와;상기 고객단말(400)에서, 해시처리엔진을 운영하여 전송된 고객제공용 제증명서 정보 및 제증명서 트랜잭션 ID정보 중 고객제공용 제증명서 정보와 해당 고객을 식별하는 고객식별정보를 해싱하여 대비용 제증명서 노드해시정보로 가공처리하고, 그 가공처리된 대비용 제증명서 노드해시정보와 상기 제증명서 트랜잭션 ID정보를 상기 인증관리서버(200)로 전송하여 상기 고객제공용 제증명서 정보의 위변조 여부에 따른 검증을 요청하는 단계(S410)와;상기 인증관리서버(200)에서, 상기 전송되는 대비용 제증명서 노드해시정보 및 제증명서 트랜잭션 ID정보를 토대로 해당 제증명서 정보가 위변조 되었는지의 여부를 판단하고, 그 판단에 따른 고객제공용 제증명서 정보의 위변조 여부를 안내하는 고객요청 제증명서 검증정보를 생성하여 상기 고객단말(400)로 전송하는 단계(S420)와;상기 고객단말(400)에서, 상기 전송된 고객요청 제증명서 검증정보를 열람하는 단계(S430);로 이루어진 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제19항에 있어서,상기 루트해시 생성구간은 기설정된 제증명서 노드해시정보의 개수이거나 또는 기설정된 시간동안 누적저장되는 제증명서 노드해시정보의 개수인 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제19항에 있어서,상기 인증관리서버(200)에서, 상기 누적저장되는 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달됐는지 확인하는 S330단계에 있어서,상기 인증관리서버(200)에서, 제증명서 노드해시정보가 기설정된 루트해시 생성구간에 도달된 경우 제증명서 위변조 감시관련정보 DB(212)에 누적저장된 제증명서 트랜잭션 ID정보를 모두 추출하고, 그 추출된 각각의 제증명서 트랜잭션 ID정보를 블록체인 보유서버(300)로 전송하는 단계(S331)와;상기 블록체인 보유서버(300)에서 전송된 각각의 제증명서 트랜잭션 ID정보를 전자지갑에 구비된 블록체인과 매칭하여, 매칭되는 각각의 제증명서 트랜잭션정보에 포함된 등록용 제증명서 루트해시정보를 추출하는 단계(S332)와;상기 블록체인 보유서버(300)에서 각각의 등록용 제증명서 루트해시정보를 상기 인증관리서버(200)로 전송하는 단계(S333)와;상기 인증관리서버(200)에서, 전송된 각각의 등록용 제증명서 루트해시정보를 전송받고, 해시처리엔진(220)을 운영하여 제증명서 등록관련정보DB(211)에 누적저장된 제증명서 노드해시정보의 개수를 기설정된 루트해시 생성구간에 해당하는 개수로 구분하고, 그 구분된 기설정된 루트해시 생성구간에 해당하는 개수마다 해싱하여 각각의 대비용 제증명서 루트해시정보로 가공처리하는 단계(S334)와;상기 인증관리서버(200)의 해시처리엔진(220)에서, 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보를 생성순번대로 양자대비하고, 생성순번대로 양자대비되는 각각의 등록용 제증명서 루트해시정보와 각각의 대비용 제증명서 루트해시정보의 해시값을 연산하여 첫 번째 생성순번부터 마지막 생성순번까지 그 연산된 양쪽의 해시값이 동일한지 여부를 확인하여, 상기 인증관리서버(200)에서 저장관리되고 있는 고객제공용 제증명서 정보의 위변조 여부를 검증하는 단계(S335);를 포함하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제19항에 있어서,상기 인증관리서버(200)에서, 트랜잭션처리엔진(230)을 운영하여 상기 등록용 제증명서 루트해시정보를 포함하는 제증명서 트랜잭션정보 및 그 제증명서 트랜잭션정보를 검색하는데 키값으로 이용되는 제증명서 트랜잭션 ID정보를 생성하고, 상기 생성된 정보 중 제증명서 트랜잭션정보를 블록체인 보유서버(300)들로 전송하는 S350단계에 있어서,상기 트랜잭션처리엔진(230)은, 상기 등록용 제증명서 루트해시정보를 상기 제증명서 트랜잭션정보 중 비트코인의 거래 결제가 아닌 사적인 정보로서 취급되도록 안내하는 OP리턴(Operation Code RETURN) 영역에 삽입하여 전송되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제22항에 있어서,상기 블록체인 보유서버(300)들에서, 상기 전송되는 제증명서 트랜잭션정보를 블록체인에 기록하여 기록 인증을 수행하는 S360단계에 있어서,상기 각 블록체인 보유서버(300)에 탑재된 전자지갑은, 상기 전송된 제증명서 트랜잭션정보를 판독하여 OP리턴 영역에 정보가 삽입된 것을 인지하면, 비트코인 결제를 인증하는 과정을 생략하고, 바로 상기 블록체인에 기록되도록 제어하는 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
- 제19항에 있어서,상기 인증관리서버(200)에서, 상기 전송되는 대비용 제증명서 노드해시정보 및 제증명서 트랜잭션 ID정보를 토대로 해당 제증명서 정보가 위변조 되었는지의 여부를 판단하고, 그 판단에 따른 고객제공용 제증명서 정보의 위변조 여부를 안내하는 고객요청 제증명서 검증정보를 생성하여 상기 고객단말(400)로 전송하는 S420단계에 있어서,상기 고객요청 제증명서 검증정보 생성과정은,상기 인증관리서버(200)에서, 상기 대비용 제증명서 노드해시정보 및 제증명서 트랜잭션 ID정보가 전송되면, 전송된 정보 중 제증명서 트랜잭션 ID정보를 상기 블록체인 보유서버(300)에게 전송하여, 제증명서 트랜잭션정보의 전송을 요청하는 단계(S421)와;상기 블록체인 보유서버(300)의 전자지갑에서 상기 제증명서 트랜잭션 ID정보를 블록체인에 매칭하여 매칭되는 제증명서 트랜잭션정보를 상기 인증관리서버(200)로 전송하는 단계(S422)와;상기 인증관리서버(200)에서, 해시처리엔진(210)을 운영하여 상기 블록체인 보유서버(300)로부터 전송된 제증명서 트랜잭션정보에 포함된 제증명서 검증용 인덱스 해시값과 상기 대비용 제증명서 노드해시정보값을 각각 연산하여, 양쪽의 해시값의 동일여부를 안내하는 고객요청 제증명서 검증정보를 생성하는 단계(S423);로 이루어진 것을 특징으로 하는 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증방법.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA3012823A CA3012823A1 (en) | 2016-02-22 | 2016-10-10 | Tampering verification system and method for financial institution certificates, based on blockchain |
CN201680082406.6A CN108885760B (zh) | 2016-02-22 | 2016-10-10 | 基于区块链的金融机构证书的篡改验证***和方法 |
US16/050,840 US11005666B2 (en) | 2016-02-22 | 2018-07-31 | Tampering verification system and method for financial institution certificates based on blockchain |
US17/226,175 US20210226804A1 (en) | 2016-02-22 | 2021-04-09 | Tampering verification system and method for financial institution certificates, based on blockchain |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR10-2016-0020437 | 2016-02-22 | ||
KR1020160020437A KR101637868B1 (ko) | 2016-02-22 | 2016-02-22 | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/050,840 Continuation US11005666B2 (en) | 2016-02-22 | 2018-07-31 | Tampering verification system and method for financial institution certificates based on blockchain |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2017146333A1 true WO2017146333A1 (ko) | 2017-08-31 |
WO2017146333A9 WO2017146333A9 (ko) | 2017-10-19 |
Family
ID=56504642
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/011288 WO2017146333A1 (ko) | 2016-02-22 | 2016-10-10 | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 |
Country Status (5)
Country | Link |
---|---|
US (2) | US11005666B2 (ko) |
KR (1) | KR101637868B1 (ko) |
CN (1) | CN108885760B (ko) |
CA (1) | CA3012823A1 (ko) |
WO (1) | WO2017146333A1 (ko) |
Cited By (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107682328A (zh) * | 2017-09-26 | 2018-02-09 | 武汉斗鱼网络科技有限公司 | 一种数据校验方法及客户端 |
CN108173937A (zh) * | 2017-12-28 | 2018-06-15 | 北京中电普华信息技术有限公司 | 访问控制方法和装置 |
US10091180B1 (en) | 2012-03-20 | 2018-10-02 | United Services Automobile Association (Usaa) | Behavioral profiling method and system to authenticate a user |
CN108648761A (zh) * | 2018-05-10 | 2018-10-12 | 北京泛融科技有限公司 | 一种在音频数字水印中嵌入区块链账本的方法 |
US10164973B1 (en) | 2015-12-02 | 2018-12-25 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
CN109194674A (zh) * | 2018-09-20 | 2019-01-11 | 浪潮电子信息产业股份有限公司 | 一种通信数据的处理方法及装置 |
WO2019144400A1 (en) * | 2018-01-29 | 2019-08-01 | Waysun Technology Development Limited | A system and a method for use in data exchange |
WO2019154736A1 (en) * | 2018-02-09 | 2019-08-15 | Airbus (S.A.S.) | Systems and methods of verifying credentials of aircraft personnel using a blockchain computer system |
US10423938B1 (en) | 2015-11-20 | 2019-09-24 | United Services Automobile Association | Identifying negotiable instrument fraud using distributed ledger systems |
US10454677B1 (en) | 2016-02-24 | 2019-10-22 | United Services Automobile Associate (USAA) | Cryptographic key generation from biometric data |
WO2020014282A1 (en) * | 2018-07-09 | 2020-01-16 | Sandor Richard L | Systems and methods for blockchain based identity verification and transaction processing |
CN110855603A (zh) * | 2018-12-24 | 2020-02-28 | 互联网域名***北京市工程研究中心有限公司 | 一种基于区块链技术的抗DoS攻击防护的方法 |
CN111492389A (zh) * | 2017-10-20 | 2020-08-04 | 慧与发展有限责任合伙企业 | 使用区块链对服务进行认证和支付 |
US10762506B1 (en) | 2017-05-11 | 2020-09-01 | United Services Automobile Association | Token device for distributed ledger based interchange |
CN111695885A (zh) * | 2019-03-14 | 2020-09-22 | 中国科学技术大学 | 基于减小交易输入的数字凭证区块链压缩方法 |
US10805085B1 (en) | 2017-08-24 | 2020-10-13 | United Services Automobile Association (Usaa) | PKI-based user authentication for web services using blockchain |
US10833843B1 (en) | 2015-12-03 | 2020-11-10 | United Services Automobile Association (USAA0 | Managing blockchain access |
US10949856B1 (en) | 2015-11-17 | 2021-03-16 | United Services Automobile Association (Usaa) | Systems and methods for adaptive learning to replicate peak performance of human decision making |
US10979410B1 (en) | 2015-05-04 | 2021-04-13 | United Services Automobile Association (Usaa) | Systems and methods for utilizing cryptology with virtual ledgers in support of transactions and agreements |
US11138590B2 (en) | 2017-12-11 | 2021-10-05 | Titan Seal, Inc. | Apparatus and method for embedding digital certifications within documents |
US11188907B1 (en) | 2015-08-21 | 2021-11-30 | United Services Automobile Association (Usaa) | ACH authorization validation using public blockchains |
US11195177B1 (en) | 2015-08-21 | 2021-12-07 | United Services Automobile Association (Usaa) | Distributed ledger systems for tracking recurring transaction authorizations |
US11361286B1 (en) | 2015-11-20 | 2022-06-14 | United Services Automobile Association (Usaa) | Identifying negotiable instrument fraud using distributed ledger systems |
US11582040B2 (en) | 2017-10-20 | 2023-02-14 | Hewlett Packard Enterprise Development Lp | Permissions from entities to access information |
US11604890B2 (en) | 2017-10-20 | 2023-03-14 | Hewlett Packard Enterprise Development Lp | Accessing information based on privileges |
US11854011B1 (en) | 2016-07-11 | 2023-12-26 | United Services Automobile Association (Usaa) | Identity management framework |
US12032716B2 (en) | 2023-01-24 | 2024-07-09 | Hewlett Packard Enterprise Development Lp | Accessing information based on privileges |
Families Citing this family (60)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101637868B1 (ko) * | 2016-02-22 | 2016-07-08 | 주식회사 코인플러그 | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 |
US11212112B2 (en) * | 2016-07-29 | 2021-12-28 | Nec Corporation | System, data management method, and program |
KR101767534B1 (ko) | 2016-09-12 | 2017-08-14 | 주식회사 코인플러그 | 근거리 무선 통신 기반의 카드를 이용하여 본인 인증 서비스를 제공하는 방법 및 이를 이용한 카드, 인증용 단말, 인증 지원 서버 및 본인 인증 서버 |
US10749684B2 (en) * | 2016-09-30 | 2020-08-18 | Entrust, Inc. | Methods and apparatus for providing blockchain participant identity binding |
KR101841928B1 (ko) * | 2016-11-02 | 2018-05-14 | 주식회사 코인플러그 | 문서를 오프라인으로 발행하며, 발행된 오프라인 문서에 대한 인증을 수행하는 방법 및 이를 이용한 서버 |
KR101841929B1 (ko) | 2016-11-02 | 2018-03-27 | 주식회사 코인플러그 | 머클트리 구조를 사용하여, 문서를 오프라인으로 발행하며 발행된 오프라인 문서에 대한 인증을 수행하는 방법 및 이를 이용한 서버 |
KR102475435B1 (ko) | 2017-01-19 | 2022-12-06 | 주식회사 케이티 | 블록 체인을 이용하여 데이터를 관리하는 장치 및 방법 |
KR102026225B1 (ko) | 2017-01-19 | 2019-09-27 | 주식회사 케이티 | 블록 체인을 이용하여 데이터를 관리하는 장치 및 방법 |
CN107040582B (zh) | 2017-02-17 | 2020-08-14 | 创新先进技术有限公司 | 一种数据处理方法及装置 |
CN113766035B (zh) * | 2017-03-28 | 2023-05-23 | 创新先进技术有限公司 | 一种业务受理及共识的方法及装置 |
CN107220896A (zh) * | 2017-04-23 | 2017-09-29 | 杭州复杂美科技有限公司 | 一种基于区块链技术的应收账款融资 |
CN108959280B (zh) * | 2017-05-17 | 2021-08-06 | ***通信有限公司研究院 | 一种存储虚拟资源关联信息的方法及装置 |
EP3418998A1 (en) * | 2017-06-22 | 2018-12-26 | Nokia Technologies Oy | Road traffic management |
KR101814989B1 (ko) * | 2017-07-06 | 2018-01-05 | 주식회사 케이뱅크은행 | 블록 체인을 이용한 이상 금융 거래 탐지 방법 및 이를 실행하는 서버 |
CN107181765A (zh) * | 2017-07-25 | 2017-09-19 | 光载无限(北京)科技有限公司 | 基于区块链技术的网络数字身份认证方法 |
KR101954268B1 (ko) * | 2017-10-24 | 2019-03-05 | 한국조폐공사 | 블록체인 기반의 문서 관리 방법 및 이를 이용한 문서 관리 서버 |
CN107832626B (zh) * | 2017-11-30 | 2019-09-17 | 中国人民解放军国防科技大学 | 一种面向数据流通的结构化数据确权方法 |
CN109905242A (zh) * | 2017-12-07 | 2019-06-18 | 航天信息股份有限公司 | 数字证书的存储、更新、验证方法及装置 |
CN108111604B (zh) * | 2017-12-21 | 2020-08-14 | 广州广电运通金融电子股份有限公司 | 区块链共识方法、装置和***、标识信息处理方法和装置 |
KR20190079324A (ko) | 2017-12-27 | 2019-07-05 | 에이치닥테크놀로지 주식회사 한국영업소 | 블록체인 시스템을 이용한 데이터베이스의 무결성 강화 방법 및 시스템 |
CN108241970B (zh) * | 2018-01-09 | 2021-05-18 | 重庆金窝窝网络科技有限公司 | 基于区块链的挖矿方法、装置及计算机可读存储介质 |
US20190228386A1 (en) * | 2018-01-19 | 2019-07-25 | Xapo Holdings Limited | Recording evidence of address/account allocations in a distributed ledger |
KR102107438B1 (ko) * | 2018-03-07 | 2020-06-02 | 주식회사 한글과컴퓨터 | 블록체인을 이용한 전자 문서 관리 장치 및 이의 동작 방법 |
KR101946555B1 (ko) * | 2018-05-15 | 2019-05-03 | 한국마필거래소(주) | 블록체인 기반의 유전자 정보 유통 방법 및 시스템 |
KR20190135763A (ko) * | 2018-05-29 | 2019-12-09 | 김태욱 | 블록체인 기반의 지급결제 서비스 방법 및 시스템 |
US10972463B2 (en) | 2018-06-06 | 2021-04-06 | Cisco Technology, Inc. | Blockchain-based NB-IoT devices |
US10505718B1 (en) | 2018-06-08 | 2019-12-10 | Cisco Technology, Inc. | Systems, devices, and techniques for registering user equipment (UE) in wireless networks using a native blockchain platform |
US10673618B2 (en) | 2018-06-08 | 2020-06-02 | Cisco Technology, Inc. | Provisioning network resources in a wireless network using a native blockchain platform |
KR102190236B1 (ko) | 2018-07-31 | 2020-12-11 | 전재균 | 블록체인을 이용한 전자문서의 소유권 이전 및 검증 방법, 그리고 시스템 |
US11335109B2 (en) | 2018-08-28 | 2022-05-17 | Marlabs Incorporated | Computing device for document authentication and a method to operate the same |
EP3627320A1 (en) * | 2018-09-19 | 2020-03-25 | Vocalink Limited | Data processing device, system and method |
CN109347806B (zh) * | 2018-09-20 | 2021-04-27 | 天津大学 | 一种基于主机监控技术的挖矿恶意软件检测***及方法 |
CN111080044A (zh) * | 2018-10-19 | 2020-04-28 | 宝硕财务科技股份有限公司 | 金融记录管理*** |
KR102268700B1 (ko) | 2018-10-29 | 2021-06-24 | 전재균 | 블록체인을 이용한 전자문서의 공증 방법, 그리고 시스템 |
CN114096977A (zh) | 2018-11-02 | 2022-02-25 | 维罗纳控股经济特区公司 | 代币化平台 |
US11334856B2 (en) * | 2018-11-21 | 2022-05-17 | Capital One Services, Llc | Check tampering prevention using blockchain |
KR102137115B1 (ko) * | 2018-12-03 | 2020-07-24 | 주식회사 우리은행 | 증명서 간편 제출 서비스 지원 시스템 및 지원 방법 |
CN109766390A (zh) * | 2019-01-16 | 2019-05-17 | 杭州趣链科技有限公司 | 一种基于区块链的防篡改机构证书*** |
EP3913890B1 (en) * | 2019-02-28 | 2023-04-12 | Advanced New Technologies Co., Ltd. | System and method for blockchain-based authentication |
WO2019144978A2 (en) | 2019-05-20 | 2019-08-01 | Alibaba Group Holding Limited | Identifying copyrighted material using embedded copyright information |
WO2019141297A2 (en) | 2019-05-20 | 2019-07-25 | Alibaba Group Holding Limited | Copyright protection based on hidden copyright information |
CN111183423B (zh) | 2019-05-20 | 2023-10-17 | 创新先进技术有限公司 | 使用嵌入在电子文件中的版权信息识别版权材料 |
SG11202002013SA (en) | 2019-05-20 | 2020-04-29 | Alibaba Group Holding Ltd | Identifying copyrighted material using embedded copyright information |
SG11202002708TA (en) | 2019-05-20 | 2020-04-29 | Alibaba Group Holding Ltd | Identifying copyrighted material using embedded copyright information |
CN110809762A (zh) | 2019-05-20 | 2020-02-18 | 阿里巴巴集团控股有限公司 | 使用嵌入式版权信息识别版权材料 |
SG11202001999UA (en) | 2019-05-20 | 2020-04-29 | Alibaba Group Holding Ltd | Identifying copyrighted material using embedded timestamped copyright information |
SG11202002417PA (en) | 2019-05-20 | 2020-04-29 | Alibaba Group Holding Ltd | Identifying copyrighted material using copyright information embedded in tables |
GB201907349D0 (en) * | 2019-05-24 | 2019-07-10 | Nchain Holdings Ltd | Verification of data fields of blockchain transactions |
CN110493174A (zh) * | 2019-07-01 | 2019-11-22 | 黄智康 | 使用区块链的通用电子文件查证***及其方法 |
US11088828B2 (en) | 2019-07-18 | 2021-08-10 | Advanced New Technologies Co., Ltd. | Blockchain-based data evidence storage method and apparatus |
CN110489488B (zh) * | 2019-08-21 | 2021-06-15 | 腾讯科技(深圳)有限公司 | 一种数据处理方法和装置 |
US10992459B2 (en) * | 2019-08-30 | 2021-04-27 | Advanced New Technologies Co., Ltd. | Updating a state Merkle tree |
US11423127B2 (en) | 2019-12-10 | 2022-08-23 | International Business Machines Corporation | Resilient watermarking |
CN111369248B (zh) * | 2020-03-03 | 2023-07-04 | 南京大学 | 一种基于区块链技术的数字产品安全交易方法和*** |
CN111984615B (zh) * | 2020-08-04 | 2024-05-28 | 中国人民银行数字货币研究所 | 一种共享文件的方法、装置及*** |
CN112214799B (zh) * | 2020-09-10 | 2023-06-02 | 中国科学院计算机网络信息中心 | 一种基于区块链技术的数据库防篡改方法及*** |
KR102276527B1 (ko) * | 2020-11-11 | 2021-07-13 | (주)소셜인프라테크 | 오브젝트의 정보 변경 방지를 위한 오브젝트 발행 시스템 |
KR102273629B1 (ko) | 2021-02-22 | 2021-07-06 | (주)지에스티 | Did 기반 블록체인 스마트 단말기 및 생체인식(안면 및 홍채)을 이용한 무인자동화 로봇 보안시스템 |
KR102598503B1 (ko) * | 2023-05-02 | 2023-11-07 | 주식회사 오에스정보통신 | 블록체인을 이용한 통합배선반 관리 시스템, 블록체인 기반의 분산저장 처리장치 및 방법 |
CN117726334B (zh) * | 2024-02-08 | 2024-06-11 | 泉州行创网络科技有限公司 | 一种金融数据处理方法及*** |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR101149695B1 (ko) * | 2011-10-20 | 2012-05-23 | 제이콥스 주식회사 | 금융거래시 전자문서상 자필 전자서명을 이용한 업무처리시스템 및 업무처리방법 |
KR20120074817A (ko) * | 2010-12-28 | 2012-07-06 | 한양대학교 산학협력단 | 저장 장치의 중복 제거 성능 향상을 위한 맵핑 관리 시스템 및 방법 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20030020675A (ko) | 2001-09-04 | 2003-03-10 | 스팍스컴 주식회사 | 워터마킹 기술을 이용한 문서 발급 및 인증시스템과 그인증방법 |
CN101484904A (zh) * | 2006-07-07 | 2009-07-15 | 桑迪士克股份有限公司 | 使用多用途控制结构的内容控制***和方法 |
KR20090000740A (ko) | 2007-03-29 | 2009-01-08 | 주식회사 신한은행 | 증명서 발급 방법 및 시스템과 이를 위한 기록매체 |
US20150206106A1 (en) | 2014-01-13 | 2015-07-23 | Yaron Edan Yago | Method for creating, issuing and redeeming payment assured contracts based on mathemematically and objectively verifiable criteria |
US9858569B2 (en) * | 2014-03-21 | 2018-01-02 | Ramanan Navaratnam | Systems and methods in support of authentication of an item |
CN104392354B (zh) * | 2014-11-05 | 2017-10-03 | 中国科学院合肥物质科学研究院 | 一种公钥地址与用户账号的关联和检索方法及其*** |
CN104320262B (zh) * | 2014-11-05 | 2017-07-21 | 中国科学院合肥物质科学研究院 | 基于加密数字货币公开账本技术的用户公钥地址绑定、检索和校验的方法及*** |
US9374373B1 (en) * | 2015-02-03 | 2016-06-21 | Hong Kong Applied Science And Technology Research Institute Co., Ltd. | Encryption techniques for improved sharing and distribution of encrypted content |
US9705851B2 (en) * | 2015-07-06 | 2017-07-11 | Verisign, Inc. | Extending DNSSEC trust chains to objects outside the DNS |
KR101560766B1 (ko) | 2015-07-10 | 2015-10-14 | 엘지전자 주식회사 | 디지털 방송 수신기 |
US9849364B2 (en) * | 2016-02-02 | 2017-12-26 | Bao Tran | Smart device |
KR101637868B1 (ko) * | 2016-02-22 | 2016-07-08 | 주식회사 코인플러그 | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 |
US10157295B2 (en) * | 2016-10-07 | 2018-12-18 | Acronis International Gmbh | System and method for file authenticity certification using blockchain network |
-
2016
- 2016-02-22 KR KR1020160020437A patent/KR101637868B1/ko active IP Right Grant
- 2016-10-10 WO PCT/KR2016/011288 patent/WO2017146333A1/ko active Application Filing
- 2016-10-10 CA CA3012823A patent/CA3012823A1/en active Pending
- 2016-10-10 CN CN201680082406.6A patent/CN108885760B/zh active Active
-
2018
- 2018-07-31 US US16/050,840 patent/US11005666B2/en active Active
-
2021
- 2021-04-09 US US17/226,175 patent/US20210226804A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20120074817A (ko) * | 2010-12-28 | 2012-07-06 | 한양대학교 산학협력단 | 저장 장치의 중복 제거 성능 향상을 위한 맵핑 관리 시스템 및 방법 |
KR101149695B1 (ko) * | 2011-10-20 | 2012-05-23 | 제이콥스 주식회사 | 금융거래시 전자문서상 자필 전자서명을 이용한 업무처리시스템 및 업무처리방법 |
Non-Patent Citations (4)
Title |
---|
AHN, SANG UK: "Bitcoin Technology, Used for Issuing Certificate", BLOTER-NET, 19 September 2014 (2014-09-19), XP055409684, Retrieved from the Internet <URL:http://www.bloter.net/archives/207040> [retrieved on 20161215] * |
AHN, SANG UK: "Fintech in Blockchain] 2. P2P Financial Innovation", BLOTER.NET, 17 June 2015 (2015-06-17), XP055409676, Retrieved from the Internet <URL:http://www.bloter.net/archives/230365> [retrieved on 20161215] * |
KYUNG HO: "All documents, Authentication with 'BlockChain", ZDNETKOREA, 17 November 2015 (2015-11-17), XP055409679, Retrieved from the Internet <URL:http://www.zdnet.co.kr/news/news_view.asp> [retrieved on 20161215] * |
LEE, SEONG BOK: "Description of Personal Cryptocurrency System of Bitcoin", SLIDESHARE, 21 May 2015 (2015-05-21), Retrieved from the Internet <URL:http://www.slideshare.net/SeongBokLee/ss-48425470> [retrieved on 20161215] * |
Cited By (43)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10091180B1 (en) | 2012-03-20 | 2018-10-02 | United Services Automobile Association (Usaa) | Behavioral profiling method and system to authenticate a user |
US10979410B1 (en) | 2015-05-04 | 2021-04-13 | United Services Automobile Association (Usaa) | Systems and methods for utilizing cryptology with virtual ledgers in support of transactions and agreements |
US11188907B1 (en) | 2015-08-21 | 2021-11-30 | United Services Automobile Association (Usaa) | ACH authorization validation using public blockchains |
US11195177B1 (en) | 2015-08-21 | 2021-12-07 | United Services Automobile Association (Usaa) | Distributed ledger systems for tracking recurring transaction authorizations |
US10949856B1 (en) | 2015-11-17 | 2021-03-16 | United Services Automobile Association (Usaa) | Systems and methods for adaptive learning to replicate peak performance of human decision making |
US11720900B1 (en) | 2015-11-17 | 2023-08-08 | United Services Automobile Association (Usaa) | Systems and methods for adaptive learning to replicate peak performance of human decision making |
US11361286B1 (en) | 2015-11-20 | 2022-06-14 | United Services Automobile Association (Usaa) | Identifying negotiable instrument fraud using distributed ledger systems |
US10423938B1 (en) | 2015-11-20 | 2019-09-24 | United Services Automobile Association | Identifying negotiable instrument fraud using distributed ledger systems |
US11615386B1 (en) | 2015-12-02 | 2023-03-28 | United Services Automobile Association (Usaa) | Block chain authentication systems and methods |
US10263981B1 (en) | 2015-12-02 | 2019-04-16 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US11201862B1 (en) | 2015-12-02 | 2021-12-14 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US10164973B1 (en) | 2015-12-02 | 2018-12-25 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US11722482B1 (en) | 2015-12-02 | 2023-08-08 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US10601819B1 (en) | 2015-12-02 | 2020-03-24 | United Services Automobile Association (Usaa) | Public authentication systems and methods |
US11032286B1 (en) | 2015-12-02 | 2021-06-08 | United Services Automobile Association (Usaa) | Block chain authentication systems and methods |
US11765158B1 (en) | 2015-12-02 | 2023-09-19 | United Services Automobile Association (Usaa) | Multi-factor authentication systems and methods |
US11539507B1 (en) | 2015-12-03 | 2022-12-27 | United Services Automobile Association (Usaa) | Managing blockchain access |
US10833843B1 (en) | 2015-12-03 | 2020-11-10 | United Services Automobile Association (USAA0 | Managing blockchain access |
US10454677B1 (en) | 2016-02-24 | 2019-10-22 | United Services Automobile Associate (USAA) | Cryptographic key generation from biometric data |
US10880080B1 (en) | 2016-02-24 | 2020-12-29 | Unites Services Automobile Association (USAA) | Cryptographic key generation from biometric data |
US11854011B1 (en) | 2016-07-11 | 2023-12-26 | United Services Automobile Association (Usaa) | Identity management framework |
US10762506B1 (en) | 2017-05-11 | 2020-09-01 | United Services Automobile Association | Token device for distributed ledger based interchange |
US11769154B1 (en) | 2017-05-11 | 2023-09-26 | United Services Automobile Association (Usaa) | Token device for distributed ledger based interchange |
US11373187B1 (en) | 2017-05-11 | 2022-06-28 | United Services Automobile Association (Usaa) | Token device for distributed ledger based interchange |
US11711219B1 (en) | 2017-08-24 | 2023-07-25 | United Services Automobile Association (Usaa) | PKI-based user authentication for web services using blockchain |
US10805085B1 (en) | 2017-08-24 | 2020-10-13 | United Services Automobile Association (Usaa) | PKI-based user authentication for web services using blockchain |
CN107682328A (zh) * | 2017-09-26 | 2018-02-09 | 武汉斗鱼网络科技有限公司 | 一种数据校验方法及客户端 |
US11604890B2 (en) | 2017-10-20 | 2023-03-14 | Hewlett Packard Enterprise Development Lp | Accessing information based on privileges |
CN111492389A (zh) * | 2017-10-20 | 2020-08-04 | 慧与发展有限责任合伙企业 | 使用区块链对服务进行认证和支付 |
US11582040B2 (en) | 2017-10-20 | 2023-02-14 | Hewlett Packard Enterprise Development Lp | Permissions from entities to access information |
US11138590B2 (en) | 2017-12-11 | 2021-10-05 | Titan Seal, Inc. | Apparatus and method for embedding digital certifications within documents |
CN108173937A (zh) * | 2017-12-28 | 2018-06-15 | 北京中电普华信息技术有限公司 | 访问控制方法和装置 |
WO2019144400A1 (en) * | 2018-01-29 | 2019-08-01 | Waysun Technology Development Limited | A system and a method for use in data exchange |
WO2019154736A1 (en) * | 2018-02-09 | 2019-08-15 | Airbus (S.A.S.) | Systems and methods of verifying credentials of aircraft personnel using a blockchain computer system |
CN108648761B (zh) * | 2018-05-10 | 2023-05-09 | 北京泛融科技有限公司 | 一种在音频数字水印中嵌入区块链账本的方法 |
CN108648761A (zh) * | 2018-05-10 | 2018-10-12 | 北京泛融科技有限公司 | 一种在音频数字水印中嵌入区块链账本的方法 |
WO2020014282A1 (en) * | 2018-07-09 | 2020-01-16 | Sandor Richard L | Systems and methods for blockchain based identity verification and transaction processing |
CN109194674A (zh) * | 2018-09-20 | 2019-01-11 | 浪潮电子信息产业股份有限公司 | 一种通信数据的处理方法及装置 |
CN110855603A (zh) * | 2018-12-24 | 2020-02-28 | 互联网域名***北京市工程研究中心有限公司 | 一种基于区块链技术的抗DoS攻击防护的方法 |
CN110855603B (zh) * | 2018-12-24 | 2021-11-09 | 互联网域名***北京市工程研究中心有限公司 | 一种基于区块链技术的抗DoS攻击防护的方法 |
CN111695885B (zh) * | 2019-03-14 | 2023-08-29 | 中国科学技术大学 | 基于减小交易输入的数字凭证区块链压缩方法 |
CN111695885A (zh) * | 2019-03-14 | 2020-09-22 | 中国科学技术大学 | 基于减小交易输入的数字凭证区块链压缩方法 |
US12032716B2 (en) | 2023-01-24 | 2024-07-09 | Hewlett Packard Enterprise Development Lp | Accessing information based on privileges |
Also Published As
Publication number | Publication date |
---|---|
CA3012823A1 (en) | 2017-08-31 |
KR101637868B1 (ko) | 2016-07-08 |
US11005666B2 (en) | 2021-05-11 |
CN108885760A (zh) | 2018-11-23 |
CN108885760B (zh) | 2022-02-08 |
WO2017146333A9 (ko) | 2017-10-19 |
US20180343128A1 (en) | 2018-11-29 |
US20210226804A1 (en) | 2021-07-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017146333A1 (ko) | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 | |
WO2016204461A1 (ko) | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 | |
US20210314313A1 (en) | Certificate issuing system based on block chain | |
KR101784219B1 (ko) | 블록체인을 기반으로 하는 금융기관 제증명서류 위변조 검증시스템 및 방법 | |
WO2023033298A1 (ko) | 블록체인 기반의 nft를 이용한 음원 플랫폼의 서버에서 수행되는 서비스 제공 방법 | |
WO2017104899A1 (ko) | 블록체인을 기반으로 하는 공인인증서 인증시스템 및 이를 이용한 인증방법 | |
WO2018070784A2 (ko) | 블록체인 내의 블록별로 발란스 데이터베이스를 관리하여 전자 바우처를 발행, 사용, 환불, 정산 및 파기하는 방법과 이를 이용한 서버 | |
KR101799343B1 (ko) | 인증 정보의 사용 방법, 파기 방법 및 이를 지원하는 블록체인기반 인증 정보 관리 서버 | |
WO2021010766A1 (ko) | 블록 체인을 이용한 전자 인증 장치 및 그 방법 | |
EP3438902A1 (en) | System for issuing public certificate on basis of block chain, and method for issuing public certificate on basis of block chain by using same | |
WO2018070781A2 (ko) | Utxo 기반 프로토콜을 사용하여 전자 바우처를 발행, 사용, 환불, 정산 및 파기하는 방법과 이를 이용한 서버 | |
GB2573622A (en) | Systems and methods for blockchain-based digital lottery ticket generation and distribution | |
US20070136198A1 (en) | Method of facilitating the tracing and/or auditing of operations performed during check image processing | |
KR102241246B1 (ko) | 발급문서의 진위 확인을 위한 블록체인 기반 스탬프 인증 시스템 | |
WO2012053817A2 (ko) | 바코드를 이용한 발급문서 진위확인 방법 및 장치 | |
WO2019035573A1 (ko) | 블록체인 기반의 거래 시스템 및 그 방법 | |
KR100991855B1 (ko) | 전자 문서 발급 및 검증 시스템, 전자 문서 발급 방법 및전자 문서 검증 방법 | |
WO2023163286A1 (ko) | 블록체인 기반의 nft를 이용하는 플랫폼의 서버에서 수행되는 nft에 대한 위변조를 감지하는 위변조 감지 방법 | |
CN111681016B (zh) | 用于建筑工程特种设备追溯的区块链*** | |
CN108701308B (zh) | 用于基于区块链发布公共证书的***、及使用该***的用于基于区块链发布公共证书的方法 | |
WO2018070783A2 (ko) | Utxo 기반으로 머클트리 구조를 사용하여 전자 바우처를 발행, 사용, 환불, 정산 및 파기하는 방법과 이를 이용한 서버 | |
WO2020222475A1 (ko) | 조회 이력 정보와 문서 인증 정보에 의하여 인증 기능이 강화된 문서 인증 방법 및 문서 인증 시스템 | |
WO2020222476A1 (ko) | 조회 이력 통지에 의하여 인증 기능이 강화된 문서 인증 방법 및 문서 인증 시스템 | |
WO2021010614A1 (ko) | 담보물 비보관 전당포 자동화 시스템 및 방법 | |
JP2009042986A (ja) | 金融商品勧誘販売経歴管理システム、金融商品勧誘販売経歴管理方法及び金融商品勧誘販売経歴管理プログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 3012823 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16891737 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 14.12.2018) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16891737 Country of ref document: EP Kind code of ref document: A1 |