Skip to content

send_payment: add Liquid address payments - #653

Merged
erdemyerebasmaz merged 1 commit into
mainfrom
send-liquid-address
Aug 3, 2026
Merged

send_payment: add Liquid address payments#653
erdemyerebasmaz merged 1 commit into
mainfrom
send-liquid-address

Conversation

@erdemyerebasmaz

@erdemyerebasmaz erdemyerebasmaz commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

This PR introduces sending to Liquid addresses.

Boltz suspended its service, that's why swap-based paths are unavailable. Paying a Liquid address needs no swap provider.

Changelist:

  • send_payment: add Liquid address payments f3a5c12

Boltz is currently down, which blocks every swap-based path in the SDK and
leaves users unable to move funds out of their wallet. Sending directly to a
Liquid address needs no swap provider, so it is the one outbound path that
still works.

The SDK already handles this end to end: prepare_send_payment resolves
InputType::LiquidAddress natively, including drain and fee estimation. Only
the app side was missing.

- Parse InputType_LiquidAddress into a new LiquidAddressInputState
- Add LiquidAddressPaymentPage: amount entry with a "use all funds" toggle,
  then a confirmation step showing recipient, amount and fees
- Route the new input state through InputHandler to the existing
  showProcessingPaymentSheet / sendPayment pipeline
- List Liquid Address in the payment info hint text

Scope is L-BTC only. Addresses that name an asset are rejected as unsupported
input, since paying them would require PayAmount_Asset handling that Misty
does not have yet.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@erdemyerebasmaz
erdemyerebasmaz merged commit 1aac62d into main Aug 3, 2026
1 check failed
erdemyerebasmaz added a commit that referenced this pull request Aug 3, 2026
Missed in #653: flutter analyze does not check formatting.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
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