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

[TASK] Add support and Chain info for Webb Alpha Bridge #504

Closed
4 tasks done
shekohex opened this issue May 12, 2023 · 0 comments · Fixed by #505
Closed
4 tasks done

[TASK] Add support and Chain info for Webb Alpha Bridge #504

shekohex opened this issue May 12, 2023 · 0 comments · Fixed by #505
Assignees
Labels
difficulty: starter 🏁 Small issues that are great for starters or easy to complete tasks p0 🔥 Critical issues that need to be resolved immediately task ✔️

Comments

@shekohex
Copy link
Collaborator

shekohex commented May 12, 2023

Overview

Currently Relayers does not have chain information about Avalance Fuji (43113)

Reproduce the issue

  1. Query the Fees information for Avalance Fuji (43113) => 1099511670889
curl https://relayer2.webb.tools/api/v1/fee_info/1099511670889/0x38e7aa90c77f86747fab355eecaa0c2e4c3a463d/2000000
  1. Relayer Responds with
Chain Not Found: 1099511670889

Task Checklist

@shekohex shekohex added p0 🔥 Critical issues that need to be resolved immediately task ✔️ difficulty: starter 🏁 Small issues that are great for starters or easy to complete tasks labels May 12, 2023
@github-project-automation github-project-automation bot moved this to Not Started 🕧 in Webb Universe May 12, 2023
@github-project-automation github-project-automation bot moved this from Not Started 🕧 to Completed ✅ in Webb Universe May 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: starter 🏁 Small issues that are great for starters or easy to complete tasks p0 🔥 Critical issues that need to be resolved immediately task ✔️
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants