pub struct FullScanRequest<K> { /* private fields */ }Expand description
Data required to perform a spk-based blockchain client full scan.
A client full scan iterates through all the scripts for the given keychains, fetching relevant
data until some stop gap number of scripts is found that have no data. This operation is
generally only used when importing or restoring previously used keychains in which the list of
used scripts is not known. The full scan process also updates the chain from the given
chain_tip (if provided).
Implementations§
Source§impl<K> FullScanRequest<K>
impl<K> FullScanRequest<K>
Sourcepub fn builder_at(start_time: u64) -> FullScanRequestBuilder<K>
pub fn builder_at(start_time: u64) -> FullScanRequestBuilder<K>
Start building a FullScanRequest with a given start_time.
start_time specifies the start time of sync. Chain sources can use this value to set
TxUpdate::seen_ats for mempool transactions. A transaction
without any seen_ats is assumed to be unseen in the mempool.
Use FullScanRequest::builder to use the current timestamp as start_time (this
requires feature = "std).
Sourcepub fn builder() -> FullScanRequestBuilder<K>
pub fn builder() -> FullScanRequestBuilder<K>
Start building a FullScanRequest with the current timestamp as the start_time.
Use FullScanRequest::builder_at to manually set the start_time, or if feature = "std" is not available.
Sourcepub fn start_time(&self) -> u64
pub fn start_time(&self) -> u64
When the full-scan-request was initiated.
Sourcepub fn chain_tip(&self) -> Option<CheckPoint>
pub fn chain_tip(&self) -> Option<CheckPoint>
Get the chain tip CheckPoint of this request (if any).