You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wagmi v2 supports injected connectors (unstable connector :D), so you can use your connected wallet as the transport for your RPC request. As the name state (and docs) state it's not stable (same as public RPCS) but we could consider it as fallbacks.
Good point, I think it's a way to go. Maybe even add it when there is a non-default API key
++
I can't think any downside of having unstable_connector as fallback, probably switching chains might cause some problem maybe not sure but yeah we should go with for sure!!
Wagmi v2 supports injected connectors (unstable connector :D), so you can use your connected wallet as the transport for your RPC request. As the name state (and docs) state it's not stable (same as public RPCS) but we could consider it as fallbacks.
https://wagmi.sh/react/api/transports/unstable_connector
Should we use it? At least like when the default API Key is not changed:
(this is just me overthinking after checking the Alchemy usage :D)
The text was updated successfully, but these errors were encountered: