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
If you search for chainId in the project, you'll find that almost all builders and quote providers fetch the network's chainId. This ticket is to check how expensive this is and if chainId should rather be passed as part of the build/quote request. This would:
avoid an extra potential network call? (performance)
make it more clear what the user wants to request*
* up to the SDK to check if the request chainId and the provider's actually connected chainId is the same. Or is the users responsibility?
The text was updated successfully, but these errors were encountered:
If you search for
chainId
in the project, you'll find that almost all builders and quote providers fetch the network's chainId. This ticket is to check how expensive this is and ifchainId
should rather be passed as part of the build/quote request. This would:* up to the SDK to check if the request chainId and the provider's actually connected chainId is the same. Or is the users responsibility?
The text was updated successfully, but these errors were encountered: