Task Description
We've got three, out of the box, transaction priorities High(H), Medium(M), and Low(L), each with their own unique sats/vbyte and estimate arrival blocks. However, when the fee is high enough for a particular priority that it cannot be accommodated within the available balance, then it falls back to the values of the previous priority(H -> M, M -> L, L -> insufficient funds).
However, with redundant total fees against different priorities on the Transaction Priority modal, it becomes confusing for the user to discern what is actually happening. This also happens during Send Max(both H and M default to L, as the send max amount is calculated using L). Hence, we would remove the redundant priorities and only show the ones with unique values or which the user has manually provided under custom priority.
Task Description We've got three, out of the box, transaction priorities High(H), Medium(M), and Low(L), each with their own unique sats/vbyte and estimate arrival blocks. However, when the fee is high enough for a particular priority that it cannot be accommodated within the available balance, then it falls back to the values of the previous priority(H -> M, M -> L, L -> insufficient funds).
However, with redundant total fees against different priorities on the Transaction Priority modal, it becomes confusing for the user to discern what is actually happening. This also happens during Send Max(both H and M default to L, as the send max amount is calculated using L). Hence, we would remove the redundant priorities and only show the ones with unique values or which the user has manually provided under custom priority.