System and method for implementing different types of blockchain contracts
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for implementing blockchain contracts are provided. One of the methods includes: obtaining bytecode of a blockchain contract, wherein the bytecode comprises an indicator indicating a type of the blockchain contract; determining a virtual machine corresponding to the type based at least on the indicator; and triggering the determined virtual machine to execute the blockchain contract.
1. A computer-implemented method for implementing blockchain contracts, comprising:
obtaining, by a blockchain node from a client, (1) first bytecode of a first blockchain contract compiled from first source code of the first blockchain contract and (2) second bytecode of a second blockchain contract compiled from second source code of the second blockchain contract, the first source code comprising a first indicator indicating that the first blockchain contract is a native contract, and the second source code comprising a second indicator indicating that the second blockchain contract is a solidity contract, wherein:
the first indicator is added by the client to the first source code based on a high-level programming language of the first source code,
the second indicator is added by the client to the second source code based on a high-level programming language of the second source code,
the first source code is written in a high-level programming language other than solidity,
the second source code is written in solidity, and
the blockchain node comprises a plurality of language-specific virtual machines configured to respectively execute bytecode of a plurality of blockchain contracts written in different high-level programming languages;
determining, by the blockchain node from the plurality of language-specific virtual machines, (1) a first language-specific virtual machine corresponding to the first indicator and (2) a second language-specific virtual machine corresponding to the second indicator; and
triggering, by the blockchain node, (1) the first language-specific virtual machine to execute the first blockchain contract and (2) the second language-specific virtual machine to execute the second blockchain contract.
2. The method of claim 1 ,
wherein the first bytecode is compiled from the first source code by the client and the second bytecode is compiled from the second source code by the client.
3. The method of claim 1 , wherein obtaining (1) the first bytecode of the first blockchain contract compiled from the first source code of the first blockchain contract and (2) the second bytecode of the second blockchain contract compiled from the second source code of the second blockchain contract comprises:
obtaining, by the blockchain node, the first source code and the second source code from the client; and
compiling, by the blockchain node, the first source code into the first bytecode and the second source code into the second bytecode.
4. The method of claim 1 , wherein obtaining (1) the first bytecode of the first blockchain contract compiled from the first source code of the first blockchain contract and (2) the second bytecode of the second blockchain contract compiled from the second source code of the second blockchain contract comprises:
obtaining, by the blockchain node from the client, the first bytecode and the second bytecode through a remote procedure call interface.
5. The method of claim 1 , wherein determining (1) the first language-specific virtual machine corresponding to the first indicator and (2) the second language-specific virtual machine corresponding to the second indicator comprises:
determining the first language-specific virtual machine by parsing a first and a second bytes of the first bytecode; and
determining the second language-specific virtual machine by parsing a first and a second bytes of the second bytecode.
6. The method of claim 1 , wherein:
the first indicator as compiled into a part of the first bytecode and the second indicator as compiled into a part of the second bytecode are in a binary representation.
7. The method of claim 1 , wherein:
the first indicator as compiled into a part of the first bytecode and the second indicator as compiled into a part of the second bytecode are in a hexadecimal representation.
8. The method of claim 1 , wherein:
a virtual machine corresponding to c++ is GNU compiler collection (GCC);
a virtual machine corresponding to java is java virtual machine (JVM);
a virtual machine corresponding to solidity is ethereum virtual machine (EVM);
a virtual machine corresponding to python is python virtual machine (PVM); and
the blockchain node comprises at least two of the GCC, JVM, EVM, and PVM.
9. A system for implementing blockchain contract, the system comprising one or more processors and one or more non-transitory computer-readable memories coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the system to perform operations comprising:
obtaining, by a blockchain node from a client, (1) first bytecode of a first blockchain contract compiled from first source code of the first blockchain contract and (2) second bytecode of a second blockchain contract compiled from second source code of the second blockchain contract, the first source code comprising a first indicator indicating that the first blockchain contract is a native contract, and the second source code comprising a second indicator indicating that the second blockchain contract is a solidity contract, wherein:
the first indicator is added by the client to the first source code based on a high-level programming language of the first source code,
the second indicator is added by the client to the second source code based on a high-level programming language of the second source code,
the first source code is written in a high-level programming language other than solidity,
the second source code is written in solidity, and
the blockchain node comprises a plurality of language-specific virtual machines configured to respectively execute bytecode of a plurality of blockchain contracts written in different high-level programming languages;
determining, by the blockchain node from the plurality of language-specific virtual machines, (1) a first language-specific virtual machine corresponding to the first indicator and (2) a second language-specific virtual machine corresponding to the second indicator; and
triggering, by the blockchain node, (1) the first language-specific virtual machine to execute the first blockchain contract and (2) the second language-specific virtual machine to execute the second blockchain contract.
10. The system of claim 9 , wherein:
the first bytecode is compiled from the first source code by the client, and the second bytecode is compiled from the second source code by the client.
11. The system of claim 9 , wherein obtaining (1) the first bytecode of the first blockchain contract compiled from the first source code of the first blockchain contract and (2) the second bytecode of the second blockchain contract compiled from the second source code of the second blockchain contract comprises:
obtaining, by the blockchain node from the client, the first bytecode and the second bytecode through a remote procedure call interface.
12. The system of claim 9 , wherein:
a virtual machine corresponding to c++ is GNU compiler collection (GCC);
a virtual machine corresponding to java is java virtual machine (JVM);
a virtual machine corresponding to solidity is ethereum virtual machine (EVM);
a virtual machine corresponding to python is python virtual machine (PVM); and
the blockchain node comprises at least two of the GCC, JVM, EVM, and PVM.
13. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising, comprising:
obtaining, by a blockchain node from a client, (1) first bytecode of the first blockchain contract compiled from first source code of the first blockchain contract and (2) second bytecode of a second blockchain contract compiled from second source code of the second blockchain contract, the first source code comprising a first indicator indicating that the first blockchain contract is a native contract, and the second source code comprising a second indicator indicating that the second blockchain contract is a solidity contract, wherein:
the first indicator is added by the client to the first source code based on a high-level programming language of the first source code,
the second indicator is added by the client to the second source code based on a high-level programming language of the second source code,
the first source code is written in a high-level programming language other than solidity,
the second source code is written in solidity, and
the blockchain node comprises a plurality of language-specific virtual machines configured to respectively execute bytecode of a plurality of blockchain contracts written in different high-level programming languages;
determining, by the blockchain node from the plurality of language-specific virtual machines, (1) a first language-specific virtual machine corresponding to the first indicator and (2) a second language-specific virtual machine corresponding to the second indicator; and
triggering, by the blockchain node, (1) the first language-specific virtual machine to execute the first blockchain contract and (2) the second language-specific virtual machine to execute the second blockchain contract.
14. The storage medium of claim 13 ,
wherein the first bytecode is compiled from the first source code by the client, and the second bytecode is compiled from the second source code by the client.
15. The storage medium of claim 13 , wherein obtaining (1) the first bytecode of the first blockchain contract compiled from the first source code of the first blockchain contract and (2) the second bytecode of the second blockchain contract compiled from the second source code of the second blockchain contract comprises:
obtaining, by the blockchain node from the client, the first bytecode and the second bytecode through a remote procedure call interface.
16. The storage medium of claim 13 , wherein:
the first indicator corresponds to a first byte of the first bytecode, and the second indicator corresponds to a first byte of the second bytecode.
17. The storage medium of claim 13 , wherein:
as compiled into a part of the second bytecode are in a binary representation.
18. The storage medium of claim 13 , wherein:
the first indicator as compiled into a part of the first bytecode and the second indicator as compiled into a part of the second bytecode are in a hexadecimal representation.
19. The storage medium of claim 13 , wherein:
a virtual machine corresponding to c++ is GNU compiler collection (GCC);
a virtual machine corresponding to java is java virtual machine (JVM);
a virtual machine corresponding to solidity is ethereum virtual machine (EVM);
a virtual machine corresponding to python is python virtual machine (PVM); and
the blockchain node comprises at least two of the GCC, JVM, EVM, and PVM.