-
Notifications
You must be signed in to change notification settings - Fork 5
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
Recheck for gateways if there isn't one saved #9
Conversation
Added a gateways route to try and make debugging this easier |
We do currently, so that's not the issue. |
If this is running for awhile, what stops a current gateway from going down and this doesn't switch to another one? |
yeah this is why I was talking to justin about this fedimint/fedimint#4722 Maybe should just throw out the cache and lookup every time. Originally i thought the lookup was expensive but it's not |
If it's a request to the federation every time then no. |
it looks up in our local db |
Then that doesn't really solve new/old gateways filtering in or out. |
my understanding is that these are broadcast to us and saved to our db, let me ask though |
cf7ccfb
to
c986a91
Compare
Okay redid this so we periodically update our gateway db every hour and we always pick from that |
c986a91
to
ea7e473
Compare
I am getting this currently: https://hermes-blinded-staging.fly.dev/lnurlp/test1234/callback?amount=10000
I assume because we don't durably save the fedimint db that we can lose the gateways we've been told about.
Finding a gateway is just lookups in the fedimint database so this shouldn't block requests.