Contract "Mint" Event delivered late #2359
Unanswered
IronSight87
asked this question in
Q&A
Replies: 1 comment 1 reply
-
The default polling period is 4s for polling-based providers. If you reduce that you may incur additional charges from your backend and it is not recommended for the community api keys. Six seconds is not a long time, but if your application requires low-latency, you should definitely be running your own infrastructure or paying for the higher-tier options for your backend services to achieve them. |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Hi there,
please see my code example below.
I am waiting for a "Mint" event for a LP contract. My callback is fired, but very late.
The actual "Mint" event was fired at 2:59:18 PM (UTC) and my function was triggered at 2:59:24 PM (UTC).
Meaning a delay of 6 seconds, which is a lot.
Futhermore I then triggered a buy action at 2:59:24 PM (UTC) which was completed at 02:59:30 PM (UTC).
Meaning another 6 seconds delay.
Other buyers (>300) where able to trigger the buy action 1 second after the Mint event occured.
Is there some kind of delay in the ethers library?
Thank you in advance for your help!
Mint event transaction: https://bscscan.com/tx/0x71206e420491ff872ff135bb1f3f95a8f8658e64e723220f453e24e4bc048e78
Beta Was this translation helpful? Give feedback.
All reactions