Filter events with multi address

[johnnguyen-nodejs]

Ethers Version

6.0.8

Search Terms

No response

Describe the Problem

i can not filter multi-address event

Code Snippet

const contract = new Contract(contractAddress, abi, provider);
const filter = contract.filters.Transfer(null, [address1, address2, ...]);
contract.on(filter, handlerEvent)

Contract ABI

No response

Errors

TypeError: unsupported addressable value

No response

Environment

No response

Environment (Other)

No response

[imaksp]

Getting same error, this was new useful feature in v6 but it seems it is not working, tried with Infura provider.
@ricmoo is it ethers issue or json rpc provider service issue?

BTW I tried with provider.getLogs function.

[imaksp]

Also does it actually reduce number of Infura calls, or does it send new eth_getLogs request for each contract address?

[imaksp]

Ignore above comment I found that this could be Infura specific issue, it requires eth_getFilterLogs method for multi address support.
but with this code will be different based on provider. see if you can support it as Infura is very popular.

NOTE: it seems Infura is not spec-compliant. it should be supported as per this official specs:
https://ethereum.github.io/execution-apis/api-documentation/

[ricmoo]

Sorry. Missed this before. Looking into it now.

Does it work with other providers?

InfuraProvider should by default use a filter ID subscriber.

Can you also make sure you are on the latest version of ethers?

[imaksp]

Hello, sorry for the confusion error was due to potentially invalid eventFilter use like contract.filters['Approval'](null, [address1, address2], null), which may be incorrect or may not be supported yet (error comes from resolveAddress if we use filter like this).
but passing addresses array works in getLogs call. & it seems it is not supported in topicFilter.

[ricmoo]

Yes, topic filters don't support that syntax, but could have something like that added in the future (using another wrapper to indicate OR), because it would complicate refining the event. You could also use the contract to generate the filter and swap out the single address with your array and use the provider.on directly. But there isn't currently a good way to do that with the Contract API...

[imaksp]

Ok, by looking closely I found that in v5 I was using code like this to get topic filter with multiple addresses:

const eventFilter = tokenContract.filters['Approval']!(
    null,
    [address1, address2, ...],
    null
  );

& then I was passing eventFilter.topics in getLogs call.

but in v6 it gives following error:
TypeError: unsupported addressable value

Also eventFilter.topics is not available directly so need to use await eventFilter.getTopicFilter().

how can I generate similar filter in v6?

[imaksp]

For now used the following code to make it work like v5:

const erc20tInterface = new ethers.Interface(erc20Contract.abi);
const topics = erc20tInterface.encodeFilterTopics('Approval', [
  null,
  [address1, address2, address3],
  null,
]);

& I have passed these topics to provider.getLogs function.

[ricmoo]

Sorry for the delay, I better understand the problem now. This was also reported in #4259, which included a fix that help me realize the error.

This should be fixed now and released in v6.6.5.

Thanks! :)