Cross-block contract asynchronous calling system

Abstract

The invention discloses a cross-block contract asynchronous calling system. The system comprises a distributed system verification unit, a distributed contract execution unit and a contract execution cache unit, wherein the distributed system verification unit comprises one or more service nodes and a plurality of verification nodes, the verification nodes are used for verifying consented {TX}, and {TX} comprises a contract calling request TX and a payment request TX; the distributed contract execution unit is located at a far end of a local verification unit, performs communication with the verification unit through a predefined protocol and is used for acquiring information needed for contraction execution and returning a result to the verification nodes after contract execution is completed; and the contract execution cache unit is used for receiving the contract calling request from the verification nodes, sending the request to the contract execution unit, receiving a contract execution result and returning a current contract execution state to the verification nodes so as to realize asynchronous calling of a contract. According to the system, block consensus does not depend on the contract execution result, the concurrence amount of contract execution and the number of contracts capable of being supported by blocks can be increased, and the fault-tolerant capability of the system is improved.

Description

technical field [0001] The invention relates to the technical field of block chains, in particular to a cross-block asynchronous call contract system. Background technique [0002] Existing smart contracts are executed in a synchronous manner, using transaction triggers or automatically triggering contract calls. When the contract is actually executed, the consensus mechanism of the blockchain must wait for the contract to be executed and return the result before continuing to operate, thus completing the current Block consensus. [0003] The above smart contract execution method has the following defects: [0004] (1) The speed of contract execution seriously affects the time of block generation: [0005] Because the block consensus depends on the result of contract execution, each node must reach a consensus on the consistency of the contract result. Therefore, the speed of contract execution directly affects the subsequent operation of the block, resulting in a delay in...

AI Technical Summary

Problems solved by technology

[0007] When the frequency of block chain generation is usually roughly fixed, in the same period of time, the execution speed of a contract will directly affect the execution of other contracts in the same block. In extreme cases, a malicious contract may cause system Unable to process other contracts, resulting in greatly reduced concurrency of contract processing

[0008] (3) Fault tolerance during contract execution is limited:

However, the total number of contracts that the system can support is limited by the total amount of gas. If the code of the contract becomes more and more complex, the number of contracts that the entire system can support will become less and less; in addition, the Ethereum consensus time is limited, and the maximum value of gas is not Cannot increase significantly

Images