Closed SinErgy84 closed 4 months ago
This is due to pruning or fast syncing from block X, big/full ranges will only work on archive mode. I think in all call/trace methods we need to catch those exceptions and return information about state being not available.
@LukaszRozmej why it worked fine on parity (openethereum) even on a fast node with pruning activated?
@LukaszRozmej why it worked fine on parity (openethereum) even on a fast node with pruning activated? separate
Parity stored traces in a separate database. We are not. We could potentially change that but only for full synced nodes (with pruning). The tradeoff would be an increased disk footprint.
@LukaszRozmej I think many here are migrating from OpenEthereum (Parity) so for them that solution would be viable, please implement it if it's easy and possible.
Increased disk footprint like +50-100 GB? That's much better tradeoff comparing to running Archive node which requires 6TB space. Thank you.
@gituser It is possible, but far from easy. OE/Parity handles sync of this DB in their warp sync?
@gituser It is possible, but far from easy. OE/Parity handles sync of this DB in their warp sync?
Not sure, but I think OE/parity only allowed tracing if you sync from scratch using Fast sync.
Also you had to specify tracing: on
in database options before starting to sync in order to generate traces DB.
@gituser @SinErgy84 created a plugin that stores the traces and retrives them through json rpc, the only thing is this needs FullSync (but not archive state).
Describe the bug While tracing different transactions on the mainnet for my use case, I've found a bug in
trace_filter
if block delta between FromBlock and ToBlock gets to large. The response from the client looks like this:To Reproduce Call
curl --data '{"method":"trace_filter","params":[{"fromBlock":"0xe3ed9c","toBlock":"0xe3eeab"}],"id":1,"jsonrpc":"2.0"}' -H "Content-Type: application/json" -X POST 172.17.0.1:18546
for example with block delta from 14937500 to 14937771Expected behavior
trace_filter
internal error
Desktop (please complete the following information):
Additional context The client is fully synced with the mainnet. config: