Elias Rohrer

Btw, feel free to ping me whenever you think this is ready for a secondary reviewer!

I still think it wouldn't be great if we just gave up and accepted an even more fragmented protocol space as it will be even worse UX (note that many...

> [@tnull](https://github.com/tnull), your comment seems to imply that your preference would be in supporting mempool.space rather than Esplora and ask Esplora to migrate to mempool instead? No, my preference is...

Also want to note that it seems a minor release was previously planned for this: https://github.com/rust-lang/hashbrown/pull/570#issuecomment-2406017398

> In the above mentioned notebook I have - in contradiction to what I have explained in the initial post - extended the algorithm to allocate sats on a path...

We now adopted `rustfmt` for the whole workspace. While we still have a bunch of `rustfmt::skip`s in the codebase that we want to remove over time, this *generally* can be...

> Agree it doesn't need to be in the rust-lightning repo per se even though I filed the issue here. Probably a new repo in the LDK GitHub org with...

While I opened a separate issue for bumping the MSRV on a patch release over at #585 (which breaks our builds with ~no options left as dependencies had already upgraded...

Seem this is a duplicate of https://github.com/lightningdevkit/rust-lightning/issues/1537 ? But since this one is more specific, maybe close the older issue?

Right, we can keep the re-export, although longer term I'd prefer a single one via `lightning::types`. Just stumbled across the inconsistency while upgrading `lightning-liquidity`, so might be good to move...