Antoine Poinsot
Antoine Poinsot
As discussed in https://github.com/re-vault/practical-revault/issues/16 , i'd like to have some UX policies for fee batching. For instance, the GUI (it could even be enforced by the watchtowers) could hint the...
As described in https://github.com/revault/practical-revault/issues/102#issuecomment-1014850960, a way to forward signed messages to the WTs through the coordinator could allow some interesting policies. For instance have a threshold for the managers and...
Ok, this've been here for almost 2 months. Now we need to discuss the actual UX of refilling the watchtower wallet as it has been brought up during the UI...
See https://github.com/re-vault/practical-revault/issues/28 too.
@JSwambo pointed in #28: > I'd like to note our working assumption here: > > A busy mempool and high fee-rate can occur at any time and so watchtowers must...
> This means actively maintaining their fee-bumping UTXO pool. Yes. And in practice have some breathing room. > What is a sufficient amount of funds per vault UTXO, and how...
Another question brought up by Edouard: Shoudl the stakeholder have a direct channel with its WT for refilling **through revaultd / the GUI** ?
> could spend time doing statistical analyses to quantify the risk involved here. We could, but let's not waste time to only get out with another arbitrary value that's going...
TODO(darosior): talk about the discussion re inactive vaults
We can also consolidate using a higher threshold (eg don't go higher than X vaults in fly) and transcribe it in the coin control screen (h/t @edouardparis)