revault / practical-revault

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

Increase the [CPFP outputs values]/[pre-signed transactions feerate] #44

Closed darosior closed 3 years ago

darosior commented 4 years ago

After #43, i think it'd create a virtuous circle and avoid too much pollution of the utxo set.

darosior commented 4 years ago

By how much ? To your sheds, there is YA bike!

darosior commented 3 years ago

Modified the title, as i also think we ought to be pragmatic and not defer the entire and constant fee bumping to the watchtowers.

In fact, the rationale for increasing the CPFP outputs value implies that we should do this if we want to lower the burden on re-filling watchtowers' funds.

darosior commented 3 years ago

Based on https://github.com/darosior/historical_bitcoin_fees, i believe picking 32sat/vbyte is a reasonable expectation for the median feerate for the year to come.

Of course, they are default values and could be made configurable to adapt to the usecase of each business (eg if one is relying on super fast confirmations, they'll likely want to increase it).

darosior commented 3 years ago

Still based on https://github.com/darosior/historical_bitcoin_fees, i believe 85sat/vbyte is a reasonable pick for the revaulting transactions, in order to lighten the charge on each watchtower's wallet during normal operations. It's approximatively 3€ for a 5-managers cancel transaction and 1BTC=14000€, for a transaction which will barely ever be used (not even talking about the emergency one).