Matt Corallo

Reliably deliver gossip messages from our `ChannelMessageHandler`

4

When our `ChannelMessageHandler` creates gossip broadcast `MessageSendEvent`s, we generally want these to be reliably delivered to all our peers, even if there's not much buffer space available. Here we do...

Allow self-payment

8

Shouldn't be too hard, really, just have to have a length-one route to ourselves with a dummy SCID (zero?) generated by the router. Then if we see it we immediately...

Don't Always Broadcast latest state on startup if we'd previously closed-without-broadcast

8

On startup the ChannelManager will broadcast the latest state transaction(s) for any ChannelMonitor it has for which it has no Channel. This is all fine and great except if we'd...

`handling_channel_announcements` is flaky on windows

1

Don't think I've seen this one yet: ``` ---- routing::gossip::tests::handling_channel_announcements stdout ---- thread 'routing::gossip::tests::handling_channel_announcements' panicked at lightning\src\routing\gossip.rs:2548:22: explicit panic stack backtrace: 0: std::panicking::begin_panic_handler at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library\std\src\panicking.rs:645 1: core::panicking::panic_fmt at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library\core\src\panicking.rs:72 2:...

We're almost here, and not doing so would allow us to avoid re-persisting `ChannelMonitor`s on startup. The only one left is the preimage replay, which is tricky to remove but...

Add an implementation of mutual message exchange

4

Based on #2828 This adds a new crate, `mutual-message-exchange` which allows two parties to maintain a list of keys with which they want to exchange messages and exchange one message...

We guarantee that `peer_disconnected` will always be called for a peer after `peer_connected`, but we don't if one message handler fails `peer_connected` (the others wont even get it). Also, `PeerManager::read_event`...

Gossip never seems to get a full take from Eclair/CLN

4

We've seen a handful of reports that seem to indicate we don't succeed fetching gossip from CLN/Eclair. If I had to guess its because they don't sort the gossip into...

https://github.com/lightning/bolts/pull/1092

Include BIP 353 name info in `invoice_request`s

7

Based on #798, BIP 353 defines a method for resolving Human Readable Names (in the form ₿`name`@`domain`) into bitcoin: URIs. In order to use them with BOLT 12 with a...