Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v3 api/suggested-fees token parameters #1

Open
ScreamingHawk opened this issue Dec 8, 2024 · 0 comments
Open

v3 api/suggested-fees token parameters #1

ScreamingHawk opened this issue Dec 8, 2024 · 0 comments

Comments

@ScreamingHawk
Copy link

The query parameters in Bridge Integration Guide use token.
The query parameters in the API Reference page use inputToken and outputToken.

It seems inputToken and outputToken are both needed to encode the calldata. When using token as per the bridge integration guide, how are we expected to get the outputToken? It doesn't appear there is an API that shows the expected mappings across chains. It would be really handy is such an enpoint was added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant