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
Unilateral closes are not onchain payments. The real on-chain credits to our onchain balance after a unilateral close happen on Sweep and Claim transactions.
Also, UnilateralClose payments currently never graduate from the Pending state, as no BDK events are emitted when these transactions confirm.
The original motivation for this change: commitment transactions in 0FC channels have zero-fees and zero-amount according to BDK (since they don't interact with the on-chain wallet), so these were not recorded in the payment store. I then failed the assertion in the channel_full_cycle test that asserts that UnilateralClose was present in the payment store.
Hmm, these don't directly interact with the onchain wallet, but wouldn't it still make sense to record them as otherwise users would have a 'gap' between channel funding and the resulting Sweep transaction? If we keep them that could allow them to track the funds end-to-end, on each step?
Would have to think more about the overall purpose of payment store, as a user I think I would find it quite confusing for there to be a zero-amount inbound payment, with a non-zero fee. In the case of zero-fee commitment channels, these would be inbound payment for zero-amount, zero-fee (but the entry could still allow us to track the movement of funds).
Also note that currently UnilteralClose only gets recorded for outbound channels, as BDK can tracks the funding output and assigns a non-zero fee only in this case. This makes sense as for inbound channels, the fee of the commitment transaction comes from the counterparty's balance, not our balance.
The reason will be displayed to describe this comment to others. Learn more.
Yeah, makes sense to me, though I still think it somehow would be nice to show users the intermediate transaction state somehow. But you're probably right that the payment store is not the right place to do it.
Hmm @tnull let me know what you think of this "unknown splice funding txid" CI failure in Rust Tests. So far on my machine I've been unable to reproduce with
RUSTFLAGS="--cfg cycle_tests --cfg tokio_unstable" cargo test channel_full_cycle_0conf_0reserve`
Hmm @tnull let me know what you think of this "unknown splice funding txid" CI failure in Rust Tests. So far on my machine I've been unable to reproduce with
RUSTFLAGS="--cfg cycle_tests --cfg tokio_unstable" cargo test channel_full_cycle_0conf_0reserve`
I think it's a flake that I have yet to investigate, so may not be related to this PR.
Unilateral closes are not onchain payments. The real on-chain credits to
our onchain balance after a unilateral close happen on `Sweep` and
`Claim` transactions.
Also, `UnilateralClose` payments previously never graduated from the
`Pending` state, as no BDK events are emitted when these transactions
confirm.
Co-Authored-By: HAL 9000
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unilateral closes are not onchain payments. The real on-chain credits to our onchain balance after a unilateral close happen on
SweepandClaimtransactions.Also,
UnilateralClosepayments currently never graduate from thePendingstate, as no BDK events are emitted when these transactions confirm.Co-Authored-By: HAL 9000