subscribe(“logs”) don't support address list?

[netpi]

as web3.js document it support subscribe(“logs”) by address array

// work well
web3.eth.subscribe('logs',{address:"address1"}).on('data',console.log)
// can't work
web3.eth.subscribe('logs',{address:["address1","address2"]}).on('data',console.log)
// also can't work
web3.eth.subscribe('logs',{address:"address1,address2"}).on('data',console.log)

So how to listen to multiple addresses?

[frozeman]

Good point. Actually it supports only one. Could you test the raw subscribe endpoint, whether it supports arrays as well? If so we can make that in 1.0 possible

[joojis]

The same problem here with the getPastLogs and the corresponding JSON-RPC doc is describing itself to support it.

https://github.com/ethereum/wiki/wiki/JSON-RPC#eth_getlogs
Contract address or a list of addresses from which logs should originate.

I hope that I could check the JSON-RPC actually supports it in the near future.

[mikemcdonald]

Is there a rough ETA on subscribe working with an array of addresses in 1.0? Trying to decide if I should rewrite a good amount of code back to 0.20 or wait until this is added.

[frozeman]

@mikemcdonald @joojis can you please test the latest 1.0 branch and see if you can receive logs from multiple addresses? Sorry for the delay!

[mikemcdonald]

Looks great, thanks again!

[swarupdonepudi]

@frozeman what version of the npm package is this change available with?

[nivida]

@swarupdonepudi since 1.0.0-beta.28