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

Isolated Apps / Dynamic Budgets followup tasks #299

Open
1 of 12 tasks
rolznz opened this issue Jul 19, 2024 · 2 comments
Open
1 of 12 tasks

Isolated Apps / Dynamic Budgets followup tasks #299

rolznz opened this issue Jul 19, 2024 · 2 comments

Comments

@rolznz
Copy link
Contributor

rolznz commented Jul 19, 2024

From #226

  • mixing DB transactions with "payment transactions" is not so good
  • Enable Roman's cleanup task for old request and response events
  • isolated app possible follow-ups (in case we wish to spend more time on isolated apps)
    • internal payments should trigger NIP-47 notifications (this can be done by the transactions service publishing its own notifications rather than the notifier subscribing to LNClient notifications - this would simplify things too)
    • restrict isolated balance to not receive more than a certain budget (it's hard to do?)
    • prevent hub not spending balance that is set aside for other apps
    • prevent paying more than actual balance from main wallet into isolated wallets (you can send an infinite amount)
    • cashu isolated app payments does not work and causes money to be "lost" - disabled for now
  • currently there are no DB indexes. I am not sure how this will perform when the number of payments grow
  • ListTransactions on LNClients that support notifications should actually just throw an error (they should never be used)
  • fee reserve calculation could be per-LNClient to completely match what the node sets
  • Extra nip-47 controller tests
    • multi_pay_keysend (partial success)
    • list_transactions (paging params)
  • onboard your friend/family flow with Dynamic Budgets and Alby Mobile
  • undo LDK database changes in Alby fork (probably by undoing changes and then deleting old payments in a migration as they will be unused after we have our own payment DB)
  • Blog post
@on4r
Copy link

on4r commented Sep 16, 2024

prevent hub not spending balance that is set aside for other apps

this seems very important if you want to share your hub with friends and family

@max-peter
Copy link

max-peter commented Sep 26, 2024

prevent hub not spending balance that is set aside for other apps

this seems very important if you want to share your hub with friends and family

Yes, I second that. Should be a high priority. At least it would be helpfull show it if this happens. Right now I have to watch this myself and that is tricky without the exact balances from each isolated / family wallets!

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

No branches or pull requests

3 participants