Skip to content
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

Channel splitting #13

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from
Draft

Channel splitting #13

wants to merge 9 commits into from

Conversation

luckysori
Copy link
Collaborator

No description provided.

@Tibo-lg Tibo-lg force-pushed the split-tx-experiment branch 3 times, most recently from e0dfa30 to 91a5eec Compare November 8, 2023 11:21
@Tibo-lg Tibo-lg force-pushed the split-tx-experiment branch from 91a5eec to 017121f Compare November 8, 2023 11:34
Tibo-lg and others added 5 commits November 9, 2023 08:40
The (de)serialisation for `ChannelTransactionParameters` changed
between 0.0.114 and 0.0.116. This type had already been modified by us
when adding the `original_funding_outpoint` field. When first
introduced, we chose a type value of 14.

After the update, we chose to reduce it down to 12 since the type 12
was no longer being used after changes between 0.0.114 and 0.0.116.
Unfortunately, this unnecessarily broke channels created before the
update.

Eventually we will need to settle on a way to handle these possible
conflicts with upstream. Tibo already suggested a few options:

- Use much larger numbers for `rust-dlc` custom fields.
- Move LDK values around as we rebase on top of new changes.
- Add a subdomain for `rust-dlc` custom fields.
@Tibo-lg Tibo-lg force-pushed the split-tx-experiment branch from 017121f to 3274833 Compare November 8, 2023 23:41
It would be even nicer to log the `ChannelDetails`, but then we would
have to modify the macro and that is too painful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants