Leonardo L.

> Maybe this belongs here better, basically, can this be disabled in anything but Network::Bitcoin? > > [#1440 (comment)](https://github.com/bitcoindevkit/bdk/issues/1440#issuecomment-2108275322) I personally don't think it's a good idea to "error-gate" based...

> Our dependencies tend to use BDK so far, so they're stuck on rust-bitcoin 0.29.x. I hope they start updating more frequently as BDK 1.0 comes out. I was taking...

@notmandatory Were you thinking of bumping something else, or having other changes, as we'll have a new release ? I think we could have #132 as well, but I am...

> This is beautiful. I'm wondering if we should change the faucet address to one that we know will be able to recycle the sats, probably doesn't need to be...

I guess we'd need either: (i) let the issue open or (ii) ignore the advisory when running `cargo-audit` until we bump the MSRV and it can be fixed, otherwise CI...

> CI failure seems unrelated, but we might have to trigger another CI run before merging Yes, the CI failure was probably due Blockstream's intermittent failure, during the past few...

Yes, I do agree with both (1) and (2), there are also issues with other features such s proxy previously mentioned by tnull, refer to https://github.com/bitcoindevkit/rust-electrum-client/issues/91, which is basically mandatory...

I got curious by this, probably some more profiling is needed, also benchmark testing against fedimint-client cli's too to see if it happens on both.

Thanks for taking on this! It's failing on CI, it'd need to pin some dependencies on MSRV step (e.g. `cc`, `libsqlite3-sys`). Also, we use the https://www.conventionalcommits.org/en/v1.0.0/ on the commit message,...

Thanks, that's a good catch. I didn't see this behavior before. Are you running a custom mempool/esplora API server ? I'd like to research a bit if it's an isolated...