-
Notifications
You must be signed in to change notification settings - Fork 21
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
Maintain Local Channels database #114
Comments
Feedback from @JPLACLAU
|
Related: #105 |
|
As part of this ticket, also use the short LDK sync interval if a channel is currently opening |
4 tasks
Removing the milestone for now - we made a significant improvement with #602 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @bumi :
We need to save all the required data in our DB and define single API calls to get all data.
Right now for example we do many calls to mempool triggered from the frontend to load the alias (not sure about rate limits there)
For example we can have a DB with channels that contains all the information from funding transaction to node alias and then have one GET /channels call to get this information from there. If I want information about the channel then I have a model that contains that data. right now if I want to get the node alias I would somehow have to go through this mempool API.
From Roland:
Also, we can save channel liquidity and other info that will be useful when events happen (like channel closures).
I would like to see an email notification or nostr DM when I get a channel closure:
"Your 500,000 sat channel with Olympus was closed. Reason: XYZ. You had 200,000 sats outgoing capacity when the channel was closed and these sats will be returned to your Alby Hub savings account within N blocks (about 2 weeks).
What to do next:
<Instructions here>
"The text was updated successfully, but these errors were encountered: