bsc
bsc copied to clipboard
we have a requirement to trace historical transactions within a week, but we encountered the following error
Hello, we have a requirement to trace historical transactions within a week, but we encountered the following error.
We are using the default pruning configuration with the following startup command.
After consulting ChatGPT, we got the response that lowering the pruning block number indirectly increases the amount of retained state data.
By looking at the source code, we found that it might be possible to break through this limitation by modifying the defaultTraceReexec variable. We are concerned about potential issues this change might cause.
For instance, if the current block height is N, and we want to trace block N-1000, with the pruning configuration set to 2000, and we change defaultTraceReexec from 128 to 2000, will the trace results be consistent with the real state?