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

Weird sweep transaction #447

Closed
roeierez opened this issue May 16, 2024 · 2 comments
Closed

Weird sweep transaction #447

roeierez opened this issue May 16, 2024 · 2 comments

Comments

@roeierez
Copy link
Contributor

Relai: https://github.com/breez/breez-sdk-relai/issues/52
Outputs are swept to the same addresses resulting in loosing fees:

Channel was closed here: https://blockstream.info/tx/463972904772472b38fa1cc907e5143a5af1a008cb373179c22f4d824d72e11f

Two first outputs are anchors and it seems that the 3rd and the 5th are the user's outputs.

The 302744 sats output was swept here: https://blockstream.info/tx/34f9063fbb2e935dd45225c9b45e68dadcd6857e145911d85e20ccee1bdf6bc0
The 72000 sats seems to be swept here: https://blockstream.info/tx/fe770e36682f73a91ee4fbe535828825f2900067492777510d1fa834f9161f93
But this transaction is really strange since it takes two outputs and send them to the same address so it only looses fees.

@JordiZDG
Copy link

Any update?

@cdecker
Copy link
Collaborator

cdecker commented May 22, 2024

Did I not have an extensive timeline prepared for this issue? I seem to remember looking into the 72k output (that's an HTLC second stage TX being materialized and then swept).

As far as I can see all outputs are swept correctly, and can be unilaterally spent. The one missing output was #2, which as mentioned above was first moved forward, via the second stage HTLC transaction (a81993c61a586c4d99e8050d70139e03223dfa7a540140d3f59261842a23a1c6:0), and then finally swept after the timeout expired in 00299a87a7180571762ff322d44817816656c1170a7ff20fce83606c658f11a6:0.

Notice that the second stage HTLC transaction is dropped on-chain before the HTLC timeout expires, and as such it is normal for an HTLC to be laying on-chain for a while before the timeout expires, and it can be swept.

@cdecker cdecker closed this as completed May 22, 2024
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