-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Android’s “Available” on the Lightning amount screen (SendAmountScreen.kt) shows maxSendLightningSats without reserving anything for routing fees, but the confirm screen does estimate routing fees (estimateLightningRoutingFeesIfNeeded()). That mismatch can make “Max”/available misleading (especially for amountless invoices), and it’s exactly why iOS can show 8 997 while Android shows 9 000, in case of total spending balance = 10 000.
Expected: available/max invoice amount ≈ maxSendLightningSats - estimatedRoutingFee (optionally with a small buffer) iOS uses additional 2 sats buffer -> https://github.com/synonymdev/bitkit-ios/blob/master/Bitkit/Views/Wallets/Send/SendAmountView.swift#L264
Actual: shows raw maxSendLightningSats; applying max available funds ends with error
Impact: user can pick an amount that fails or is confusing; cross-platform inconsistency
See iOS left/Android right (both having 10 000 spending balance and trying to send max available to each other; Android fails):