Matt Corallo

Document that `accept_forwards_to_priv_channels` does not apply for intercepted payments that we manually forward

3

https://github.com/lightningdevkit/ldk-node/issues/499

The ability to build a `ReplyPath` to send messages outside of `ChannelManager`

3

Currently we lean on `ChannelManager` to build all the reply paths we need to receive replies to our onion messages. As a part of the ongoing `OffersFlow` work that should...

Add `BackgroundProcessor::start_without_om`

5

`BackgroundProcessor::start` takes an `Option` for the `OnionMessenger` which is quite annoying as it requires a concrete type for the `OnionMessenger` even when passing `None`. We should add a new constructor...

Add a simple test of upgrading from LDK 0.1 and correct `in_flight_monitor_updates` on upgrade

6

One major hole in our test coverage historically has been tests covering upgrades or downgrades across LDK versions. Luckily, these aren't particularly hard to write as cargo lets us depend...

Add Test for same-payment_hash-different-CLTV HTLC sorting

9

This was fixed in #319 but no test was added.

Can we merge `Channel::tx_complete` and `Channel::funding_tx_constructed`?

1

Looks like we can? I think we maybe didn't because at the time those were written we didn't have the `Channel`-can-switch-state-internally stuff done, but now that we do we can...

Its not really acceptable to have message decoders that don't have fuzzers hooked up. We need to do this.

Route Randomization

4

We should do (or have an option to do) something much more private than simply "cheapest path" wrt route selection. We may want to take inspiration from c-lightning's "select random...

Handle htlc_max != channel capacity better in scoring

2

There's two issues today with the way we handle channels with an htlc-max being different from the channel's capacity (which historically was never a thing but we expect to happen...

Handle nodes with multiple channels between them better in scoring

1

Currently we treat them each as distinct edges with different available liquidity, but this isn't how it works in practice - nodes will just forward over any channel they have....