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

[Issue-014] : Only allows adding one RPC per chain #622

Open
function0xMarki opened this issue Sep 6, 2024 · 4 comments
Open

[Issue-014] : Only allows adding one RPC per chain #622

function0xMarki opened this issue Sep 6, 2024 · 4 comments
Labels
bug Something isn't working stale-issue

Comments

@function0xMarki
Copy link
Collaborator

What happened?

This issue with Pali Wallet had been identified and previously corrected; however, it has returned. It has not been possible to retrieve the original report due to changes in our error classification system.

The specific problem is that Pali Wallet currently does not allow setting more than one RPC for the same chain. This significantly limits users, as they cannot set up alternative RPCs that could be used in case the primary one fails.

Currently, the only solution available for users is to manually modify the existing RPC each time they need to switch to an alternative server.

Captura de pantalla 2024-09-06 a las 22 30 09

According to the console, we can see that the error corresponds to "Network already exists!"
The new error message that appears now is less intuitive than before.
image

However, we need to allow the option of having multiple RPCs for the same chain.

In the event that an RPC is not available for some reason, the user should be able to have the option of having one or more RPCs for that same chain.

Small note.
The error message says Erro (the final r is missing)

Version

v3.0.0 QA

What platform are you using?

macOS

What browser are you using?

Brave

Is this a trezor issue?

No

Relevant log output

No response

@function0xMarki function0xMarki added the bug Something isn't working label Sep 6, 2024
@Potolski
Copy link
Collaborator

Let's postpone this feature to after MV3 is done.

Copy link

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

Copy link

github-actions bot commented Oct 3, 2024

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 3, 2024
Copy link

This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale-issue
Projects
None yet
Development

No branches or pull requests

2 participants