Daniela Brozzoni

> Have stricter state transitions (you can only go from one state to the next), which means we don't track Unvault broadcasts for non-active vaults. > Reasonably assume that it...

I thought about it a while, I can't come up with one. It was also a stupid take, if you don't have the Cancel you can't Cancel anyway 🤷🏻‍♀️ ....

Instead, why not sending it back to the 1ofM descriptor? I don't see why wasting money sending to an OP_RETURN. This way we might end up with some small inputs...

Ah yeah, now it makes sense :) Concept ACK on lowering it - right now it's 30,000 sats (~16 eur), and "spending" 32 euros (unvault and spend) in "fees" for...

I really like the proposal! I think Revault should offer both products, and then let the clients choose what's best for them. > Coordinator > [...] It may still be...

Aaaand it's possible :sob: ``` rsm updatespendtx cHNidP8BAH0CAAAAAWQYLaJLKOGr2VUPYwlZz5UStWUr7SlxGT+K8S8ubTM1AAAAAAADAAAAAoDw+gIAAAAAFgAUKB/hlNJv8KljBZr5anTJEwgmhVh/gPgCAAAAACIAIHXyaRd0yBZ3gxhGsCgiAOKIssWXELWPdDGD1JJVB9vFAAAAAAABASvJt/MFAAAAACIAIKhAWcoy8EwVBnWnLxovA+lFTqlQLH8soZT1Uyn//Og7AQMEAQAAAAEFqCECApM6sQN+rQqkp4WMbUnWcF4fs7xfZrAJGK97nwDs1SasUYdkdqkUcqlfIq+aG664UvmpUnL4wh2Y8mSIrGt2qRS2ya24nIyTcmyD4qG12UeJ13uVYYisbJNSh2dSIQMPZLkiruL9WX8QS8bLO2cPHKLGxJsQcaGmwBBXXZT+WiECq+R1sZnsPWL6V2+u4WozT9uG/7JtznW+zrqu3zKKw/5Sr1OyaAAAAQFHUiECWC3tv0T0ZWTl2M2wZ1NtYOvjTNHRgBz/Ubv516wom0MhA0cE3stVtaqI/9HvXQY2YkjBMU4ZZVETb/FOq4u6SkkOUq4A { "result": {} } ```

One thing we have in rust-hwi in order to avoid pinning dependencies for everyone (as it caused some troubles: https://github.com/bitcoindevkit/rust-hwi/issues/72) is a feature with a lower msrv, in which the...

Rebased on top of #157 (Still doesn't work though)

> Don't hold a mutable reference of the tracker when syncing. We need a structure (imo, like an iterator), where we only grab initial data from the tracker to create....

I pushed a rebase of this PR on https://github.com/danielabrozzoni/bdk_core_staging/tree/rpc Double-check if it's alright: it's using the new methods of the KeychainTxOutIndex, and while I'm fairly confident I'm using them properly,...