evm

🎉 Description

The ECDSA contract has a function toEthSignedMessage(bytes32), but we should have a function that works for any length of a bytes array:

function toEthSignedMessage(bytes s) pure internal returns (bytes32) {
  return keccak256(
    "\x19Ethereum Signed Message:\n",
    uintToBytes(s.length),
    s);
}

Where uintToBytes is implemented from an ideally

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

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

Depends on #1048

Another Ethers issue 😄 : I lately had the use case where I wanted to pull in some tx data via RPC with Ethers which I wanted to use in some client testing context but I finally gave up since the conversion to our tx format here was not so clearly spottable and I used some direct client data extraction

We can safely disallow any use of solc below 0.4.25.

https://blog.soliditylang.org/2021/04/21/custom-errors/

Currently if a solidity file throws a custom error the dapptools trace will just show the abi encoded hash of the error.

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

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

Motivation

It’s good to support as many local languages as it possible. One of steps of it is creating easy method to support multiple languages in docs. Currently documentation located in staketechnologies/plasmdocs repo.

Results

Result for closing this is PR into staketechnologies/plasmdocs repo with implementation multi language feature for gitbook generator and moving

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

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