Matt Corallo d629a7edb7 Expand chain::Listen trivially to accept filtered block data ... The `chain::Listen` interface provides a block-connection-based alternative to the `chain::Confirm` interface, which supports providing transaction data at a time separate from the block connection time. For users who are downloading the full headers tree (e.g. from a node over the Bitcoin P2P protocol) but who are not downloading full blocks (e.g. because they're using BIP 157/158 filtering) there is no API that matches exactly their event stream - `chain::Listen` requries full blocks for each block, `chain::Confirm` requires breaking each connection event into two calls. Given its incredibly trivial to take a `TransactionData` in addition to a `Block` in `chain::Listen` we do so here, adding a default-implementation `block_connected` which simply creates the `TransactionData`, which ultimately all of the `chain::Listen` implementations currently do anyway. Closes #1128.		2022-04-26 19:14:19 +00:00
..
src	Expand chain::Listen trivially to accept filtered block data	2022-04-26 19:14:19 +00:00
Cargo.toml	Bump crate versions to 0.0.106/invoice 0.14	2022-04-03 08:05:08 -05:00