search

revault / practical-revault

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

Refactor the revocation signatures transmission to watchtowers #109

Closed darosior closed 2 years ago

darosior commented 3 years ago

Currently we'd share the signatures in 3 sig messages, 1 per transaction type. We leverage this in the implementation of the watchtower to avoid allocating fee-bumping reserves to vaults that are not delegated yet:

  1. Share the Emergency signature at revocation sigs exchange time to the watchtower
  2. Share the Cancel and UnvaultEmergency sigs at delegation time, wait ACK from watchtower before sharing Unvault sig with other participants

However, this is not applicable to watchtowers which don't store the Emergency signatures. It's also awkward for the wallet to sit on signatures and seems better to share them with the watchtower as soon as we can. We should instead have:

  1. A single revocation txs batch, the watchtower stores them but doesn't allocate reserves
  2. A request before delegating, if it can the watchtower allocates reserves and otherwise NACKs

EDIT: this fixes #98

darosior commented 2 years ago

Conflicts with #98

darosior commented 2 years ago

So we wouldn't need 2. if we get rid of fee-bumping.