CN111310206A - Data encryption method, node equipment and storage medium - Google Patents
Data encryption method, node equipment and storage medium Download PDFInfo
- Publication number
- CN111310206A CN111310206A CN202010090219.0A CN202010090219A CN111310206A CN 111310206 A CN111310206 A CN 111310206A CN 202010090219 A CN202010090219 A CN 202010090219A CN 111310206 A CN111310206 A CN 111310206A
- Authority
- CN
- China
- Prior art keywords
- encryption algorithm
- transaction data
- encryption
- node device
- middleware
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 230000008569 process Effects 0.000 claims abstract description 24
- 230000001960 triggered effect Effects 0.000 claims abstract description 22
- 238000012795 verification Methods 0.000 claims description 87
- 230000015654 memory Effects 0.000 claims description 21
- 238000012545 processing Methods 0.000 claims description 9
- 238000004590 computer program Methods 0.000 claims description 3
- 238000003672 processing method Methods 0.000 claims 1
- 238000004891 communication Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- OTZZZISTDGMMMX-UHFFFAOYSA-N 2-(3,5-dimethylpyrazol-1-yl)-n,n-bis[2-(3,5-dimethylpyrazol-1-yl)ethyl]ethanamine Chemical compound N1=C(C)C=C(C)N1CCN(CCN1C(=CC(C)=N1)C)CCN1C(C)=CC(C)=N1 OTZZZISTDGMMMX-UHFFFAOYSA-N 0.000 description 1
- 241001441724 Tetraodontidae Species 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- 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
- 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/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Bioethics (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Health & Medical Sciences (AREA)
- Technology Law (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the invention discloses a data encryption method, node equipment and a storage medium. The data encryption method is applied to the first node equipment and comprises the following steps: in the process of running the intelligent contract, if a first encryption event is triggered, invoking a middleware, wherein the first encryption event indicates that first transaction data is encrypted, and the middleware comprises an encryption algorithm library; searching an encryption algorithm corresponding to the first encryption event in the middleware; and calling an encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext. By adopting the embodiment of the invention, the encryption algorithm for the first transaction data is specified in the encryption algorithm library, and if the encryption algorithm is modified, only the encryption algorithm in the encryption algorithm library needs to be modified, so that the workload for modifying the encryption algorithm can be reduced.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data encryption method, a node device, and a storage medium.
Background
When a user encrypts transaction data by operating a program code, the encryption algorithm called in the program code realizes the encryption of the transaction data, and the encryption algorithm is added into the program code in advance by developers in the mode of an encryption algorithm library. When a user needs to change the encryption algorithm of the transaction data, a developer needs to traverse all program codes, change the encryption algorithm at a position where the transaction data needs to be encrypted, compile the changed program and provide the compiled program to the user, so that the user can encrypt the transaction data by using a new encryption algorithm by running the compiled program.
In the encryption processing process, the requirement of users for changing the encryption algorithm is gradually increased, so that the workload of simplifying and changing the encryption algorithm becomes a problem to be solved.
Disclosure of Invention
Embodiments of the present invention provide a data encryption method, a node device, and a storage medium, which can reduce the workload of modifying an encryption algorithm.
In a first aspect, an embodiment of the present invention provides a data encryption method, where the method is applied to a first node device, and the method includes:
in the process of running the intelligent contract, if a first encryption event is triggered, invoking a middleware, wherein the first encryption event indicates that first transaction data is encrypted, and the middleware comprises an encryption algorithm library; searching an encryption algorithm library corresponding to the first encryption event in the middleware; and calling an encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext.
In the technical scheme, in the process of operating the intelligent contract, if a first encryption event is triggered, the first node equipment calls the middleware, the first transaction data is encrypted by using an encryption algorithm in an encryption algorithm library in the middleware, the encryption algorithm for encrypting the first transaction data is specified in the encryption algorithm library, and if the encryption algorithm is modified, only the encryption algorithm in the encryption algorithm library needs to be modified, so that the workload for modifying the encryption algorithm can be reduced by the data encryption method.
In a second aspect, an embodiment of the present invention provides a node device, which is applied to a first node device, and includes a memory, a processor, and a communication interface, where the memory stores a set of program codes, and the processor calls the program codes stored in the memory, so as to execute the method according to the first aspect.
In a third aspect, an embodiment of the present invention provides a data encryption apparatus, where the encryption apparatus includes:
the calling unit is used for calling the middleware if a first encryption event is triggered in the process of running the intelligent contract, wherein the first encryption event indicates that the first transaction data is encrypted, and the middleware comprises an encryption algorithm library;
the searching unit is used for searching an encryption algorithm library corresponding to the first encryption event in the middleware;
and the calling unit is used for calling the encryption algorithm library so as to encrypt the first transaction data to obtain a first ciphertext.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing computer program instructions for a first node device, which includes a program for executing the first aspect.
By implementing the embodiment of the invention, if the first encryption event is triggered in the process of operating the intelligent contract, the first node equipment calls the middleware, then searches the encryption algorithm corresponding to the first encryption event in the middleware, and finally calls the encryption algorithm library to encrypt the first transaction data to obtain the first ciphertext. The encryption algorithm library defines an encryption algorithm for encrypting the first transaction data, and if the encryption algorithm is modified, only the encryption algorithm in the encryption algorithm library needs to be modified, so that the workload of modifying the encryption algorithm can be reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present invention, the drawings required to be used in the embodiments or the background art of the present invention will be described below.
Fig. 1 is a block chain network architecture according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a data encryption method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of another data encryption method according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a path of another data encryption method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a node device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a data encryption apparatus according to an embodiment of the present invention.
Detailed Description
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
At present, in the encryption process of transaction data, if a user needs to change an encryption algorithm, only developers can traverse all program codes, and the encryption algorithm at the encryption position in the program codes is modified, so that the modification mode can only be operated by the developers and the workload is large. The embodiment of the application introduces the password library middleware into data encryption, and provides a data encryption method, node equipment and a storage medium. In the method, in the process of running an intelligent contract by first node equipment, if a first encryption event is triggered, middleware is called, wherein the first encryption event indicates that first transaction data is encrypted, and the middleware comprises an encryption algorithm library; then the first node equipment searches an encryption algorithm library corresponding to the first encryption event in the middleware; and finally, the first node equipment calls an encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext. In the data encryption method, when the first node equipment triggers a first encryption event in the process of operating the intelligent contract, the middleware is called, the first transaction data is encrypted through the encryption algorithm library of the middleware, the encryption algorithm used when the first transaction data is encrypted is specified in the encryption algorithm library, the encryption algorithm of the first transaction data is modified only by modifying the encryption algorithm in the encryption algorithm library, and the workload of modifying the encryption algorithm can be reduced.
Referring to fig. 1, fig. 1 is a block chain network architecture according to an embodiment of the present invention. As shown in fig. 1, the blockchain network includes a first node device 101 and a second node device 102, and the exemplary blockchain network shown in fig. 1 includes three second node devices 102, and optionally, the blockchain network may include four second node devices 102, five second node devices, and so on, which are not limited herein. The first node device 101 and the second node device 102 may both run an intelligent contract, when the first node device 101 triggers a first encryption event in the process of running the intelligent contract, the middleware is invoked, the first transaction data is encrypted through an encryption algorithm in an encryption algorithm library in the middleware, and the second node device 102 may receive the first transaction data and the third transaction data sent by the first node device 101, and check the third transaction data according to the first transaction data. The blockchain network shown in fig. 1 is composed of four node devices for example only, and does not constitute a limitation to the embodiments of the present application.
The block chain is a novel application mode of computer technologies such as distributed data storage, consensus mechanism and encryption algorithm, and is essentially a decentralized database; the blockchain can be composed of a plurality of serial transaction records (also called blocks) which are connected in series by cryptography and protect the contents, and the distributed accounts connected in series by the blockchain can effectively record the transaction by multiple parties and can permanently check the transaction (can not be tampered).
The consensus mechanism refers to a mathematical algorithm for establishing trust and obtaining rights and interests among different nodes in a block chain network, the consensus mechanism is a mathematical algorithm commonly accepted by the nodes in the block chain network, and the consensus algorithm in the consensus mechanism includes, but is not limited to, a Proof of Work (PoW) algorithm, a Proof of rights and interests (PoS) algorithm, a granted Proof of rights and interests (DPoS) algorithm, a Practical Byzantine Fault Tolerance (PBFT) algorithm, and the like.
In the data encryption process of the application, the first node device and the second node device in the blockchain network both store intelligent contracts, and the intelligent contracts can trigger a first encryption event by running the intelligent contracts. Smart contracts are, among other things, computer protocols intended to propagate, verify or execute contracts in an informational manner, allowing for trusted transactions to be conducted without third parties, which transactions are traceable and irreversible. An intelligent contract is a set of commitments defined in digital form, including the protocol on which the contract participants can execute the commitments, and is a piece of code written on a blockchain.
The encryption algorithm includes a symmetric encryption algorithm, an asymmetric encryption algorithm, and a hash algorithm. The symmetric encryption algorithm may include, but is not limited to, DES algorithm, 3DES algorithm, TDEA algorithm, Blowfish algorithm, RC5 algorithm, IDEA algorithm, etc., the asymmetric encryption algorithm may include, but is not limited to, RSA algorithm, Elgamal algorithm, knapsack algorithm, Rabin algorithm, D-H algorithm, ECC algorithm, etc., and the hash algorithm may include, but is not limited to, SHA512 algorithm, SHA224 algorithm, SHA384 algorithm, etc.
Based on the above description, the present application embodiment proposes a data encryption method as shown in fig. 2, and the data encryption method may include the following steps S201 to S203:
s201: and in the process of running the intelligent contract, if a first encryption event is triggered, the first node equipment calls the middleware.
The first encryption event indicates that the first transaction data is encrypted, namely the first encryption event is an event that needs to execute an encryption task on the first transaction data in the smart contract. The middleware is a kind of computer software connecting software components and applications, the middleware in the application comprises an encryption algorithm library, the encryption algorithm library comprises a symmetrical encryption algorithm library, an asymmetrical encryption algorithm library and a Hash algorithm library, each node device specifies an encryption algorithm in the encryption algorithm library in advance, namely a symmetrical encryption algorithm is specified in the symmetrical encryption algorithm library, an asymmetrical encryption algorithm is specified in the asymmetrical encryption algorithm library, and a Hash algorithm is specified in the Hash algorithm library, namely when one encryption algorithm library in the encryption algorithm library is called, the encryption algorithm in the encryption algorithm library is used for encrypting transaction data.
Illustratively, in a symmetric encryption algorithm library in the encryption algorithm library of the middleware, the symmetric encryption algorithm is specified as a DES algorithm, in an asymmetric encryption algorithm library in the encryption algorithm library, the asymmetric encryption algorithm is specified as an RSA algorithm, and in a hash algorithm library in the encryption algorithm library, the hash algorithm is specified as an SHA512 algorithm. Namely, if the first node equipment calls the symmetric encryption algorithm library in the encryption algorithm library when the middleware is called, the first node equipment encrypts the transaction data by using the DES algorithm of the symmetric encryption algorithm library; if the first node equipment calls an asymmetric encryption algorithm library in the encryption algorithm library, encrypting the transaction data by using an RSA algorithm in the asymmetric encryption algorithm library; if the first node device calls the hash algorithm library in the encryption algorithm library, the SHA512 algorithm in the hash algorithm library is used for encrypting the transaction data.
The intelligent contract is stored in the first node device, and when the first node device needs to execute the encryption task, the intelligent contract stored in the node device is operated. In the process of running the intelligent contract, if a first encryption event is triggered, invoking the middleware, for example, when the intelligent contract runs at a, a needs to encrypt the first transaction data, which also means that the a is the first encryption event, that is, the first encryption event is triggered at the a of the intelligent contract, the first node device invokes the middleware, so that the first node device can continue to invoke the encryption algorithm library in the middleware.
S202: and the first node equipment searches an encryption algorithm library corresponding to the first encryption event in the middleware.
In the process of writing the intelligent contract, the developer already specifies the type of the encryption algorithm used when the first transaction data in the first encryption event is encrypted, for example, the first encryption event is a first encryption event a, and when the developer writes the intelligent contract, the developer specifies the type of the encryption algorithm used when the first transaction data a in the first encryption event a in the intelligent contract is encrypted as a symmetric encryption algorithm, and optionally, the developer may specify the type of the encryption algorithm used when the first transaction data a in the first encryption event a is encrypted as an asymmetric encryption algorithm or a hash algorithm in the intelligent contract. Therefore, after the first node device invokes the middleware, the encryption algorithm library corresponding to the first encryption event needs to be searched in the middleware according to the type of the encryption algorithm corresponding to the first transaction data in the first encryption event.
For example, in an intelligent contract, if the type of the encryption algorithm for the first encryption event a is specified to be an asymmetric encryption algorithm, and the first node device triggers the first encryption event a during the operation of the intelligent contract, the middleware is invoked, and then the first node device searches the encryption algorithm library corresponding to the first encryption event a in the middleware according to the type of the encryption algorithm corresponding to the first encryption event a, that is, according to the asymmetric encryption algorithm, and since the type of the encryption algorithm corresponding to the first encryption event a is the asymmetric encryption algorithm, the encryption algorithm library searched by the first node device in the middleware is the asymmetric encryption algorithm library.
S203: the first node device calls the encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext.
Specifically, the first node device calls the encryption algorithm library according to the encryption algorithm library corresponding to the first encryption event searched in the middleware, so that the encryption algorithm in the called encryption algorithm library encrypts the first transaction data to obtain a first ciphertext, wherein the first ciphertext is the transaction data after encryption processing.
For example, the first node device finds that the encryption algorithm library corresponding to the first encryption event a is an asymmetric encryption algorithm library in S202, and if the asymmetric encryption algorithm library corresponding to the first encryption event a is specified as the RSA algorithm in S201, the first node device encrypts the first transaction data a by using the RSA algorithm in the asymmetric encryption algorithm library when calling the asymmetric encryption algorithm library corresponding to the first encryption event a, so as to obtain a first ciphertext a, where the first ciphertext a is the transaction data obtained by encrypting the first transaction data a.
In the embodiment of the application, in the process of running the intelligent contract, if the first encryption event is triggered, the first node device invokes the middleware, searches for an encryption algorithm library corresponding to the first encryption event in the middleware, and finally invokes the encryption algorithm library to encrypt the first transaction data to obtain the first ciphertext. In this way, the encryption algorithm used is specified in one type of encryption algorithm library, that is, when the first node device calls one type of encryption algorithm library in the middleware, it is determined that the first transaction data is encrypted by using the specific encryption algorithm in the encryption algorithm library, so that if the encryption algorithm is modified, the encryption algorithm in the encryption algorithm library can be directly modified, and the workload of modifying the encryption algorithm can be reduced.
Referring to fig. 3, fig. 3 is a block diagram illustrating another data encryption method proposed in the embodiment of the present application on the basis of the embodiment shown in fig. 2, which may include, but is not limited to: S301-S306.
S301: the first node device receives update information of the target encryption algorithm.
The target encryption algorithm is a symmetric encryption algorithm or an asymmetric encryption algorithm or a Hash algorithm, the middleware comprises three encryption algorithm libraries, each encryption algorithm library defines a corresponding encryption algorithm, namely the first node equipment calls one encryption algorithm library to determine that the encryption algorithm corresponding to the encryption algorithm library is used for encrypting the transaction data. When a user needs to modify the encryption algorithm of the transaction data, the update information of the target encryption algorithm is sent to the first node device, that is, the first node device receives the update information of the target encryption algorithm, the target encryption algorithm corresponds to the encryption algorithm needing to be modified in the encryption algorithm library, and the update information of the target encryption algorithm is used for indicating the first node device to update the encryption algorithm library corresponding to the target encryption algorithm.
In one implementation, the update information of the target encryption algorithm carries a new encryption algorithm, and the new encryption algorithm is an encryption algorithm corresponding to the updated target encryption algorithm.
In one implementation manner, the update information of the target encryption algorithm carries an identifier of a new encryption algorithm, and after receiving the update information of the target encryption algorithm, the node device may determine the new encryption algorithm according to the carried identifier of the new encryption algorithm, so as to modify the target encryption algorithm into the new encryption algorithm.
S302: the first node device determines a target configuration file corresponding to a target encryption algorithm in the at least one configuration file.
The middleware includes at least one configuration file, and the at least one configuration file includes a configuration file of a symmetric encryption algorithm or a configuration file of an asymmetric encryption algorithm or a configuration file of a hash algorithm, that is, the middleware may include one or two or three of a configuration file of a symmetric encryption algorithm, a configuration file of an asymmetric encryption algorithm and a configuration file of a hash algorithm, which is not limited herein, for example, the middleware only includes a configuration file of a hash algorithm, or the middleware includes a configuration file of a symmetric encryption algorithm and a configuration file of an asymmetric encryption algorithm, and so on. The configuration file specifies the encryption algorithm in the encryption algorithm library, for example, the configuration file of the symmetric encryption algorithm specifies the encryption algorithm used in the symmetric encryption algorithm library as the DES algorithm, the configuration file of the asymmetric encryption algorithm specifies the encryption algorithm used in the asymmetric encryption algorithm library as the RSA algorithm, and the configuration file of the hash algorithm specifies the encryption algorithm used in the hash algorithm library as the SHA512 algorithm.
The first node device receives the update information of the target encryption algorithm, which means that the target encryption algorithm needs to be modified, and the modification of the target encryption algorithm needs to modify the target encryption algorithm in the target encryption algorithm library through the target configuration file because the target encryption algorithm is the encryption algorithm in the encryption algorithm library specified in the configuration file, so that the first node device needs to determine the target configuration file corresponding to the target encryption algorithm in at least one configuration file. For example, if the target encryption algorithm is a hash algorithm, the first node device determines that a target configuration file corresponding to the hash algorithm is a hash configuration file in at least one configuration file in the middleware.
The first node device determines a target configuration file corresponding to the target encryption algorithm in the at least one configuration file, and determines an update path of the target encryption algorithm, namely the target configuration file.
S303: and the first node equipment updates the target encryption algorithm library corresponding to the target encryption algorithm based on the updating information through the target configuration file to obtain the updated target encryption algorithm library.
The configuration file specifies the encryption algorithm in each encryption algorithm library, and after the first node device determines the target configuration file corresponding to the target encryption algorithm, the target encryption algorithm library corresponding to the target encryption algorithm is updated through the target configuration file based on the update information, so that the updated target encryption algorithm library is obtained. The updated encryption algorithm in the target encryption algorithm library is a new encryption algorithm, that is, the first node device modifies the encryption algorithm in the target encryption algorithm library into the new encryption algorithm through the target configuration file, so as to update the target encryption algorithm library.
Illustratively, the target encryption algorithm is a hash algorithm, the target configuration file determined by the first node device is a hash configuration file, and the new encryption algorithm carried by the update information is an SHA224 algorithm, so that the first node device updates the hash algorithm library by changing an SHA512 algorithm in the hash algorithm library corresponding to the hash algorithm into an SHA224 algorithm based on the update information through the hash configuration file, so as to obtain an updated hash algorithm library, the encryption algorithm in the updated hash algorithm library is an SHA224 algorithm, and when the first node device calls the updated hash algorithm library in the middleware, the SHA224 algorithm in the updated hash algorithm library encrypts the transaction data.
The node equipment updates the target encryption algorithm library through the target configuration file to obtain an updated target encryption algorithm library, namely, the encryption algorithm in the target encryption algorithm library is updated, and when the target encryption algorithm library is called subsequently, the transaction data can be encrypted by using the encryption algorithm in the updated target encryption algorithm library.
S304: and in the process of running the intelligent contract, the first node equipment calls the middleware if a second encryption event is triggered.
The second encryption event indicates that second transaction data is encrypted, the second transaction data being transaction data that requires encryption by the first node device. In an implementation manner, the second encryption event is the first encryption event in S201, the second transaction data is the first transaction data, and before the first encryption event is triggered, the first node device receives the update information of the target encryption algorithm, and updates the target encryption algorithm library according to the update information through the target configuration file, so as to obtain an updated target encryption algorithm library.
In one implementation manner, the second encryption event is an encryption event after the first encryption event, and after the first node device triggers the first encryption event, the first node device receives update information of the target encryption algorithm, and updates the target encryption database according to the update information through the target configuration file, so as to obtain an updated target encryption database.
After the target encryption database is updated, if a second encryption event is triggered in the process of running the intelligent contract and indicates that encryption processing needs to be performed on second transaction data indicated by the second encryption event, the first node equipment calls the middleware. The middleware comprises a symmetric encryption algorithm library, an asymmetric encryption algorithm library and a Hash algorithm library, and the encryption algorithm in each encryption algorithm library can encrypt the second transaction data, so that the middleware is called when the first node equipment triggers a second encryption event, and the encryption processing of the second transaction data can be realized.
S305: and the first node equipment searches the updated target encryption algorithm library corresponding to the second encryption event in the middleware.
Specifically, after the first node device invokes the middleware, the updated target encryption algorithm library corresponding to the second encryption event is searched for in the middleware, that is, when the first node device invokes the middleware after updating the target encryption algorithm library, the updated target encryption algorithm library corresponding to the second encryption event is determined, so that the second transaction data is encrypted by using the encryption algorithm in the updated target encryption algorithm library subsequently. For example, in the intelligent contract, the encryption algorithm corresponding to the second encryption event specified in advance is a hash algorithm, the target encryption algorithm library is a hash algorithm library, and when the first node device calls the middleware, the updated target encryption algorithm library corresponding to the second encryption event is searched in the middleware and is the updated hash algorithm library.
S306: and the first node equipment calls the updated target encryption algorithm library to encrypt the second transaction data to obtain a second ciphertext.
And after the first node equipment determines the updated target encryption algorithm library corresponding to the second encryption event, calling the updated target encryption algorithm library to encrypt the second transaction data by using the encryption algorithm in the updated target encryption algorithm library to obtain a second ciphertext, wherein the second ciphertext is the transaction data obtained after the first node equipment encrypts the second transaction data by using the encryption algorithm in the updated target encryption algorithm library.
For example, the updated target encryption algorithm library is an updated hash algorithm library as shown in S305, so that the node device calls the updated hash algorithm library to encrypt the second transaction data by using the SHA224 algorithm in the updated hash algorithm library to obtain the second ciphertext.
In the embodiment of the application, the first node device updates the target encryption algorithm library according to the update information of the target encryption algorithm through the configuration file, calls the middleware when a second encryption event is triggered after the target encryption algorithm library is updated, and encrypts second transaction data by calling the encryption algorithm in the updated target encryption algorithm library in the middleware to obtain a second ciphertext. In the method, the first node device modifies the encryption algorithm in the target encryption algorithm library directly through the configuration file based on the updating information to complete updating of the target encryption algorithm library, so that the workload of changing the encryption algorithm is reduced, and meanwhile, when a second encryption event is triggered after the updated target encryption algorithm library is obtained, the updated target encryption algorithm library in the middleware is called, and the second transaction data is encrypted by using the encryption algorithm in the updated target encryption algorithm library, namely, the encryption algorithm for encrypting the second transaction data is different from the encryption algorithm for encrypting the first transaction data.
Fig. 4 is a step that may be further executed after S203, including: s401-406.
S401: and the first node equipment sends the first transaction data and the first ciphertext to each second node equipment in the blockchain network.
The second node devices are node devices in the blockchain network except the first node device, and the first node device sends the first transaction data and the first ciphertext to each second node device in the blockchain network, so that each second node device can decrypt the first ciphertext.
S402: and each second node device decrypts the first ciphertext to obtain third transaction data.
Before encrypting the first transaction data, the first node device and each second node device define an encryption algorithm for encrypting the first transaction data, so that after each second node device receives the first ciphertext, each second node device can decrypt the first ciphertext by using the encryption algorithm defined in advance to obtain third transaction data.
In one implementation, if the second node device fails to decrypt the first ciphertext by using the encryption algorithm specified in advance, it is indicated that the first node device uses the encryption algorithm inconsistent with the specification in advance, or the first ciphertext is tampered by the malicious node device in the process of sending the first ciphertext to the second node device, so that the second node device sends notification information of the failure to decrypt the first ciphertext to the first node device to prompt the first node device to check the encryption algorithm for encrypting the first transaction data, or to re-encrypt the first transaction data. The second node device sends the notification information of the failure of decrypting the first ciphertext to the first node device, so that the correctness of the first ciphertext can be ensured, and the safety of the first ciphertext can be improved.
S403: and each second node device verifies the third transaction data according to the first transaction data to obtain a verification result.
The third verification data is obtained by decrypting the first ciphertext by the second node device, and the first ciphertext is obtained by encrypting the first transaction data by the first node device, so that each second node device can verify the third transaction data according to the first transaction data, and if the third transaction data obtained by decrypting each second node device is the same as the first transaction data, the third transaction data is verified to be passed. Whether the second node device passes or fails the verification of the third transaction data, a verification result related to the third transaction data is obtained, and the verification result indicates that the second node device passes or fails the verification of the third transaction data, that is, the verification result may be a verification pass or a verification fail.
S404: and the first node equipment receives the verification result and the third transaction data sent by each second node equipment.
After the verification of the third transaction data by each second node device is completed and a verification result is generated, the verification result and the third transaction data are sent to the first node device, and therefore the first node device receives the verification result and the third transaction data sent by each second node device. And whether the second node equipment passes or fails to check the third check data, the check result and the third transaction data are sent to the first node equipment, so that the first node equipment can commonly identify the third transaction data according to the check result.
In one implementation manner, after the second node device passes the verification of the third transaction data, the verification result and the third transaction data are sent to the first node device, that is, the verification results received by the first node device are both verification results that pass the verification. Optionally, the second node device sends the verification result to the first node device only when the third transaction data is not verified, that is, the verification results received by the first node device are all verification results that are not verified. The method can enable the first node device to determine whether the third transaction data passes the consensus or not according to the number of the received verification results.
In one implementation manner, each second node device sends the verification result and the third transaction data to all node devices except the node device, so that each node device can commonly identify the third transaction data according to the verification result. The mode can enable each node device to determine whether to execute the transaction according to the third transaction data according to the consensus result of the node device on the third transaction data.
Illustratively, the first node device is a node device a, the second node devices include a node device B, a node device C and a node device D, when the node device B, the node device C and the node device D complete the verification of the third verification data, the node device B sends the verification result B and the third transaction data for the third transaction data to the node device a, the node device C and the node device D, the node device C sends the verification result C and the third transaction data for the third transaction data to the node device a, the node device B and the node device D, the node device D sends the verification result D and the third transaction data for the third transaction data to the node device a, the node device B and the node device C, so that each second node device except the first node device receives the verification result of the second node device except the first node device, and the first node device can perform consensus on the third transaction data according to the verification result and the third transaction data from the second node devices, and the second node devices can perform consensus on the third transaction data according to the second node devices and the third transaction data.
S405: and the first node equipment identifies the third transaction data according to each verification result.
Specifically, the first node device identifies the third transaction data according to the number of the verification results that are passed or the number of the verification results that are failed.
In one implementation manner, the first node device determines that each check result is the number of passed checks; and if the number of the passed verification is larger than a first preset threshold value, the first node equipment commonly identifies the third transaction data, and the first preset threshold value is preset by all the node equipment in the block chain network. The first preset threshold may be one half of the total number of each node device in the blockchain network, and optionally, the first preset threshold may also be two thirds of the total number of each node device in the blockchain network, and so on, which is not limited herein. For example, the first preset threshold is one half of the total number of each node device in the blockchain network, the total number of the node devices in the blockchain network is 127, and the first node device determines that the number of the check results that pass the check is 75 in all the received check results, and then in all the check results, if the number of the check results that pass the check is greater than the first preset threshold, that is, greater than one half of the total number of all the node devices, the first node device recognizes the third transaction data.
In one implementation manner, the first node device determines that each check result is the number of failed checks; if the number of failed checks is greater than a second preset threshold, the first node device does not recognize the third transaction data together, where the second preset threshold is preset in advance for each node device in the blockchain network, the second preset threshold may be one third of the total number of each node device in the blockchain network, optionally, the second preset threshold may also be two thirds of the total number of each node device in the blockchain network, and so on. The second preset threshold may be the same as or different from the first preset threshold, and is not limited herein. For example, the second preset threshold is two-thirds of the total number of all node devices in the blockchain network, the total number of all node devices is 218, the number of failed verifications determined by the first node device in the received verification result is 169, and in all the verification results, if the number of failed verifications is greater than the second preset threshold, that is, greater than two-thirds of the total number of all node devices, the first node device does not pass the third transaction data consensus.
In one implementation manner, the first node device determines that each check result is the number of passed checks and each check result is the number of failed checks; and if the number of passed checks is larger than the number of failed checks, the first node equipment agrees with the third transaction data. For example, 261 verification results are received by the first node device, the number of verification results determined in all the verification results is 184 verification passed, the number of verification results is 77 verification failed, and the number of verification results determined is that the number of verification passed is greater than the number of verification results that are verification failed, so that the first node device agrees with the third transaction data.
In an implementation manner, if the second node device sends the verification result and the third transaction data to the first node device only when the third transaction data is verified to pass, when the number of the received verification results is greater than a first preset threshold, the first node device passes the third transaction data in a consensus, and the first preset threshold is as described above and is not described again; or if the second node device sends the verification result and the third transaction data to the first node device only under the condition that the verification of the third transaction data is failed, when the number of the received verification results is greater than a second preset threshold, the first node device does not pass the consensus of the third transaction data, and if the second preset threshold is the same, the repeated description is omitted.
In an implementation manner, each second node device sends the verification result of the node device and the third transaction data to each second node device except the node device, each second node device may also perform consensus on the third transaction data according to the received verification result, and the consensus method of each second node device on the third transaction data is the same as the consensus method of the first node device on the third transaction data, which is not described herein again.
S406: and if the third transaction data is agreed, the first node equipment executes the transaction according to the third transaction data.
If the first node device agrees with the third transaction data, which indicates that the third transaction data is reliable transaction data, that is, the first transaction data is encrypted and decrypted, and the obtained third transaction data is reliable data and is not tampered by a malicious node, the first node device may execute a transaction according to the third transaction data, and the transaction executed by the first node device may be uplink processing of the third transaction data, or may be conversion algorithm processing of the third transaction data to obtain other transaction data, and so on.
In an implementation manner, when any one of the second node devices agrees with the third transaction data, if the any one of the second node devices agrees with the third transaction data, the second node device may execute the transaction according to the third transaction data.
In the embodiment of the application, the first node device sends the first transaction data and the first ciphertext to each second node device, each second node device decrypts the first ciphertext to obtain third transaction data, verifies the third transaction data according to the first transaction data to obtain a verification result, the first node device performs consensus on the third transaction data according to each verification result and the third transaction data from the second node device, and if the consensus on the third transaction data is passed, the first node device executes transaction according to the third transaction data. The first node device executes the transaction according to the third transaction data after the third transaction data is commonly identified, so that the reliability of the transaction can be improved.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a node device according to an embodiment of the present invention, where the node device may be applied in a first node device, the node device 50 includes a processor 501, a memory 502, and a communication interface 503, and the processor 501, the memory 502, and the communication interface 503 are connected through one or more communication buses.
The processor 501 is configured to support the first node device to perform the corresponding functions of the first node device in the embodiments shown in fig. 2, fig. 3 and fig. 4. The processor 501 may be a Central Processing Unit (CPU), a Network Processor (NP), a hardware chip, or any combination thereof.
The memory 502 is used to store program codes and the like. Memory 502 may include volatile memory (volatile), such as Random Access Memory (RAM); the memory 502 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a Hard Disk Drive (HDD), or a solid-state drive (SSD); the memory 502 may also comprise a combination of memories of the kind described above.
The communication interface 503 is configured to receive and transmit data, for example, the communication interface 503 is configured to transmit the first transaction data and the first ciphertext to each second node device in the blockchain network, or the communication interface 503 is configured to receive the check result and the third transaction data transmitted by each second node device.
In the embodiment of the present invention, the first node device 50 includes a plurality of communication interfaces, wherein the communication interface for transmitting data and the communication interface for receiving data may not be the same communication interface.
The processor 501 may call the program code stored in the memory 502 to perform the following operations:
in the process of running the intelligent contract, if a first encryption event is triggered, invoking a middleware, wherein the first encryption event indicates that first transaction data is encrypted, and the middleware comprises an encryption algorithm library;
the processor 501 searches an encryption algorithm library corresponding to the first encryption event in the middleware;
the processor 501 calls the encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext.
In one implementation, the middleware includes at least one configuration file, the at least one configuration file includes a configuration file of a symmetric encryption algorithm or a configuration file of an asymmetric encryption algorithm or a configuration file of a hash algorithm, and the processor 501 receives update information of a target encryption algorithm, where the target encryption algorithm is a symmetric encryption algorithm or an asymmetric encryption algorithm or a hash algorithm; the processor 501 determines a target configuration file corresponding to a target encryption algorithm in at least one configuration file; the processor 501 updates the target encryption algorithm library corresponding to the target encryption algorithm based on the update information through the target configuration file, so as to obtain an updated target encryption algorithm library.
In one implementation, after the processor 501 updates the target encryption algorithm library corresponding to the target encryption algorithm based on the update information through the target configuration file to obtain an updated target encryption algorithm library, the following operations may be further performed:
in the process of running the intelligent contract, if a second encryption event is triggered, the processor 501 invokes middleware, wherein the second encryption event indicates that second transaction data is encrypted; the processor 501 searches for an updated target encryption algorithm library corresponding to the second encryption event in the middleware; the processor 501 calls the updated target encryption algorithm library to encrypt the second transaction data to obtain a second ciphertext.
In one implementation, after the processor 501 calls the encryption algorithm library to encrypt the first transaction data to obtain the first ciphertext, the following operations may be further performed:
the processor 501 sends the first transaction data and the first ciphertext to each second node device in the blockchain network, so that after each second node device decrypts the first ciphertext to obtain third transaction data, the third transaction data is verified according to the first transaction data to obtain a verification result, and the second node devices are the node devices in the blockchain network except the first node device; the processor 501 receives the verification result and the third transaction data sent by each second node device; the processor 501 performs consensus on the third transaction data according to each verification result; if the processor 501 agrees with the third transaction data, the transaction is executed according to the third transaction data.
In one implementation, the processor 501 performs consensus on the third transaction data according to each verification result, and specifically performs the following operations:
the processor 501 determines that each check result is the number of passed checks; if the number of verification passes is greater than the first preset threshold, the processor 501 agrees with the third transaction data.
In one implementation, the processor 501 performs consensus on the third transaction data according to each verification result, and specifically performs the following operations:
the processor 501 determines that each check result is the number of failed checks; if the number of failed checks is greater than the second preset threshold, the processor 501 recognizes that the third transaction data is failed.
In one implementation, the processor 501 performs consensus on the third transaction data according to each verification result, and specifically performs the following operations:
the processor 501 determines that each check result is the number of passed checks and each check result is the number of failed checks; if the number of passed checks is greater than the number of failed checks, the processor 501 agrees with the third transaction data.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a data encryption apparatus according to an embodiment of the present invention, where the data encryption apparatus may be disposed in a first node device, and the data encryption apparatus 60 may include:
a calling unit 601, configured to, in a process of running an intelligent contract, if a first encryption event is triggered, call a middleware, where the first encryption event indicates to encrypt first transaction data, and the middleware includes an encryption algorithm library;
a searching unit 602, configured to search, in the middleware, an encryption algorithm library corresponding to the first encryption event;
the invoking unit 601 is configured to invoke the encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext.
In one implementation, the middleware includes at least one configuration file, the at least one configuration file includes a configuration file of a symmetric encryption algorithm or a configuration file of an asymmetric encryption algorithm or a configuration file of a hash algorithm, and the data encryption apparatus further includes:
a communication unit 603, configured to receive update information of a target encryption algorithm, where the target encryption algorithm is a symmetric encryption algorithm or an asymmetric encryption algorithm or a hash algorithm;
the searching unit 602 is further configured to determine a target configuration file corresponding to the target encryption algorithm in the at least one configuration file;
an updating unit 604, configured to update, based on the update information, the target encryption algorithm library corresponding to the target encryption algorithm through the target configuration file, so as to obtain an updated target encryption algorithm library.
In an implementation manner, the updating unit 604 updates the target encryption algorithm library corresponding to the target encryption algorithm based on the update information through the target configuration file to obtain an updated target encryption algorithm library, and then the invoking unit 601 is further configured to invoke the middleware if a second encryption event is triggered, where the second encryption event indicates to encrypt the second transaction data; the searching unit 602 is further configured to search, in the middleware, an updated target encryption algorithm library corresponding to the second encryption event; the invoking unit 601 is further configured to invoke the updated target encryption algorithm library to encrypt the second transaction data to obtain a second ciphertext.
In an implementation manner, the invoking unit 601 invokes an encryption algorithm library to encrypt first transaction data to obtain a first ciphertext, and then the communication unit 603 is further configured to send the first transaction data and the first ciphertext to each second node device in the blockchain network, so that each second node device performs verification on the third transaction data according to the first transaction data after decrypting the first ciphertext to obtain third transaction data to obtain a verification result, and the second node device is a node device in the blockchain network except the first node device; the communication unit 603 is further configured to receive the verification result and the third transaction data sent by each second node device; a consensus unit 605, configured to perform consensus on the third transaction data according to each verification result; an executing unit 606, configured to execute the transaction according to the third transaction data if the third transaction data is agreed.
In one implementation manner, the determining unit 606 is configured to determine that each verification result is the number of passed verifications; the consensus unit 605 is further configured to agree on the third transaction data if the number of passes is greater than the first preset threshold.
In one implementation manner, the determining unit 606 is configured to determine that each verification result is the number of failed verifications; the consensus unit 605 is further configured to perform consensus on the third transaction data if the number of verification failures is greater than a second preset threshold.
In an implementation manner, the determining unit 606 is configured to determine that each check result is a number of passed checks and each check result is a number of failed checks; the consensus unit 605 is further configured to agree on the third transaction data if the number of passed checks is larger than the number of failed checks.
The specific implementation of each unit included in the data encryption device provided in the embodiment of the present invention may refer to the description of related content in the foregoing embodiments, which is not repeated herein, and each module in the data encryption device shown in fig. 6 may be respectively or completely merged into one or several other modules to form, or some module(s) therein may be further split into multiple modules with smaller functions to form, which may implement the same operation without affecting the implementation of the technical effect of the embodiment of the present application. The modules are divided based on logic functions, and in practical application, the functions of one module can be realized by a plurality of modules, or the functions of a plurality of modules can be realized by one module. In other embodiments of the present application, other modules may also be included, and in practical applications, these functions may also be implemented by being assisted by other modules, and may be implemented by cooperation of a plurality of modules, which is not limited in this application.
An embodiment of the present invention further provides a computer-readable storage medium, which can be used to store computer software instructions for the first node device in the embodiments shown in fig. 2, fig. 3, and fig. 4, and which contains a program designed for the first node device in the foregoing embodiments.
The computer readable storage medium includes, but is not limited to, flash memory, hard disk, solid state disk.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (10)
1. A data encryption method is applied to a first node device and comprises the following steps:
in the process of running the intelligent contract, if a first encryption event is triggered, invoking a middleware, wherein the first encryption event indicates that first transaction data is encrypted, and the middleware comprises an encryption algorithm library;
searching an encryption algorithm library corresponding to the first encryption event in the middleware;
and calling the encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext.
2. The method of claim 1, wherein the middleware comprises at least one profile, wherein the at least one profile comprises a profile for a symmetric encryption algorithm or a profile for an asymmetric encryption algorithm or a profile for a hashing algorithm, and wherein the method further comprises:
receiving update information of a target encryption algorithm, wherein the target encryption algorithm is a symmetric encryption algorithm or an asymmetric encryption algorithm or a Hash algorithm;
determining a target configuration file corresponding to the target encryption algorithm in the at least one configuration file;
and updating the target encryption algorithm library corresponding to the target encryption algorithm based on the updating information through the target configuration file to obtain an updated target encryption algorithm library.
3. The method according to claim 2, wherein after the updating, by the target configuration file, the target encryption algorithm library corresponding to the target encryption algorithm based on the update information to obtain an updated target encryption algorithm library, the method further comprises:
in the process of running the intelligent contract, if a second encryption event is triggered, the middleware is called, and the second encryption event indicates that second transaction data are encrypted;
searching the updated target encryption algorithm library corresponding to the second encryption event in the middleware;
and calling the updated target encryption algorithm library to encrypt the second transaction data to obtain a second ciphertext.
4. The method of any of claim 1, wherein said invoking said encryption algorithm library to encrypt said first transaction data to obtain a first ciphertext, further comprises:
sending the first transaction data and the first ciphertext to each second node device in the blockchain network, so that after each second node device decrypts the first ciphertext to obtain third transaction data, the third transaction data is verified according to the first transaction data to obtain a verification result, and the second node devices are the node devices except the first node device in the blockchain network;
receiving the verification result and the third transaction data sent by each second node device;
performing consensus on the third transaction data according to each verification result;
and if the third transaction data is agreed, executing the transaction according to the third transaction data.
5. The method of claim 4, wherein said consensus on said third transaction data based on said respective verification results comprises:
determining the number of the verification results as verification passes;
and if the number of the verification passes is larger than a first preset threshold value, the third transaction data are identified to pass.
6. The method of claim 4, wherein said consensus on said third transaction data based on said respective verification results comprises:
determining the number of failed verification results as the number of failed verification;
and if the number of failed verification is larger than a second preset threshold value, the third transaction data is identified and failed.
7. The method of claim 4, wherein said consensus on said third transaction data based on said respective verification results comprises:
determining the number of passed checks and the number of failed checks as the check results;
and if the number of passed checks is larger than the number of failed checks, the third transaction data is agreed to pass.
8. A node device comprising a processor and a memory, the processor and the memory being coupled, wherein the memory is configured to store a computer program comprising program instructions, and wherein the processor is configured to invoke the program instructions to perform the method of any one of claims 1-7.
9. An apparatus for encrypting data, the apparatus comprising:
the intelligent contract processing method comprises a calling unit, a processing unit and a processing unit, wherein the calling unit is used for calling a middleware if a first encryption event is triggered in the process of operating an intelligent contract, the first encryption event indicates that first transaction data are encrypted, and the middleware comprises an encryption algorithm library;
the searching unit is used for searching the encryption algorithm library corresponding to the first encryption event in the middleware;
and the calling unit is used for calling the encryption algorithm library to encrypt the first transaction data to obtain a first ciphertext.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010090219.0A CN111310206A (en) | 2020-02-12 | 2020-02-12 | Data encryption method, node equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010090219.0A CN111310206A (en) | 2020-02-12 | 2020-02-12 | Data encryption method, node equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111310206A true CN111310206A (en) | 2020-06-19 |
Family
ID=71148966
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010090219.0A Pending CN111310206A (en) | 2020-02-12 | 2020-02-12 | Data encryption method, node equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111310206A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112835854A (en) * | 2021-02-01 | 2021-05-25 | 北京百度网讯科技有限公司 | File storage method and device, electronic equipment and storage medium |
| CN112953715A (en) * | 2021-01-27 | 2021-06-11 | 北京众享比特科技有限公司 | Method for dynamically identifying cryptographic algorithm by block chain node points |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103475463A (en) * | 2013-08-19 | 2013-12-25 | 华为技术有限公司 | Encryption realization method and apparatus |
| WO2016209326A1 (en) * | 2015-03-30 | 2016-12-29 | Airbnb, Inc. | Database encryption to provide write protection |
| US20170171170A1 (en) * | 2015-12-09 | 2017-06-15 | Xasp Security, Llc | Dynamic encryption systems |
| CN106909411A (en) * | 2015-12-23 | 2017-06-30 | 中国移动通信集团江苏有限公司 | A kind of file updating method and device |
| CN107277591A (en) * | 2017-06-16 | 2017-10-20 | 深圳市亿联智能有限公司 | A kind of method that pattern of fusion set top box is encrypted by OTG modes |
| CN107294955A (en) * | 2017-05-24 | 2017-10-24 | 创元网络技术股份有限公司 | E-file encrypts middleware managing and control system and method |
| CN108768607A (en) * | 2018-05-14 | 2018-11-06 | 中钞信用卡产业发展有限公司杭州区块链技术研究院 | A kind of voting method, device, equipment and medium based on block chain |
| CN109313685A (en) * | 2016-06-06 | 2019-02-05 | 微软技术许可有限责任公司 | The encryption application of block catenary system |
| CN109829013A (en) * | 2018-12-27 | 2019-05-31 | 上海点融信息科技有限责任公司 | For running the method for intelligent contract in block chain network, storage medium, calculating equipment |
| CN109995536A (en) * | 2019-03-15 | 2019-07-09 | 广州杰赛科技股份有限公司 | A kind of block chain common recognition method, apparatus and readable storage medium storing program for executing |
-
2020
- 2020-02-12 CN CN202010090219.0A patent/CN111310206A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103475463A (en) * | 2013-08-19 | 2013-12-25 | 华为技术有限公司 | Encryption realization method and apparatus |
| WO2016209326A1 (en) * | 2015-03-30 | 2016-12-29 | Airbnb, Inc. | Database encryption to provide write protection |
| US20170171170A1 (en) * | 2015-12-09 | 2017-06-15 | Xasp Security, Llc | Dynamic encryption systems |
| CN106909411A (en) * | 2015-12-23 | 2017-06-30 | 中国移动通信集团江苏有限公司 | A kind of file updating method and device |
| CN109313685A (en) * | 2016-06-06 | 2019-02-05 | 微软技术许可有限责任公司 | The encryption application of block catenary system |
| CN107294955A (en) * | 2017-05-24 | 2017-10-24 | 创元网络技术股份有限公司 | E-file encrypts middleware managing and control system and method |
| CN107277591A (en) * | 2017-06-16 | 2017-10-20 | 深圳市亿联智能有限公司 | A kind of method that pattern of fusion set top box is encrypted by OTG modes |
| CN108768607A (en) * | 2018-05-14 | 2018-11-06 | 中钞信用卡产业发展有限公司杭州区块链技术研究院 | A kind of voting method, device, equipment and medium based on block chain |
| CN109829013A (en) * | 2018-12-27 | 2019-05-31 | 上海点融信息科技有限责任公司 | For running the method for intelligent contract in block chain network, storage medium, calculating equipment |
| CN109995536A (en) * | 2019-03-15 | 2019-07-09 | 广州杰赛科技股份有限公司 | A kind of block chain common recognition method, apparatus and readable storage medium storing program for executing |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112953715A (en) * | 2021-01-27 | 2021-06-11 | 北京众享比特科技有限公司 | Method for dynamically identifying cryptographic algorithm by block chain node points |
| CN112953715B (en) * | 2021-01-27 | 2023-03-14 | 北京众享比特科技有限公司 | Method for dynamically identifying cryptographic algorithm by block chain node points |
| CN112835854A (en) * | 2021-02-01 | 2021-05-25 | 北京百度网讯科技有限公司 | File storage method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113438289B (en) | Block chain data processing method and device based on cloud computing | |
| EP3937046B1 (en) | Trusted startup methods and apparatuses of blockchain integrated station | |
| CN110008735B (en) | Method, node and storage medium for realizing contract calling in block chain | |
| CN109886682B (en) | Method, node and storage medium for realizing contract calling in block chain | |
| CN111047450A (en) | Method and device for calculating down-link privacy of on-link data | |
| US11616636B2 (en) | Hash updating methods and apparatuses of blockchain integrated station | |
| CN110032885B (en) | Method, node and storage medium for implementing privacy protection in block chain | |
| US20210328810A1 (en) | Methods and apparatuses for processing transactions based on blockchain integrated station | |
| CN110263544B (en) | Receipt storage method and node combining transaction type and judgment condition | |
| CN110020549B (en) | Method, node and storage medium for implementing privacy protection in block chain | |
| CN110245947B (en) | Receipt storage method and node combining conditional restrictions of transaction and user types | |
| CN110245945B (en) | Receipt storage method and node combining code marking and user type | |
| JP5777810B2 (en) | Secure host execution architecture | |
| CN110020856B (en) | Method, node and storage medium for realizing mixed transaction in block chain | |
| CN110245942B (en) | Receipt storage method and node combining user type and judgment condition | |
| CN111612462B (en) | Method, node and storage medium for implementing privacy protection in blockchain | |
| CN110263543B (en) | Object-level receipt storage method and node based on code labeling | |
| AU2013277539B2 (en) | Network based management of protected data sets | |
| CN111639362B (en) | Method, node and storage medium for implementing privacy protection in blockchain | |
| CN110245943B (en) | Receipt storage method and node based on judgment condition | |
| CN110033265B (en) | Method, node and storage medium for implementing privacy protection in block chain | |
| US12010249B1 (en) | Method and device for zero-trust fusion computation of multi-party data | |
| CN111310206A (en) | Data encryption method, node equipment and storage medium | |
| CN115409619A (en) | Data processing method based on block chain and block chain link point device | |
| WO2024027598A1 (en) | Data transmission method and apparatus, storage medium, and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40024707 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |