CN113472512A - Intelligent contract execution method and device, storage medium and electronic equipment - Google Patents
Intelligent contract execution method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN113472512A CN113472512A CN202110648090.5A CN202110648090A CN113472512A CN 113472512 A CN113472512 A CN 113472512A CN 202110648090 A CN202110648090 A CN 202110648090A CN 113472512 A CN113472512 A CN 113472512A
- Authority
- CN
- China
- Prior art keywords
- resource
- contract
- binary
- homomorphic
- target
- 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 45
- 230000006870 function Effects 0.000 claims abstract description 50
- 230000004044 response Effects 0.000 claims abstract description 7
- 238000005192 partition Methods 0.000 claims description 36
- 239000012634 fragment Substances 0.000 claims description 34
- 238000004364 calculation method Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 12
- 238000006243 chemical reaction Methods 0.000 claims description 8
- 238000011161 development Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000004891 communication Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000000638 solvent extraction Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000000126 substance Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/008—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving homomorphic encryption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Abstract
The present disclosure relates to an intelligent contract execution method, apparatus, storage medium and electronic device, the method comprising: in response to receiving a contract calling request, determining a functional requirement corresponding to the contract calling request according to a calling parameter in the contract calling request; acquiring a binary resource corresponding to the function requirement from a block chain, wherein the binary resource is obtained by converting a third-party function component; converting the acquired binary resource into an executable file; and executing the executable file to meet the functional requirement. In this way, when the related functional requirements are met, the corresponding functional code does not need to be written in the intelligent contract, and the function can be realized by calling the binary resource of the third-party functional component. That is to say, the functions of the intelligent contract can be enriched through the technical scheme.
Description
Technical Field
The present disclosure relates to the field of block chain technologies, and in particular, to an intelligent contract execution method and apparatus, a storage medium, and an electronic device.
Background
Blockchain technology is a technology that can collectively maintain a reliable database through decentralized and distrust. In a blockchain network, contract participants may formulate a series of intelligent contracts. In this way, after contract deployment, relevant operations may be automatically performed by the contract to implement the corresponding functionality.
However, the smart box also faces difficulties in practical applications. For example, smart contracts also have the technical problem of being less functional due to the limiting factors of development language, contract capacity, and the like.
Disclosure of Invention
The present disclosure is directed to a method, an apparatus, a storage medium, and an electronic device for executing an intelligent contract, so as to solve the above related technical problems.
In order to achieve the above object, according to a first aspect of embodiments of the present disclosure, there is provided an intelligent contract execution method, including:
in response to receiving a contract calling request, determining a functional requirement corresponding to the contract calling request according to a calling parameter in the contract calling request;
acquiring a binary resource corresponding to the function requirement from a block chain, wherein the binary resource is obtained by converting a third-party function component;
converting the acquired binary resource into an executable file;
and executing the executable file to meet the functional requirement.
Optionally, before, in response to receiving a contract invoking request, determining a functional requirement corresponding to the contract invoking request according to an invoking parameter in the contract invoking request, the method further includes:
acquiring the third-party functional component;
converting the executable file of the third-party functional component into a binary resource;
saving the binary resource to a blockchain;
and recording the storage position information of the binary resource.
Optionally, the saving the binary resource to the blockchain includes:
when the capacity of the binary resource is larger than a block capacity threshold value, dividing the binary resource into a plurality of resource fragments;
storing each resource fragment into a blockchain;
the storage location information includes an offset between a block where a target resource partition is located and a block where a last resource partition of the target resource partition is located, where the target resource partition is any resource partition of the plurality of resource partitions except for a first resource partition.
Optionally, the binary resource includes a plurality of resource fragments, the contract includes a homomorphic check field and a homomorphic checksum, the homomorphic check field includes a digital digest of each resource fragment, and the homomorphic checksum is determined by:
aiming at each digital abstract, calculating a ciphertext corresponding to the digital abstract based on a target homomorphic encryption key;
summing each ciphertext to obtain the homomorphic checksum;
before the obtaining the binary resource corresponding to the functional requirement from the block chain, the method further includes:
calculating a target homomorphic check sum according to the owned homomorphic encryption key and the homomorphic check field;
and determining that the target homomorphic checksum is consistent with the homomorphic checksum stored in the contract.
Optionally, the calculating, for each of the digital digests, a ciphertext corresponding to the digital digest based on a homomorphic encryption key includes:
calculating the ciphertext c corresponding to the digital abstract m by the following calculation formulam：
cm＝E(m，r)＝gmrtmodt2，r∈Zn；
The summing each of the ciphertexts comprises: the homomorphic checksum c is calculated by the following calculation:
wherein the target homomorphic encryption key is (t, g, r), i is the quantity value of the digital abstract, and x belongs to [1, i ∈]And x is an integer, mod is a remainder function, ZnIs an integer field.
Optionally, the target homomorphic encryption key is determined by:
randomly determining a first prime number and a second prime number, wherein the digits of the first prime number and the second prime number are the same, and the digits of the first prime number and the second prime number are greater than a digit threshold value;
taking the product of the first prime number and the second prime number as a parameter t in the target homomorphic encryption key;
determining a target random integer as a parameter g in the target homomorphic encryption key, wherein,
and the parameter t divides the order of the parameter g,
the existence of multiplication inverse elements under the residual system;
from ZnWherein a random number is determined as a parameter r in the target homomorphic encryption key.
Optionally, the obtaining the binary resource corresponding to the functional requirement from the blockchain includes:
when the capacity of the binary resource is larger than a memory capacity threshold value, dividing the binary resource into a plurality of binary resource fragments;
and sequentially loading the binary resource fragments into a memory for release.
According to a second aspect of the embodiments of the present disclosure, there is provided an intelligent contract execution apparatus, including:
the determining module is used for responding to the received contract calling request and determining the functional requirement corresponding to the contract calling request according to the calling parameter in the contract calling request;
the resource acquisition module is used for acquiring a binary resource corresponding to the function requirement from the block chain, wherein the binary resource is obtained by converting a third-party function component;
the first resource conversion module is used for converting the acquired binary resource into an executable file;
and the execution module is used for executing the executable file so as to meet the functional requirements.
Optionally, the apparatus further comprises:
a function component acquiring module, configured to acquire the third-party function component before the determining module determines the function requirement corresponding to the contract invoking request;
the second resource conversion module is used for converting the executable file of the third-party functional component into a binary resource;
the resource storage module is used for storing the binary resources into a block chain;
and the recording module is used for recording the storage position information of the binary resource.
Optionally, the resource storage module includes:
a resource partitioning submodule, configured to partition the binary resource into a plurality of resource partitions when the capacity of the binary resource is greater than a block capacity threshold;
the resource storage submodule is used for storing each resource fragment into a block chain;
the storage location information includes an offset between a block where a target resource partition is located and a block where a last resource partition of the target resource partition is located, where the target resource partition is any resource partition of the plurality of resource partitions except for a first resource partition.
Optionally, the binary resource includes a plurality of resource fragments, the contract includes a homomorphic check field and a homomorphic checksum, the homomorphic check field includes a digital digest of each resource fragment, and the homomorphic checksum is determined by: aiming at each digital abstract, calculating a ciphertext corresponding to the digital abstract based on a target homomorphic encryption key; summing each ciphertext to obtain the homomorphic checksum;
the device further comprises:
the calculation module is used for calculating a target homomorphic check sum according to the owned homomorphic encryption key and the homomorphic check field before the resource acquisition module acquires the binary resource corresponding to the functional requirement from the block chain;
and the checksum determining module is used for determining that the target homomorphic checksum is consistent with the homomorphic checksum stored in the contract.
Optionally, the calculating, for each of the digital digests, a ciphertext corresponding to the digital digest based on a homomorphic encryption key includes:
calculating the ciphertext c corresponding to the digital abstract m by the following calculation formulam：
cm＝E(m，r)＝gmrtmodt2，r∈Zn；
The summing each of the ciphertexts comprises: the homomorphic checksum c is calculated by the following calculation:
wherein the target homomorphic encryption key is (t, g, r), i is the quantity value of the digital abstract, and x belongs to [1, i ∈]And x is an integer, mod is a remainder function, ZnIs an integer field.
Optionally, the target homomorphic encryption key is determined by:
randomly determining a first prime number and a second prime number, wherein the digits of the first prime number and the second prime number are the same, and the digits of the first prime number and the second prime number are greater than a digit threshold value;
taking the product of the first prime number and the second prime number as a parameter t in the target homomorphic encryption key;
determining a target random integer as a parameter g in the target homomorphic encryption key, wherein,
and the parameter t divides the order of the parameter g,
the existence of multiplication inverse elements under the residual system;
from ZnWherein a random number is determined as a parameter r in the target homomorphic encryption key.
Optionally, the obtaining the binary resource corresponding to the functional requirement from the blockchain includes:
when the capacity of the binary resource is larger than a memory capacity threshold value, dividing the binary resource into a plurality of binary resource fragments;
and sequentially loading the binary resource fragments into a memory for release.
According to a third aspect of embodiments of the present disclosure, there is provided a non-transitory computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of the method of any one of the above first aspects.
According to a fourth aspect of the embodiments of the present disclosure, there is provided an electronic apparatus including:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to implement the steps of the method of any of the first aspects above.
The technical scheme at least has the following beneficial effects:
by converting the third-party functional component into the binary resource, the obtained binary resource can be stored in the block chain. In this way, after receiving the contract invoking request, the contract executing apparatus may determine the functional requirement corresponding to the contract invoking request according to the invoking parameter in the contract invoking request, and obtain the corresponding binary resource from the block chain according to the functional requirement. After the binary resource is acquired, the acquired binary resource can be converted into an executable file, and the functional requirement is met by executing the executable file. In this way, when the related functional requirements are met, the corresponding functional code does not need to be written in the intelligent contract, and the function can be realized by calling the binary resource of the third-party functional component. That is to say, the functions of the intelligent contract can be enriched through the technical scheme. In addition, the third-party functional component is converted into the binary resource, and the binary resource is converted into the executable file, so that the limitation of the contract development language can be broken through, and the functions of the intelligent contract are further enriched.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description serve to explain the disclosure without limiting the disclosure. In the drawings:
FIG. 1 is a schematic diagram illustrating the execution of a contract according to an exemplary embodiment of the present disclosure.
FIG. 2 is a flowchart illustrating a method for intelligent contract execution, according to an exemplary embodiment of the present disclosure.
FIG. 3 is a flowchart illustrating a method for intelligent contract execution, according to an exemplary embodiment of the present disclosure.
Fig. 4 is a schematic diagram of a data conversion flow shown in an exemplary embodiment of the present disclosure.
Fig. 5 is a block diagram of an intelligent contract execution apparatus according to an exemplary embodiment of the present disclosure.
FIG. 6 is a block diagram of an electronic device shown in an exemplary embodiment of the present disclosure.
Detailed Description
The following detailed description of specific embodiments of the present disclosure is provided in connection with the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present disclosure, are given by way of illustration and explanation only, not limitation.
Before introducing the intelligent contract execution method, apparatus, storage medium, and electronic device of the present disclosure, an application scenario of the present disclosure is first introduced.
An intelligent contract (hereinafter, this disclosure will be referred to as a contract) may be viewed as a protocol that automatically performs tasks that otherwise would need to be performed manually. By constructing and deploying contracts, a variety of operations may be implemented in a blockchain network. However, contracts are subject to many limitations in practical applications, such as limitations in development languages, limitations in contract capacity, and so on, which ultimately results in less functionality that the contracts can implement.
FIG. 1 is a schematic diagram of the execution of one type of contract shown in the present disclosure. In a related scenario, in order for a contract to perform more functions, necessary out-of-chain environment information may be recorded in the blockchain network. Accordingly, the contract may read this information and call the interfaces of the out-of-chain environment to perform the associated operations from the out-of-chain environment. After the out-of-chain environment performs the associated operation, the contract virtual machine may receive the execution result of the out-of-chain environment, thereby completing the contract invocation.
It is noted that such an approach also has a problem of low security since the out-of-chain environment cannot guarantee trust. Moreover, after the off-chain environment changes, the off-chain environment information recorded on the block chain may not be consistent with the actual off-chain environment information, thereby affecting the usability of the contract. In addition, there may be more interference factors in the interaction process of the contract virtual machine with the out-of-chain environment, which also results in reduced availability of the contract.
To this end, the present disclosure provides an intelligent contract execution method. Fig. 2 is a flow chart illustrating a method of intelligent contract execution, as shown in fig. 2, the method comprising:
in step 21, in response to receiving a contract invoking request, determining a functional requirement corresponding to the contract invoking request according to an invoking parameter in the contract invoking request.
The method provided by the embodiment can be applied to a contract execution device. According to the difference of the block chain network, the contract execution device can have corresponding difference. For example, in an ethernet house, the contract execution apparatus may refer to an ethernet house virtual machine, and in an associated alliance chain network, the contract execution apparatus may also be some contract container.
Thus, the receipt of the contract invocation request may refer to the receipt by the contract execution apparatus of the relevant contract invocation parameter. Accordingly, the contract execution apparatus may determine a functional requirement associated with the contract invocation request based on the contract invocation parameter.
It should be understood that the functionality of the contract may be set as desired in the contract-making. These functions may be one or more, such as accessing pictures, performing encryption operations, performing decryption operations, etc., and the present disclosure is not limited in this respect. In particular implementation, the contracts can be called by different calling parameters to execute different functions.
In step 22, a binary resource corresponding to the function requirement is obtained from the blockchain, and the binary resource is obtained by converting the third-party function component.
The third-party functional component may be, for example, a processing tool developed for different application requirements. These third party functional components are often difficult to run directly in the contract execution apparatus due to the restrictions of the contract on the development language. Moreover, the difficulty of writing and realizing the functions of the corresponding third-party functional components through the contract development language is high.
Therefore, in this embodiment, the executable file corresponding to the third-party functional component may be converted into a binary resource, and the binary resource may be stored in the block chain. For example, for a decryption component written in C language, the decryption component may be compiled into an exe executable file, and the exe executable file is converted into a binary resource and stored in a blockchain.
In this way, the binary resource can be acquired from the block chain when the function requirement corresponding to the contract calling request is decryption. For example, in some implementations, the executable file may be embedded in the contract in a binary stream and associated resource location information may be recorded at the time of contract construction. In this case, the binary resource of the exe executable file may be acquired based on resource location information saved in the contract.
In step 23, the acquired binary resource is converted into an executable file.
Following the above example, the retrieved binary resource may be reconverted to an. exe executable file.
Thus, in step 24, the executable file is executed to meet the functional requirements.
For example, the. exe executable file may be executed to implement functionality corresponding to the native decryption component written in the C language.
According to the technical scheme, the third-party functional components are converted into the binary resources, so that the obtained binary resources can be stored in the block chain. In this way, after receiving the contract invoking request, the contract executing apparatus may determine the functional requirement corresponding to the contract invoking request according to the invoking parameter in the contract invoking request, and obtain the corresponding binary resource from the block chain according to the functional requirement. After the binary resource is acquired, the acquired binary resource can be converted into an executable file, and the functional requirement is met by executing the executable file.
In this way, when the related functional requirements are met, the corresponding functional code does not need to be written in the intelligent contract, and the function can be realized by calling the binary resource of the third-party functional component. That is to say, the functions of the intelligent contract can be enriched through the technical scheme. Moreover, the limitation of the contract development language can be broken through by converting the third-party functional component into the binary resource and converting the binary resource into the executable file. For example, in the above embodiment, assuming that the contract development language is the go language, the function corresponding to the decryption component originally written in the C language can also be executed in the contract execution apparatus by using the above technical solution. Therefore, the technical scheme can break through the limitation of the contract development language and provide a foundation for realizing more functions of the contract.
FIG. 3 is a flowchart illustrating a method for intelligent contract execution, as shown in FIG. 3, in an exemplary embodiment of the present disclosure, the method comprising:
and S31, acquiring the third-party functional component. The third-party functional component may be, for example, a processing tool developed for different application requirements, such as a picture access tool, an encryption tool, a decryption tool, and the like.
And S32, converting the executable file of the third-party functional component into a binary resource.
S33, saving the binary resource to the block chain.
For example, for a decryption component written in C language, the decryption component may be compiled into an exe executable file, and the exe executable file is converted into a binary resource and stored in a blockchain.
And S34, recording the storage position information of the binary resource.
Here, the storage location information may be, for example, a hash value of a storage block corresponding to the binary resource. Therefore, when the binary resource needs to be acquired, the corresponding block can be searched according to the hash value, and the binary resource stored in the block can be acquired.
In some possible implementation scenarios, the capacity of the binary resource may also exceed the capacity limit of the block, in which case step S34 further includes:
when the capacity of the binary resource is larger than a block capacity threshold value, the binary resource is divided into a plurality of resource fragments, and each resource fragment is stored in a block chain.
The number of resource shards may be set based on the capacity of the binary resource and the block capacity threshold. When there are multiple resource fragments, in order to facilitate subsequent searching of the resource fragments, the offset between the blocks stored in adjacent resource fragments may be saved. That is, in this case, the storage location information may include an offset between a chunk at which a target resource slice is located and a chunk at which a resource slice immediately preceding the target resource slice is located. The target resource partition is any resource partition except the first resource partition in the plurality of resource partitions.
And S35, responding to the received contract calling request, and determining the function requirement corresponding to the contract calling request according to the calling parameter in the contract calling request.
And S36, acquiring the binary resource corresponding to the function requirement from the block chain.
In a possible implementation, the obtaining the binary resource corresponding to the functional requirement from the blockchain includes:
when the capacity of the binary resource is larger than a memory capacity threshold value, dividing the binary resource into a plurality of binary resource fragments;
and sequentially loading the binary resource fragments into a memory for release.
That is, the contract execution apparatus may first store a part of the binary resources in the memory to release the binary resources, and replace the resources in the memory after the release is completed. By the method, the problem that resources cannot be used due to the limitation of the memory size of the virtual machine can be avoided.
And S37, converting the acquired binary resource into an executable file.
S38, executing the executable file to meet the function requirement.
Regarding steps S35 to S38, please refer to the above description of the embodiment of fig. 2, and for brevity of description, the disclosure is not repeated herein.
According to the technical scheme, the third-party functional components can be converted into the binary resources and deployed into the block chain, so that when the relevant functions are required to be executed by the contracts, the binary resources can be obtained and converted into the executable file. In this way, by executing the executable file, the functions corresponding to the third-party functional components can be realized in the contract, thereby enriching the functions of the intelligent contract. Moreover, the mode can break through the limitation of contract development language.
Furthermore, it should be noted that the embodiments described in the specification are preferred embodiments for convenience and brevity of description, and the related components are not necessarily essential to the present invention. For example, in some possible embodiments, the above steps S31 and S32 may also be performed by the relevant node. Correspondingly, the contract execution device can acquire the binary resources calculated by the relevant nodes and store the binary resources into the block chain.
Fig. 4 is a schematic diagram of a data conversion process shown in this disclosure, and in some possible embodiments, a binary stream of a resource may be written into a blockchain ledger through a resource write contract, and a binary resource is obtained from the blockchain ledger through a resource call contract, so as to restore an executable file.
For the resource write contract, the following protocol fields may be included in the resource write contract, for example:
{
resource name:
resource owner:
resource content:
}
in some possible embodiments, when the capacity of the binary stream is large, the binary stream may be stored in multiple chunks in a shard manner. In this case, the resource write contract may further include a field "offset from the last resource block (i.e. the block storing the binary stream slices)" to facilitate subsequent lookups on the respective binary stream slices.
For the resource invocation contract, there may be an associated record field in the resource invocation contract to record the hash value of the resource block. When the contract is called, the corresponding resources can be read and released from the block chain account book according to the hash value, and then the conversion of the executable file is completed. Thus, by executing the executable file, the corresponding functional requirements can be satisfied.
It should be noted that the resource writing contract and the resource calling contract may be deployed as different parts of the same contract, or may be deployed as two different contracts, which is not limited in this disclosure.
In one possible implementation, the binary resource includes a plurality of resource fragments, the contract includes a homomorphic check field and a homomorphic checksum, and the homomorphic check field includes a digital digest of each resource fragment. Here, the digital digest may be, for example, a hash value obtained by performing a hash calculation on the resource fragment. At contract construction, a contract participant may write a digital digest of each resource slice to a homomorphic check field in the contract.
Further, the homomorphic checksum in the contract may also be determined by:
aiming at each digital abstract, calculating a ciphertext corresponding to the digital abstract based on a target homomorphic encryption key;
and summing each ciphertext to obtain the homomorphic checksum.
For example, the target homomorphic encryption key may be generated by the resource owner under the chain, and the generation process may include:
and randomly determining the first prime number and the second prime number. The first prime number and the second prime number have the same number of bits, and the number of bits of the first prime number and the second prime number is larger than a bit number threshold value. The bit number threshold may be set based on application requirements, for example, in some implementation scenarios, the bit number threshold may be set to 32, and the first and second prime numbers may be selected accordingly.
For example, a first prime p and a second prime q having a greater number of bits than 32 bits may be determined, where p and q satisfy gcd (pq, (p-1) (q-1)) ═ 1, thereby ensuring that the number of bits of the first prime p and the second prime q are identical. Wherein gcd () is the greatest common divisor computation function.
After determining the first and second prime numbers, a product of the first and second prime numbers may be used as a parameter t in the target homomorphic encryption key. Following the above example, t ═ pq.
Furthermore, a target random integer may be determined as a parameter g in the target homomorphic encryption key, and from ZnWherein a random number is determined as a parameter r in the target homomorphic encryption key. Wherein the content of the first and second substances,
and the parameter t divides the order of the parameter g,
the multiplicative inverse exists for the remaining system. In this way, the target homomorphic encryption key (t, g, r) can be obtained.
After the target homomorphic encryption key is determined, the ciphertext c corresponding to the digital digest m may be calculated by the following calculation formulam：
cm＝E(m，r)＝gmrtmodt2，r∈Zn；
For example, when the number of resource fragments is 4, the number digests m of the 4 resource fragments can be calculated respectively1、m2、m3And m4And respectively calculating the digital abstract m by the above calculation formula1、m2、m3And m4The corresponding ciphertext.
In this way, each of the ciphertexts may be summed to obtain a homomorphic checksum c:
wherein the target homomorphic encryption key is (t, g, r), i is the quantity value of the digital abstract, and x belongs to [1, i ∈]And x is an integer, mod is a remainder function, ZnIs an integer field.
After the homomorphic checksum and the digital abstract of each resource fragment are obtained through calculation, the homomorphic checksum and the digital abstract of each resource fragment can be stored in a contract so as to facilitate subsequent verification.
Correspondingly, before the obtaining the binary resource corresponding to the functional requirement from the block chain, the method further includes:
calculating a target homomorphic check sum according to the owned homomorphic encryption key and the homomorphic check field;
and determining that the target homomorphic checksum is consistent with the homomorphic checksum stored in the contract.
It should be understood that, in implementation, the target homomorphic encryption key may be authorized to the corresponding execution device according to requirements. In addition, please refer to the description in the above embodiments for the calculation of the homomorphic checksum, and for the brevity of the description, the details of the disclosure are not repeated herein.
It is to be noted that, when the homomorphic encryption key owned by the contract execution apparatus is different from the target homomorphic encryption key, the target homomorphic checksum calculated by the contract execution apparatus is not identical to the homomorphic checksum stored in the contract. Similarly, if the contract execution device possesses the target homomorphic encryption key but the digital digest is in error, the target homomorphic checksum calculated by the contract execution device may also be inconsistent with the homomorphic checksum stored in the contract.
Therefore, when the calculated target homomorphic checksum is consistent with the homomorphic checksum stored in the contract, it can be determined that the homomorphic encryption key owned by the contract execution apparatus is correct (i.e., the contract execution apparatus has the right to invoke the resource), and the content of the binary resource is correct.
That is to say, the technical scheme can simultaneously verify the legality of the resource loading and the correctness of the resource, thereby being beneficial to improving the execution efficiency of the contract. In addition, the homomorphic verification mode can also verify the correctness of the binary resources under the condition of not acquiring the original text of the binary resources stored on the chain, thereby avoiding the problem of data leakage in the verification process and simultaneously improving the verification speed.
Of course, in some implementation scenarios, the contract execution end may also calculate the digital digest based on the binary resource acquired on the chain, and further calculate the target homomorphic checksum. Therefore, the legality of the resource loading and the correctness of the resource can be verified in a mode of comparing the target homomorphic checksum with the homomorphic checksum stored in the contract.
According to the same inventive concept, the present disclosure also provides an intelligent contract execution apparatus. Fig. 5 is a block diagram of an intelligent contract execution apparatus provided by the present disclosure, and as shown in fig. 5, the apparatus 500 includes:
the determining module 501 is configured to, in response to receiving a contract invoking request, determine a functional requirement corresponding to the contract invoking request according to an invoking parameter in the contract invoking request;
a resource obtaining module 502, configured to obtain a binary resource corresponding to the function requirement from a blockchain, where the binary resource is obtained by converting a third-party function component;
a first resource conversion module 503, configured to convert the obtained binary resource into an executable file;
an execution module 504, configured to execute the executable file to meet the functional requirement.
According to the technical scheme, the third-party functional components are converted into the binary resources, so that the obtained binary resources can be stored in the block chain. In this way, after receiving the contract invoking request, the contract executing apparatus may determine the functional requirement corresponding to the contract invoking request according to the invoking parameter in the contract invoking request, and obtain the corresponding binary resource from the block chain according to the functional requirement. After the binary resource is acquired, the acquired binary resource can be converted into an executable file, and the functional requirement is met by executing the executable file. In this way, when the related functional requirements are met, the corresponding functional code does not need to be written in the intelligent contract, and the function can be realized by calling the binary resource of the third-party functional component. That is to say, the functions of the intelligent contract can be enriched through the technical scheme. In addition, the third-party functional component is converted into the binary resource, and the binary resource is converted into the executable file, so that the limitation of the contract development language can be broken through, and the functions of the intelligent contract are further enriched.
Optionally, the apparatus 500 further comprises:
a function component acquiring module, configured to acquire the third-party function component before the determining module determines the function requirement corresponding to the contract invoking request;
the second resource conversion module is used for converting the executable file of the third-party functional component into a binary resource;
the resource storage module is used for storing the binary resources into a block chain;
and the recording module is used for recording the storage position information of the binary resource.
Optionally, the resource storage module includes:
a resource partitioning submodule, configured to partition the binary resource into a plurality of resource partitions when the capacity of the binary resource is greater than a block capacity threshold;
the resource storage submodule is used for storing each resource fragment into a block chain;
the storage location information includes an offset between a block where a target resource partition is located and a block where a last resource partition of the target resource partition is located, where the target resource partition is any resource partition of the plurality of resource partitions except for a first resource partition.
Optionally, the binary resource includes a plurality of resource fragments, the contract includes a homomorphic check field and a homomorphic checksum, the homomorphic check field includes a digital digest of each resource fragment, and the homomorphic checksum is determined by: aiming at each digital abstract, calculating a ciphertext corresponding to the digital abstract based on a target homomorphic encryption key; summing each ciphertext to obtain the homomorphic checksum;
the apparatus 500 further comprises:
a calculating module, configured to calculate a target homomorphic checksum according to an owned homomorphic encryption key and the homomorphic check field before the resource obtaining module 502 obtains the binary resource corresponding to the function requirement from the block chain;
and the checksum determining module is used for determining that the target homomorphic checksum is consistent with the homomorphic checksum stored in the contract.
Optionally, the calculating, for each of the digital digests, a ciphertext corresponding to the digital digest based on a homomorphic encryption key includes:
calculating the ciphertext c corresponding to the digital abstract m by the following calculation formulam：
cm＝E(m，r)＝gmrtmodt2，r∈Zn；
The summing each of the ciphertexts comprises: the homomorphic checksum c is calculated by the following calculation:
wherein the target homomorphic encryption key is (t, g, r), i is the quantity value of the digital abstract, and x belongs to [1, i ∈]And x is an integer, mod is a remainder function, ZnIs an integer field.
Optionally, the target homomorphic encryption key is determined by:
randomly determining a first prime number and a second prime number, wherein the digits of the first prime number and the second prime number are the same, and the digits of the first prime number and the second prime number are greater than a digit threshold value;
taking the product of the first prime number and the second prime number as a parameter t in the target homomorphic encryption key;
determining a target random integer as a parameter g in the target homomorphic encryption key, wherein,
and the parameter t divides the order of the parameter g,
the existence of multiplication inverse elements under the residual system;
from ZnWherein a random number is determined as a parameter r in the target homomorphic encryption key.
Optionally, the obtaining the binary resource corresponding to the functional requirement from the blockchain includes:
when the capacity of the binary resource is larger than a memory capacity threshold value, dividing the binary resource into a plurality of binary resource fragments;
and sequentially loading the binary resource fragments into a memory for release.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
The present disclosure also provides a non-transitory computer readable storage medium having stored thereon a computer program that, when executed by a processor, performs the steps of the intelligent contract execution method provided by the present disclosure.
The present disclosure also provides an electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to implement the steps of the intelligent contract execution method provided by the present disclosure.
Fig. 6 is a block diagram illustrating an electronic device 600 according to an example embodiment. As shown in fig. 6, the electronic device 600 may include: a processor 601 and a memory 602. The electronic device 600 may also include one or more of a multimedia component 603, an input/output (I/O) interface 604, and a communications component 605.
The processor 601 is configured to control the overall operation of the electronic device 600 to complete all or part of the steps of the intelligent contract execution method. The memory 602 is used to store various types of data to support operation at the electronic device 600, such as instructions for any application or method operating on the electronic device 600 and application-related data, such as messaging, pictures, contract code, and the like. The Memory 602 may be implemented by any type of volatile or non-volatile Memory device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic Memory, flash Memory, magnetic disk or optical disk. The multimedia components 603 may include a screen and audio components. Wherein the screen may be, for example, a touch screen and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may further be stored in the memory 602 or transmitted through the communication component 605. The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 604 provides an interface between the processor 601 and other interface modules, such as a keyboard, mouse, buttons, etc. These buttons may be virtual buttons or physical buttons. The communication component 605 is used for wired or wireless communication between the electronic device 600 and other devices. Wireless Communication, such as Wi-Fi, bluetooth, Near Field Communication (NFC), 2G, 3G, 4G, NB-IOT, eMTC, or other 5G, etc., or a combination of one or more of them, which is not limited herein. The corresponding communication component 605 may therefore include: Wi-Fi module, Bluetooth module, NFC module, etc.
In an exemplary embodiment, the electronic Device 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for executing the above-described smart contract execution method.
In another exemplary embodiment, a computer-readable storage medium is also provided that includes program instructions that, when executed by a processor, implement the steps of the intelligent contract execution method described above. For example, the computer readable storage medium may be the memory 602 described above that includes program instructions that are executable by the processor 601 of the electronic device 600 to perform the intelligent contract execution method described above.
In another exemplary embodiment, a computer program product is also provided, which comprises a computer program executable by a programmable apparatus, the computer program having code portions for performing the intelligent contract execution method described above when executed by the programmable apparatus.
The preferred embodiments of the present disclosure are described in detail with reference to the accompanying drawings, however, the present disclosure is not limited to the specific details of the above embodiments, and various simple modifications may be made to the technical solution of the present disclosure within the technical idea of the present disclosure, and these simple modifications all belong to the protection scope of the present disclosure.
It should be noted that, in the foregoing embodiments, various features described in the above embodiments may be combined in any suitable manner, and in order to avoid unnecessary repetition, various combinations that are possible in the present disclosure are not described again.
In addition, any combination of various embodiments of the present disclosure may be made, and the same should be considered as the disclosure of the present disclosure, as long as it does not depart from the spirit of the present disclosure.
Claims (10)
1. An intelligent contract execution method, comprising:
in response to receiving a contract calling request, determining a functional requirement corresponding to the contract calling request according to a calling parameter in the contract calling request;
acquiring a binary resource corresponding to the function requirement from a block chain, wherein the binary resource is obtained by converting a third-party function component;
converting the acquired binary resource into an executable file;
and executing the executable file to meet the functional requirement.
2. The method of claim 1, wherein prior to determining a functional requirement corresponding to the contract invocation request based on invocation parameters in the contract invocation request in response to receiving the contract invocation request, further comprising:
acquiring the third-party functional component;
converting the executable file of the third-party functional component into a binary resource;
saving the binary resource to a blockchain;
and recording the storage position information of the binary resource.
3. The method of claim 2, wherein saving the binary resource into a blockchain comprises:
when the capacity of the binary resource is larger than a block capacity threshold value, dividing the binary resource into a plurality of resource fragments;
storing each resource fragment into a blockchain;
the storage location information includes an offset between a block where a target resource partition is located and a block where a last resource partition of the target resource partition is located, where the target resource partition is any resource partition of the plurality of resource partitions except for a first resource partition.
4. The method of claim 1, wherein the binary resource comprises a plurality of resource shards, wherein the contract comprises a homomorphic check field and a homomorphic checksum, wherein the homomorphic check field comprises a digital digest of each of the resource shards, and wherein the homomorphic checksum is determined by:
aiming at each digital abstract, calculating a ciphertext corresponding to the digital abstract based on a target homomorphic encryption key;
summing each ciphertext to obtain the homomorphic checksum;
before the obtaining the binary resource corresponding to the functional requirement from the block chain, the method further includes:
calculating a target homomorphic check sum according to the owned homomorphic encryption key and the homomorphic check field;
and determining that the target homomorphic checksum is consistent with the homomorphic checksum stored in the contract.
5. The method of claim 4, wherein said computing, for each of the digital digests, the ciphertext corresponding to the digital digest based on the homomorphic encryption key comprises:
calculating the ciphertext c corresponding to the digital abstract m by the following calculation formulam：
cm＝E(m,r)＝gmrtmodt2,r∈Zn；
The summing each of the ciphertexts comprises: the homomorphic checksum c is calculated by the following calculation:
wherein the target homomorphic encryption key is (t, g, r), i is the quantity value of the digital abstract, and x belongs to [1, i ∈]And x is an integer, mod is a remainder function, ZnIs an integer field.
6. The method of claim 5, wherein the target homomorphic encryption key is determined by:
randomly determining a first prime number and a second prime number, wherein the digits of the first prime number and the second prime number are the same, and the digits of the first prime number and the second prime number are greater than a digit threshold value;
taking the product of the first prime number and the second prime number as a parameter t in the target homomorphic encryption key;
determining a target random integer as a parameter g in the target homomorphic encryption key, wherein,
and the parameter t divides the order of the parameter g,
the existence of multiplication inverse elements under the residual system;
from ZnWherein a random number is determined as a parameter r in the target homomorphic encryption key.
7. The method of claim 1, wherein the obtaining the binary resource corresponding to the functional requirement from the blockchain comprises:
when the capacity of the binary resource is larger than a memory capacity threshold value, dividing the binary resource into a plurality of binary resource fragments;
and sequentially loading the binary resource fragments into a memory for release.
8. An intelligent contract execution apparatus, comprising:
the determining module is used for responding to the received contract calling request and determining the functional requirement corresponding to the contract calling request according to the calling parameter in the contract calling request;
the resource acquisition module is used for acquiring a binary resource corresponding to the function requirement from the block chain, wherein the binary resource is obtained by converting a third-party function component;
the first resource conversion module is used for converting the acquired binary resource into an executable file;
and the execution module is used for executing the executable file so as to meet the functional requirements.
9. A non-transitory computer readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
10. An electronic device, comprising:
a memory having a computer program stored thereon;
a processor for executing the computer program in the memory to carry out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110648090.5A CN113472512A (en) | 2021-06-10 | 2021-06-10 | Intelligent contract execution method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110648090.5A CN113472512A (en) | 2021-06-10 | 2021-06-10 | Intelligent contract execution method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113472512A true CN113472512A (en) | 2021-10-01 |
Family
ID=77869597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110648090.5A Pending CN113472512A (en) | 2021-06-10 | 2021-06-10 | Intelligent contract execution method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113472512A (en) |
Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140223196A1 (en) * | 2013-02-01 | 2014-08-07 | Brian Ignomirello | Methods and Systems for Storing and Retrieving Data |
| CN108235772A (en) * | 2017-12-29 | 2018-06-29 | 深圳前海达闼云端智能科技有限公司 | Data processing method, device, storage medium and electronic equipment based on block chain |
| CN109040133A (en) * | 2018-09-27 | 2018-12-18 | 上海点融信息科技有限责任公司 | The method, apparatus and storage medium of intelligent contract are installed in block chain network |
| CN109146413A (en) * | 2018-08-02 | 2019-01-04 | 珠海宏桥高科技有限公司 | A kind of construction method of the intelligent contract based on block chain |
| CN109271255A (en) * | 2018-09-25 | 2019-01-25 | 深圳市元征科技股份有限公司 | Resource regulating method, system and electronic equipment and storage medium |
| CN109587253A (en) * | 2018-12-11 | 2019-04-05 | 浙江大学 | A method of distributed storage is realized to file based on block chain |
| CN109656617A (en) * | 2018-11-30 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | A kind of front end Web Service dispositions method, storage medium, electronic equipment and system |
| CN110096338A (en) * | 2019-05-10 | 2019-08-06 | 百度在线网络技术（北京）有限公司 | Intelligent contract executes method, apparatus, equipment and medium |
| US20190244294A1 (en) * | 2018-11-27 | 2019-08-08 | Alibaba Group Holding Limited | Function-as-a-service (faas) platform in blockchain networks |
| CN110297689A (en) * | 2019-05-06 | 2019-10-01 | 百度在线网络技术（北京）有限公司 | Intelligent contract executes method, apparatus, equipment and medium |
| CN110390213A (en) * | 2019-07-31 | 2019-10-29 | 中国工商银行股份有限公司 | The security deployment method and system of intelligent contract under block chain network environment |
| CN110959282A (en) * | 2019-03-04 | 2020-04-03 | 阿里巴巴集团控股有限公司 | Software interface for intelligent contracts |
| CN111381938A (en) * | 2020-05-29 | 2020-07-07 | 支付宝(杭州)信息技术有限公司 | Method and system for executing intelligent contracts in block chain based on basic instruction set |
| US20200320529A1 (en) * | 2019-04-03 | 2020-10-08 | Bloomio Ag | Method for user management for blockchain-based operations |
| CN111880777A (en) * | 2020-06-23 | 2020-11-03 | 北京三快在线科技有限公司 | Program information issuing method and device and electronic equipment |
| CN112104709A (en) * | 2020-08-28 | 2020-12-18 | 腾讯科技（深圳）有限公司 | Intelligent contract processing method, device, medium and electronic equipment |
| CN112632573A (en) * | 2020-12-15 | 2021-04-09 | 东软集团股份有限公司 | Intelligent contract execution method, device and system, storage medium and electronic equipment |
| CN112651741A (en) * | 2021-01-04 | 2021-04-13 | 北京京东乾石科技有限公司 | Data processing method and device based on block chain |
| CN112905447A (en) * | 2021-01-22 | 2021-06-04 | 支付宝(杭州)信息技术有限公司 | Test method and system for block chain virtual machine |
| CN112929396A (en) * | 2019-12-06 | 2021-06-08 | 顺丰科技有限公司 | Service processing method, device and equipment based on block chain and readable storage medium |
-
2021
- 2021-06-10 CN CN202110648090.5A patent/CN113472512A/en active Pending
Patent Citations (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140223196A1 (en) * | 2013-02-01 | 2014-08-07 | Brian Ignomirello | Methods and Systems for Storing and Retrieving Data |
| CN108235772A (en) * | 2017-12-29 | 2018-06-29 | 深圳前海达闼云端智能科技有限公司 | Data processing method, device, storage medium and electronic equipment based on block chain |
| CN109146413A (en) * | 2018-08-02 | 2019-01-04 | 珠海宏桥高科技有限公司 | A kind of construction method of the intelligent contract based on block chain |
| CN109271255A (en) * | 2018-09-25 | 2019-01-25 | 深圳市元征科技股份有限公司 | Resource regulating method, system and electronic equipment and storage medium |
| CN109040133A (en) * | 2018-09-27 | 2018-12-18 | 上海点融信息科技有限责任公司 | The method, apparatus and storage medium of intelligent contract are installed in block chain network |
| US20190244294A1 (en) * | 2018-11-27 | 2019-08-08 | Alibaba Group Holding Limited | Function-as-a-service (faas) platform in blockchain networks |
| CN109656617A (en) * | 2018-11-30 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | A kind of front end Web Service dispositions method, storage medium, electronic equipment and system |
| CN109587253A (en) * | 2018-12-11 | 2019-04-05 | 浙江大学 | A method of distributed storage is realized to file based on block chain |
| CN110959282A (en) * | 2019-03-04 | 2020-04-03 | 阿里巴巴集团控股有限公司 | Software interface for intelligent contracts |
| US20200320529A1 (en) * | 2019-04-03 | 2020-10-08 | Bloomio Ag | Method for user management for blockchain-based operations |
| CN110297689A (en) * | 2019-05-06 | 2019-10-01 | 百度在线网络技术（北京）有限公司 | Intelligent contract executes method, apparatus, equipment and medium |
| CN110096338A (en) * | 2019-05-10 | 2019-08-06 | 百度在线网络技术（北京）有限公司 | Intelligent contract executes method, apparatus, equipment and medium |
| CN110390213A (en) * | 2019-07-31 | 2019-10-29 | 中国工商银行股份有限公司 | The security deployment method and system of intelligent contract under block chain network environment |
| CN112929396A (en) * | 2019-12-06 | 2021-06-08 | 顺丰科技有限公司 | Service processing method, device and equipment based on block chain and readable storage medium |
| CN111381938A (en) * | 2020-05-29 | 2020-07-07 | 支付宝(杭州)信息技术有限公司 | Method and system for executing intelligent contracts in block chain based on basic instruction set |
| CN111880777A (en) * | 2020-06-23 | 2020-11-03 | 北京三快在线科技有限公司 | Program information issuing method and device and electronic equipment |
| CN112104709A (en) * | 2020-08-28 | 2020-12-18 | 腾讯科技（深圳）有限公司 | Intelligent contract processing method, device, medium and electronic equipment |
| CN112632573A (en) * | 2020-12-15 | 2021-04-09 | 东软集团股份有限公司 | Intelligent contract execution method, device and system, storage medium and electronic equipment |
| CN112651741A (en) * | 2021-01-04 | 2021-04-13 | 北京京东乾石科技有限公司 | Data processing method and device based on block chain |
| CN112905447A (en) * | 2021-01-22 | 2021-06-04 | 支付宝(杭州)信息技术有限公司 | Test method and system for block chain virtual machine |
Non-Patent Citations (1)
| Title |
|---|
| 黄石;刘文卓;曹天杰;: "改进的基于同态哈希的云存储数据完整性验证方案", 河海大学学报(自然科学版), no. 03 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3591510A1 (en) | Method and device for writing service data in block chain system | |
| CN111475824B (en) | Data access method, device, equipment and storage medium | |
| KR102288521B1 (en) | Apparatus and method for storing data based on blockchain | |
| CN112862490B (en) | Output consensus method under asynchronous network | |
| CN110570196A (en) | Transaction data processing method and device, terminal equipment and storage medium | |
| CN111444547B (en) | Method, apparatus and computer storage medium for data integrity attestation | |
| CN110022315A (en) | Weight management method, device and equipment in a kind of piece of chain type account book | |
| CN110659905A (en) | Transaction verification method, device, terminal equipment and storage medium | |
| CN110989934B (en) | Block chain link point data storage method, block chain system and block chain node | |
| CN111045722B (en) | Intelligent contract packaging method, device, system, computer equipment and storage medium | |
| CN111339547B (en) | Method for generating data tag, electronic device and computer storage medium | |
| CN111339193B (en) | Category encoding method and device | |
| CN115481440B (en) | Data processing method, device, electronic equipment and medium | |
| CN113472512A (en) | Intelligent contract execution method and device, storage medium and electronic equipment | |
| CN113051622B (en) | Index construction method, device, equipment and storage medium | |
| CN111324645A (en) | Data processing method and device for block chain | |
| CN115391801A (en) | Method and device for updating encryption module in block chain system and related products | |
| CN112363967B (en) | Method, device, equipment and medium for unifying interface standards of password equipment | |
| CN112306466A (en) | AAR packet generation method, electronic device, and storage medium | |
| CN111949738A (en) | Block chain-based data storage deduplication method, terminal device and storage medium | |
| CN113364821A (en) | Functional service access method, device and storage medium | |
| CN110995437A (en) | ETC system-based user information input method, device, equipment and storage medium | |
| CN111444548B (en) | Method, apparatus and computer storage medium for data integrity attestation | |
| CN114331447B (en) | Cross-link message submitting method and device | |
| CN113486375B (en) | Storage method and device of equipment information, storage medium and electronic device |
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 |