Serialize HTLCs only once #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pm47
previously approved these changes
Mar 23, 2023
HTLCs are duplicated in local and remote commit(s), and across commitments when splices are ongoing. We now serialize them only once, which reduces the size of the encrypted backup that needs to be stored.
t-bast
force-pushed
the
serialize-htlcs-only-once
branch
from
818cb6c
to
0534d3d
Compare
|
Rebased. |
pm47
approved these changes
Mar 23, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HTLCs are duplicated in local and remote commit(s), and across commitments when splices are ongoing. We now serialize them only once, which reduces the size of the encrypted backup that needs to be stored.