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

[HUMAN App] Duplicate oracle entries when Amoy and Sepolia networks are enabled #2804

Open
portuu3 opened this issue Nov 18, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@portuu3
Copy link
Collaborator

portuu3 commented Nov 18, 2024

Describe the bug
If Amoy and Sepolia networks are enabled oracles active in two networks appears twice.

Expected behavior
It should appear only once

Screenshots
Image

@portuu3 portuu3 added the bug Something isn't working label Nov 18, 2024
@portuu3 portuu3 moved this to Todo in Core-tech - 2024 Nov 18, 2024
@Dzeranov Dzeranov changed the title [HUMNA App] [HUMAN App] Nov 18, 2024
@portuu3 portuu3 changed the title [HUMAN App] [HUMAN App] Duplicate oracle entries when Amoy and Sepolia networks are enabled Nov 18, 2024
@eugenvoronov eugenvoronov moved this from Todo to In Progress in Core-tech - 2024 Nov 21, 2024
@eugenvoronov eugenvoronov moved this from In Progress to In Review in Core-tech - 2024 Nov 28, 2024
@dnechay dnechay assigned dnechay and unassigned eugenvoronov Nov 29, 2024
@dnechay dnechay moved this from In Review to In Progress in Core-tech - 2024 Nov 29, 2024
@dnechay dnechay moved this from In Progress to Backlog in Core-tech - 2024 Dec 5, 2024
@dnechay
Copy link
Contributor

dnechay commented Dec 5, 2024

Taking into account that there might be oracles with same address, but different URLs in different chains, we decided to hold the development of this and discuss how we approach this from UX perspective. Once we have an agreement - will share it here

@dnechay
Copy link
Contributor

dnechay commented Dec 12, 2024

After discussing internally with the team we came up to next conclusions:

  • we might want to introduce a bigger UI/UX redesign, where users will see just a list of available jobs (and that's a different story)
  • we are not going to have something like described in this issue in production, so we can hold it a bit and decide later if we going to make a redesign or implement some sort of "network selector" to address this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: No status
Development

No branches or pull requests

3 participants