pub struct LockedChannelMonitor<'a, ChannelSigner: Sign> { /* private fields */ }
Expand description

A read-only reference to a current ChannelMonitor.

Note that this holds a mutex in ChainMonitor and may block other events until it is released.

Methods from Deref<Target = ChannelMonitor<ChannelSigner>>

Updates a ChannelMonitor on the basis of some new information provided by the Channel itself.

panics if the given update is not the next update by update_id.

Gets the update_id from the latest ChannelMonitorUpdate which was applied to this ChannelMonitor.

Gets the funding transaction outpoint of the channel this ChannelMonitor is monitoring for.

Gets a list of txids, with their output scripts (in the order they appear in the transaction), which we must learn about spends of via block_connected().

Loads the funding txo and outputs to watch into the given chain::Filter by repeatedly calling chain::Filter::register_output and chain::Filter::register_tx until all outputs have been registered.

Get the list of HTLCs who’s status has been updated on chain. This should be called by ChannelManager via chain::Watch::release_pending_monitor_events.

Gets the list of pending events which were generated by previous actions, clearing the list in the process.

This is called by ChainMonitor::get_and_clear_pending_events() and is equivalent to EventsProvider::get_and_clear_pending_events() except that it requires &mut self as we do no internal locking in ChannelMonitors.

Used by ChannelManager deserialization to broadcast the latest holder state if its copy of the Channel was out-of-date. You may use it to get a broadcastable holder toxic tx in case of fallen-behind, i.e when receiving a channel_reestablish with a proof that our counterparty side knows a higher revocation secret than the holder commitment number we are aware of. Broadcasting these transactions are UNSAFE, as they allow counterparty side to punish you. Nevertheless you may want to broadcast them if counterparty don’t close channel with his higher commitment transaction after a substantial amount of time (a month or even a year) to get back funds. Best may be to contact out-of-band the other node operator to coordinate with him if option is available to you. In any-case, choice is up to the user.

Processes transactions in a newly connected block, which may result in any of the following:

  • update the monitor’s state against resolved HTLCs
  • punish the counterparty in the case of seeing a revoked commitment transaction
  • force close the channel and claim/timeout incoming/outgoing HTLCs if near expiration
  • detect settled outputs for later spending
  • schedule and bump any in-flight claims

Returns any new outputs to watch from txdata; after called, these are also included in get_outputs_to_watch.

Determines if the disconnected block contained any transactions of interest and updates appropriately.

Processes transactions confirmed in a block with the given header and height, returning new outputs to watch. See block_connected for details.

Used instead of block_connected by clients that are notified of transactions rather than blocks. See chain::Confirm for calling expectations.

Processes a transaction that was reorganized out of the chain.

Used instead of block_disconnected by clients that are notified of transactions rather than blocks. See chain::Confirm for calling expectations.

Updates the monitor with the current best chain tip, returning new outputs to watch. See block_connected for details.

Used instead of block_connected by clients that are notified of transactions rather than blocks. See chain::Confirm for calling expectations.

Returns the set of txids that should be monitored for re-organization out of the chain.

Gets the latest best block which was connected either via the chain::Listen or chain::Confirm interfaces.

Gets the balances in this channel which are either claimable by us if we were to force-close the channel now or which are claimable on-chain (possibly awaiting confirmation).

Any balances in the channel which are available on-chain (excluding on-chain fees) are included here until an Event::SpendableOutputs event has been generated for the balance, or until our counterparty has claimed the balance and accrued several confirmations on the claim transaction.

Note that the balances available when you or your counterparty have broadcasted revoked state(s) may not be fully captured here.

See Balance for additional details on the types of claimable balances which may be returned here and their meanings.

Trait Implementations

The resulting type after dereferencing.

Dereferences the value.

Auto Trait Implementations

Blanket Implementations

Gets the TypeId of self. Read more

Immutably borrows from an owned value. Read more

Mutably borrows from an owned value. Read more

Returns the argument unchanged.

Calls U::from(self).

That is, this conversion is whatever the implementation of From<T> for U chooses to do.

The type returned in the event of a conversion error.

Performs the conversion.

The type returned in the event of a conversion error.

Performs the conversion.