search

revault / practical-revault

Version 0 specifications for a Revault deployment
Creative Commons Attribution 4.0 International
33 stars 9 forks source link

Automated refill of the fee-bumping utxo pool with vault's funds #28

Closed darosior closed 3 years ago

darosior commented 3 years ago

I can already imagine the really poor UX of having user to refill their utxo pools in order to be able to operate.

Can we come up with a mechanism to automatically refill as we use the architecture ?

An obvious one would be eg (did not think much about it) appending a [pre-defined value]sats output for each participant to the unvault transaction. It drains a small part of funds out of it, and the created outputs being unencumbered by a timelock they could directly be used to revault the attempt. This means we can account for them as well so this could avoid the dread of "please refill your WT's utxo pool" as long as feerate does not go crazy.

The only alternatives i can see to automated fee utxo pool refill are "batching ceremonies" and "refill ceremonies", which, well, we certainly want to prevent as much as possible.

ref https://github.com/re-vault/practical-revault/issues/16

kloaec commented 3 years ago

Seems okay-ish, not super clean tho. I suppose one could use the sync server to somewhat request to have a refill UTXO in a spend? (automagically I suppose, when fee wallet gets low)

JSwambo commented 3 years ago

---DELETED-- See https://github.com/re-vault/practical-revault/issues/16#issuecomment-707628960

darosior commented 3 years ago

Closing this, not relevant anymore. See #16.