Skip to content

Conversation

RCasatta
Copy link
Contributor

No description provided.

@RCasatta RCasatta force-pushed the boltz_patch branch 15 times, most recently from 636e961 to c5ede30 Compare October 7, 2025 14:15
@RCasatta RCasatta force-pushed the boltz_patch branch 7 times, most recently from 947eabb to 7210d3e Compare October 15, 2025 12:33
@RCasatta RCasatta force-pushed the boltz_patch branch 2 times, most recently from cdd0ffd to d0f6221 Compare October 16, 2025 17:23
the restore logic that drops the first update doesn't work in all case
but only in the initial one, so instead of always dropping it we allow to
expect invoice.set in the invoice.set state

If there is no listener after creating a swap the state after a restore
can become directly transaction.claim.pending, thus we allow also that
flow (by refactoring out the code that handle the cooperating claim).
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.

1 participant