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

Trusted Node Versioning Validation #136

Open
rodvar opened this issue Dec 20, 2024 · 0 comments
Open

Trusted Node Versioning Validation #136

rodvar opened this issue Dec 20, 2024 · 0 comments
Labels
BisqClients This issue is applicable ONLY for `xClients` apps

Comments

@rodvar
Copy link
Collaborator

rodvar commented Dec 20, 2024

For androidNode we manage versioning directly using gradle because we have static control of it.

For the xClients, after the first release we will need some sort of versioning handshake to manage the app bisq required version (R) and the trusted node runing version (V):

  • R <= V. -> proceed normally
  • R > V -> Overlay error requesting the user to upgrade the trusted node, only option is to quit the client

From a UX perspective, I think the best is to present the user with the TrustedNode onboarding setup screen to give the option to connect to other trusted node, and also use the test button to verify it can connect and check if the trusted node upgraded its running version

@rodvar rodvar added the BisqClients This issue is applicable ONLY for `xClients` apps label Dec 20, 2024
@rodvar rodvar added this to the MVP (version 0.1.0) milestone Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BisqClients This issue is applicable ONLY for `xClients` apps
Projects
None yet
Development

No branches or pull requests

1 participant