[Feature] Filter::filter(Log) -> Option<Log>

[kayabaNerve]

Component

rpc

Describe the feature you would like

Filters can specify a block range to fetch all logs within that range. Sometimes, the desired range is a single transaction. This leaves the user:

A) To fetch all logs within the block, then filter by transaction ID
B) To fetch all logs within the transaction, then filter by topics and so on

The former is trivial, yet requires requesting the data of a larger object. The latter would be trivial if filters could be applied to in-memory logs, but unfortunately, they cannot be at this time.

The proposed fn would check if a given Log matches the Filter in order to make the latter flow trivial.

Additional context

No response

[mattsse]

tbh unclear what this means, could you perhaps prototype this?

[kayabaNerve]

If I have a Log in memory, I just want to check if it'd pass a Filter in memory. That'd mean for all topics the filter filters to, checking if the log has those topics (along with any other filter options set). If the log has topics not filtered to, None is returned.

I don't want to have make an RPC request to the node with my Filter for the node to fetch all logs which match it, return those to me, and then check if the log I already have is present within the list (an extremely naive way to see if the held log matches the held filter).