Wilmer Paulino
Wilmer Paulino
While working on the integration of `option_anchors_zero_fee_htlc_tx` for `rust-lightning`, I noticed that the test vectors were only for the original `option_anchors` commitment format, which is also the case for BOLT-3....
This PR ensures all new incoming HTLCs going forward will have their onion decoded when they become fully committed to decide how we should proceed with each one. As a...
The [spec](https://github.com/lightning/bolts/blob/master/02-peer-protocol.md#requirements-6) outlines a few scenarios where channels should be force closed after a co-op close attempt stops making progress after some time. LDK will currently only adhere to this...
Closes https://github.com/tigerbeetle/tigerbeetle/issues/1183.
#### 21ebfd588d61aaacfdf6c7971d27b860f9d18ecf Implement relaxed laneselect SIMD instructions https://bugs.webkit.org/show_bug.cgi?id=281581 Reviewed by NOBODY (OOPS!). The specification[1] notes that these instructions should behave as a bitwise select SIMD instruction when the mask has...
We previously provided non-dust HTLC sources to avoid storing duplicate non-dust HTLC data in the `htlc_outputs` `Vec` where all HTLCs would be tracked in a holder commitment update. With splicing,...
Without this, if a channel has already closed, we're unable to determine if the funding transaction has actually confirmed and we have balances to claim. An added bonus would be...
`HolderCommitmentPoint` currently tracks the current and next point used on counterparty commitments, which are unrevoked. When we reestablish a channel, the counterparty sends us the commitment height, along with the...
- [x] Add utility to simplify handling of `BumpTransactionEvent`s for users (#2089) - [x] Remove anchors config flag (#2367) - [x] Require manual inbound acceptance (#2368) - [x] Restrict inbound...