Skip to content

fix: boltz 0.5.2 restore hardening — rescue skipped-swap reporting (6.12.6+206) - #2666

Open
i5hi wants to merge 2 commits into
mainfrom
fix/restore-rescue-hardening
Open

fix: boltz 0.5.2 restore hardening — rescue skipped-swap reporting (6.12.6+206)#2666
i5hi wants to merge 2 commits into
mainfrom
fix/restore-rescue-hardening

Conversation

@i5hi

@i5hi i5hi commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Internal test build for the users failing to claim/refund restored swaps. Based off main (6.12.4+201) so the only delta vs what those users run is the restore fix chain.

What

What this fixes for the affected users

  • One submarine swap in the history no longer aborts the entire restore batch (Claim details required… — boltz-dart Recieve Page Address Label Save  #56), which previously blocked rescuing every other swap too.
  • Submarine swaps restore even without a parseable BOLT11 invoice (refund needs neither preimage nor amount — boltz-dart Make wallet label mandatory on new wallets #61).
  • Unrebuildable swaps are skipped, reported, and logged instead of silently vanishing or failing the batch.

Verification

  • dart analyze lib test: 0 issues. Full test suite: 499/499.
  • Underlying boltz-dart changes covered by 20 rust tests (5 new) + verified fund-path analysis (refund never reads preimage/amount; script hashlock comes from the swap tree).

Test protocol on the affected device

  1. Settings → Bitcoin settings → Swap restore: list should populate (previously errored).
  2. Rescue the stuck swap: refund should broadcast, or the UI/logs name the concrete rebuild failure.
  3. Export logs: SWAP_RESTORE: lines show restored/skipped ids for diagnosis.

Note: develop owes main a merge-back of this after the release (along with the existing 6.12.x debt).

@i5hi i5hi changed the title fix: boltz 0.5.2 restore hardening — rescue skipped-swap reporting (6.12.5+203) fix: boltz 0.5.2 restore hardening — rescue skipped-swap reporting (6.12.6+206) Aug 12, 2026
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