fix(rpc/trace): trace_filter filting with trace's address #9722
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
waiting for alloy-rs/alloy#1090 to be merged first.
Currently, we're filtering the trace result by transaction's from and to address, but indeed this API should filtering with trace {action, result}'s address, the latter is more useful and meaningful.
eg I want to fetch the traces with the below RPC:
reth's can't produce any results, because https://etherscan.io/address/0x6b75d8af000000e20b7a7ddf000ba900b4009a80 is a contract, no exists in tx's from_address.