evm

The cpp-ethereum homepage is not exactly helpful... http://cpp-ethereum.org/ which just takes you to here: http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/ which only helps with building and installing.. and the only useful link is the "Running" which is only this: "Running eth without any argument will synchronise your node to the public blockchain. It is also possible to create or

Currently TraceConfig type on protobuf has Timeout as string and is later parse inside of the function. This Timeout parameter should be of type time.duration to avoid having this extra step.

This was done in the first place to comply with Go-Ethereum debug_traceTransaction grpc endpoint.

What is wrong?

Previous to ethereum/py-evm#1805 we had classes like eth.vm.BaseVM that served as the reference. Now, we have interfaces defined in eth.abc.

There are now two primary problems.

• Many of our docstrings might still refer to the wrong class. Most class references in docstrings should be referencing the abc base classes now.
• Most of the met

Would be really nice to get native BSC support :)

Right now env vars that accept boolean-esque values (like DAPP_TEST_FFI, HEVM_RPC, and DAPP_BUILD_OPTIMIZE) each require slightly different values to represent true.

Sometimes 1 means true, sometimes yes means true, sometimes any non 0 value means true, and sometimes the variable being set at all means true!

Ideally all boolean-esque env vars would only accept one of these value

We can safely disallow any use of solc below 0.4.25.

Add an example to load file from a directory along with https://remix-ide.readthedocs.io/en/latest/locations.html#load-one-of-the-default-remix-files

The current config allows us to set up only one URL for JsonRPC. For security reasons, our node has to be able to set up many URLs/ports. After the merge, we will need to listen to different ports for different RPC modules. The node should be able to duplicate RPC modules for many ports. AFAIK, the consensus clients use these modules: engine, eth, net, subscribe, web3, and maybe more.

The ques

We should create a corpus of tests to verify that CFG recovery is accurate and complete, and there are no regressions.

The ethabi::errors::InvalidData error could use some more info such that the user can find which part of their input is invalid.

recently CI failed many times testing cluster because of port already used, which can be very annoying.