optout

Upgrade bech32 dependency

1

https://github.com/lightningdevkit/rust-lightning/issues/3100#issuecomment-2152108517 LDK currently uses `bech32` `0.9.1` (Aug'22 https://github.com/rust-bitcoin/rust-bech32/releases/tag/v0.9.1). Latest version is `0.11.0`, and `0.10` was a major rewrite. Currently used `bitcoin 0.31.2` uses `bech32 0.10.0-beta`. Latest `bitcoin 0.32.2` uses `bech32...

[Splicing] Preserve `funding_transaction` for the later lifecycle of the channel

1

Fixes #3300 In splicing, the funding transaction (not just the ID) is needed during splice negotiation. Funding transaction is kept in field `ChannelContext.funding_transaction`. However, the way it is currently used...

Splicing prototype, draft; PR for visibility (not intended for merging as for now). Current __baseline__: `v0.0.123`, plus a not-latest version of dual-funding PR #2302 . For start, run the __splicing...

[Splicing] Clone for ChannelContext

3

Update: This assumes that the whole `ChannelContext` is duplicated, which may not be the case in the final solution. Cloning of a channel -- more precisely of `ChannelContext` -- is...

Support multiple funding transaction (candidates) per channel (Splicing, Dual Funding)

2

Currently one channel has one funding transaction, this is expected to change with [Dual funding and Splicing](https://github.com/lightningdevkit/rust-lightning/issues/1621) use cases. This issue is created to collect some of the concerns. ##...

Splicing needs support for shared signatures during interactive transaction negotiations -- when there is an input that has to be signed by both peers (the previous multisig funding tx becomes...

[Splicing] Signer extended with method to sign prev funding transaction input

1

Fixes #3312 . (#1621 ) New method to sign an input of a transaction with our funding key. Used for splicing, when signing the previous funding transaction. The previous funding...

Base32 followups, Features serialization

2

Some followups to Base32/Bech32 changes #3270 `Bolt11InvoiceFeatures` are serialized to 5-bit values internally, but in a way that is not compatible with Bech32. The grouping of bits is done in...

This is in preparation for Splicing (#1621 ) In splicing the channel has to sign the previous funding as an input to the new funding transactions. For this, the `EcdsaChannelSigner`...

This is is a relatively minor change preparation for splicing ( #1621 ). The funding transaction is available in the `ChannelContext::funding_transaction` field. However, it is available only during channel negtiation,...