-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random RPC errors when attempting MetaTransactions #14
Comments
I added some debug and this seems to be coming from inside As you say, it seems intermittent, we can add some retry code around the call to How would you like to progress this? Thanks! |
@frankie13, i was looking at the repo, and it looks like we are using the public matic virgil RPC endpoints in the test scene, and I am guessing that these RPC endpoints are flaky, I was trying to Bridge on the polygon testnet, and their bridge was being flaky. Could you try passing your own, non-public, RPC endpoint in to see if this is still an issue, you can get a free RPC endpoint from INFURA for example ? |
I am not sure that the right thing is to change the CORE sdk, having talked about it briefly with @levalleux-ludo. I guess i wouldn't mind @albertfolch-redeemeum's opinion too. But we feel like the core sdk shouldn' have such retry logic in it. |
Thanks @mischat, yes I see what you mean. I will have a look at this today. |
Am guessing you probably aren't hitting the their public rate limits, you would see 429's if so https://support.blockvigil.com/support/solutions/articles/67000346291-what-is-the-rate-limit-for-matic-rpc- |
i was looking for a status page for matic virgil but i couldn't find one |
@mischat I've just successfully put through 20 transactions in a row using my free polygon-mumbai alchemy endpoint. |
Random RPC error occasionally prevents the metatransaction from occurring on commit
Happens 1 approximately 8 times with any type of purchase
Occurs when metamask is set to Polygon, Ethereum or Polygon Mumbai (have not checked by changing scene config as suggested by James in this morning's meeting)
The text was updated successfully, but these errors were encountered: