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

Unlock swap-in utxos if initial channel creation fails #689

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

t-bast
Copy link
Member

@t-bast t-bast commented Jul 18, 2024

Add a replyTo field when opening or accepting a channel. This is used for swaps, to free utxos in case a failure happens during funding. Without this mechanism, the user needs to restart the app to be able to reuse those utxos.

Fixes #680

@t-bast t-bast force-pushed the unlock-channel-utxos-on-failures branch from d8f653b to 70d4ae6 Compare September 16, 2024 09:02
Add a `replyTo` field when opening or accepting a channel. This is used
for swaps, to free utxos in case a failure happens during funding.
Without this mechanism, the user needs to restart the app to be able to
reuse those utxos.

Fixes #680
@t-bast t-bast force-pushed the unlock-channel-utxos-on-failures branch from 70d4ae6 to 6b8162d Compare September 26, 2024 01:28
@t-bast t-bast requested a review from pm47 September 26, 2024 01:28
@pm47
Copy link
Member

pm47 commented Sep 26, 2024

@dpad85 Peer.spliceOut/spliceCpfp/requestInboundLiquidity now return a ChannelFundingResponse instead of ChannelCommand.Commitment.Splice.Response. It's a simple rename, no functional changes.

@pm47 pm47 merged commit 8316872 into master Sep 26, 2024
2 checks passed
@pm47 pm47 deleted the unlock-channel-utxos-on-failures branch September 26, 2024 11:38
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 this pull request may close these issues.

Unlock swap-in utxos if initial channel creation fails
2 participants