Antoine Poinsot
Antoine Poinsot
- ~~What if the software is killed after requesting the spend tx signature to the cosigning server but before broadcasting it~~ Not a concern anymore once we have the cosigning...
We need a dust-watch-limit on the watchtower. What is a good default value ? 1M sat sounds good
That would be a pretty nice feature to have, at least at first sight. My last coordinator refactoring (coming soon :tm: contains a `TODO` for this, and the patch for...
This is tightly related to the ceremony and the setup.
After discussion IRL with @JSwambo and @kloaec , the process the more aligned with a decent UX for stakeholders and futures extensions of the protocol (watchtower rental) is to: -...
Marking as settled as it seems to be the best solution but needs some re-hashing imo
Hmm so i'm now really hesitating with tweaking the public keys à la BIP32 or Lightning Network with the tweak being the unvault outpoint, it'd be a huge win... At...
We could also "just" change the Cancel descriptor from ``` wsh(thresh(4, stk_a, stk_b, stk_c, stk_d)) ``` To ``` wsh(thresh(5, stk_a, stk_b, stk_c, stk_d, hash160(H))) ``` With `H = hash160(unvault_txid |...
To be honest i don't think we should do this for the Cancel, but rather https://github.com/revault/practical-revault/pull/83#issuecomment-812465918 . > What about the Spend Tx? Are they always signed with ALL? Yes....
> What verification do we have that the H are unique? They would not exchange signatures for the same transaction. Say A, B, C are stakeholders and C is trying...