Actually, this turns out to be an issue with web3.js, and it'll be fixed with the imminent release of v1.2.2. Watch this space!
1 Like
Actually, this turns out to be an issue with web3.js, and it'll be fixed with the imminent release of v1.2.2. Watch this space!