CN108833398B - Block chain intelligent contract updating method, device and equipment - Google Patents
Block chain intelligent contract updating method, device and equipment Download PDFInfo
- Publication number
- CN108833398B CN108833398B CN201810586324.6A CN201810586324A CN108833398B CN 108833398 B CN108833398 B CN 108833398B CN 201810586324 A CN201810586324 A CN 201810586324A CN 108833398 B CN108833398 B CN 108833398B
- Authority
- CN
- China
- Prior art keywords
- consensus verification
- transaction request
- node
- intelligent contract
- transaction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
- H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- 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/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a method, a device and equipment for updating a block chain intelligent contract. The method comprises the following steps: receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit updating information of the intelligent contract to an uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract; determining a security level of the intelligent contract, and performing consensus verification on the first transaction request based on the security level; responding or denying the response to the first transaction request based on the result of the consensus verification. As can be seen, the security levels of the intelligent contract are divided based on different requirements of the application scenario to obtain a plurality of security levels with different characteristics, for example: the level of the upgrade contract is unconditionally updated by the owner, the level of the upgrade contract is conditionally updated by the owner, the level of the upgrade contract is not updatable, and so on. And a proper updating mechanism is configured for the intelligent contracts of each security level, and compared with the prior art, the development iteration and deployment flexibility of the intelligent contracts can be effectively improved.
Description
Technical Field
The application relates to the technical field of computers, in particular to a block chain intelligent contract updating method, device and equipment.
Background
Smart contracts are a computer protocol intended to propagate, validate or execute contracts in an informational manner, allowing trusted transactions to be conducted without third parties, which transactions are traceable and irreversible. It is actually the right and obligations of the agreement that are presented by the developer in the form of code, on the basis of which the code executes automatically as soon as a certain event triggers a term in the contract.
The blockchain technique is a decentralized distributed database technique. Each piece of data in the block chain is broadcasted to the block chain nodes of the whole network, and each node can store the whole amount of consistent data. Blockchain techniques require that the state of each node remain consistent, including the state of the database, etc.
The intelligent block chain contract is written into a block chain in a digitalized form, so that the advantages of the intelligent contract in the aspect of cost efficiency can be exerted, and the interference of malicious behaviors on the normal execution of the contract is avoided; the transparent, trackable and non-tamper-able whole process of storage, reading and execution can be guaranteed based on the characteristics of the block chain technology; and a set of state machine system can be constructed based on the block chain self-contained consensus algorithm, so that the intelligent contract can run efficiently.
With the continuous maturity of the block chain and the intelligent contract bottom layer technology, the application of the large-scale intelligent contract will be concurrent on the block chain, and therefore, a flexible update mechanism needs to be provided for the development iteration and deployment of the intelligent contract.
Disclosure of Invention
The embodiment of the specification provides a method, a device and equipment for updating a block chain intelligent contract, which are used for providing a flexible updating mechanism for development iteration and deployment of the intelligent contract.
An embodiment of the present specification provides a method for updating a block chain intelligent contract, including:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or denying response to the first transaction request based on the result of the consensus verification.
Optionally, before receiving the first transaction request initiated by the first transaction node, the method further includes:
receiving a second transaction request initiated by the first transaction node, wherein the second transaction request is used for requesting to submit the intelligent contract to the uplink, and the second transaction request comprises the security level;
and performing consensus verification on the second transaction request, and responding to the second transaction request when the result of the consensus verification is passed.
Optionally, the performing consensus verification on the first transaction request based on the security level includes:
determining an update rule of the intelligent contract based on the security level and a pre-configured corresponding relationship between the security level and the update rule;
performing consensus verification on the first transaction request based on the update rule.
Optionally, performing consensus verification on the first transaction request based on the update rule includes:
when the updating rule is a first type updating rule, performing consensus verification on the signature carried by the updating information;
and if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed.
Optionally, performing consensus verification on the first transaction request based on the update rule includes:
when the updating rule is a second type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed;
wherein the target transaction node comprises: some or all of the corresponding nodes in the parties to the intelligent contract, and the first trading node.
Optionally, performing consensus verification on the first transaction request based on the update rule includes:
and when the update rule is a third type update rule, determining that the result of the consensus verification is failed.
Optionally, responding or denying response to the first transaction request according to the result of the consensus verification includes:
responding to the first transaction request when the result of the consensus verification is passed;
and refusing to respond to the first transaction request when the result of the consensus verification is failed.
Optionally, the first transaction request includes address information of a storage node, where the intelligent contract is stored in the storage node;
wherein responding to the first transaction request comprises:
acquiring the intelligent contract based on the address information of the storage node;
and updating the intelligent contract based on the updating information.
An embodiment of the present specification further provides a device for updating a block chain intelligent contract, including:
a first receiving module, configured to receive a first transaction request initiated by a first transaction node, where the first transaction request is used to request that update information of an intelligent contract be submitted to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
the first consensus verification module is used for determining the security level of the intelligent contract and performing consensus verification on the first transaction request based on the security level;
and the first response module is used for responding or refusing to respond to the first transaction request according to the result of the consensus verification.
An embodiment of the present specification further provides an electronic device, including:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or denying response to the first transaction request based on the result of the consensus verification.
The present specification embodiments also provide a computer-readable storage medium storing one or more programs that, when executed by an electronic device including a plurality of application programs, cause the electronic device to perform operations comprising:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or denying response to the first transaction request based on the result of the consensus verification.
The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:
based on different requirements of an application scenario, the security level of an intelligent contract is divided to obtain a plurality of security levels with different characteristics, for example: the level of the upgrade contract is unconditionally updated by the owner, the level of the upgrade contract is conditionally updated by the owner, the level of the upgrade contract is not updatable, and so on. Compared with the prior art, the intelligent contract updating method and the intelligent contract updating system can effectively improve the development iteration and deployment flexibility of the intelligent contract on the basis of not influencing a credible mechanism.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic diagram of an application scenario provided in the present specification;
fig. 2 is a schematic flowchart of a method for updating a blockchain intelligent contract according to an embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating an intelligent contract uplink method according to an embodiment of the present disclosure;
FIGS. 4a and 4b are schematic diagrams of an intelligent contract updating method according to another embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a blockchain intelligent contract updating apparatus according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As stated in the background section, a large-scale application of intelligent contracts may be concurrent on a blockchain in the prior art, but the intelligent contracts on the blockchain in the prior art have a single characteristic and cannot meet the requirements of different application scenarios. For example: some intelligent contracts have strong contract attribute, and any party has no right to modify and withdraw after the contract is established, namely, the contract is law, namely, the code is law; if the contract participant wants to update and upgrade the contract subsequently, the problem that the contract cannot be updated and upgraded occurs; still other intelligent contracts are more like applications built on a block chain distributed operating system in the traditional sense, and contract owners can update and upgrade the intelligent contracts at any time, but the problem that the trusted mechanism is destroyed occurs, for example: the contract owner can move the contract fund of the participant privately.
Therefore, with the continuous increase of the scale of the intelligent contracts on the block chain, the intelligent contracts with single characteristics obviously and more difficultly meet the requirements of multiple application scenarios.
Based on the above, the invention provides a block chain intelligent contract updating method, which can obtain a plurality of security levels with different characteristics by dividing the security level of an intelligent contract so as to adapt to the requirements of different application scenes on a block chain.
An application scenario of the present invention is exemplarily described below with reference to the drawings.
Referring to fig. 1, one application scenario may be:
included in the blockchain are node 1, node 2 …, node 6, and so on. And each node is provided with an updating management module which is used for determining the security level of the intelligent contract submitted to the block chain so as to provide a basis for updating and upgrading the intelligent contract subsequently. Optionally, the specific number of nodes on the block chain is not limited herein.
Taking node 1 as a node corresponding to an owner (account) of the first intelligent contract as an example, when the owner needs to update and upgrade the first intelligent contract, node 1 submits an update information request to the uplink in the form of a transaction request. Then, the consensus node on the blockchain determines the security level of the first intelligent contract, further performs consensus verification on the transaction request based on the contract characteristics corresponding to the security level, and if the contract characteristics pass the consensus verification, allows the information uplink to be updated so as to update and upgrade the first intelligent contract.
Wherein, the consensus verification means that the verification and the confirmation of the transaction are completed in a short time through the voting of the special node.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 2 is a schematic flow chart of a method for updating a blockchain intelligent contract according to an embodiment of the present disclosure, and referring to fig. 2, the method may specifically include the following steps:
step 22, receiving a first transaction request initiated by a first transaction node, where the first transaction request is used to request to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to an owner of the intelligent contract;
wherein the intelligent contract is an intelligent contract which is linked; the updating information is information for modifying the right, obligation, condition of triggering clauses and the like in the intelligent contract and is used for updating operations such as adding clauses, deleting clauses and the like; all parties are accounts with the intelligent contract authority, and can be contract participants or third parties managed by the contract participants.
It should be noted that, before step 22, the method further includes: an intelligent contract chaining step, which specifically includes the following steps in combination with fig. 3:
the second transaction request comprises the security level of the intelligent contract, the security level is a parameter which is pre-configured and is used for representing the risk degree of the transaction corresponding to the intelligent contract, the greater the security level is, the greater the risk of the transaction is, otherwise, the smaller the risk of the current transaction is; the smart contract is provided with a signature of the first transaction node.
It should be noted that, a first implementation manner of the step of pre-configuring the security level may be:
when the contract participants formulate or upload the intelligent contract, the corresponding node provides a security level selection frame for the contract participants, the security level selection frame is used for displaying at least one security level, and the contract participants negotiate to select one security level from the security level as the security level of the intelligent contract.
A second implementation of the step of pre-configuring the security level may be:
a default security level is configured for the intelligent contract by the corresponding node. Specific examples can be as follows:
example 1, a corresponding node scans keywords in an intelligent contract, and evaluates security levels required by the contract based on the keywords; specifically, the method comprises the following steps:
the corresponding node scans the intelligent contract to determine keywords related to amount, participant type (company, unit, college, individual, and the like), clause quantity and the like; evaluating the intelligent contract based on the keywords to determine the security level possibly required by the intelligent contract, wherein the evaluation rule can be as follows: the more money, the higher the required security level; the more terms, the higher the required level of security; the security level required for the participant type is typically company > unit > college > individual;
example 2, determining a contract category of the intelligent contract by the corresponding node, and evaluating a security level required by the contract based on the contract category; specifically, the method comprises the following steps:
the corresponding node scans the header of the intelligent contract or scans the content of the intelligent contract to determine the contract category of the intelligent contract; the security level corresponding to the intelligent contract is selected from the security levels configured for various contract categories, such as empirical values/expert advice. The security levels configured by various contract categories may be, for example: configuring the highest security level for the business contract; contracts that are common in life (e.g., electricity, water, gas, heat contracts, etc.) configure a lower level of security.
The corresponding node may be a node corresponding to a contract participant or a node corresponding to a contract owner.
it should be noted that, one implementation manner of step 34 may be:
verifying whether the intelligent contract is provided with the signature of the specified user and whether the signature is legal, and if so, determining that the consensus verification result is passed; if not, determining that the consensus verification result is failed;
wherein the specified user depends on the category of the intelligent contract and the requirements of the participants in the formulation.
And step 36, responding to the second transaction request when the result of the consensus verification is passed.
When the result of the consensus verification is passed, the intelligent contract is allowed to be linked up in response to the second transaction request so as to store the intelligent contract into the storage node;
therefore, in the embodiment, before the intelligent contract is linked up, an appropriate security level is configured for the intelligent contract in advance based on the requirement of the application scenario, so that the updating mechanism of the intelligent contract can be determined, and a basis is provided for updating the subsequent contract.
that is, the step discriminatively performs consensus verification on the intelligent contracts based on the characteristics of the intelligent contracts of different categories, and one implementation manner of the step may be as follows:
step S1, determining the updating rule of the intelligent contract based on the security level and the pre-configured corresponding relationship between the security level and the updating rule;
step S2, performing consensus verification on the first transaction request based on the update rule.
For step S1, it should be noted that the characteristics of the smart contract required by different application scenarios are different, for example: some application scenarios require that the intelligent contract is not modifiable, and some application scenarios require that the intelligent contract be modifiable in a multi-party collaboration. Therefore, the preconfigured correspondence between the security level and the update rule in the present embodiment may be exemplified as including:
a first security level (lower) applicable to the application scenario of weak contract strong services, corresponding to a first type of update rule, i.e. contract code can be upgraded arbitrarily by contract owners;
for example: in an application scenario where a medical institution deploys a contract to maintain personal health data of a user, since the contract does not affect the benefit of the user, the medical institution may arbitrarily upgrade the contract after the user authorizes the medical institution in general.
A second security level (higher) applicable to application scenarios of multi-party collaboration, corresponding to a second class of update rules, i.e. contract-proprietors are upgradable after getting signatures of all or part of the specified users;
for example: in the application scene of signing both parties A and B and hosting the contract to the third party, the third party is used as a contract owner, and when the contract is updated and upgraded, the signature party needing to obtain both parties A and B or at least one party can be authorized to update and upgrade the contract.
The third security level (highest), which is applicable to most application scenarios on the blockchain, corresponds to a third class of update rules, i.e., once a contract is successfully deployed, it cannot be updated and upgraded by either the contract owner or other users. Optionally, the third security level may be used as a default security level for the blockchain.
In addition, although only three security levels are illustrated herein, it will be understood that the security levels are flexibly divisible and the corresponding update rules are also flexibly configurable. Therefore, other security levels and the division of their update rules are also within the scope of the present embodiment.
Based on the correspondence between the security level and the update rule exemplified in step S1, a first implementation manner of the consensus verification step in step S2 may be:
if the intelligent contract is of a first security level, determining that the updating rule of the intelligent contract is a first type of updating rule; further, the signature carried on the updating information can be subjected to consensus verification based on the first type of updating rule; and if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed.
That is, the signature of the contract owner can be verified, so that the goal of arbitrarily upgrading the contract code at the same address by the contract owner can be achieved.
A second implementation of the consensus verification step may be:
if the intelligent contract is of a second security level, determining that the updating rule of the intelligent contract is a second type updating rule; further, based on the second type of update rule, performing consensus verification on the signature carried on the update information; if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed; wherein the target transaction node comprises: the first trading node and a node corresponding to a participant of the intelligent contract. The participants can be all participants or part of the participants; in particular by the updating requirements of all participants in the preparation of the smart contract.
A third implementation of the consensus verification step may be:
if the intelligent contract is of a third security level, determining that the updating rule of the intelligent contract is a third type updating rule; further, the result of the consensus verification may be determined to be failed based on the third type of update rule.
That is, when the consensus node determines that the intelligent contract is the third security level that is not updatable, the verification is determined to be invalid without information such as a verification signature.
It is understood that, when the result of the consensus verification is failed, the first transaction request is refused to be responded, and the intelligent contract is not allowed to be updated and upgraded;
when the result of the consensus verification is passed, responding to the first transaction request, and allowing the intelligent contract to be updated and upgraded;
one implementation manner of updating and upgrading the intelligent contract may be:
acquiring address information of a storage node included in the first transaction request, wherein the storage node stores the intelligent contract; when the consensus verification result is passed, acquiring an intelligent contract based on the address information of the storage node; and updating the intelligent contract based on the updating information.
Wherein, the storage node is used for: the intelligent contract used in the transaction between the transaction nodes is stored, and the storage nodes can be contract participation nodes or other nodes.
As can be seen, in this embodiment, based on different requirements of an application scenario, security levels of an intelligent contract are divided to obtain multiple security levels with different characteristics, for example: the level of the upgrade contract is unconditionally updated by the owner, the level of the upgrade contract is conditionally updated by the owner, the level of the upgrade contract is not updatable, and so on. Compared with the prior art, the intelligent contract updating method and the intelligent contract updating system can effectively improve the development iteration and deployment flexibility of the intelligent contract on the basis of not influencing a credible mechanism.
Fig. 4a and 4b are schematic diagrams of an intelligent contract updating method according to another embodiment of the present disclosure, and the method is exemplarily described below with reference to fig. 4a and 4 b:
referring to fig. 4a, an example may specifically include the steps of:
firstly, assuming that a transaction occurs between a node 2 and a node 3, the two parties interact with each other through a line to formulate an intelligent contract to be observed and a security level thereof, and sign on the intelligent contract;
the intelligent contract may be, for example:
when the highest temperature on the next day is greater than 38 °, account 2 on node 2 pays 100 dollars to account 3 on node 3;
when the highest temperature on the next day is less than or equal to 38 °, account 3 on node 3 pays 100 dollars to account 2 on node 2;
the security level configured for the intelligent contract by both parties is a second security level for subsequent modification.
Secondly, the node 2 or the node 3 trustees the intelligent contract to the node 1;
that is, node 2 and node 3 collectively delegate trusted node 1 to the intelligent contract owner.
Initiating a transaction request for submitting the intelligent contract to the uplink by the node 1;
carrying out consensus verification on the transaction request by a consensus node, and if the result of the consensus verification is passed, allowing the intelligent contract to chain and storing the intelligent contract into a storage node;
wherein the consensus verification comprises: verifying whether the signatures of the node 1, the node 2 and the node 3 on the intelligent contract are legal or not;
fourthly, the node 2 and the node 3 interact through the offline, agree on the update information of the contract and sign on the update information;
for example: both users corresponding to the node 2 and the node 3 may feel that 38 degrees in the contract are unreasonable, agree to change 38 degrees into 35 degrees, and then either party constructs contract updating information (changes 38 degrees into 35 degrees) and signs; then, a request for updating the contract is sent to the other party, and the other party also signs after verifying that the updating information is correct and the signature of the other party is legal;
fifthly, initiating an updating request to the node 1 by the node 2 or the node 3;
correspondingly, the node 1 firstly checks the security level of the intelligent contract and the corresponding updating rule; then, verifying whether the updating request meets the requirement of the updating rule; if yes, signing and executing the step (sixth);
step sixthly, initiating a transaction request for submitting the updated information to the uplink;
and carrying out consensus verification on the transaction request by a consensus node, and if the result of the consensus verification is passed, allowing the updated information to be uplink, so as to find the intelligent contract based on the address information of the storage node, and further modifying 38 degrees in the contract to 35 degrees.
Referring to fig. 4b, the difference from the example shown in fig. 4a is that the step (r) in this example can be performed on-line. Assuming that node 2 is the transaction initiator, the implementation of step (i) can be briefly described as follows:
the node 2 makes a contract based on the rights and obligations of both sides, and initiates a first transaction request to the block chain after signing, wherein the first transaction request carries the identity information of the node 3;
the node 3 verifies the signature of the node 2 and the content of the intelligent contract, and if the verification is passed, a second transaction request is initiated to the block chain after the signature is verified, wherein the second transaction request carries the identity information of the node 2;
and the node 2 verifies the signature of the node 3, if the signature passes the verification, the intelligent contract with the signatures of the node 2 and the node 3 is trusteed to the node 1, and the node 1 submits the uplink after verification.
The implementation of step (iv) can be briefly described as follows:
the node 2 formulates updating information of the intelligent contract based on the content needing to be modified, and initiates a third transaction request to the block chain after signing, wherein the third transaction request carries the identity information of the node 3;
the node 3 verifies the signature of the node 2 and the content of the update information, if the verification is passed, a fourth transaction request is initiated to the block chain after the signature is verified, and the fourth transaction request carries the identity information of the node 2;
and the node 2 verifies the signature of the node 3, if the signature passes the verification, the update information with the signatures of the node 2 and the node 3 is managed to the node 1, and the node 1 submits the uplink after verification.
It can be seen that, in the embodiment, a security level is configured for the uplink intelligent contract before the uplink intelligent contract, and thus, the blockchain can determine the corresponding update rule; furthermore, when the intelligent contract is updated subsequently, consensus verification can be performed based on the corresponding update rule, so that the intelligent contract with different security levels can be updated and upgraded by adopting the corresponding update rule. Compared with the prior art, the development iteration and deployment flexibility of the intelligent contract can be effectively improved on the basis of not influencing a credible mechanism.
In addition, for simplicity of explanation, the above-described method embodiments are described as a series of acts or combinations, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts or steps described, as some steps may be performed in other orders or simultaneously according to the present invention. Furthermore, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.
Fig. 5 is a schematic structural diagram of a block chain intelligent contract updating apparatus according to an embodiment of the present disclosure, and referring to fig. 5, the apparatus may specifically include: a first receiving module 51, a first consensus verification module 52 and a first response module 53, wherein:
a first receiving module 51, configured to receive a first transaction request initiated by a first transaction node, where the first transaction request is used to request that update information of an intelligent contract be submitted to a uplink, and the first transaction node is a node corresponding to an owner of the intelligent contract;
a first consensus verification module 52 configured to determine a security level of the intelligent contract and perform consensus verification on the first transaction request based on the security level;
a first response module 53, configured to respond or refuse to respond to the first transaction request according to a result of the consensus verification.
Optionally, the apparatus further comprises:
a second receiving module, configured to receive a second transaction request initiated by the first transaction node, where the second transaction request is used to request that the intelligent contract be submitted to uplink, and the second transaction request includes the security level;
the second consensus verification module is used for carrying out consensus verification on the second transaction request;
and the second response module is used for responding to the second transaction request when the result of the consensus verification is passed.
Optionally, the first contract verification module 52 is specifically configured to determine an update rule of the intelligent contract based on the security level and a preconfigured correspondence between the security level and the update rule; performing consensus verification on the first transaction request based on the update rule.
Optionally, the first consensus verification module 52 is specifically configured to perform consensus verification on the signature carried in the update information when the update rule is the first type of update rule; and if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed.
Optionally, the first consensus verification module 52 is specifically configured to perform consensus verification on the signature carried in the update information when the update rule is the second type of update rule; if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed;
wherein the target transaction node comprises: some or all of the corresponding nodes in the parties to the intelligent contract, and the first trading node.
Optionally, the first consensus verification module 52 is specifically configured to determine that the result of the consensus verification is failed when the update rule is the third type of update rule.
Optionally, the first response module 53 is specifically configured to respond to the first transaction request when the result of the consensus verification is that the result is passed; and refusing to respond to the first transaction request when the result of the consensus verification is failed.
Optionally, the first transaction request includes address information of a storage node, where the intelligent contract is stored in the storage node;
correspondingly, the first response module 53 is specifically configured to, when the result of the consensus verification is that the agreement is passed, obtain the intelligent contract based on the address information of the storage node; and updating the intelligent contract based on the updating information.
As can be seen, in this embodiment, based on different requirements of an application scenario, security levels of an intelligent contract are divided to obtain multiple security levels with different characteristics, for example: the level of the upgrade contract is unconditionally updated by the owner, the level of the upgrade contract is conditionally updated by the owner, the level of the upgrade contract is not updatable, and so on. Compared with the prior art, the intelligent contract updating method and the intelligent contract updating system can effectively improve the development iteration and deployment flexibility of the intelligent contract on the basis of not influencing a credible mechanism.
As for the above device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.
It should be noted that, in the respective components of the apparatus of the present invention, the components therein are logically divided according to the functions to be implemented thereof, but the present invention is not limited thereto, and the respective components may be newly divided or combined as necessary.
Fig. 6 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure, and referring to fig. 6, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required by other services. The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to form the intelligent contract updating device of the block chain on the logic level. Of course, besides the software implementation, the present application does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
The network interface, the processor and the memory may be interconnected by a bus system. The bus may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 6, but that does not indicate only one bus or one type of bus.
The memory is used for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory may include both read-only memory and random access memory, and provides instructions and data to the processor. The Memory may include a Random-Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory.
The processor is used for executing the program stored in the memory and specifically executing:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or denying response to the first transaction request based on the result of the consensus verification.
The method performed by the blockchain intelligent contract updating apparatus or manager (Master) node according to the embodiment of fig. 5 of the present application may be applied to or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
The blockchain intelligent contract updating apparatus may also perform the methods of fig. 2-3 and implement the method performed by the manager node.
Based on the same invention creation, the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores one or more programs, and when the one or more programs are executed by an electronic device including a plurality of application programs, the electronic device is caused to execute the block chain intelligent contract updating method provided by the corresponding embodiment in fig. 2 to 3.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for updating a blockchain intelligent contract, comprising:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or refusing to respond to the first transaction request according to the result of the consensus verification;
wherein the consensus verification of the first transaction request based on the security level comprises:
determining an update rule of the intelligent contract based on the security level and a pre-configured corresponding relationship between the security level and the update rule;
performing consensus verification on the first transaction request based on the update rule;
wherein consensus verification of the first transaction request based on the update rule comprises:
when the updating rule is a first type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed;
when the updating rule is a second type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed;
wherein the target transaction node comprises: some or all of the nodes corresponding to the participants of the intelligent contract, and the first transaction node;
and when the update rule is a third type update rule, determining that the result of the consensus verification is failed.
2. The method of claim 1, prior to receiving the first transaction request initiated by the first transaction node, further comprising:
receiving a second transaction request initiated by the first transaction node, wherein the second transaction request is used for requesting to submit the intelligent contract to the uplink, and the second transaction request comprises the security level;
and performing consensus verification on the second transaction request, and responding to the second transaction request when the result of the consensus verification is passed.
3. The method of claim 1 or 2, wherein responding to or denying response to the first transaction request based on the result of consensus verification comprises:
responding to the first transaction request when the result of the consensus verification is passed;
and refusing to respond to the first transaction request when the result of the consensus verification is failed.
4. The method of claim 3, wherein the first transaction request includes address information of a storage node in which the smart contract is stored;
wherein responding to the first transaction request comprises:
acquiring the intelligent contract based on the address information of the storage node;
and updating the intelligent contract based on the updating information.
5. A blockchain intelligent contract updating apparatus, comprising:
a first receiving module, configured to receive a first transaction request initiated by a first transaction node, where the first transaction request is used to request that update information of an intelligent contract be submitted to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
the first consensus verification module is used for determining the security level of the intelligent contract and performing consensus verification on the first transaction request based on the security level;
the first response module is used for responding or refusing to respond to the first transaction request according to the result of the consensus verification;
the first contract verification module is specifically used for determining an update rule of the intelligent contract based on the security level and a pre-configured corresponding relationship between the security level and the update rule; performing consensus verification on the first transaction request based on the update rule;
the first consensus verification module is specifically configured to perform consensus verification on a signature carried in the update information when the update rule is a first-class update rule; if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed;
when the updating rule is a second type updating rule, performing consensus verification on the signature carried by the updating information; if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed;
wherein the target transaction node comprises: some or all of the nodes corresponding to the participants of the intelligent contract, and the first transaction node;
and when the update rule is a third type update rule, determining that the result of the consensus verification is failed.
6. The apparatus of claim 5, further comprising:
a second receiving module, configured to receive a second transaction request initiated by the first transaction node, where the second transaction request is used to request that the intelligent contract be submitted to uplink, and the second transaction request includes the security level;
the second consensus verification module is used for carrying out consensus verification on the second transaction request;
and the second response module is used for responding to the second transaction request when the result of the consensus verification is passed.
7. The apparatus of claim 5 or 6,
the first response module is specifically used for responding to the first transaction request when the result of the consensus verification is passed; and refusing to respond to the first transaction request when the result of the consensus verification is failed.
8. The apparatus of claim 7,
the first transaction request comprises address information of a storage node, and the intelligent contract is stored in the storage node;
correspondingly, the first response module is specifically configured to obtain the intelligent contract based on the address information of the storage node; and updating the intelligent contract based on the updating information.
9. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or refusing to respond to the first transaction request according to the result of the consensus verification;
wherein the consensus verification of the first transaction request based on the security level comprises:
determining an update rule of the intelligent contract based on the security level and a pre-configured corresponding relationship between the security level and the update rule;
performing consensus verification on the first transaction request based on the update rule;
wherein consensus verification of the first transaction request based on the update rule comprises:
when the updating rule is a first type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed;
when the updating rule is a second type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed;
wherein the target transaction node comprises: some or all of the nodes corresponding to the participants of the intelligent contract, and the first transaction node;
and when the update rule is a third type update rule, determining that the result of the consensus verification is failed.
10. A computer-readable storage medium storing one or more programs which, when executed by an electronic device including a plurality of application programs, cause the electronic device to:
receiving a first transaction request initiated by a first transaction node, wherein the first transaction request is used for requesting to submit update information of an intelligent contract to a uplink, and the first transaction node is a node corresponding to all parties of the intelligent contract;
determining a security level of the smart contract and performing consensus verification on the first transaction request based on the security level;
responding or refusing to respond to the first transaction request according to the result of the consensus verification;
wherein the consensus verification of the first transaction request based on the security level comprises:
determining an update rule of the intelligent contract based on the security level and a pre-configured corresponding relationship between the security level and the update rule;
performing consensus verification on the first transaction request based on the update rule;
wherein consensus verification of the first transaction request based on the update rule comprises:
when the updating rule is a first type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information carries the signature of the first transaction node, determining that the result of the consensus verification is passed;
when the updating rule is a second type updating rule, performing consensus verification on the signature carried by the updating information;
if the updated information has the signature of the target transaction node, determining that the result of the consensus verification is passed;
wherein the target transaction node comprises: some or all of the nodes corresponding to the participants of the intelligent contract, and the first transaction node;
and when the update rule is a third type update rule, determining that the result of the consensus verification is failed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810586324.6A CN108833398B (en) | 2018-06-08 | 2018-06-08 | Block chain intelligent contract updating method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810586324.6A CN108833398B (en) | 2018-06-08 | 2018-06-08 | Block chain intelligent contract updating method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108833398A CN108833398A (en) | 2018-11-16 |
| CN108833398B true CN108833398B (en) | 2020-12-15 |
Family
ID=64143259
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810586324.6A Active CN108833398B (en) | 2018-06-08 | 2018-06-08 | Block chain intelligent contract updating method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108833398B (en) |
Families Citing this family (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11354727B2 (en) | 2018-11-27 | 2022-06-07 | Advanced New Technologies Co., Ltd. | System and method for improving security of smart contract on blockchain |
| US11138597B2 (en) | 2018-11-27 | 2021-10-05 | Advanced New Technologies Co., Ltd. | System and method for improving security of smart contract on blockchain |
| AU2018348329B2 (en) * | 2018-11-30 | 2020-11-05 | Advanced New Technologies Co., Ltd. | Blockchain smart contract updates using decentralized decision |
| JP6727435B2 (en) | 2018-11-30 | 2020-07-22 | アリババ・グループ・ホールディング・リミテッドＡｌｉｂａｂａ Ｇｒｏｕｐ Ｈｏｌｄｉｎｇ Ｌｉｍｉｔｅｄ | Blockchain network test platform |
| CN109377231A (en) * | 2018-12-12 | 2019-02-22 | 北京中电普华信息技术有限公司 | A kind of the credits method of commerce and system of supply chain finance |
| CN110032598B (en) * | 2018-12-20 | 2020-05-12 | 阿里巴巴集团控股有限公司 | Method and device for updating field and electronic equipment |
| CN109451061B (en) * | 2018-12-20 | 2021-06-01 | 全链通有限公司 | Contract adjustment processing method and system for block chain |
| CN109885612B (en) * | 2018-12-26 | 2021-04-20 | 联动优势科技有限公司 | Synchronous validation method and device for intelligent contracts of block chains |
| CN109859038B (en) * | 2018-12-26 | 2021-06-25 | 联动优势科技有限公司 | Method and device for taking block chain intelligent contract into effect |
| CN109547488B (en) * | 2018-12-29 | 2021-11-05 | 杭州趣链科技有限公司 | Credible data computing and exchanging system based on alliance block chain |
| CN109934593B (en) * | 2019-03-26 | 2023-07-04 | 众安信息技术服务有限公司 | Design method and device for realizing block chain system supporting multiple signatures |
| CN110009362B (en) * | 2019-04-02 | 2021-07-06 | 北京众享比特科技有限公司 | Block chain intelligent contract modification method and device and computer readable storage medium |
| US11188521B2 (en) * | 2019-06-05 | 2021-11-30 | International Business Machines Corporation | Flexible transaction validation |
| US11283594B2 (en) | 2019-06-05 | 2022-03-22 | International Business Machines Corporation | Context data update in a blockchain network |
| CN110413304B (en) * | 2019-07-31 | 2023-07-14 | 中国工商银行股份有限公司 | Intelligent contract hot upgrading method and device based on block chain network |
| CN110427385B (en) * | 2019-08-02 | 2022-06-10 | 中国工商银行股份有限公司 | Block chain data updating method, related node and block chain |
| CN110751555B (en) * | 2019-09-25 | 2021-01-12 | 支付宝(杭州)信息技术有限公司 | Method and device for realizing contract calling based on FPGA |
| CN110766554A (en) * | 2019-09-29 | 2020-02-07 | 南京金宁汇科技有限公司 | Intelligent contract consensus method, system and storage medium based on multi-centralization management |
| TWI724667B (en) * | 2019-12-03 | 2021-04-11 | 臺灣銀行股份有限公司 | System of identity management and authorization and method thereof |
| CN111182527B (en) * | 2019-12-27 | 2022-07-26 | 深圳市云伽智能技术有限公司 | OTA (over the air) firmware upgrading method and device, terminal equipment and storage medium thereof |
| CN111445257A (en) * | 2020-03-27 | 2020-07-24 | 北京瑞卓喜投科技发展有限公司 | Block chain-based evidence-based transaction verification method and device, memory and computer |
| CN111581077A (en) * | 2020-04-08 | 2020-08-25 | 腾讯科技（深圳）有限公司 | Intelligent contract testing method and device |
| CN111639127B (en) * | 2020-05-11 | 2022-05-13 | 支付宝实验室(新加坡)有限公司 | Method, system, device and equipment for updating intelligent contract |
| CN113672988B (en) * | 2020-05-14 | 2023-11-10 | 腾讯科技（深圳）有限公司 | Information management method, system, medium and electronic equipment based on block chain |
| CN111402058B (en) * | 2020-05-29 | 2021-05-04 | 支付宝(杭州)信息技术有限公司 | Data processing method, device, equipment and medium |
| CN111885050B (en) * | 2020-07-21 | 2022-01-11 | 腾讯科技（深圳）有限公司 | Data storage method and device based on block chain network, related equipment and medium |
| CN111859457B (en) * | 2020-07-31 | 2024-10-18 | 联想(北京)有限公司 | Intelligent contract setting method and system |
| CN112001794A (en) * | 2020-09-02 | 2020-11-27 | 上海市建筑学会 | Intelligent contract generating method, computer device, and storage medium |
| CN112085604A (en) * | 2020-09-10 | 2020-12-15 | 北京金山云网络技术有限公司 | Method and device for upgrading intelligent contract |
| CN114327531A (en) * | 2020-11-30 | 2022-04-12 | 青岛海尔电冰箱有限公司 | Refrigerator program upgrading method based on block chain and refrigerator |
| CN112651741B (en) * | 2021-01-04 | 2024-06-18 | 北京京东乾石科技有限公司 | Block chain-based data processing method and device |
| CN112835605B (en) * | 2021-03-30 | 2024-02-20 | 中国工商银行股份有限公司 | Block chain version gray scale upgrading verification method, device and system |
| CN113220701B (en) * | 2021-05-25 | 2023-05-02 | 成都佰纳瑞信息技术有限公司 | Block chain-based data structure self-adaptive change upgrading method, device, equipment and product |
| TWI778733B (en) * | 2021-08-02 | 2022-09-21 | 新加坡商鴻運科股份有限公司 | Blockchain-based rule updating method, electronic equipment and storage medium |
| CN114780968A (en) * | 2022-06-23 | 2022-07-22 | 国网区块链科技(北京)有限公司 | Intelligent contract upgrading method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106709704A (en) * | 2016-11-23 | 2017-05-24 | 杭州秘猿科技有限公司 | Intelligent contract upgrading method based on permission chain |
| CN106778329A (en) * | 2016-11-28 | 2017-05-31 | 中国银行股份有限公司 | A kind of block chain intelligence contract template dynamic updating method, apparatus and system |
| CN107464148A (en) * | 2017-08-23 | 2017-12-12 | 众安信息技术服务有限公司 | A kind of intelligent contract upgrade method and system based on alliance's chain |
| CN107835166A (en) * | 2017-10-31 | 2018-03-23 | 济南浪潮高新科技投资发展有限公司 | A kind of high value crystal retroactive method and device based on block chain |
| US9990504B1 (en) * | 2017-12-18 | 2018-06-05 | Northern Trust Corporation | Systems and methods for generating and maintaining immutable digital meeting records within distributed network nodes |
-
2018
- 2018-06-08 CN CN201810586324.6A patent/CN108833398B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106709704A (en) * | 2016-11-23 | 2017-05-24 | 杭州秘猿科技有限公司 | Intelligent contract upgrading method based on permission chain |
| CN106778329A (en) * | 2016-11-28 | 2017-05-31 | 中国银行股份有限公司 | A kind of block chain intelligence contract template dynamic updating method, apparatus and system |
| CN107464148A (en) * | 2017-08-23 | 2017-12-12 | 众安信息技术服务有限公司 | A kind of intelligent contract upgrade method and system based on alliance's chain |
| CN107835166A (en) * | 2017-10-31 | 2018-03-23 | 济南浪潮高新科技投资发展有限公司 | A kind of high value crystal retroactive method and device based on block chain |
| US9990504B1 (en) * | 2017-12-18 | 2018-06-05 | Northern Trust Corporation | Systems and methods for generating and maintaining immutable digital meeting records within distributed network nodes |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108833398A (en) | 2018-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108833398B (en) | Block chain intelligent contract updating method, device and equipment | |
| US20240028587A1 (en) | System and method for a hybrid contract execution environment | |
| US11514164B2 (en) | Methods and systems for secure and reliable identity-based computing | |
| CN109981679B (en) | Method and apparatus for performing transactions in a blockchain network | |
| Bryatov et al. | Blockchain technology in the pharmaceutical supply chain: Researching a business model based on Hyperledger Fabric | |
| JP7284747B2 (en) | Execution of smart contracts with distributed cooperation | |
| US20190050855A1 (en) | Blockchain-based systems, methods, and apparatus for securing access to information stores | |
| CN109040029B (en) | Method and apparatus for executing transactions in a blockchain | |
| JP2022103346A (en) | Method and system for secure and reliable identity-based computing | |
| US11475453B2 (en) | System and techniques for utilizing a smart contracts library | |
| US20240346241A1 (en) | Data reuse computing architecture | |
| TWI830722B (en) | System and method for a thing machine to perform models | |
| CN110263580B (en) | Data processing method and device based on block chain and block chain link points | |
| CN111967958B (en) | Drug supply management system and method based on blockchain | |
| TW202030691A (en) | Block chain intelligent contract execution method, device and electronic apparatus | |
| CN115705571A (en) | Protecting privacy of auditable accounts | |
| CN110009497B (en) | Block chain-based decision method and device and electronic equipment | |
| Alwhishi et al. | Three-valued model checking smart contract systems with trust under uncertainty | |
| CN116975901A (en) | Identity verification method, device, equipment, medium and product based on block chain | |
| Baset et al. | Blockchain Development with hyperledger: build decentralized applications with hyperledger fabric and composer | |
| CN118052620A (en) | Task scheduling method, device, equipment and medium based on responsibility chain | |
| Margret et al. | Smarter and resilient smart contracts applications for smart cities environment using blockchain technology | |
| CN116997895A (en) | Reducing transaction aborts in an execution ordering validation blockchain model | |
| Liu et al. | A cloud‐based and web‐based group decision support system in multilingual environment with hesitant fuzzy linguistic preference relations | |
| Sun et al. | Smart Contract as a Service: A Paradigm of Reusing Smart Contract in Web3 Ecosystem |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200717 Address after: B1910, building 9, zone 2, Shenzhen Bay science and technology ecological park, 3609 Baishi Road, community, high tech Zone, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province Applicant after: Shenzhen smart chain Future Technology Co., Ltd Address before: 310026 401 unit -1, 3 unit of Wen Yi Road 1218, Cang Qian Road, Yuhang District, Hangzhou, Zhejiang, China, 401 Applicant before: ZHEJIANG ULTRAIN SPACE TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 518054 unit 201, 202, 203, 2nd floor, unit 301, 302, 303, 3rd floor, building A1, commercial plaza, 191 science Avenue, Huangpu District, Guangzhou City, Guangdong Province Patentee after: Guangzhou smart chain Future Technology Co.,Ltd. Address before: B1910, building 9, zone 2, Shenzhen Bay science and technology ecological park, 3609 Baishi Road, high tech Zone community, Yuehai street, Nanshan District, Shenzhen, Guangdong 518054 Patentee before: Shenzhen smart chain Future Technology Co., Ltd |