Steve Myers
Steve Myers
Closing this in favor of a new issue based on changing new `bdk_bitcoind_rpc` crate.
@oleonardolima has experience with this from his work adding arti in the fedimint client.
Targeting this for BDK 1.1 milestone for now. Would be a great feature to have.
Very old PR and not part of 1.0.0 milestone so closing for now.
Could this issue be related to the default number for file descriptors running out? This is mentioned for core here: [JSON-RPC-interface limitations]. [JSON-RPC-interface limitations]:https://github.com/bitcoin/bitcoin/blob/a63192afb832bdd73de8705b2ada882b086a7e2f/doc/JSON-RPC-interface.md#limitations
Here's another request from @BitcoinComfy for no_std support and to be able to create a static build for `thumbv4t-none-eabi` and run on a feature phone. twitter thread: https://twitter.com/BitcoinComfy/status/1611332656570191873
@bucko13 I've extracted this code into a new standalone project that uses the new bdk 1.0-alpha as a dependency and is compiled to wasm for use in a web page....
Very old PR and not part of 1.0 milestone so closing for now. May take it back up post 1.0 as an example or new add-on module.
This is fixed in 1.0, no `database` parameter in `CoinSelectionAlgorithm` trait.
This issue should be fixed in #976, that PR includes the field `CanonicalTx.observed_as` of type `ChainPosition` which has a variant `Unconfirmed(u64)` which encapsulates when it was seen in the mempool.