Struct lightning_transaction_sync::EsploraSyncClient

pub struct EsploraSyncClient<L: Deref>where
    L::Target: Logger,{ /* private fields */ }

Available on crate features esplora-blocking or esplora-async only.

Synchronizes LDK with a given Esplora server.

Needs to be registered with a ChainMonitor via the Filter interface to be informed of transactions and outputs to monitor for on-chain confirmation, unconfirmation, and reconfirmation.

Note that registration via Filter needs to happen before any calls to Watch::watch_channel to ensure we get notified of the items to monitor.

This uses and exposes either a blocking or async client variant dependent on whether the esplora-blocking or the esplora-async feature is enabled.

Implementations

impl<L: Deref> EsploraSyncClient<L>where L::Target: Logger,

pub fn new(server_url: String, logger: L) -> Self

Returns a new EsploraSyncClient object.

pub fn from_client(client: AsyncClient, logger: L) -> Self

Returns a new EsploraSyncClient object using the given Esplora client.

pub async fn sync( &self, confirmables: Vec<&(dyn Confirm + Sync + Send)> ) -> Result<(), TxSyncError>

Available on WebAssembly or crate feature async-interface only.

Synchronizes the given confirmables via their Confirm interface implementations. This method should be called regularly to keep LDK up-to-date with current chain data.

For example, instances of ChannelManager and ChainMonitor can be informed about the newest on-chain activity related to the items previously registered via the Filter interface.

pub fn client(&self) -> &AsyncClient

Returns a reference to the underlying esplora client.

Trait Implementations

impl<L: Deref> Filter for EsploraSyncClient<L>where L::Target: Logger,

fn register_tx(&self, txid: &Txid, _script_pubkey: &Script)

Registers interest in a transaction with txid and having an output with script_pubkey as a spending condition.

fn register_output(&self, output: WatchedOutput)

Registers interest in spends of a transaction output.