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

There is actually a lot of redundancy between the ETH and LES protocol implementation. This should be combined into a superclass sitting between e.g. ETH and EventEmitter at some point. This will likely lead to a substantially cleaner implementation of the subclasses, increase readability as well as ease adding new features and avoid introducing consistency gaps along the way.

(this new sup

Component

Cast

Have you ensured that all of these are up to date?

• Foundry
• Foundryup

What version of Foundry are you on?

cast 0.1.0 (fe2dbfe 2022-02-04T00:24:58.188894+00:00)

What command(s) is the bug in?

cast keccak and possibly others

Operating System

macOS (amd)

Describe the bug

Right now, cast keccak does not handle strings vs. bytes correctly

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.

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.

With 32+ cody padding it is aways safe to up to 32 bytes when loading push data. The partial word can always be read as 8 bytes + bswap + shift.

TODO:

• Clean-up the change which pads code with fixed 33 bytes.
• Implement optimization for all PUSH variants.

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