When withdrawing sats from the Savings Balance to an on-chain address, you can't see or decide what the miner fee is going to be – it doesn't show on the first screen (where you enter amount and address), nor is it on the popup (after clicking Withdraw, to confirm the on-chain transaction).
It's unclear whether the fee is taken from the amount you entered, or from the remaining savings balance.
The uncertainty can be a problem, for example if you're withdrawing to a Boltz atomic swap or similar, where you should send an exact amount of funds. Not knowing the fee (or where it's spent from) means you can't know how much money is actually going to the destination.
It would be helpful to see the fee at minimum, but ideally we would be able to set the miner fee based on existing fee rate and personal preference around time-sensitivity.
Thank you team 🐝
Hey Alby team, what are the chances of getting this feature implemented? It's odd to try and create an on-chain withdrawal from the node but not have any idea what the on-chain fees are going to be. cc Moritz undefined
consciousdruid hi, currently we focus on keeping a simple UI and using a fee rate that should confirm within 1 block confirmation. In the latest release (1.16) we fixed that LND was not using a high fee rate, in case you are running Alby Hub on Umbrel/Start9 with LND.
roland thanks for getting back to me. I do understand the UI decision, and while fees are low this makes sense. At the same time, it seems like fee control is an essential component of any self-custody wallet, and when rates inevitably increase, it will be problematic for users making on-chain transactions. BlueWallet is a good example of a clean and simple interface that gives beginners an easy default without preventing more experienced users to access basic controls. My two sats ;)
This is relevant on the opening channels too. Would like more transparency around sats/vb miner fee, Alby fee (if there is one) etc. just throws a blanket recommended amount.
written_winks_0l there is no Alby fee attached when opening channels. You can either buy a channel from an LSP (then it is their responsibility for publishing the channel transaction) or open an outbound channel (we use LND/LDK defaults and for most users it makes sense to ensure the transaction gets into the next block, so that it's actually useable in a reasonable amount of time)