Elias Rohrer

Currently, `LiquidityManager::next_event`/`LiquidityManager::next_event_async` return the next event an repersist the event queue (post #4059), which puts the responsibility to safely handle any important events on the user. While some events are...

Currently, we allow to interface with the `LSPS2ServiceHandler` via events and API methods. We however do *not* allow to access its internal state to get a view into which channel-open...

Drop reference to `Self` in `GossipVerifier::new`

15

In `GossipVerifier::new` we currently force an argument of type signature of `gossiper: Arc`, which is not only terrible in it's own right, but also enforces the type signature of everything...

Just hit this randomly failing CI over at https://github.com/lightningdevkit/rust-lightning/pull/4083: ``` test tests::test_payment_path_scoring ... FAILED failures: ---- tests::test_payment_path_scoring stdout ---- node 0 TRACE [lightning_background_processor:1387] Calling ChannelManager's timer_tick_occurred on startup node 0...

The LSPS2 service handler has a lot going on. In particular, it might currently is hard to follow when we actually make a state change that needs to be persisted....

Implement `invalid-parameters-error` in LSPS1 / LSPS2

1

When we dropped versioning support a new error type was introduced: `invalid-parameters-error` (see https://github.com/BitcoinAndLightningLayerSpecs/lsp/tree/main/LSPS0#-32602-invalid-parameters-error). We currently don't return it, but should, at least if it's not too cumbersome. Other implementors...

Feature: Support Electrum protocol v1.6

7

**Is your feature request related to a problem? Please describe.** The Electrum protocol v1.6 was just merged. See [the docs](https://electrum-protocol.readthedocs.io/en/latest/protocol-changes.html#version-1-6) for changes in the new version: > **Changes** > -...

BOLT 1: Clarify optionality of message format `extension`

1

BOLT 1 currently states: ``` ## Lightning Message Format After decryption, all Lightning messages are of the form: 1. `type`: a 2-byte big-endian field indicating the type of message 2....

Previous research [1], [2] has shown that the Lightning Network is susceptible to passive network-layer attacks on privacy that can exploit metadata leaking from transmitted network messages. While other factors...

Allow to access response payload in `retry::Builder::{classify, classify_fn}`

2

I'm currently trying to replace our homebrewn retry logic with the `retry::Builder` shipped in `reqwest` v0.12.23. Two things stand out to me that currently make it hard for us to...