qk-santi

Hi @hkalina ! We checked out 0b72c064bc49b209455a983b160df6e94e730362 and it was totally impossible to use. Sometimes it won't even add a new block once restarted and other times it will never...

@Inphi, thanks for the quick response! How would be the way to send the code inside `params/tracer`? I've tried a few ways, but getting always: `{"jsonrpc":"2.0","id":null,"error":{"code":-32600,"message":"failed to parse request"}}`

@Inphi Great! It works like a charm :smile: Leaving this gist with a test request and the code escaped in case it is useful for anyone: https://gist.github.com/qk-santi/c73f01788c2bf75d09cc330efe4d730d

Is this due to reaching the internal EVM timeout when processing each call? Would we be able to have a similar flag to Geth's `--rpc.evmtimeout` available to override that default...

Is there any plan to support proofs for blocks older than 1k blocks? ``` {"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"requested block is too old, block must be within 1000 blocks of the head block number...

I initially thought it would be just the first 4,5M blocks as in #372 , but it is still happening on block 6,045,149 (0x5C3DDD) ``` curl --request POST --data '[{"id":1,"jsonrpc":"2.0","method":"trace_block","params":["0x5C3DDD"]}]'...