pocinnovation / evmjs Goto Github PK

• Setup npm's package.json
• Setup ts_sources directory
• Setup sources directory
• Setup jest

The core class should take several arguments when built:

• smart contract bytecode
• address of caller
• data payload of caller

For V0.1, we will only take these arguments. When implementing the opcodes, you will see that you will need other variables (like block number, balances etc) Ignore them for the moment and set default values on them.

No gas for the moment, when you run a method, it either succeed, fail, or run infinitely.
Gas will be added in V1.

The final script should be able to take command line arguments and give them to the Core Class. Then it should run a simulation and output any result

This is how the command line script should work:

node script.js smart_contract.sol method_name arg1 arg2 ... argn

You should ouput as much informations as possible:

• State after call
• Return values if any
• Storage after call

Create a encoder that takes as argument an ABI definition, a method name and a non-fixed amount of arguments, and returns an encoded output (an hexadecimal string).

This link might help you =>https://solidity.readthedocs.io/en/develop/abi-spec.html

The examples section is explaining very well how to encode.

• Use the ABI definition of the smart contract to determine the number of arguments and their types
• Use the method name to create the method signature described in the document above
• Use the remaining arguments and encode them according to the documentation above
• Return the result string

Implement all the EVM OpCodes.

All of them should take the exact same arguments:

• Current PC (Program Counter)
• Contract Bytecode (the bytecode of the smart contract as he would be after being compiled)
• Data Bytecode (the bytecode received from the transaction)
• Memory Data (Memory, Stack and Storage sections)
• Env (all the data accessible from the code, block number, transaction hash etc)

Also think of a smart way of retrieving internal errors (throws, stack underflows ...) and display them with the most possible informations.

• Create README.md file