Method for executing smart contract and blockchain node

A blockchain node for executing a smart contract, comprising:

• one or more processors;
• and
• one or more computer-readable memories coupled to the one or more processors and having executable instructions stored thereon that are executable by the one or more processors to perform acts including:
• after a smart contract of bytecodes has been deployed in a blockchain network, determining that a bytecode of the bytecodes of the smart contract is a high-frequency type of bytecode or a low-frequency type of bytecode via a hotspot analysis;
• starting, at a first time point when the smart contract is not in execution, to compile the high-frequency type of bytecode of the bytecodes of the smart contract into a first machine code by using just-in-time (JIT) compilation and storing the first machine code locally at a blockchain node of the blockchain network;
• at a second time point different from the first time point and in execution of the smart contract, interpreting the low-frequency type of bytecode into a second machine code, the second machine code not being stored locally at the blockchain node;
• and
• in the execution of the smart contract, improving a speed of the execution by directly executing the first machine code corresponding to the high-frequency type of bytecode of the smart contract in response to the first machine code being locally stored.

A non-transitory storage medium, the storage medium having executable instructions stored thereon that are executable by one or more processors to perform acts including:

• after a smart contract of bytecodes has been deployed in a blockchain network, determining that a bytecode of the bytecodes of the smart contract is a high-frequency type of bytecode or a low-frequency type of bytecode via a hotspot analysis;
• starting, at a first time point when the smart contract is not in execution, to compile the high-frequency type of bytecode of the bytecodes of the smart contract into a first machine code by using just-in-time (JIT) compilation and storing the first machine code locally at a blockchain node of the blockchain network;
• at a second time point different from the first time point and in execution of the smart contract, interpreting the low-frequency type of bytecode into a second machine code, the second machine code not being stored locally at the blockchain node;
• and
• in the execution of the smart contract, improving a speed of the execution by directly executing the first machine code corresponding to the high-frequency type of bytecode of the smart contract in response to the first machine code being locally stored.