The below link does not work for Flare (net ID is 14) and Songbird (net ID is 19):
gas-api.metaswap.codefi.network/networks/19/suggestedGasFees
@midotrinh Welcome Aboard!
Your issue has been forwarded to our Dev team and we will get back with further updates.
Hello @midotrinh welcome to the community
Is this issue occuring problem with web3auth pnp sdk?
It would be great if you give us the initialization and login code, your sdk version and error log.
Thanks.
The currently-used libraries:
“@web3auth/base”: “^7.1.0”,
“@web3auth/modal”: “^7.1.1”,
“@web3auth/web3auth-wagmi-connector”: “^5.0.1”
“wagmi”: “1.3.4”
I’ve followed the below instructions:
I can login and connect to the wallet and see that the wallet address is created for a given social login like email. However, all the transactions get failed because of the gas estimation API that is the blocker
Hello @midotrinh
so it seems that all logic related to web3auth is working fine,
and the only failure point is the api for gas estimation.
Have you tried with other api endpoint which is working fine?
Can you pls tell how to switch to use another working API for gas estimation on Songbird and Flare?
I think, this API comes internally from the web3auth lib? or can we configure it externally? Pls detail it.
Thanks
you can adjust the rpctarget field from your side.
check the document for more details. Thanks
Maybe, you don’t get the issue that I’ve described.
Again, the issue is about the fact that web3auth internal thing that is the API for gas estimation:
https://gas-api.metaswap.codefi.network/networks/19/suggestedGasFees
This API is internal stuff of web3auth and it is not related to the rpctarget.
Actually, I’m also using the exact rpctarget mentioned on your document.
Just click the above API link and see that it does not work at all.
Okay, now I got the point. Sorry for my misunderstanding.
We’ll look into this issue and let you know when it’s fixed.
We use fallback if the api of codefi.network doesn’t work.
we look at eth_gasPrice api and eth_feeHistory to determine the appropriate gas price.
you can safely ignore if the api call fails
The problem is we cannot safely ignore that because it causes the entire transaction to be failed. Meaning that, no transaction can be sent. It is internal of the web3auth stuff. Right now, we get totally stuck because we cannot submit any transaction when using web3auth.
@chai @pepper
No further reply?
This issue happens only on Songbird and Flare.
We get stuck totally!
Fix is released in v7.1.2
Not all packages are updated. It’s a monorepo. Only relevant ones are updated. Pls check the list here: GitHub - Web3Auth/web3auth-web: Simple infrastructure that enables Web3 wallets and applications to provide seamless user logins for both mainstream and Web3.0 users. on what package is at what version.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.