Steve Myers
Steve Myers
@storopoli we can close this one now right?
Since this doesn't touch the wallet APIs I moved it to the beta milestone.
Moving this and #1489 back to the 1.0.0-alpha milestone.
Will https://github.com/bitcoindevkit/rust-esplora-client/pull/58 make it easier to handle these in a more graceful way or do we need full parsing of the returned messages as proposed in https://github.com/bitcoindevkit/rust-esplora-client/issues/47?
fixed by bitcoindevkit/rust-esplora-client#98
Still need to publish 0.10.0 version of `rust-esplora-client` and then update `bdk_esplora` to use it.
I agree, it looks like `bwt` wouldn't be a good fit since you need to start it up with the xpub(s) you want to track and then it only offers...
hi @shesek, thanks for the feed back, bwt is certainly a cool project so I'm happy to reopen this issue to continue the discussion on how we can work together....
@shesek we discussed your question today at our team meeting and didn't find a particular reason the `bdk` electrum client is using `listunspent` instead of `get_history` to get the wallet's...
As @ValuedMammal pointed out this looks like an issue with the `https://mempool.drivechain.live/api/address` implementation. You can see in the response to `curl https://mempool.space/api/tx/4256321f15100fedb2380c856799e26e95b627b997e4bbe8cb69bac33cf45782 | jq` that mempool.space already adds all zeros...