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

KS-THA-F-14

in ethereum/rpc/namespaces/debug/trace.go , ethereum/rpc/namespaces/debug/internal.go , ethereum/rpc/namespaces/debug/utils.go , ethereum/rpc/websockets.go

Errors returned when closing files are not properly handled. This can cause panics. Moreover, deferring unsafe method "Close" on type "*os.File" can create panic.
We recommend always handling errors when closing files an

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

Adding the new debugging capabilities (see title) within the devp2p packages along #1449 had the side effect of producing redundant messages on certain DEBUG logger combinations, mostly visible if the plain devp2p:* logger is used, see e.g.:

This is distracting and reduces ove

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

It will help to observe consensus issues. In geth the bad blocks are saved in the database. However, we can start with having the objects in memory.
The method is used in https://forkmon.ethdevops.io/

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.