Struct breez_sdk_core::lightning::util::test_utils::TestPersister

pub struct TestPersister {
    pub update_rets: Mutex<VecDeque<ChannelMonitorUpdateStatus>>,
    pub chain_sync_monitor_persistences: Mutex<HashMap<OutPoint, HashSet<MonitorUpdateId>>>,
    pub offchain_monitor_updates: Mutex<HashMap<OutPoint, HashSet<MonitorUpdateId>>>,
}

Fields

update_rets: Mutex<VecDeque<ChannelMonitorUpdateStatus>>

The queue of update statuses we’ll return. If none are queued, ::Completed will always be returned.

chain_sync_monitor_persistences: Mutex<HashMap<OutPoint, HashSet<MonitorUpdateId>>>

When we get an update_persisted_channel call with no ChannelMonitorUpdate, we insert the MonitorUpdateId here.

offchain_monitor_updates: Mutex<HashMap<OutPoint, HashSet<MonitorUpdateId>>>

When we get an update_persisted_channel call with a ChannelMonitorUpdate, we insert the MonitorUpdateId here.

Implementations

impl TestPersister

pub fn new() -> TestPersister

pub fn set_update_ret(&self, next_ret: ChannelMonitorUpdateStatus)

Queue an update status to return.

Trait Implementations

impl<Signer> Persist<Signer> for TestPersister

where Signer: WriteableEcdsaChannelSigner,

fn persist_new_channel( &self, _funding_txo: OutPoint, _data: &ChannelMonitor<Signer>, _id: MonitorUpdateId, ) -> ChannelMonitorUpdateStatus

Persist a new channel’s data in response to a chain::Watch::watch_channel call. This is called by ChannelManager for new channels, or may be called directly, e.g. on startup.

fn update_persisted_channel( &self, funding_txo: OutPoint, _update: Option<&ChannelMonitorUpdate>, _data: &ChannelMonitor<Signer>, update_id: MonitorUpdateId, ) -> ChannelMonitorUpdateStatus

Update one channel’s data. The provided ChannelMonitor has already applied the given update.