configure client wagmi provider with api keys

tablelandnetwork / studio

Discover, design, deploy, and manage data driven web3 apps on Tableland.

https://studio.tableland.xyz

4 stars 1 forks source link

configure client wagmi provider with api keys #217

Closed asutula closed 7 months ago

asutula commented 7 months ago

Can't believe I'm changing my analysis of this again, but turns out the client does indeed need the provider API keys and that when the user deploys a table via the wagmi provider, the ETH provider does come from wagmi and this means that wagmi does need to be configured with API keys. Really final answer now.

railway-app[bot] commented 7 months ago

This PR is being deployed to Railway 🚅

web: ◻️ REMOVED