CN112231397B - Transaction file transfer method and device based on blockchain - Google Patents
Transaction file transfer method and device based on blockchain Download PDFInfo
- Publication number
- CN112231397B CN112231397B CN202011020650.4A CN202011020650A CN112231397B CN 112231397 B CN112231397 B CN 112231397B CN 202011020650 A CN202011020650 A CN 202011020650A CN 112231397 B CN112231397 B CN 112231397B
- Authority
- CN
- China
- Prior art keywords
- transaction
- hash
- file
- transaction file
- encrypted
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Databases & Information Systems (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application provides a transaction file transfer method based on a blockchain, which comprises the following steps: calculating a first hash of the transaction file through a transaction file making tool; encrypting a transaction file through an electronic signature APP; uploading the encrypted transaction file, the first hash, the transaction subject information and the transaction item information to a chain service device; integrally encrypting the encrypted transaction file, the first hash and the transaction main body information to form an integral transaction file; storing the encrypted integrated transaction file and transaction item information in a blockchain point server; when the mark is opened, the transaction center system acquires the corresponding encrypted integral transaction file from the blockchain node server according to the transaction item information and carries out integral decryption; decrypting the encrypted transaction file and calculating a third hash of the decrypted transaction file; and comparing the first hash with the third hash, and when the first hash and the third hash are the same, enabling the transaction file to be valid. The transaction main body information is stored in the block chain link point server in an encrypted mode, and information leakage can be avoided; the transaction file hash comparison ensures that the file has not been tampered with.
Description
Technical Field
The present application relates to the field of network security and blockchain technologies, and in particular, to a blockchain-based transaction file transfer method and apparatus, an electronic device, and a computer readable medium.
Background
In the process of participating in a transaction, a transaction entity needs to submit transaction files, such as bidding files, bidder information and the like, to different transaction centers. In the process from the transaction main body submitting the bidding information to the bidding project opening, the conditions that a bidder list is leaked, a bidding file is tampered and the like can occur, and the fairness of the transaction result is seriously affected.
Disclosure of Invention
The application aims to provide a transaction file transfer method based on a blockchain. The characteristics of transparency and tamper resistance of the blockchain disclosure are utilized, and bidding documents submitted by transaction subjects, the hashes thereof and the transaction subject information are stored in a blockchain node server after being integrally encrypted, so that the transaction subject information is ensured not to be leaked by a transaction center system; in addition, when the mark is opened, whether the acquired transaction file is consistent with the transaction file uploaded by the transaction main body or not is judged by recalculating the decrypted transaction file hash and the stored transaction file hash, so that the validity of the transaction file is determined, and the transaction file is prevented from being tampered.
According to a first aspect of the present application, a blockchain-based transaction file delivery method is provided. The method comprises the following steps:
calculating a first hash of the transaction file through a transaction file making tool;
encrypting the transaction file through an electronic signature APP;
uploading the encrypted transaction file, the first hash, the transaction subject information and the transaction item information to a chain service device;
the encrypted transaction file, the first hash and the transaction main body information are integrally encrypted to form an integral transaction file;
storing the encrypted overall transaction file and transaction item information in a blockchain node server;
the transaction center system obtains the corresponding encrypted integral transaction file from the blockchain node server according to the transaction item information and carries out integral decryption during opening;
decrypting the encrypted transaction file and calculating a third hash of the decrypted transaction file;
comparing the first hash with the third hash, and when the first hash and the third hash are the same, enabling the transaction file to be valid.
According to some embodiments of the present application, encrypting the transaction file by the electronic signature APP includes:
the transaction file is encrypted and a symmetric key is generated using a standard SM2 encryption algorithm.
According to some embodiments of the present application, the overall encryption includes:
the public key of the transaction center system is used for integral encryption.
According to some embodiments of the present application, storing the encrypted overall transaction file and transaction item information in a blockchain node server includes:
storing the encrypted whole transaction file and transaction item information to a blockchain node master server;
and the blockchain node main server synchronizes the encrypted whole transaction file and the transaction item information to a blockchain point backup server.
According to some embodiments of the present application, the overall decryption includes: decryption is performed using the private key of the transaction center system.
According to some embodiments of the present application, decrypting the encrypted transaction file includes:
decrypting the digital envelope by using the private key of the transaction main body through the electronic signature APP to obtain a symmetric key and transmitting the symmetric key to a transaction center system;
the transaction center system decrypts the encrypted transaction file using the symmetric key.
According to some embodiments of the present application, the transaction file transfer method further includes:
when the first hash is different from the third hash, the transaction center system receives a re-submitted transaction file;
Calculating a fourth hash of the re-submitted transaction file and comparing the fourth hash with the first hash;
when the first hash is the same as the fourth hash, the re-submitted transaction file is valid;
when the first hash is different from the fourth hash, the re-submitted transaction file is invalid.
According to some embodiments of the present application, the transaction file transfer method further includes:
calculating a second hash of the encrypted transaction file;
and encrypting the first hash, the second hash, the transaction item information and the transaction center information through a chain service device to obtain the uplink certificate.
According to some embodiments of the present application, the transaction file transfer method further includes:
manufacturing a two-dimensional code of the second hash;
and downloading the two-dimensional code of the second hash through the electronic signature APP, and referring to the synchronous information of the transaction file.
According to some embodiments of the present application, the transaction file transfer method further includes:
and carrying out digital envelope pre-decryption on the encrypted transaction file through the electronic signature APP so as to obtain a symmetric key in the digital envelope.
According to some embodiments of the present application, the transaction file transfer method further includes:
The transaction file is imported into a transaction file creation tool.
The application also provides a transaction file transfer method based on the blockchain, which comprises the following steps:
calculating a first hash of the transaction file;
calculating a second hash of the encrypted transaction file;
and uploading the encrypted transaction file, the first hash, the second hash, the transaction main body information, the transaction item information and the transaction center information to a chain service device.
According to some embodiments of the present application, the transaction file transfer method further includes:
and manufacturing the second hash two-dimensional code for consulting the synchronous information of the transaction file.
The application also provides a transaction file transfer method based on the blockchain, which comprises the following steps:
encrypting the transaction file in the transaction file making tool;
pre-decrypting the encrypted transaction file in a digital envelope to obtain a symmetric key in the digital envelope;
downloading a second hash two-dimensional code generated by a transaction file manufacturing tool, and referring to the synchronous information of the transaction file;
and decrypting the encrypted transaction file acquired by the transaction center system by using the private key of the transaction main body to acquire a symmetric key and transmitting the symmetric key to the transaction center system.
The application also provides a transaction file transfer method based on the blockchain, which comprises the following steps:
Receiving an encrypted transaction file, a first hash, a second hash of the encrypted transaction file, transaction subject information, transaction item information and transaction center information;
the encrypted transaction file, the first hash and the transaction main body information are integrally encrypted to form an integral transaction file;
storing the encrypted overall transaction file and transaction item information in a blockchain node server;
encrypting the first hash of the transaction file, the second hash of the encrypted transaction file, the transaction item information and the transaction center information for uplink certification.
The application also provides a transaction file transfer method based on the blockchain, which comprises the following steps:
when the bid is opened, transaction item information is sent to a blockchain node server, and an encrypted integral transaction file corresponding to the transaction item information is received, wherein the encrypted integral transaction file is sent by the blockchain node server;
performing integral decryption on the encrypted integral transaction file;
acquiring an encrypted transaction file;
acquiring a first hash of the transaction file;
decrypting the encrypted transaction file through the electronic signature APP, and calculating a third hash of the decrypted transaction file;
comparing the first hash with the third hash, and when the first hash and the third hash are the same, enabling the transaction file to be valid.
According to some embodiments of the present application, the transaction file transfer method further includes:
when the first hash is different from the third hash, calculating a fourth hash of the re-submitted transaction file, and comparing the fourth hash with the first hash;
when the first hash is the same as the fourth hash, the re-submitted transaction file is valid;
when the first hash is different from the fourth hash, the re-submitted transaction file is invalid.
The application also provides a transaction file transfer device based on a blockchain, which comprises:
the file hash calculation module is used for calculating a first hash of the transaction file through the transaction file manufacturing tool;
the transaction file encryption module is used for encrypting the transaction file through the electronic signature APP;
the whole file uploading module is used for uploading the encrypted transaction file, the first hash, the transaction main body information and the transaction item information to the chain service device;
the whole file encryption module is used for carrying out whole encryption on the encrypted transaction file, the first hash and the transaction main body information to form a whole transaction file;
the whole file storage module is used for storing the encrypted whole transaction file and transaction item information in a blockchain node server;
The system comprises an integral file acquisition module, a block chain node server and a transaction center system, wherein the integral file acquisition module is used for acquiring a corresponding encrypted integral transaction file from the block chain node server according to transaction item information and integrally decrypting the encrypted integral transaction file;
the transaction file decryption module is used for decrypting the encrypted transaction file in the whole transaction file by the transaction center system;
and the file hash comparison module is used for calculating a third hash of the decrypted transaction file, comparing the first hash with the third hash, and enabling the transaction file to be effective when the first hash and the third hash are identical.
According to some embodiments of the present application, the transaction file delivery device further includes:
and the transaction file receiving module is used for receiving the re-submitted transaction file by the transaction center system when the first hash is different from the third hash.
According to some embodiments of the present application, the file hash comparison module is further configured to calculate a fourth hash of the resubmitted transaction file, and compare the fourth hash with the first hash.
According to some embodiments of the present application, the file hash calculation module is further configured to calculate a second hash of the encrypted transaction file; the whole file uploading module is further used for uploading the second hash and the transaction center information to the chain service device.
According to some embodiments of the present application, the transaction file delivery device further comprises:
and the uplink certification module is used for encrypting the uplink certification through the chain service device by the first hash, the second hash, the transaction item information and the transaction center information.
The application also provides a transaction file transfer device based on a blockchain, which comprises:
the file hash calculation module is used for calculating a first hash of the transaction file and a second hash of the encrypted transaction file;
the whole file uploading module is used for uploading the encrypted transaction file, the first hash, the second hash, the transaction main body information, the transaction project information and the transaction center information to the chain service device;
and the two-dimension code manufacturing module is used for manufacturing the two-dimension code of the second hash.
The application also provides a transaction file transfer device based on a blockchain, which comprises:
the transaction file encryption module is used for encrypting the transaction file in the transaction file making tool;
the transaction file pre-decryption module is used for carrying out digital envelope pre-decryption on the encrypted transaction file so as to obtain a symmetric key in the digital envelope;
the two-dimension code consulting module is used for downloading the second hash two-dimension code generated by the transaction file making tool and consulting the synchronous information of the transaction file;
And the symmetric key acquisition module is used for decrypting the encrypted transaction file received by the transaction center system by using the private key of the transaction main body to acquire the symmetric key and transmitting the symmetric key to the transaction center system.
The application also provides a transaction file transfer device based on a blockchain, which comprises:
the whole file receiving module is used for receiving the encrypted transaction file, the first hash, the second hash of the encrypted transaction file, the transaction main body information, the transaction project information and the transaction center information;
the whole file encryption module is used for integrally encrypting the encrypted transaction file, the first hash and the transaction main body information to form an integral transaction file;
the whole file storage module is used for storing the encrypted whole transaction file and transaction item information in the blockchain node server;
and the uplink certificate module is used for encrypting the uplink certificate of the first hash, the second hash, the transaction item information and the transaction center information.
The application also provides a transaction file transfer device based on a blockchain, which comprises:
the whole file acquisition module is used for sending transaction item information to the block chain link point server and receiving an encrypted whole transaction file corresponding to the transaction item information, which is sent by the block chain link point server, when the mark is opened;
The whole file decryption module is used for carrying out whole decryption on the encrypted whole transaction file to obtain the encrypted transaction file;
the transaction file decryption module is used for decrypting the encrypted transaction file through the electronic signature APP and calculating a third hash of the decrypted transaction file;
and the file hash comparison module is used for comparing the first hash with the third hash, and the transaction file is valid when the first hash and the third hash are identical.
The application also provides an electronic device comprising: one or more processors; a storage means for storing one or more programs; the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the transaction file delivery method described above.
The present application also provides a computer readable medium having stored thereon a computer program which when executed by a processor implements the transaction file delivery method described above.
Additional aspects and advantages of the application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the application.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application.
Fig. 1A illustrates a first portion of a transaction file delivery method timing diagram according to an example embodiment of the present application.
Fig. 1B illustrates a first portion of a transaction file delivery method timing diagram according to an example embodiment of the present application.
Fig. 1C illustrates a transaction file transfer method application diagram according to an example embodiment of the present application.
Fig. 2 shows a flow chart of a transaction file delivery method according to a first example embodiment of the present application.
Fig. 3 shows a flow chart of a transaction file delivery method according to a second example embodiment of the present application.
Fig. 4 is a flowchart of a transaction file delivery method according to a third exemplary embodiment of the present application.
Fig. 5 is a flow chart of a transaction file delivery method according to a fourth example embodiment of the present application.
Fig. 6 is a flow chart of a transaction file delivery method according to a fifth exemplary embodiment of the present application.
Fig. 7 shows a block diagram of a transaction file delivery device according to a first example embodiment of the present application.
Fig. 8 shows a block diagram of a transaction file delivery device according to a second example embodiment of the present application.
Fig. 9 shows a block diagram of a transaction file delivery device according to a third example embodiment of the present application.
Fig. 10 shows a block diagram of a transaction file delivery device according to a fourth example embodiment of the present application.
Fig. 11 shows a block diagram of a transaction file delivery device according to a fifth exemplary embodiment of the present application.
Fig. 12 shows a block diagram of transaction file delivery electronics according to an example embodiment of the present application.
Detailed Description
Example embodiments are described more fully below with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. These embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present application. One skilled in the relevant art will recognize, however, that the aspects of the application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the application.
It will be understood that, although the terms first, second, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another element. Thus, a first component discussed below could be termed a second component without departing from the teachings of the present application concept. As used herein, the term "and/or" includes any one of the associated listed items and all combinations of one or more.
Those skilled in the art will appreciate that the drawings are schematic representations of example embodiments and may not be to scale. The modules or flows in the figures are not necessarily required to practice the present application and therefore should not be taken to limit the scope of the present application.
Aiming at the problems that the information of the transaction main body is revealed, the transaction file is tampered and the like in the transaction process, the application provides a transaction file transfer method based on the blockchain, and the characteristics of transparency and tamper resistance of the blockchain are utilized, so that the occurrence of disclosure and tamper is avoided through the encryption storage of the information of the transaction main body and the comparison of hash values of the transaction file.
The technical solutions of the present application will be described in detail below with reference to the accompanying drawings.
Fig. 1A illustrates a first portion of a transaction file delivery method timing diagram according to an example embodiment of the present application.
FIG. 1B illustrates a second portion of a transaction file delivery method timing diagram according to an example embodiment of the present application.
Fig. 1C illustrates a transaction file transfer method application diagram according to an example embodiment of the present application.
As shown in fig. 1A, 1B, and 1C, the overall flow of the transaction file transfer method provided in the present application includes:
the transaction agent imports the transaction document through the transaction document creation tool 120. A first hash of the transaction file, denoted h1, is calculated in the transaction file creation tool 120 for determining if the transaction file has been tampered with at the time of opening the label.
The transaction file in the transaction file creation tool 120 is encrypted by the electronic signature APP 110. For example, the transaction file may be encrypted and a symmetric key generated using a standard SM2 encryption algorithm.
The encrypted transaction file is pre-decrypted in the transaction file creation tool 120 by the electronic signature APP 110. The transaction body user can pre-decrypt the encrypted transaction file through the electronic signature APP110 so as to ensure that the symmetric key in the digital envelope can be normally acquired. When the pre-decryption is unsuccessful, the transaction file needs to be reintroduced. The reliability of the encrypted transaction file can be improved through pre-decryption, and the situation that decryption is unsuccessful in opening a label is avoided.
A second hash of the encrypted transaction file is calculated in the transaction file creation tool 120, denoted h2. The transaction subject client can view the uploading and synchronizing states of the transaction file through h2.
The encrypted transaction file, h1, h2, transaction body information, transaction item information, and transaction center information are uploaded to the chain service device 130 in the transaction file making tool 120. According to other embodiments of the present application, this information may also be stored locally; when bidding, the information is selected from the bidding system for submission.
The chain service device 130 integrally encrypts the encrypted transaction file, h1, and transaction body information to form an encrypted integrated transaction file. According to some embodiments of the present application, the chain service 130 may be integrally encrypted using the public key of the transaction center system 150. Since the information of the transaction body is stored in an encrypted manner, information leakage can be avoided. The chain service device 130 sends the encrypted overall transaction file and item information to the blockchain node server 140. In addition, the received first hash of the transaction file, the second hash of the encrypted transaction file, the transaction item information, and the transaction center information are encrypted for upchain certification.
The two-dimensional code of the second hash is created in the transaction file creation tool 120. And the transaction subject client can download the two-dimensional code of the second hash through the electronic signature APP 110 so as to review the synchronous information of the transaction file.
After the overall encryption, the overall encrypted overall transaction file and transaction item information are stored in the blockchain node server 140. According to some embodiments of the present application, as shown in fig. 1C, in order to further ensure the security of the overall transaction file, the encrypted overall transaction file and transaction item information may be stored in the blockchain node master server 141, and then the blockchain node master server 141 synchronizes the encrypted overall transaction file and transaction item information to the blockchain node backup server 142. The blockchain node server may be a fair node server, such as an authority server of a national trust center, among others. By synchronously storing the main server and the backup server, the safety of transaction file storage can be improved.
At the time of opening the bid, the transaction center system 150 obtains the corresponding encrypted overall transaction file from the blockchain node server according to the transaction item information. The transaction center system 150 sends the transaction item information of the current opening label to the blockchain node server 140. The blockchain node server 140 sends all encrypted overall transaction files related to the transaction item to the transaction center system 150. The transaction center system 150 integrally decrypts the received encrypted overall transaction file using the private key of the transaction center system 150 and obtains the encrypted transaction file and the first hash. The symmetric key may be obtained by the electronic signature APP 110 decrypting the encrypted transaction file using the private key of the transaction body. Transaction center system 150 may decrypt the encrypted transaction file using the symmetric key.
After the transaction center system 150 decrypts the transaction file, a third hash of the decrypted transaction file is calculated and may be denoted as h3. Comparing h1 with h3, and when the two are the same, judging that the transaction file is valid. When h1 is not the same as h3, the transaction subject client may resubmit the transaction file to the transaction center system 150.
After the transaction center system 150 receives the resubmitted transaction file, a fourth hash of the resubmitted transaction file is calculated, which may be denoted as h4. Comparing h1 with h4, and when h1 is the same as h4, validating the resubmitted transaction file. When h1 is different from h4, the re-submitted transaction file is invalid and the transaction file is not adopted.
Fig. 2 shows a flow chart of a transaction file delivery method according to a first example embodiment of the present application.
The application provides a transaction file transfer method based on a blockchain, as shown in fig. 2, comprising the following steps:
in step S210, a first hash, denoted as h1, of the transaction file is calculated by the transaction file creation tool, and is used for determining whether the transaction file is tampered when opening a label.
In step S220, the transaction file is encrypted by means of an electronic signature APP. For example, the transaction file may be encrypted and a symmetric key generated using a standard SM2 encryption algorithm.
In step S230, the encrypted transaction file, the first hash, the transaction body information, and the transaction item information are uploaded to a chain service device.
In step S240, the chain service device integrally encrypts the received encrypted transaction file, the first hash, and the transaction body information to form an integral transaction file. According to some embodiments of the present application, the chain service may be integrally encrypted using the public key of the transaction center system. Since the information of the transaction body is stored in an encrypted manner, information leakage can be avoided.
After the overall encryption, the encrypted overall transaction file and transaction item information are stored in the blockchain node server in step S250. According to some embodiments of the present application, in order to further ensure the security of the overall transaction file, the blockchain node master server may synchronize the encrypted overall transaction file and transaction item information to the blockchain link point backup server after storing the encrypted overall transaction file and transaction item information to the blockchain node master server. The blockchain node server can be a fair node server such as an authority server of a national confidence center. By synchronously storing the main server and the backup server, the safety of transaction file storage can be improved.
In step S260, when the bid is opened, the transaction center system obtains the corresponding encrypted whole transaction file from the blockchain node server according to the transaction item information and performs the whole decryption. The transaction center system sends the transaction item information of the current opening label to the block chain link point server. The block link point server transmits all encrypted overall transaction files associated with the transaction item to the transaction center system. After the encrypted integral transaction file is integrally decrypted, the encrypted transaction file and the first hash can be obtained;
in step S270, the transaction center system decrypts the encrypted transaction file and calculates a third hash of the decrypted transaction file, which may be denoted as h3. The encrypted transaction file and the first hash may be obtained after the decrypted overall transaction file is received by the transaction center system. The symmetric key may be obtained by the electronic signature APP110 decrypting the encrypted transaction file using the private key of the transaction body. The transaction center system may decrypt the encrypted transaction file using the symmetric key.
In step S280, the obtained first hash is compared with the calculated third hash, and the transaction file is valid when the obtained first hash and the calculated third hash are identical. Comparing h1 with h3, and when the two are the same, judging that the transaction file is valid, namely that the transaction file is not tampered. According to some embodiments of the present application, when h1 and h3 are not the same, the transaction subject user may self-resubmit the transaction file to the transaction center system.
Fig. 3 shows a flow chart of a transaction file delivery method according to a second example embodiment of the present application.
According to a second exemplary embodiment of the present application, there is provided another blockchain-based transaction file delivery method, as shown in fig. 3, including:
in step S310, a first hash of the transaction file is calculated. The first hash may be denoted as h1 and is used to determine whether the transaction file is tampered with during the opening. According to some embodiments of the application, the transaction file may be encrypted and a symmetric key generated using a standard SM2 encryption algorithm.
In step S320, a second hash of the encrypted transaction file is calculated, denoted h2. The transaction subject client can view the uploading and synchronizing states of the transaction file through h2.
In step S330, the encrypted transaction file, the first hash, the second hash, the transaction body information, the transaction item information, and the transaction center information are uploaded to a chain service device.
According to some embodiments of the present application, the transaction file transfer method may further include making the two-dimensional code of the second hash, for referring to synchronization information of the transaction file.
Fig. 4 is a flowchart of a transaction file delivery method according to a third exemplary embodiment of the present application.
According to a third exemplary embodiment of the present application, there is provided another blockchain-based transaction file delivery method, as shown in fig. 4, including:
in step S410, the transaction file in the transaction file creation tool is encrypted.
In step S420, the encrypted transaction file is digitally pre-decrypted to obtain the symmetric key in the digital envelope.
In step S430, the two-dimensional code of the second hash generated by the transaction file creation tool is downloaded, and the synchronization information of the transaction file is referred to.
In step S440, the encrypted transaction file received by the transaction center system is decrypted using the private key of the transaction body to obtain a symmetric key and sent to the transaction center system.
Fig. 5 is a flowchart of a transaction file delivery method according to a fourth exemplary embodiment of the present application.
According to a fourth exemplary embodiment of the present application, there is provided another blockchain-based transaction file delivery method, as shown in fig. 5, including:
in step S510, an encrypted transaction file, a first hash, a second hash of the encrypted transaction file, transaction body information, transaction item information, and transaction center information are received.
In step S520, the encrypted transaction file, the first hash, and the transaction body information are integrally encrypted to form an integral transaction file. According to some embodiments of the present application, blockchain node server 140 may use the public key of the transaction center system for overall encryption. Since the information of the transaction body is stored in an encrypted manner, information leakage can be avoided.
After the overall encryption, the encrypted overall transaction file and transaction item information are stored in the blockchain node server 140 in step S530. In order to further ensure the security of the whole transaction file, the encrypted whole transaction file and transaction item information can be stored in the blockchain node main server, and then the blockchain node main server synchronizes the encrypted whole transaction file and the transaction item information to the blockchain link point backup server.
In step S540, the first hash of the transaction file, the second hash of the encrypted transaction file, the transaction item information, and the transaction center information are encrypted for up-chain certification.
Fig. 6 is a flow chart of a transaction file delivery method according to a fifth exemplary embodiment of the present application.
According to a fifth exemplary embodiment of the present application, there is provided another blockchain-based transaction file delivery method, as shown in fig. 6, including:
in step S610, the transaction item information of the current opening label is sent to the blockchain node server during the opening label, and all the encrypted whole transaction files related to the transaction item sent by the blockchain node server are received.
In step S620, the encrypted overall transaction file is overall decrypted.
In step S630, an encrypted transaction file is acquired.
In step S640, a first hash of the transaction file is obtained.
In step S650, the encrypted transaction file is decrypted by the electronic signature APP, and a third hash of the decrypted transaction file is calculated.
In step S660, the obtained first hash is compared with the calculated third hash, and when the two hashes are identical, the transaction file can be determined to be valid.
Fig. 7 shows a block diagram of a transaction file delivery device according to a first example embodiment of the present application.
The present application also provides a transaction file transfer device 200 based on blockchain, as shown in fig. 7, including a file hash calculation module 210, a transaction file encryption module 220, an overall file uploading module 230, an overall file encryption module 240, an overall file storage module 250, an overall file acquisition module 260, a transaction file decryption module 270, and a file hash comparison module 280.
The file hash calculation module 210 is configured to calculate a first hash of the transaction file through the transaction file creation tool.
The transaction file encryption module 220 is configured to encrypt the transaction file through the electronic signature APP.
And the whole file uploading module 230 is configured to upload the encrypted transaction file, the first hash, the transaction subject information, and the transaction item information to the chain service device.
The integral file encrypting module 240 is configured to integrally encrypt the encrypted transaction file, the first hash, and the transaction body information to form an integral transaction file.
And the whole file storage module 250 is used for storing the encrypted whole transaction file and the transaction item information in the blockchain node server.
The whole file obtaining module 260 is configured to obtain, by the transaction center system at the time of opening the label, the corresponding encrypted whole transaction file from the blockchain node server according to the transaction item information, and decrypt the whole.
The transaction file decryption module 270 is configured to decrypt the encrypted transaction file in the whole transaction file by the transaction center system.
The file hash comparison module 280 is configured to calculate a third hash of the decrypted transaction file, compare the obtained first hash with the calculated third hash, and when the two hashes are identical, the transaction file is valid.
Fig. 8 shows a block diagram of a transaction file delivery device according to a second example embodiment of the present application.
According to another embodiment of the present application, there is further provided a transaction file transfer device 300 based on a blockchain, as shown in fig. 8, including a file hash calculation module 310, an overall file uploading module 320, and a two-dimensional code making module 330
The file hash calculation module 310 is configured to calculate a first hash of the transaction file and a second hash of the encrypted transaction file.
And the whole file uploading module 320 is configured to upload the encrypted transaction file, the first hash, the second hash, the transaction body information, the transaction item information and the transaction center information to the chain service device.
The two-dimensional code manufacturing module 330 is configured to manufacture the second hashed two-dimensional code.
Fig. 9 shows a block diagram of a transaction file delivery device according to a third example embodiment of the present application.
According to another embodiment of the present application, there is further provided a transaction file transfer device 400 based on a blockchain, as shown in fig. 9, including a transaction file encryption module 410, a transaction file pre-decryption module 420, a two-dimensional code review module 430, and a symmetric key acquisition module 440.
A transaction file encryption module 410 that encrypts a transaction file in the transaction file creation tool;
the transaction file pre-decryption module 420 performs digital envelope pre-decryption on the encrypted transaction file to obtain a symmetric key in the digital envelope;
the two-dimension code consulting module 430 is configured to download the second hashed two-dimension code generated by the transaction file creating tool, and consult the synchronization information of the transaction file;
The symmetric key obtaining module 440 is configured to decrypt the encrypted transaction file received by the transaction center system by using the private key of the transaction main body to obtain a symmetric key, and send the symmetric key to the transaction center system.
Fig. 10 shows a block diagram of a transaction file delivery device according to a fourth example embodiment of the present application.
According to another embodiment of the present application, there is further provided a transaction file transfer device 500 based on a blockchain, as shown in fig. 10, including an overall file receiving module 510, an overall file encrypting module 520, an overall file storing module 530, and a ul certification module 540.
The whole file receiving module 510 is configured to receive the encrypted transaction file, the first hash, the second hash of the encrypted transaction file, the transaction body information, the transaction item information, and the transaction center information.
The integral file encrypting module 520 is configured to integrally encrypt the encrypted transaction file, the first hash, and the transaction body information to form an integral transaction file.
And the whole file storage module 530 is used for storing the encrypted whole transaction file and the transaction item information in the blockchain node server.
The upchain credit module 540 is configured to encrypt the upchain credit with the first hash of the transaction file, the second hash of the encrypted transaction file, the transaction item information, and the transaction center information.
Fig. 11 shows a block diagram of a transaction file delivery device according to a fifth exemplary embodiment of the present application.
According to another embodiment of the present application, there is further provided a transaction file transfer device 600 based on a blockchain, as shown in fig. 11, including an overall file acquisition module 610, an overall file decryption module 620, a transaction file acquisition module 630, a first hash acquisition module 640, a transaction file decryption module 650, and a file hash comparison module 660.
The whole file obtaining module 610 is configured to send transaction item information to the blockchain node main server and receive a decrypted whole transaction file corresponding to the transaction item information sent by the blockchain node point server when opening a label.
The global file decryption module 620 is configured to decrypt the encrypted global transaction file.
The transaction file acquisition module 630 is configured to acquire an encrypted transaction file. According to some embodiments of the present application, the encrypted transaction file may be obtained after decryption of the overall transaction file.
A first hash obtaining module 640, configured to obtain a first hash of the transaction file. According to some embodiments of the present application, the first hash of the transaction file may be obtained after decryption of the entire transaction file. According to some embodiments of the present application, the first hash of the transaction file may also be obtained directly from the chain.
The transaction file decryption module 650 is configured to decrypt the encrypted transaction file through the electronic signature APP, and calculate a third hash of the decrypted transaction file.
And the file hash comparison module 660 is configured to compare the first hash with the third hash, and when the first hash and the third hash are the same, the transaction file is valid.
Fig. 12 shows a block diagram of transaction file delivery electronics according to an example embodiment of the present application.
The present application also provides a blockchain-based transaction file delivery electronic device 900. The electronic device 900 shown in fig. 12 is merely an example, and should not be construed as limiting the functionality and scope of use of the embodiments herein.
As shown in fig. 12, the control device 900 is in the form of a general purpose computing device. The components of the control device 900 may include, but are not limited to: at least one processing unit 910, at least one storage unit 920, a bus 930 that connects the different system components (including the storage unit 920 and the processing unit 910), and so forth.
The storage unit 920 stores program codes that can be executed by the processing unit 910, so that the processing unit 910 performs the transaction file transfer method according to the embodiments of the present application described in the present specification.
The storage unit 920 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 9201 and/or cache memory 9202, and may further include Read Only Memory (ROM) 9203.
The storage unit 920 may also include a program/utility 9204 having a set (at least one) of program modules 9205, such program modules 9205 include, but are not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The bus 930 may be one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.
The electronic device 900 may also communicate with one or more external devices 9001 (e.g., touch screen, keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 900, and/or any device (e.g., router, modem, etc.) that enables the electronic device 900 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 950. Also, electronic device 900 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 960. The network adapter 960 can communicate with other modules of the electronic device 900 via the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 900, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The present application also provides a computer readable medium having stored thereon a computer program which when executed by a processor implements the transaction file delivery method described above.
It is apparent that the above examples are only examples for clearly illustrating the present application and are not limited to the embodiments. Other variations or modifications of the above teachings will be apparent to those of ordinary skill in the art. It is not necessary here nor is it exhaustive of all embodiments. And obvious variations or modifications thereof are intended to be within the scope of the present application.
Claims (16)
1. A blockchain-based transaction document delivery method, the transaction document delivery method comprising:
calculating a first hash of the transaction file through a transaction file making tool;
encrypting the transaction file through an electronic signature APP;
performing digital envelope pre-decryption on the encrypted transaction file through the electronic signature APP to obtain a symmetric key in a digital envelope;
uploading the encrypted transaction file, the first hash, the transaction subject information and the transaction item information to a chain service device;
the chain service device uses a public key of the transaction center system to carry out integral encryption on the encrypted transaction file, the first hash and the transaction main body information to form an integral transaction file;
Storing the encrypted overall transaction file and transaction item information in a blockchain node server;
when the trade center system is opened, the corresponding encrypted integral trade file is obtained from the blockchain node server according to the trade item information, and integral decryption is carried out by using the private key of the trade center system;
decrypting the digital envelope by using a private key of a transaction main body through the electronic signature APP, obtaining a symmetric key, sending the symmetric key to a transaction center system, decrypting the encrypted transaction file by using the symmetric key by using the transaction center system, and calculating a third hash of the decrypted transaction file;
comparing the obtained first hash with the calculated third hash, and when the obtained first hash and the calculated third hash are the same, enabling the transaction file to be valid.
2. The transaction document transfer method according to claim 1, wherein encrypting the transaction document by an electronic signature APP comprises:
the transaction file is encrypted and a symmetric key is generated using a standard SM2 encryption algorithm.
3. The transaction file transfer method according to claim 1, wherein storing the encrypted overall transaction file and transaction item information in a blockchain node server includes:
Storing the encrypted whole transaction file and transaction item information to a blockchain node master server;
and the blockchain node main server synchronizes the encrypted whole transaction file and the transaction item information to a blockchain point backup server.
4. The transaction file transfer method according to claim 1, further comprising:
when the first hash is different from the third hash, the transaction center system receives a re-submitted transaction file;
calculating a fourth hash of the re-submitted transaction file and comparing the fourth hash with the first hash;
when the first hash is the same as the fourth hash, the re-submitted transaction file is valid;
when the first hash is different from the fourth hash, the re-submitted transaction file is invalid.
5. The transaction file transfer method according to claim 1, further comprising:
calculating a second hash of the encrypted transaction file;
and encrypting the first hash, the second hash, the transaction item information and the transaction center information through a chain service device to obtain the uplink certificate.
6. The transaction file transfer method according to claim 5, further comprising:
Manufacturing a two-dimensional code of the second hash;
and downloading the two-dimensional code of the second hash through the electronic signature APP, and referring to the synchronous information of the transaction file.
7. The transaction file transfer method according to claim 1, further comprising:
the transaction file is imported into a transaction file creation tool.
8. The transaction file transfer method according to claim 5, further comprising:
and manufacturing the second hash two-dimensional code for consulting the synchronous information of the transaction file.
9. The transaction file transfer method according to claim 1, further comprising:
when the first hash is different from the third hash, calculating a fourth hash of the re-submitted transaction file, and comparing the fourth hash with the first hash;
when the first hash is the same as the fourth hash, the re-submitted transaction file is valid;
when the first hash is different from the fourth hash, the re-submitted transaction file is invalid.
10. A blockchain-based transaction file delivery device, comprising:
the file hash calculation module is used for calculating a first hash of the transaction file through the transaction file manufacturing tool;
The transaction file encryption module is used for encrypting the transaction file through the electronic signature APP;
the transaction file pre-decryption module is used for carrying out digital envelope pre-decryption on the encrypted transaction file through the electronic signature APP so as to obtain a symmetric key in the digital envelope;
the whole file uploading module is used for uploading the encrypted transaction file, the first hash, the transaction main body information and the transaction item information to the chain service device;
the whole file encryption module is used for integrally encrypting the encrypted transaction file, the first hash and the transaction main body information by using a public key of the transaction center system to form an integral transaction file;
the whole file storage module is used for storing the encrypted whole transaction file and transaction item information in the blockchain node server;
the system comprises a block chain node server, a whole file acquisition module, a transaction center system and a public key, wherein the block chain node server is used for providing a block chain with a transaction project information;
the symmetric key acquisition module is used for decrypting the encrypted transaction file received by the transaction center system by using the private key of the transaction main body through the electronic signature APP to obtain a symmetric key and sending the symmetric key to the transaction center system;
The transaction file decryption module is used for decrypting the encrypted transaction file in the whole transaction file by the transaction center system by using the symmetric key and calculating a third hash of the decrypted transaction file;
and the file hash comparison module is used for comparing the first hash with the third hash, and the transaction file is valid when the first hash and the third hash are identical.
11. The transaction file transfer device according to claim 10, further comprising:
and the transaction file receiving module is used for receiving the re-submitted transaction file by the transaction center system when the first hash is different from the third hash.
12. The transaction file transfer device of claim 11, wherein the file hash comparison module is further configured to calculate a fourth hash of the resubmitted transaction file and compare the fourth hash with the first hash.
13. The transaction file transfer device according to claim 10, wherein,
the file hash calculation module is further used for calculating a second hash of the encrypted transaction file;
the whole file uploading module is further used for uploading the second hash and the transaction center information to the chain service device.
14. The transaction file transfer device according to claim 13, further comprising:
and the uplink certification module is used for encrypting the uplink certification through the chain service device by the first hash, the second hash, the transaction item information and the transaction center information.
15. An electronic device, comprising:
one or more processors;
a storage means for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the transaction file delivery method of any of claims 1-9.
16. A computer readable medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements a transaction file transfer method according to any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011020650.4A CN112231397B (en) | 2020-09-25 | 2020-09-25 | Transaction file transfer method and device based on blockchain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011020650.4A CN112231397B (en) | 2020-09-25 | 2020-09-25 | Transaction file transfer method and device based on blockchain |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112231397A CN112231397A (en) | 2021-01-15 |
| CN112231397B true CN112231397B (en) | 2023-06-30 |
Family
ID=74107597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011020650.4A Active CN112231397B (en) | 2020-09-25 | 2020-09-25 | Transaction file transfer method and device based on blockchain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231397B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114143306A (en) * | 2021-11-08 | 2022-03-04 | 北京标信智链科技有限公司 | Block chain-based bid document transmission method and transmission device |
| CN114760111A (en) * | 2022-03-24 | 2022-07-15 | 标信智链(杭州)科技发展有限公司 | File security method and file security device based on block chain |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110570313A (en) * | 2019-09-27 | 2019-12-13 | 深圳市网心科技有限公司 | data transaction method, data transaction device and system based on block chain |
| CN110597908A (en) * | 2019-09-10 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Credit investigation recording method, device and storage medium based on block chain |
| KR102065315B1 (en) * | 2019-10-04 | 2020-01-13 | 주식회사 도우테크 | System and method for keeping and sharing a file based on block chain network |
| CN111427954A (en) * | 2020-03-20 | 2020-07-17 | 标信智链(杭州)科技发展有限公司 | Method and device for sharing transaction subject data based on block chain |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106888089B (en) * | 2015-12-16 | 2019-12-13 | 卓望数码技术（深圳）有限公司 | method and system for electronic signature and mobile communication terminal for electronic signature |
| US10063379B2 (en) * | 2016-06-16 | 2018-08-28 | The Bank Of New York Mellon | Distributed, centrally authored block chain network |
| KR102005111B1 (en) * | 2017-12-20 | 2019-07-29 | 주식회사 유니로보틱스 | Goods or service providing method between things using block chain system |
| KR102084674B1 (en) * | 2018-05-30 | 2020-03-05 | 한국과학기술연구원 | Method for managing content based on blockchain and system performing the method |
| CN109472166B (en) * | 2018-11-01 | 2021-05-07 | 恒生电子股份有限公司 | Electronic signature method, device, equipment and medium |
| CN110069906A (en) * | 2019-03-11 | 2019-07-30 | 平安科技（深圳）有限公司 | A kind of encryption and decryption method and its device of electronic document |
| CN110197445B (en) * | 2019-05-16 | 2021-08-10 | 中细软集团有限公司 | Intellectual property state generation method, intellectual property state query method, computer device and storage medium |
-
2020
- 2020-09-25 CN CN202011020650.4A patent/CN112231397B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110597908A (en) * | 2019-09-10 | 2019-12-20 | 腾讯科技（深圳）有限公司 | Credit investigation recording method, device and storage medium based on block chain |
| CN110570313A (en) * | 2019-09-27 | 2019-12-13 | 深圳市网心科技有限公司 | data transaction method, data transaction device and system based on block chain |
| KR102065315B1 (en) * | 2019-10-04 | 2020-01-13 | 주식회사 도우테크 | System and method for keeping and sharing a file based on block chain network |
| CN111427954A (en) * | 2020-03-20 | 2020-07-17 | 标信智链(杭州)科技发展有限公司 | Method and device for sharing transaction subject data based on block chain |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112231397A (en) | 2021-01-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11483161B2 (en) | Method for information processing and non-transitory computer readable storage medium | |
| CN109150499B (en) | Method and device for dynamically encrypting data, computer equipment and storage medium | |
| US10439804B2 (en) | Data encrypting system with encryption service module and supporting infrastructure for transparently providing encryption services to encryption service consumer processes across encryption service state changes | |
| US8321669B2 (en) | Electronic data communication system | |
| US9800416B2 (en) | Distributed validation of digitally signed electronic documents | |
| US8649522B2 (en) | Electronic data communication system | |
| CN102077213B (en) | Techniques for ensuring authentication and integrity of communications | |
| US8271788B2 (en) | Software registration system | |
| US20080083039A1 (en) | Method for integrity attestation of a computing platform hiding its configuration information | |
| CN111177801B (en) | Signature method and device of electronic document, storage medium and electronic equipment | |
| US11374975B2 (en) | TLS integration of post quantum cryptographic algorithms | |
| KR20060045440A (en) | A method and system for recovering password protected private data via a communication network without exposing the private data | |
| US20020101998A1 (en) | Fast escrow delivery | |
| CN112231397B (en) | Transaction file transfer method and device based on blockchain | |
| CN110912920A (en) | Data processing method, apparatus and medium | |
| CN110597836B (en) | Information inquiry request response method and device based on block chain network | |
| CN111970109B (en) | Data transmission method and system | |
| KR100563515B1 (en) | Method and system for transient key digital time stamps | |
| CN113836506A (en) | Identity authentication method, device, system, electronic equipment and storage medium | |
| JP2017531951A (en) | Method, device, terminal and server for security check | |
| CN112073433B (en) | SSL certificate updating method and device, electronic equipment and storage medium | |
| CN113114654A (en) | Terminal equipment access security authentication method, device and system | |
| CN108848094B (en) | Data security verification method, device, system, computer equipment and storage medium | |
| WO2023215373A1 (en) | Secure data exchange using format-preserving encryption | |
| KR20180024389A (en) | Apparatus and method for key management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Jin Shicheng Inventor after: Fu Shijian Inventor after: Zhang Junfeng Inventor after: Li Xuezhi Inventor before: Jin Shicheng Inventor before: Wang Tongzhou Inventor before: Fu Shijian Inventor before: Zhang Junfeng Inventor before: Li Xuezhi |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |