I implemented walletConnect in a vue app but it bother me a bit that it request the infuraId since its client side and will be exposed. Then anyone could use it and use my API request quota?..
Is it fine to expose the infuraId like that? No other way?
Thank you in advance
check this out:
We’ve noticed a trendy use case of building NFT minting dApps that run on the client side only, no backend services. Understandably this comes with a great simplicity, allowing users to send transactions using their wallets and why not avoiding usually the request per second
limits since the requests to Infura will be coming from multiple different IP user’s addresses.
However, this simplicity comes with a great cost and that is exposing the keys to anyone who would try to inspec…
it might help.
Chris | Infura | ConsenSys
Thank you, i actually do have a backend API and i would love to use it but i think walletconnect work in front end only and will expose the infuraid no matter what so i guess there is no solution for that.