Lloyd Fournier
Lloyd Fournier
@MaxFangX indeed. There is no "caching" in `BDK 1.0`. Script pubkeys are not stored on disk at all. I am quite surprised that the old implementation performs so badly though....
I don't think we have a `importdescriptors` feature at all anymore. you can still do things this way at the application level if you want but there are no guiderails...
I think the code coverage tool should be used to find non-trivial functions or branches in the code that are not being hit by tests at all. Goal seeking a...
FWIW I have made it `no_std` in #793
> From the above research plus goal of making `Wallet` easier to use for the basic two descriptor wallet scenario I propose a few modifications to above: > #### Wallet...
Can we just make the user be explicit about which addresses they want rather than it being implicitly defined by a trait? It seems to me like the application should...
So this could be done now for `bdk` and `bdk_chain` with a few tiny fixups here and there. The problem is that it's extremely hard to get CI to build...
See this PR which makes progress on how to build for 1.48.0 separately: https://github.com/bitcoindevkit/bdk/pull/924 (it's not pretty).
@jurglic what are you trying to build? There are plenty of ways to use bdk 1.0.0-alpha.* without using descriptors at all (miniscript is an optional dependency of `bdk_chain`).
> > @jurglic what are you trying to build? There are plenty of ways to use bdk 1.0.0-alpha.* without using descriptors at all (miniscript is an optional dependency of `bdk_chain`)....