exception_handler: surface disabled swap creation as a swap outage - #657
Merged
Conversation
Verified against device logs: Boltz keeps its pairs endpoint live while
refusing to create swaps, so prepare_receive_payment succeeds with real
fees and limits, and the refusal only lands on receive_payment as
Generic { err: "Boltz API returned error status 400 Bad Request:
{\"error\":\"swap creation is disabled\"}" }.
Users on Receive > Bitcoin Address saw that raw JSON. PairsNotFound, which
#655 assumed was the error hit during this outage, never fires. Route both
to the same message and reuse it via a shared constant.
Matching on the error text is fragile, but the SDK flattens the Boltz 400
body into an untyped Generic error, so there is nothing else to match on.
The adjacent non-final / rpc error -26 check sets the precedent.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR replaces the raw Boltz error shown on Receive > Bitcoin Address, and bumps the version to 0.3.1.
Boltz disabled swap creation while keeping its pairs endpoint live, that's why
prepare_receive_paymentsucceeds and the refusal only surfaces onreceive_paymentas an untypedGenericerror.PairsNotFound, handled in #655, never fires.Changelist: