Bump bdk_kyoto version

The CBF crate, renamed on crates.io from `kyoto` to `bip157`, includes
some performance improvements and dependency reduction.

Starting with a relatively simple change, the configuration of a DNS
resolver has been removed, as DNS is now carried out by the operating
system. In testing this has resolved problems for DNS queries while
using a VPN or on public WiFi (with firewalls).

Now the CBF node does no disk I/O over `sqlite`. This removes a number
of warings and errors related to persistance. All chain data is stored
within the `Wallet` structure and subsequently persisted to
`bdk_chain`'s extension for `sqlite`. This creates a single
source-of-truth for persistance between sessions, which has been a huge
pain point in the past. The logic of `CheckPoint::insert` handles
competing forks. The builder has no error cases at the FFI level with
this change.

The `ScanType` has been reduced to two options, `Scan` or `Recovery`.
The `Recovery` variant contains a few notable checkpoints to start from.
It also contains a field that the user may set to peek scripts while
scanning filters. This should be approximately the number of scripts
revealed by the wallet being recovered. The guidance for developers here
would be to set conservatively. One scheme is setting the peek to 1_000,
10_000, 100_000, depending on profiles: normal, power user, enterprise.

The `Info` variants have been reduced to a single `Progress` containing
all info related to the sync.

Broadcasting a transaction now waits for the confirmation of gossip, as
in at least one remote node asked for the transaction be shared with
them.

`Node::run` is now mutable. This implies `CbfNode.run()` can only be
called once. I think that is perferctly reasonable as any other type of
behavior is faulty.

`bitcoin-address-book` is a simple crate I created to abstract peer
selection, which `bip157` depends on.

Author: rustaceanrob

bdk-ffi/Cargo.lock

@@ -18,7 +18,7 @@ path = "uniffi-bindgen.rs"
 bdk_wallet = { version = "2.1.0", features = ["all-keys", "keys-bip39", "rusqlite"] }
 bdk_esplora = { version = "0.22.1", default-features = false, features = ["std", "blocking", "blocking-https-rustls"] }
 bdk_electrum = { version = "0.23.1", default-features = false, features = ["use-rustls-ring"] }
-bdk_kyoto = { version = "0.14.0" }
+bdk_kyoto = { version = "0.15.0" }
 
 uniffi = { version = "=0.29.4", features = ["cli"]}
 thiserror = "1.0.58"

bdk-ffi/Cargo.toml

@@ -776,12 +776,6 @@ pub enum TxidParseError {
     InvalidTxid { txid: String },
 }
 
-#[derive(Debug, thiserror::Error, uniffi::Error)]
-pub enum CbfBuilderError {
-    #[error("the database could not be opened or created: {reason}")]
-    DatabaseError { reason: String },
-}
-
 #[derive(Debug, thiserror::Error, uniffi::Error)]
 pub enum CbfError {
     #[error("the node is no longer running")]
@@ -1569,16 +1563,8 @@ pub enum HashParseError {
     InvalidHexString { hex: String },
 }
 
-impl From<bdk_kyoto::builder::SqlInitializationError> for CbfBuilderError {
-    fn from(value: bdk_kyoto::builder::SqlInitializationError) -> Self {
-        CbfBuilderError::DatabaseError {
-            reason: value.to_string(),
-        }
-    }
-}
-
-impl From<bdk_kyoto::kyoto::ClientError> for CbfError {
-    fn from(_value: bdk_kyoto::kyoto::ClientError) -> Self {
+impl From<bdk_kyoto::bip157::ClientError> for CbfError {
+    fn from(_value: bdk_kyoto::bip157::ClientError) -> Self {
         CbfError::NodeStopped
     }
 }