Skip to content
This repository has been archived by the owner on Apr 18, 2023. It is now read-only.

Polygon Testnet (Mumbai) block number lags behind provider current block number. #27

Open
ochikov opened this issue Aug 19, 2021 · 0 comments

Comments

@ochikov
Copy link

ochikov commented Aug 19, 2021

Hello,
I am using the multicall contract on Mumbai with address: 0x08411ADd0b5AA8ee47563b146743C13b3556c9Cc
When calling the method aggregate the block number returned in the result sometimes is not the current block number and I have to make multiple more calls, so the result in the contract to be for the current block.
The current block is taken from the web3 provider.
How can I optimise it ?

Thank you.

@ochikov ochikov changed the title Polygon Testnet (Mumbai) block number lags behind current block number. Polygon Testnet (Mumbai) block number lags behind provider current block number. Aug 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant