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
Input validation currently does not provide a good error message for missing configs (e.g. router addresses), which usually happens on chains that are yet not supported.
Context/Thoughts
We currently check if chain exists within chains list, but this is not a good enough check as is.
Do we need to enforce configs properly set for every chain in the chains list?
Should we be more explicit on which chains are supported? (e.g. on docs)
We should keep in mind that not everything is supported on all chains (e.g. nested operations are not supported for Balancer v3 on AVAX)
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Input validation currently does not provide a good error message for missing configs (e.g. router addresses), which usually happens on chains that are yet not supported.
Context/Thoughts
The text was updated successfully, but these errors were encountered: