Bug: Listening to topic sets doesn't work

I am referring to the documentation provided here My goal is to listen to events on a list of addresses of my choice. I figured the topicset would be useful in this regard.

const topicSet = [
  '0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef',
  null,
  [ '0xf687BfA503376e088C6032cD277EEbdf19af4c7d' ]
]

This is the topic set I tried using, and got this error

p.on(topicSet, (event) => console.log(event))
Uncaught:
Error: invalid topic (argument="topic", value="0xf687BfA503376e088C6032cD277EEbdf19af4c7d", code=INVALID_ARGUMENT, version=providers/5.0.14)
    at Logger.makeError (@ethersproject/logger/lib/index.js:179:21)
    at Logger.throwError (@ethersproject/logger/lib/index.js:188:20)
    at Logger.throwArgumentError (@ethersproject/logger/lib/index.js:191:21)
    at checkTopic (@ethersproject/providers/lib/base-provider.js:75:16)
    at @ethersproject/providers/lib/base-provider.js:90:26
    at Array.forEach (<anonymous>) {
  reason: 'invalid topic',
  code: 'INVALID_ARGUMENT',
  argument: 'topic',
  value: '0xf687BfA503376e088C6032cD277EEbdf19af4c7d'
}

[ricmoo]

Sorry it’s been so long since I looked into this. Yes, after investigating, I see that the topics were incorrectly encoded. Every topic must be 32 bytes, so the address needs to be zero padded to be 32 bytes wide.

Thanks @andrevmatos! Yes, that is the easiest way to encode any of the static types. To encode any dynamic types, you will need to use utils.id for string and utils.keccak256 for bytes.

I’m guessing that solution worked for you @rymnc?

[andrevmatos]

I think that, when you’re passing raw topics, you need to encode them first. If you use the interface’s factories for events/topics, then it already encodes it for you. On your case, you’re trying to pass an address (20 bytes long) as topic[2]. Try to encode it with [defaultAbiCoder.encode(['address'], [address])].