-
Notifications
You must be signed in to change notification settings - Fork 906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lightningd: use CPFP on peer's commitment tx if we can't broadcast our own #6752
lightningd: use CPFP on peer's commitment tx if we can't broadcast our own #6752
Commits on Oct 26, 2023
-
pytest: test (fails!) that we push anchor on peer's commitment tx.
We try to use anchors to CPFP our own commitment, but what if they get there first? We also need to use anchors on the commitment txs they broadcast. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 6693d23 - Browse repository at this point
Copy the full SHA 6693d23View commit details -
channeld: get rid of unused commit_sig and htlc_sigs in channeld_send…
…ing_commitsig We don't actually use this at all. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 2544068 - Browse repository at this point
Copy the full SHA 2544068View commit details -
channeld: rename channel_splice_txs to channel_txs.
channel_txs was a thin wrapper around channel_splice_txs, but that's just confusing. Rename channel_splice_txs to channel_txs, and just call it everywhere. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 0229359 - Browse repository at this point
Copy the full SHA 0229359View commit details -
channeld: have commit_tx tell is what output was the other's anchor.
We're going to want this, soon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 061f680 - Browse repository at this point
Copy the full SHA 061f680View commit details -
channeld: tell lightningd about local anchor for each commitment tx.
It's going to want to remember these, in case it encounters peers' commitment tx and needs to boost it with CPFP on the anchor. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for e4fd6af - Browse repository at this point
Copy the full SHA e4fd6afView commit details -
lightningd: routines to deal with peer commitment anchor info in db.
Store enough to know how to CPFP the peer's commitment tx. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for 03560ca - Browse repository at this point
Copy the full SHA 03560caView commit details -
lightningd: save peer's commitment anchor info into db.
We actually only need to remember the last two, worst case. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for b9fab74 - Browse repository at this point
Copy the full SHA b9fab74View commit details -
channeld: use anchors on peer's commitment(s) if we can't broadcast o…
…ur own. This means refactoring out some of the generic anchor info, from the per-commitment-tx info (we can have at least two, perhaps more with splicing!). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Configuration menu - View commit details
-
Copy full SHA for d3d6e5b - Browse repository at this point
Copy the full SHA d3d6e5bView commit details