We need to give the user insight into when balances are claimable / delayed outputs will be ready. A short-term solution would be to hand-through ChainMonitor::get_claimable_balances. However, this would require the user to query 2-3 different APIs go get a good overview of what is going on.
We therefore should introduce a unified interface (enum Balance ?) with variants for on-chain (possibly re-using bdk::balance), delayed/claimable (possibly wrapping LDK's Balance) and "spend in-progress" that reflects the state of outputs that are not listed as part of get_claimable_balance anymore but pending sweeping / on-chain confirmation.