-
Notifications
You must be signed in to change notification settings - Fork 1
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 #11
Conversation
@Tibo-lg: I've finally created the draft PR I mentioned. I had to update the fork's |
That's awesome thanks! |
db8bc0d
to
9a9cecd
Compare
I've squashed the fixup and removed the merge commit in the process since we don't even want it. I'll open a PR to update |
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.
Looks like something's wrong with the build? |
I don't think so. We just get warnings because of all the things that are not linted properly in LDK, right? |
The build used to pass at least AFAIR |
Never mind, the build works but not after rebase so it's the same as before sorry. |
Superseded by #13 to use a differently named branch: |
No description provided.