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

Gateway selection should consider VETTED gateways #5250

Open
douglaz opened this issue May 10, 2024 · 4 comments
Open

Gateway selection should consider VETTED gateways #5250

douglaz opened this issue May 10, 2024 · 4 comments
Labels
lightning Lightning module

Comments

@douglaz
Copy link
Contributor

douglaz commented May 10, 2024

Perhaps related to #4722

But we already have https://github.com/fedimint/fedimint/blob/df4b7be8ec9a7907828331128e5abe4bf4ba8c59/docs/meta_fields/vetted_gateways.md?plain=1

So the client should filter based on it, if defined.

@douglaz douglaz added the lightning Lightning module label May 10, 2024
@maan2003
Copy link
Member

@douglaz 🤷 it is reponsiblity of client integrator, is this issue for fedimint cli?

@douglaz
Copy link
Contributor Author

douglaz commented May 11, 2024

@douglaz 🤷 it is reponsiblity of client integrator, is this issue for fedimint cli?

fedimint-cli is one example. If we can't rely on the client to implement it, then perhaps we should implement this policy server side?

@m1sterc001guy
Copy link
Contributor

We used to have this logic when we had the active gateway, but while removing active gateway we had to remove it since there were difficulties querying the metadata #4427

@elsirion
Copy link
Contributor

#4722 with a sane default will solve this. We don't want guardians to have too much say in gateway selection imo, it's a friendly hint, but a client/integrator can always choose otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lightning Lightning module
Projects
None yet
Development

No branches or pull requests

4 participants