You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debug_traceBlockByNumber JSON-RPC call is issued for block 0xb542, the response is "intrinsic gas too low" error. This ONLY happens when the node is fully synced -- when the node is syncing, the command works normally. There are other blocks which give the same error, this is just an example.
The result I get (when the node is fully synced): {"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"intrinsic gas too low"}}
The (expected) result I get when the node is still syncing (restart the node and issue the request fast enough): {"jsonrpc":"2.0","id":1,"result":[{"result":{"0x01434e4ac3238bec44a39ad642ababbb68d097e6":{"balance":"0x10c570cb5c6a798000"},"0x9a049f5d18c239efaa258af9f3e7002949a977a0":{"balance":"0x0","storage":{"0x0000000000000000000000000000000000000000000000000000000000000000":"0x0000000000000000000000000000000000000000000000000000000000000000"}},"0xa1e4380a3b1f749673e270229993ee55f35663b4":{"balance":"0x6c3ed29108159090c5","nonce":3}},"txHash":"0x6c929e1c3d860ee225d7f3a7addf9e3f740603d243260536dfa2f3cf02b51de4"}]}
Describe the bug
When
debug_traceBlockByNumber
JSON-RPC call is issued for block0xb542
, the response is"intrinsic gas too low"
error. This ONLY happens when the node is fully synced -- when the node is syncing, the command works normally. There are other blocks which give the same error, this is just an example.Steps to reproduce
Run:
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc": "2.0", "method": "debug_traceBlockByNumber", "params": ["0xb542", {"tracer":"prestateTracer"}, {"tracerConfig":"diffMode"}], "id":1}' localhost:8545
The result I get (when the node is fully synced):
{"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"intrinsic gas too low"}}
The (expected) result I get when the node is still syncing (restart the node and issue the request fast enough):
{"jsonrpc":"2.0","id":1,"result":[{"result":{"0x01434e4ac3238bec44a39ad642ababbb68d097e6":{"balance":"0x10c570cb5c6a798000"},"0x9a049f5d18c239efaa258af9f3e7002949a977a0":{"balance":"0x0","storage":{"0x0000000000000000000000000000000000000000000000000000000000000000":"0x0000000000000000000000000000000000000000000000000000000000000000"}},"0xa1e4380a3b1f749673e270229993ee55f35663b4":{"balance":"0x6c3ed29108159090c5","nonce":3}},"txHash":"0x6c929e1c3d860ee225d7f3a7addf9e3f740603d243260536dfa2f3cf02b51de4"}]}
Node logs
Platform(s)
Linux (x86)
Container Type
Not running in a container
What version/commit are you on?
reth Version: 1.1.4
Commit SHA: 15fac08
Build Timestamp: 2024-12-11T10:16:09.724578576Z
Build Features: asm_keccak,jemalloc
Build Profile: maxperf
What database version are you on?
Current database version: 2
Local database version: 2
Which chain / network are you on?
mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: