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
newer frame versions connect to all added networks, so we don't need to switch to a network to send requests.
the docs are lacking but from what i can tell, there are at least two methods available:
found here. we can add a chainId parameter to any request and it will be processed on the corresponding chain. this seems very simple to implement and looks like a preferred way to go.
found here and loosely based on caip-27. here a request is wrapped into wallet_request structure:
ape-frame/ape_frame/providers.py
Line 57 in c2c1545
newer frame versions connect to all added networks, so we don't need to switch to a network to send requests.
the docs are lacking but from what i can tell, there are at least two methods available:
found here. we can add a
chainId
parameter to any request and it will be processed on the corresponding chain. this seems very simple to implement and looks like a preferred way to go.found here and loosely based on caip-27. here a request is wrapped into
wallet_request
structure:both seem to work but the first option sounds way easier. the only thing to clarify is whether frame plans to keep support for it.
The text was updated successfully, but these errors were encountered: