sander2

The main issue with bitcoin 23 was that it uses descriptor wallets by default

The strategy will be to call `createwallet` with `descriptor=false`, for which I made the upstream pr: https://github.com/rust-bitcoin/rust-bitcoincore-rpc/pull/278

I'm not sure we can rely on the `RocksDbWeight` as determined by parity, unless we are sure we are running our nodes on machines that are _at least_ as fast...

I agree that disallowing redeem does not really punish vaults - rather the opposite, since it's in the vault's interest to have as many issued tokens as possible for maximum...

Simplifying bumpfee is blocked on my PR on the rpc library: https://github.com/rust-bitcoin/rust-bitcoincore-rpc/pull/226

This change in isolation will break the funding process, so I don't think it's a good idea to merge without having the vault side ready

> My reasoning is that we cannot trust that the BTC payment for a parachain request will definitely be in the mempool I am not sure this is true, if...

As discussed, the way forward here is probably to store the raw transaction in the database prior to sending them out. Then at startup, you can just resend any transactions...

- Importing addresses is not too difficult - you just add a new descriptor. The basic steps are: - Given the private key (for example, `cPGN28WXdwXtr2cpMmVVBnBAdWBCrEfiy67WatyKfWYhx3cX4k1X`), - Call `getdescriptorinfo("wpkh(cPGN28WXdwXtr2cpMmVVBnBAdWBCrEfiy67WatyKfWYhx3cX4k1X)")`. This...

> For finding the descriptor/UTXO, does it add a lot of complexity when e.g., a vault needs to restart? Well we need to do the the iteration over all descriptors...