You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
App and coordinator should handle LDK events differently. For instance:
The coordinator doesn't want to claim certain payments straight away.
The coordinator can intercept payments to create JIT channels.
The app needs to pay a channel-opening fee as soon as a new JIT channel has been created.
These systems will diverge more as we keep evolving 10101. It's a good idea to tackle this as soon as possible so that we don't keep building technical debt unnecessarily. At the moment this lack of separation doesn't even lead to simpler solutions, so it's hard to justify.
Some PRs where the status quo has created friction:
979: Fail intercepted HTLC backwards when we should r=luckysori a=luckysori
Fixes#943.
Fixes#944.
---
This is yet another instance where we have to consider the fact that the same event handler code runs for both app and coordinator even though certain parts need to be specific to each role. I've increased the implicit annoyance counter of #885.
Co-authored-by: Lucas Soriano del Pino <[email protected]>
979: Fail intercepted HTLC backwards when we should r=luckysori a=luckysori
Fixes#943.
Fixes#944.
---
This is yet another instance where we have to consider the fact that the same event handler code runs for both app and coordinator even though certain parts need to be specific to each role. I've increased the implicit annoyance counter of #885.
Co-authored-by: Lucas Soriano del Pino <[email protected]>
App and coordinator should handle LDK events differently. For instance:
These systems will diverge more as we keep evolving 10101. It's a good idea to tackle this as soon as possible so that we don't keep building technical debt unnecessarily. At the moment this lack of separation doesn't even lead to simpler solutions, so it's hard to justify.
Some PRs where the status quo has created friction:
The text was updated successfully, but these errors were encountered: