53fa35096f
Previously there was a tx cache that you passed in as part of the sync request. This seems bad and the example show'd that you should copy all your transactions from the transaction graph into the sync request every time you sync'd. If you forgot to do this then you would always download everything. Instead just do a plain old simple cache inside the electrum client. This way at least you only download transactions once. You can pre-populate the cache with a method also and I did this in the examples.
23 lines
1.1 KiB
Rust
23 lines
1.1 KiB
Rust
//! This crate is used for updating structures of [`bdk_chain`] with data from an Electrum server.
|
|
//!
|
|
//! The two primary methods are [`BdkElectrumClient::sync`] and [`BdkElectrumClient::full_scan`]. In most cases
|
|
//! [`BdkElectrumClient::sync`] is used to sync the transaction histories of scripts that the application
|
|
//! cares about, for example the scripts for all the receive addresses of a Wallet's keychain that it
|
|
//! has shown a user. [`BdkElectrumClient::full_scan`] is meant to be used when importing or restoring a
|
|
//! keychain where the range of possibly used scripts is not known. In this case it is necessary to
|
|
//! scan all keychain scripts until a number (the "stop gap") of unused scripts is discovered. For a
|
|
//! sync or full scan the user receives relevant blockchain data and output updates for
|
|
//! [`bdk_chain`].
|
|
//!
|
|
//! Refer to [`example_electrum`] for a complete example.
|
|
//!
|
|
//! [`example_electrum`]: https://github.com/bitcoindevkit/bdk/tree/master/example-crates/example_electrum
|
|
|
|
#![warn(missing_docs)]
|
|
|
|
mod bdk_electrum_client;
|
|
pub use bdk_electrum_client::*;
|
|
|
|
pub use bdk_chain;
|
|
pub use electrum_client;
|