evm

https://github.com/tharsis/ethermint/blob/main/crypto/ethsecp256k1/ethsecp256k1.go#L21

probably worth mentioning it's the compressed form in the comments

What is wrong?

• After London changes, certain genesis header params became unconfigurable. Introduce back the ability to configure block_number. See eth-tester issue #225.

How can it be fixed

• fill_header_params_from_parent() needs the ability to pass in a block_number kwarg to be configurable again. This call is made fr

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

deploying libraries can take a long time. One can easily skip this stage if we make it possible to save the deployed library state and pass it to dapp test:

1. Write a new little dapp helper script which is the dapp --library-addresses above
2. Make dapp build and dapp --make-library-state use this helper script instead
3. Allow a flag --state to be passed to dapp test (probably a

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 can safely disallow any use of solc below 0.4.25.

We should add some wallet management commands:

1. cast wallet new: Creates a new random keypair, outputs it in some format (maybe directly to stdout, maybe encrypted json keystore)
2. cast wallet address: Given a private key it converts it to an address
3. cast wallet sign: Given a private key and a message it signs the message (or its hash maybe prefixed with eth signed message?)
4. `ca

Describe the solution you'd like
Nethermind currently uses the Parity chainspec format while virtually all other clients use the Geth chainspec format. It would be great for composability if Nethermind also supported the Geth chainspec format

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

First of all, when upgrading CI to clang-13 to do coverage report, the llvm-profdata reports malformed data. So we need to make it work with clang-13 first. Try reproducing the issue locally with clang-13 toolchain.

The CI steps: https://github.com/ethereum/evmone/blob/dca15dfd3a7a998b38821061e329d54df41484e6/circle.yml#L335-L357
Clang documentation: https://clang.llvm.org/docs/SourceBasedC

Summary of Bug

1. Describe

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