Paweł Bylica

I changed the name for the "full unmodified code" to `raw_code`. Any better ideas? - `raw_code` - `account_code` - `original_code` - `full_code` - `container_code`

Sorry, geth don't support this option any more. This information is outdated.

We don't verify signatures at all, but we can start doing so in the future (as we have some kind of ecrecovery implemented). In general, `evmone-blockchaintest` don't pass all the...

We simply don't have all historical "transitional" revisions added. You can add more in: https://github.com/ethereum/evmone/blob/master/test/utils/utils.cpp#L45. Please make a PR with what you need.

@rodiazet or me will do this in evmone.

I will implement this in evmone for testing but maybe I could expose "system calls" to Silkworm too.

First of all, I think node and sentry should have its own secp256k1 contexts. They differ in capabilities and sentry is additionally handling private keys (for that you can consider...

Option 2 is probably the quickest. I can make a PR if you this is good start.

Reading the context is thread safe (parameter `const secp256k1_context*`), creating/randomizing it is not (parameter `secp256k1_context*`). You can have single context for both capabilities `allow_verify=true, allow_sign=true`. I don't think there are...

It looks I'm also affected by this although I have `to`/`from` defined for my type. I've got the error: ``` glaze/beve/write.hpp:102:56: error: no member named 'no_header' in 'glz::detail::to' ```