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

JIT - Channel Fee: LSP Flow #843

Closed
bonomat opened this issue Jun 26, 2023 · 5 comments · Fixed by #1528
Closed

JIT - Channel Fee: LSP Flow #843

bonomat opened this issue Jun 26, 2023 · 5 comments · Fixed by #1528
Assignees

Comments

@bonomat
Copy link
Contributor

bonomat commented Jun 26, 2023

Follow-up ticket from #577

LSP flow: there is work on Bolt X (TBD) which says that nodes may accept payments smaller than amounts in the invoice. Once this is done, we can subtract a channel fee from the payment amount same as Breez does. This is defined in LSPS2 of the upcoming LSP Spec and will find its way into bolts and all implementations soon. #393

@bonomat
Copy link
Contributor Author

bonomat commented Jun 26, 2023

Might be available in LDK 116 : lightningdevkit/rust-lightning#1999

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Jul 27, 2023
@bonomat bonomat removed the Stale label Jul 27, 2023
@bonomat
Copy link
Contributor Author

bonomat commented Jul 27, 2023

Looks like we might need to wait for one more release.

luckysori added a commit that referenced this issue Aug 18, 2023
Fixes #1087.

We fix two issues here:

- We no longer assume that the order-matching fee is constant. It
actually depends on the state of the blockchain, which can change as
we run the e2e tests (even if run sequentially!).
- We wait for the app to confirm the payment before continuing with
test assertions. Otherwise these tests can be flaky.

The fact that the test needs to know about certain implementation
details (e.g. that the order-matching fee is paid via a payment after
the JIT channel is open) is not great, but it's pretty hard to know
what fee will be charged from within the test before it is actually
paid.

This test will probably have to change when we address
#843.
luckysori added a commit that referenced this issue Aug 18, 2023
Fixes #1087.

We fix two issues here:

- We no longer assume that the order-matching fee is constant. It
actually depends on the state of the blockchain, which can change as
we run the e2e tests (even if run sequentially!).
- We wait for the app to confirm the payment before continuing with
test assertions. Otherwise these tests can be flaky.

The fact that the test needs to know about certain implementation
details (e.g. that the order-matching fee is paid via a payment after
the JIT channel is open) is not great, but it's pretty hard to know
what fee will be charged from within the test before it is actually
paid.

This test will probably have to change when we address
#843.
@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions
Copy link

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

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

Successfully merging a pull request may close this issue.

2 participants