Polygon blocks polled only every ~15 seconds #3653
Unanswered
hiroshi-yamamoto-dublr
asked this question in
Q&A
Replies: 1 comment
-
Ethers by default polls every 4 seconds, which you can adjust on the provider using Keep in mind this will drastically increase your requests to your host, so it they charge you per request costs can go up. You can also check to make sure the backend is keeping up? During times of congestion, I have seen these networks get bogged down and return out-of-date info. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ethers Version
5.7.0
Search Terms
polygon block interval, polygon block samplerate
Describe the Problem
If I watch for new blocks using
then on Polygon Mumbai, via Alchemy RPC, a chunk of ~5 blocks are delivered together every ~15 seconds. Furthermore, transactions take up to 15 seconds to commit on Mumbai (averaging half of that), when they should take 2-3 seconds to commit (averaging half of that).
It would therefore appear that Ethers (?) is polling for new blocks with the expected interval of Ethereum.
The block interval has dropped to a fixed 12 seconds for Ethereum PoS. But the block interval is 2-3 seconds for Polygon. Therefore blockchain operations have much higher latency than they should on Polygon. On average the user has to wait 6 or more seconds longer than they should have to wait for a Polygon transaction to be committed.
Code Snippet
No response
Contract ABI
No response
Errors
No response
Environment
Other (please specify)
Environment (Other)
Polygon Mumbai
Beta Was this translation helpful? Give feedback.
All reactions