Matt Corallo
Matt Corallo
I can answer that because I originally invited people. The list was "people who actively contributed to the spec (or were invited by a major lightning implementation cause they regularly...
> I would prefer to not add it in codecov until we have a good public corpora of fuzz inputs to run the report on. One reason to do this...
Do you intend to go ahead and run this in CI? Or would you prefer not to?
Also update the anchor reserves re: https://github.com/lightningdevkit/rust-lightning/pull/3487#discussion_r1951591121 once that PR lands
In theory we can just do the end-user bits first, but when we ship that there won't be any LSPs for the users, so we really need to implement the...
Sorry for the delay here. So given we're gonna do #3738, is the point of this change to have less diff across the two update types? In #3738 it was...
fwiw `clippy` is unhappy.
`ln::async_signer_tests::test_async_force_close_on_invalid_secret_for_stale_state` is failing in CI.
That one is a bit old and was generated with a prior LDK which may or may not be up to date with the spec. This one should be, though,...