-
Notifications
You must be signed in to change notification settings - Fork 100
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
Address prefixes should be received from API #3402
Comments
This was referenced Jan 14, 2020
But this is not used in the FE. We are hardcoding network to prefix lookup rn. |
Exactly. Today I am making a PR to refactor this EDIT: I just saw you already did it xD |
this is done already? |
Yes, we just need to merge it. It is here |
This was referenced Jan 25, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
To be able to scale networks without needing to update the client we should deliver as much data from the API as possible. Currently the bech 32 prefixes for the Ledger handling are in config.js. These should be received from the API (networks query). Same goes for identifying valid addresses in the explore input.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: