You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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, it is cleared afterwards.
In splicing, the funding transaction is needed later (for tx_add_input message).
Two possible approaches:
Safe (less invasive), but ugly (redundant): duplicate funding_transaction field, set it at the same time, but don't clear it. This approach is used in [Early Draft] Splicing prototype #3274 (proto).
Clean but risky: change the behavior that funding_transaction holds the transaction during the whole lifetime of the channel. The risk is that there might be code logic that relies on the field being cleared (which has to be found and adapted).
The text was updated successfully, but these errors were encountered:
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, it is cleared afterwards.In splicing, the funding transaction is needed later (for
tx_add_input
message).Two possible approaches:
funding_transaction
field, set it at the same time, but don't clear it. This approach is used in [Early Draft] Splicing prototype #3274 (proto).funding_transaction
holds the transaction during the whole lifetime of the channel. The risk is that there might be code logic that relies on the field being cleared (which has to be found and adapted).The text was updated successfully, but these errors were encountered: